Subject: Re: tcp/IP errors on MOL
From: Charlie McLachlan (cim@uk.research.att.com)
Date: Thu Jun 08 2000 - 02:43:32 MDT
On Wed, 7 Jun 2000, Stefan Jeglinski wrote:
This might be related to my IP filter.
Take a look at your kernel messages (usually in ./var/log/messages)
Do you have any "New Filter : xxxxxxxx" lines?
My IP filter will output one of these when it changes the IP address it is
filtering on. The xxxxxxx number should be the hexadecimal representation
of the filter address. If it is not a sensible number then this might be
the cause of the ethernet deafness.
> via-cuda: Unimplemented packet type 160 received
> <*> Can't allocate packet datas (621)
> <*> Can't allocate packet datas (561)
> <*> Can't allocate packet datas (621)
> <*> Turning off allocation warnings.WARNING: Ethernet packet dropped
> WARNING: Ethernet packet dropped
> WARNING: Ethernet packet dropped
> (warning repeated several more times before ending)
The "Can't allocate packet datas" are currently a fact of MOL life. I see
them regulalrly when attepting large downloads. They indicate the
networking is getting a bit stressed. Similarly "WARNING: Ethernet packet
dropped". They should not be fatal.
> I had never seen the "Unimplemented packet type 160 received"
> message. Also, the only way I have been able to get ethernet going
> again is by rebooting.
Have you tried rmmod sheep_net; insmod sheep_net instead of rebooting?
> Simply unloading and reloading the TCP/IP stack does not do it.
Which might mean that its not my filter. Unloading/ reloading TCP/IP
*should* cause my filter to reset itself to the correct address.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Charlie McLachlan
AT&T Research Lab. Cambridge.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This archive was generated by hypermail 2a24 : Thu Jun 08 2000 - 02:42:05 MDT