Before we keep asking for more and more info, perhaps we should look a bit
at what we do know and interpret the actual report. As Michael correctly
pointed out yesterday, the important log line is the one that preceded the
"NET" line, and we're finally seeing it.
It reads:
> > May 22 02:53:54 NRP-413 kernel: Redirect from D08A145C/eth0 to D08A1401
> > ignored.Path = D08A1469 -> 42DA4753, tos 00
Unpacked, this says that the kernel is reporting that it received and
refused an instruction to redirect from 208.138.20.92 (0xD08A145, which is
the external gateway address in the routing table) to 208.138.20.01
(0xD08A1401, another host on the external network). It is connected with a
packet going from the router's external address 208.138.20.105 (0xD08A1469)
to the non-local address 66.218.71.83 (0x42DA4753).
While I have not actually seen a message like this one before, it reads
like a report of a message received fom the external gateway telling the
system to use a different external gateway address ... probably sent via
some standard routing protocol. (Perhaps someone here who knows routing
protocols better than I can recognize it; I have a hazy memory of an "icmp
redirect" packet type that may be involved.)
Given that 208.138.20.01 is a more typical address for an ISP gateway than
208.138.20.92, I would guess that this is nothing more than an ISP that is
too lazy to supply its customers with correct, up-to-date routing
information, instead using a quick technofix to update its routing.
If my guess is correct, -AND- if my assumption is correct that there is no
actual service failure associated with these messages, then there are two
courses of action:
1. Ignore them. For the on-screeen part, figure out what their
priority is (probably a klogd issue, not a syslogd one, since they come
from the kernel) and revise the klogd setting not to display them. My man
page for klogd says its default behavior is to display only panic messages
to the console, so you need to check how Eigerstein 2 changes that.
2. Try changing the routing table so the router uses 208.138.20.01
as its default gateway, and see if everything works.
If my reading is right, there really would be a godawful flood of these
things, since the gateway is probably asking this router to redirect every
packet that goes to the external gateway.
At 11:13 AM 5/22/02 -0500, Omar D. Samuels wrote:
> > On Wed, 2002-05-22 at 08:42, Omar D. Samuels wrote:
> > > I'm sorry, I just realised that my msgs weren't going thru because I had
> > > these msgs as attachments, which I imagine needs to be moderator
>approved.
> >
> > Omar,
> > I'm the list admin. Attachments are rejected due to the amount of
> > viruses circulating. You should have received instructions to include
> > all diagnostic information in-line.
>
>Okay, I got it not long ago.
> >
> > > Hope this is what you were talking about:
> > >
> > > May 22 02:53:54 NRP-413 kernel: NET: 4 messages suppressed.
> > > May 22 02:53:54 NRP-413 kernel: Redirect from D08A145C/eth0 to D08A1401
> > > ignored.Path = D08A1469 -> 42DA4753, tos 00
> > > May 22 02:53:59 NRP-413 kernel: NET: 4 messages suppressed.
> > > May 22 02:53:59 NRP-413 kernel: Redirect from D08A145C/eth0 to D08A1401
> > > ignored.Path = D08A1469 -> 42DA4753, tos 00
> >
> > This is better. :-)
> > Would you also please post the output of:
> >
> > ip addr show
>ip addr show
>1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
>2: brg0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> link/ether fe:fd:0a:21:8b:5f brd ff:ff:ff:ff:ff:ff
>3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:00:21:da:ed:06 brd ff:ff:ff:ff:ff:ff
> inet 208.138.20.105/24 brd 208.138.20.255 scope global eth0
>4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 52:54:4c:18:ca:11 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
>
> > ip route show
>ip route show
>192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254
>208.138.20.0/24 dev eth0 proto kernel scope link src 208.138.20.105
>default via 208.138.20.92 dev eth0
> >
> > The contents of network.conf would be of use too.
> >
>You want me to e-mail the entire contents of network.conf... or merely
>specific parts?
--
-----------------------------------------------"Never tell me the
odds!"--------------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------------------
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
