Re: change_mtu boundary checking error
> But Ethernet is not only for IP, what about other protocols ? For 2.4 the checks were moved into the protocol layers. Any remaining check in the driver layer for 68 would be a bug. For 2.2 its not going to change - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: change_mtu boundary checking error
But Ethernet is not only for IP, what about other protocols ? -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 17, 2001 3:41 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: change_mtu boundary checking error > Now, the high boundary seemed reasonable (ETH_FRAME_LEN - ETH_HLEN = > ETH_DATA_LEN) which gives 1500, but why is the low boundary set to 68 ? > According to my calculations, it should have been ETH_ZLEN - ETH_HLEN which > gives 46. The IPv4 minimum MTU is 68 bytes. Below that not all frames can be delivered - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: change_mtu boundary checking error
> Now, the high boundary seemed reasonable (ETH_FRAME_LEN - ETH_HLEN = > ETH_DATA_LEN) which gives 1500, but why is the low boundary set to 68 ? > According to my calculations, it should have been ETH_ZLEN - ETH_HLEN which > gives 46. The IPv4 minimum MTU is 68 bytes. Below that not all frames can be delivered - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
