![]() | |||||||||||||
Messages in this thread |
>> ben soo wrote: [...] >>> This last might be an artifact caused by the firewall, i dunno. [...] > Bill Davidsen <davidsen@tmr.com> wrote: >> Yes, I have found that I get far less problem in this area leaving the >> MTU at 1500, then putting a larger MTU (usually 9000) into the routing >> table for segments, or even just machines, where I know there is direct >> connectivity. [...] Stephen Hemminger wrote: > If you want to use Jumbo frames, you need to have routers and firewalls > that correctly handle ICMP and do path MTU discovery. If you have bridges > or firewalls that aren't Jumbo aware on both interfaces, then there will > be long timeouts retries for each connection. If you have busted routers > and firewalls that swallow ICMP then PMTU won't work well either. i turned off the motherboard Marvell Gbit devices and installed a Realtek 8169 card, all the while keeping to kernel version 2.6.23-rc6, and saw all the network problems go away. Must mean it was a sky2 driver bug. Am currently running 2.6.23-rc7 on the affected server and the rc7 sky2 driver is holding up fine so far. thank you! b - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-09-20 08:45 [from the cache] ©2003-2008 | |||||||||||||