Subject: Re: tcp/IP errors on MOL
From: Charlie McLachlan (cim@uk.research.att.com)
Date: Thu Jun 08 2000 - 10:05:31 MDT
On Thu, 8 Jun 2000, Stefan Jeglinski wrote:
All the filter addresses are the same. Which probably means the problem
isn't in the IP filter.
> >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.
Indeed it does. The fact that resetting MOL solves the problem might mean
the problem is in MOL rather than sheep_net.
> 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.
The filter filters on the source address of the last packet sent.
It starts of with the special value of 0 (let everything through)
Hence a "New Filter :" log line just after bootup is totally normal.
Sending a packet out with a different source address will set the filter
to this new address.
During normal operation "New Filter:" log lines should only appear
with addresses different to the preceding one.
If the filter is sending out multiple "New Filter:" lines with the same
address then something weird is going on.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Charlie McLachlan
AT&T Research Lab. Cambridge.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This archive was generated by hypermail 2a24 : Thu Jun 08 2000 - 10:04:01 MDT