Re: IP fragmentation (DF) and ip_no_pmtu_disc in 2.2 vs 2.4

2000-12-01 Thread H. Peter Anvin
Followup to: <[EMAIL PROTECTED]> By author:Paul Jakma <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > On Fri, 1 Dec 2000, Alan Cox wrote: > > > > Intel PXE uses tftp to download boot images and discards IP packets with > > > the DF bit set; so a tftpd server on 2.4 with the default >

Re: IP fragmentation (DF) and ip_no_pmtu_disc in 2.2 vs 2.4

2000-12-01 Thread Paul Jakma
On Fri, 1 Dec 2000, Alan Cox wrote: > > Intel PXE uses tftp to download boot images and discards IP packets with > > the DF bit set; so a tftpd server on 2.4 with the default > > Then Intel PXE is buggy and you should go spank whoever provided > it as well as doing the workarounds. Supporting rec

Re: IP fragmentation (DF) and ip_no_pmtu_disc in 2.2 vs 2.4

2000-12-01 Thread Alan Cox
> With 2.4.0-test11, when ip_no_pmtu_disc is still 0/false we're seeing > outbound udp packets with the IP DF bit set. Is this change in default > behavior a fix or a break? Its a change in behaviour > So, it appears that 2.4 fixed a problem with 2.2, correct? > [stop non expert thinking] 2

IP fragmentation (DF) and ip_no_pmtu_disc in 2.2 vs 2.4

2000-12-01 Thread JP Navarro
In 2.2.17 when /proc/sys/net/ipv4/ip_no_pmtu_disc is 0/false we're seeing outbound udp packets with the IP DF (don't fragment) bit clear. With 2.4.0-test11, when ip_no_pmtu_disc is still 0/false we're seeing outbound udp packets with the IP DF bit set. Is this change in default behavior a fix