Subject: Re: tcp/IP errors on MOL
From: Stefan Jeglinski (jeglin@4pi.com)
Date: Thu Jun 08 2000 - 09:29:00 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?
Yes, they appeared after one of my MOL upgrades (clearly the one with
your filtering stuff:-)
I do note that I always get similar to this in the logs:
Jun 4 19:57:21 linux kernel: MOL module inited
Jun 4 19:57:23 linux kernel: cdrom: open failed.
Jun 4 19:57:25 linux modprobe: can't locate module block-major-3
Jun 4 19:57:26 linux modprobe: can't locate module block-major-3
The cd-rom I think fails either because it is not an Apple CD-ROM
(CD-ROM Toolkit 3.02 crashes MOL by the way) or maybe I don't have
the cdrom entry in molrc set up correctly. Either way, this is not an
issue at this time. However, I don't know what "can't locate module
block-major-3" refers to or whether it is relevant to MOL.
>
>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.
Some examples:
New filter : ce069c0b
Filter packet: 00 0030 81a7 4000 ff 06 2605 ce069c0b ce069c02
Ether packet: (14) 0000c5506274,00059a20023a,0800
New filter : ce069c0b
Filter packet: 00 0039 aa3c 4000 ff 06 fd63 ce069c0b ce069c05
Ether packet: (14) 0030653dc6b6,00059a20023a,0800
New filter : ce069c0b
Filter packet: 00 0030 bbd7 4000 ff 06 ebd4 ce069c0b ce069c02
Ether packet: (14) 0000c5506274,00059a20023a,0800
New filter : ce069c0b
Filter packet: 00 0030 d994 4000 ff 06 ce17 ce069c0b ce069c02
Ether packet: (14) 0000c5506274,00059a20023a,0800
New filter : ce069c0b
Filter packet: 00 0030 16e8 4000 ff 06 90c4 ce069c0b ce069c02
Ether packet: (14) 0000c5506274,00059a20023a,0800
New filter : ce069c0b
Filter packet: 00 0030 b51f 4000 ff 06 f28c ce069c0b ce069c02
Ether packet: (14) 0000c5506274,00059a20023a,0800
They only seem to appear at MOL startup, but there were a couple of
exceptions (see end of this e-mail). I have to admit that I do not
know what the "IP filtering" is even doing and don't know how to
interpret any of the above. Where should I look for a discussion of
this - list archives? (I saw nothing in the dox or FAQ about it, only
the News mention that it had been added).
> > 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?
No. I will. BTW, I was unclear above. By "rebooting" I was meant MOL,
not Linux, in case it matters.
> > 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.
I will try this. A couple of the Filter log entries confused me as
they didn't appear to be attached to a MOL reboot. I'll bet this is
why.
Thanks for writing.
Stefan Jeglinski
This archive was generated by hypermail 2a24 : Thu Jun 08 2000 - 09:27:45 MDT