* pinging and routing tables
@ 2009-12-01 1:53 sinkyh
2009-12-03 8:48 ` Mart Frauenlob
0 siblings, 1 reply; 2+ messages in thread
From: sinkyh @ 2009-12-01 1:53 UTC (permalink / raw)
To: netfilter
Hello all,
I have, I hope, a simple question. From my understanding, by default
ping looks up up the IP address in the Linux kernel routing tables.
What happens if the IP is not in the routing table? Is the ping packet
simply dropped?
The reason I ask this is that I have a few wireless devices for
testing purposes and I am using iptables to mimic a particular
topology. Mainly forcing the presence of only two possible routes from
a source to a destination over a series of hops. These devices have
their own routing protocol and basically routes are added/ deleted
from the Linux kernel routing tables based on metric measurements bla
bla bla. That is just fine and normal.
However, since the devices are all in range of each other (due to
space restriction), if lets say the destination node IP is temporarily
lost from the source's routing table, for some reason the source is
still able to ping the destination directly. I assumed that if an IP
is not in the source's routing table that the outgoing ping would be
dropped/ ignored until the IP reappears. Not continue on ignoring
routing tables....
Can anyone shed some light on this?
Thanks for your help and suggestions.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: pinging and routing tables
2009-12-01 1:53 pinging and routing tables sinkyh
@ 2009-12-03 8:48 ` Mart Frauenlob
0 siblings, 0 replies; 2+ messages in thread
From: Mart Frauenlob @ 2009-12-03 8:48 UTC (permalink / raw)
To: netfilter
sinkyh@onid.orst.edu wrote:
> Hello all,
>
> I have, I hope, a simple question. From my understanding, by default
> ping looks up up the IP address in the Linux kernel routing tables. What
> happens if the IP is not in the routing table? Is the ping packet simply
> dropped?
>
> The reason I ask this is that I have a few wireless devices for testing
> purposes and I am using iptables to mimic a particular topology. Mainly
> forcing the presence of only two possible routes from a source to a
> destination over a series of hops. These devices have their own routing
> protocol and basically routes are added/ deleted from the Linux kernel
> routing tables based on metric measurements bla bla bla. That is just
> fine and normal.
>
> However, since the devices are all in range of each other (due to space
> restriction), if lets say the destination node IP is temporarily lost
> from the source's routing table, for some reason the source is still
> able to ping the destination directly. I assumed that if an IP is not in
> the source's routing table that the outgoing ping would be dropped/
> ignored until the IP reappears. Not continue on ignoring routing tables....
>
> Can anyone shed some light on this?
>
> Thanks for your help and suggestions.
Hello,
without being a network/routing guru, imho if there's not route to host
X, you should see a message like 'no route to host'...
Did you flush the cache?
`ip route flush cache` - should clear it, so old records are removed.
btw: bit offtopic here.... (not netfilter, tc, related)
Hope it helps.
regards
Mart
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-12-03 8:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-01 1:53 pinging and routing tables sinkyh
2009-12-03 8:48 ` Mart Frauenlob
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.