[9fans] reminder about the tcp-mss patch, a must for venti users

[9fans] reminder about the tcp-mss patch, a must for venti users

[hahahahacker2009]

In case anyone is using Richard Miller's raspberry pi image (not the
9legacy one)
or the images from 9p.io, if you use venti, you MUST APPLY this patch:
https://9legacy.org/9legacy/patch/9-tcp-mss.diff
patch for 9k kernels: https://9legacy.org/9legacy/patch/9k-jmk-tcp-mss.diff

I can't imagine I have lived with the "acceptable speed" of ~150kb/s
for 4 months...
and now it's about 5800kb/s.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-Md9db063ea309f62cc1281275
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] reminder about the tcp-mss patch, a must for venti users

[ron minnich]

[-- Attachment #1: Type: text/plain, Size: 839 bytes --]

There's some sort of problem with 9legacy.org, looks like. Those links come
up with warnings.

On Sat, Nov 1, 2025 at 8:01 AM hahahahacker2009 <hahahahacker2009@gmail.com>
wrote:

> In case anyone is using Richard Miller's raspberry pi image (not the
> 9legacy one)
> or the images from 9p.io, if you use venti, you MUST APPLY this patch:
> https://9legacy.org/9legacy/patch/9-tcp-mss.diff
> patch for 9k kernels:
> https://9legacy.org/9legacy/patch/9k-jmk-tcp-mss.diff
> 
> I can't imagine I have lived with the "acceptable speed" of ~150kb/s
> for 4 months...
> and now it's about 5800kb/s.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-M92fde3f5b79f9a64846c7c2f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2454 bytes --]

Re: [9fans] reminder about the tcp-mss patch, a must for venti users

[ori]

Quoth hahahahacker2009 <hahahahacker2009@gmail.com>:
> In case anyone is using Richard Miller's raspberry pi image (not the
> 9legacy one)
> or the images from 9p.io, if you use venti, you MUST APPLY this patch:
> https://9legacy.org/9legacy/patch/9-tcp-mss.diff
> patch for 9k kernels: https://9legacy.org/9legacy/patch/9k-jmk-tcp-mss.diff
> 
> I can't imagine I have lived with the "acceptable speed" of ~150kb/s
> for 4 months...
> and now it's about 5800kb/s.

It may also be worth looking at the recent 9front fixes to tcp:

https://git.9front.org/plan9front/9front/0bfae3882383682b214ac45c41199c53b54d8c63/commit.html


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-Me3b4af6283727fd910b8533b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] reminder about the tcp-mss patch, a must for venti users

[David du Colombier]

> There's some sort of problem with 9legacy.org, looks like. Those links 
> come up with warnings.

http://9legacy.org/ doesn't handle HTTPS. The same web server is serving
other websites (https://9grid.fr/ and so on), and because of the lack of SNI
support, the web server is not able to serve X509 certificates for each domain.

-- 
David du Colombier

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-M718254b89302203004387da1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] reminder about the tcp-mss patch, a must for venti users

[David du Colombier]

For the record, here is the original story about the 9-tcp-mss.diff patch:

https://9fans.topicbox.com/groups/9fans/T5eda8934b4c0557f-M271bf0f976a3efe0fae8ff95/9fans-fossilventi-performance-question

-- 
David du Colombier

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-M505cfa84a9a681ac7f7727ab
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] reminder about the tcp-mss patch, a must for venti users

[ori]

Quoth David du Colombier <0intro@gmail.com>:
> > There's some sort of problem with 9legacy.org, looks like. Those links 
> > come up with warnings.
> 
> http://9legacy.org/ doesn't handle HTTPS. The same web server is serving
> other websites (https://9grid.fr/ and so on), and because of the lack of SNI
> support, the web server is not able to serve X509 certificates for each domain.
> 

At risk of derailing the thread: it should be possible to
get a certificate that is valid for multiple names without
trouble. For example:

        https://shithub.us
        https://only9fans.com
        https://hjgit.org

all point at the same server, and serve the same certificate.

As far as I recall, it's as simple as ensuring that (assuming
you use ACME for the certificates) you can serve the all the
challenges on all domans, and having a comma spearated list of
CNs when you create the CSR:

        auth/rsa2csr 'CN=shithub.us,only9fans.com,hjgit.org' $key | ...

and then when you run

        auth/acmed $account $dir/$site.csr > $cert

it'll give you a cert that will validate all domains at once.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4828dfdfa860fd3e-M74068d759295ff80886ddad6
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription