| To: | Sven-Haegar Koch <haegar@xxxxxxxxx> |
|---|---|
| Subject: | Re: Problem with e100.c and packets >mtu in 2.6.4 |
| From: | Glen Turner <glen.turner@xxxxxxxxxxxxx> |
| Date: | Mon, 15 Mar 2004 11:59:26 +1030 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.58.0403150035530.27707@xxxxxxxxxxxxxxxxx> |
| Organization: | Australian Academic and Research Network |
| References: | <Pine.LNX.4.58.0403150035530.27707@xxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
> What is the reason behind this check? Could it be removed from the > official sources again? Alternatively, I'd like to suggest that too-big frames be discarded by all drivers. The configuration described (an inconsistent MTU in a subnet) is wrong and having it fail-and-count rather than subtly "work" (eg, frames up to some hardware-dependent magic number are received but can't be sent, but frames beyond that don't) is a significant help to network operators. Those operators then just need to know the RFCs, not the inner details of the popular NICs and their drivers. -- Glen Turner Tel: (08) 8303 3936 or +61 8 8303 3936 Network Engineer Email: glen.turner@xxxxxxxxxxxxx Australian Academic & Research Network www.aarnet.edu.au |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Problem with e100.c and packets >mtu in 2.6.4, Sven-Haegar Koch |
|---|---|
| Next by Date: | Re: [patch/RFC] networking menus, Nivedita Singhvi |
| Previous by Thread: | Problem with e100.c and packets >mtu in 2.6.4, Sven-Haegar Koch |
| Next by Thread: | Re: [patch/RFC] networking menus, Nivedita Singhvi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |