Re: kernel 2.6 routing anomaly

Dan Miller wrote:
I'm porting our old satellite-networking package from kernel 2.2 to kernel 2.6. Most everything is coming along okay. Today, for the first time, I have two gateways connected via the "satellite" link (using a satellite-
delay simulator), and I can ping across the link. If I ping the remote gateway at its satellite interface, I see a normal ping response:

hub26:/usr/src/sat # ping 192.168.13.2
PING 192.168.13.2 (192.168.13.2) 56(84) bytes of data.
64 bytes from 192.168.13.2: icmp_seq=1 ttl=64 time=541 ms
64 bytes from 192.168.13.2: icmp_seq=2 ttl=64 time=541 ms
64 bytes from 192.168.13.2: icmp_seq=3 ttl=64 time=541 ms

However, if I ping the ethernet interface of the remote gateway, I see something odd:

hub26:/usr/src/sat # ping 192.168.14.1
PING 192.168.14.1 (192.168.14.1) 56(84) bytes of data.
From 192.168.13.2: icmp_seq=1 Redirect Host(New nexthop: 192.168.13.1)
From 192.168.13.2: icmp_seq=2 Redirect Host(New nexthop: 192.168.13.1)
From 192.168.13.2: icmp_seq=3 Redirect Host(New nexthop: 192.168.13.1)
From 192.168.13.2: icmp_seq=4 Redirect Host(New nexthop: 192.168.13.1)


However, I *have* a route to the 14.0 network, via the 13.2 address which is the remote satellite gateway. I don't understand what this "redirect host: new nexthop: 192.13.1" entry is telling me; the 13.1 address is my own eth1 interface; that shouldn't require redirecting anything??

Can anyone tell me what I'm doing wrong here?? I'm enclosing my routing table and interface info at the end of this message for reference.

The remote gateway (192.168.13.2) has a route to the target
(192.168.14.x) via your own host (192.168.13.1), and it's
trying to tell you that according to his route table, you're
the proper way to the target. It seems that you've set up a
bounce automaton.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi
.

Relevant Pages

  • kernel 2.6 routing anomaly
    ... I'm porting our old satellite-networking package from kernel 2.2 to kernel ... have two gateways connected via the "satellite" link (using a satellite- ... and I can ping across the link. ... However, if I ping the ethernet interface of the remote gateway, I see ...
    (comp.os.linux.networking)
  • Re: Ip address problem
    ... And that 10003 was the interface and the metric was one but i still do not ... "Chuck" wrote: ... >>The gateway is my ip address but what i dont understand is what is the 10003? ... >>notice is that all 3 of the computers that could not get on internet or ping ...
    (microsoft.public.windowsxp.network_web)
  • Re: Routing problem
    ... >(that will ping using the external interface) ... The modem has a very simple html display ... FreeBSD 4.9 "gateway". ...
    (freebsd-questions)
  • Re: kernel 2.6 routing anomaly
    ... I have two gateways connected via the "satellite" link ... which is the remote satellite gateway. ... address is my own eth1 interface; ... The remote gateway has a route to the target ...
    (comp.os.linux.networking)
  • Help with a routing issue
    ... The default gateway is 192.168.254.1 which is the inside interface of the ... When i ping 196.25.37.18 from the clients box i get this. ... My routes on the clients box look as follows: ...
    (freebsd-questions)