On 2007/06/13 16:38, Jeff Santos wrote:
RTM_LOSING happens when TCP segments are lost, look for packet loss
somewhere. The usual suspects are bad cables, bad connectors, mismatched
duplex etc. I had it with bge(4) nics onboard Supermicro H8SSL boards,
associated with errors showing up in netstat -ni - in that case moving
to PCI-X em(4) sidestepped the issue.
People who aren't running routed would see these messages, if they
happened, by looking at 'route monitor'.
> I noticed that, even with a static default route, every now and then I
If enough packets are lost to prevent ARP from getting through, you
might see that.
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Bart Van Assche | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
