Re: adjusting the mtu with vr(4)
Sevan / Venture37 wrote: On Sunday 25 November 2007 00:00:45 Sevan / Venture37 wrote: Is the support for adjusting the mtu with VIA Rhine-II chipset based interfaces missing because of hardware limitations or because support for it hasn't been written yet?? # ifconfig vr0 mtu 1492 ifconfig: SIOCSIFMTU: Inappropriate ioctl for device Sevan / Venture37 Appears to me that via hands out specs on a nda case-by-case basis. Not sure why soekris decided to use those chips in the net-5501. Actually they use via rhine-III but they behave the same. If you're routing to dsl you can workaround in pf.conf by putting a line like scrub out on $ext_if max-mss 1452 in the normalization section. Regards, Dorian Hi Dorian I'm aware of that option from reading the pppoe(4) man page, but I'm not too keen on the side effects, hence why I was asking on the list about the interface as I wouldn't mind testing a snapshot which did support it. The system I'm going to be using is a jetway mini-itx board with a vr interface built onboard 3 re interfaces on a daughterboard, it'd be a shame to waste a gigabit interface for the pppoe connection. Use the suggested pf setting. It is the right way do handle it and there will be no ill side effects. Sevan / Venture37 _ 100s of Music vouchers to be won with MSN Music https://www.musicmashup.co.uk
Re: adjusting the mtu with vr(4)
Use the suggested pf setting. It is the right way do handle it and there will be no ill side effects. Ok, so where does this statement from the pppoe(4) man page come in to play? Note that setting the MSS this way can have undesirable effects, such as reducing TCP/IP throughput, and interfering with the OS detection features of pf(4). Should I go back to reading the man pages because I've missed something?? Sevan / Venture37 _ 100s of Music vouchers to be won with MSN Music https://www.musicmashup.co.uk
Re: adjusting the mtu with vr(4)
On 2007/11/27 09:44, Sevan / Venture37 wrote: Use the suggested pf setting. It is the right way do handle it and there will be no ill side effects. Ok, so where does this statement from the pppoe(4) man page come in to play? Note that setting the MSS this way can have undesirable effects, such as reducing TCP/IP throughput, and interfering with the OS detection features of pf(4). That's usually better than the alternative (i.e. going to all the machines behind the NAT and changing their MTU).
Re: adjusting the mtu with vr(4)
On Tue, Nov 27, 2007 at 04:22:23AM +, Sevan / Venture37 wrote: On Sunday 25 November 2007 00:00:45 Sevan / Venture37 wrote: Is the support for adjusting the mtu with VIA Rhine-II chipset based interfaces missing because of hardware limitations or because support for it hasn't been written yet?? # ifconfig vr0 mtu 1492 ifconfig: SIOCSIFMTU: Inappropriate ioctl for device Sevan / Venture37 Appears to me that via hands out specs on a nda case-by-case basis. Not sure why soekris decided to use those chips in the net-5501. Actually they use via rhine-III but they behave the same. If you're routing to dsl you can workaround in pf.conf by putting a line like scrub out on $ext_if max-mss 1452 in the normalization section. Regards, Dorian Hi Dorian I'm aware of that option from reading the pppoe(4) man page, but I'm not too keen on the side effects, hence why I was asking on the list about the interface as I wouldn't mind testing a snapshot which did support it. The system I'm going to be using is a jetway mini-itx board with a vr interface built onboard 3 re interfaces on a daughterboard, it'd be a shame to waste a gigabit interface for the pppoe connection. If you run pppoe over the vr(4) interface so why do you need to reduce the MTU of the interface. Do you like to break your network before it is working? -- :wq Claudio
Re: adjusting the mtu with vr(4)
If you run pppoe over the vr(4) interface so why do you need to reduce the MTU of the interface. Do you like to break your network before it is working? Read the MTU/MSS issues of pppoe(4) _ Celeb spotting Play CelebMashup and win cool prizes https://www.celebmashup.com
Re: adjusting the mtu with vr(4)
On 2007/11/27 11:32, Sevan / Venture37 wrote: If you run pppoe over the vr(4) interface so why do you need to reduce the MTU of the interface. Do you like to break your network before it is working? Read the MTU/MSS issues of pppoe(4) You need to read it again, paying more careful attention to *which* interface has the changed MTU. Hint: not the one with pppoe(4) running over it. But, this is the wrong way to do things anyway, please just use scrub max-mss.
Re: adjusting the mtu with vr(4)
Date: Tue, 27 Nov 2007 13:00:38 + From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: misc@openbsd.org Subject: Re: adjusting the mtu with vr(4) On 2007/11/27 11:32, Sevan / Venture37 wrote: If you run pppoe over the vr(4) interface so why do you need to reduce the MTU of the interface. Do you like to break your network before it is working? Read the MTU/MSS issues of pppoe(4) You need to read it again, paying more careful attention to *which* interface has the changed MTU. Hint: not the one with pppoe(4) running over it. But, this is the wrong way to do things anyway, please just use scrub max-mss. http://marc.info/?l=openbsd-cvsm=119616724432197w=2 :) _ Get free emoticon packs and customisation from Windows Live. http://www.pimpmylive.co.uk
Re: adjusting the mtu with vr(4)
On Sunday 25 November 2007 00:00:45 Sevan / Venture37 wrote: Is the support for adjusting the mtu with VIA Rhine-II chipset based interfaces missing because of hardware limitations or because support for it hasn't been written yet?? # ifconfig vr0 mtu 1492 ifconfig: SIOCSIFMTU: Inappropriate ioctl for device Sevan / Venture37 Appears to me that via hands out specs on a nda case-by-case basis. Not sure why soekris decided to use those chips in the net-5501. Actually they use via rhine-III but they behave the same. If you're routing to dsl you can workaround in pf.conf by putting a line like scrub out on $ext_if max-mss 1452 in the normalization section. Regards, Dorian Hi Dorian I'm aware of that option from reading the pppoe(4) man page, but I'm not too keen on the side effects, hence why I was asking on the list about the interface as I wouldn't mind testing a snapshot which did support it. The system I'm going to be using is a jetway mini-itx board with a vr interface built onboard 3 re interfaces on a daughterboard, it'd be a shame to waste a gigabit interface for the pppoe connection. Sevan / Venture37 _ 100s of Music vouchers to be won with MSN Music https://www.musicmashup.co.uk
Re: adjusting the mtu with vr(4)
On Sunday 25 November 2007 00:00:45 Sevan / Venture37 wrote: Is the support for adjusting the mtu with VIA Rhine-II chipset based interfaces missing because of hardware limitations or because support for it hasn't been written yet?? # ifconfig vr0 mtu 1492 ifconfig: SIOCSIFMTU: Inappropriate ioctl for device Sevan / Venture37 _ The next generation of MSN Hotmail has arrived - Windows Live Hotmail http://www.newhotmail.co.uk Appears to me that via hands out specs on a nda case-by-case basis. Not sure why soekris decided to use those chips in the net-5501. Actually they use via rhine-III but they behave the same. If you're routing to dsl you can workaround in pf.conf by putting a line like scrub out on $ext_if max-mss 1452 in the normalization section. Regards, Dorian
