* [LARTC] Can't one filter based on a single destination address?
@ 2000-12-11 19:58 Andrew
0 siblings, 0 replies; only message in thread
From: Andrew @ 2000-12-11 19:58 UTC (permalink / raw)
To: lartc
<PRE>Greetings:
I'm running kernel 2.2.17 and I've been trying to add a rule which looks up
table main based on a single destination address. Here it is:
><i>ip rule add from 0.0.0.0/0 to 192.168.107.28 lookup main prio 110
</I>
The rule adds fine however it seems that the kernel fails to match the
destination condition.
Incidentally 192.168.107.28 is the local address of an interface on
the box where I'm adding the rule. The machine I'm testing from is
on the same physical network and has address 192.168.107.27. I'm using
ping to test.
With the above rule in place, and a blackhole rule immediately following
it. I can't ping 192.168.107.28 from .27. However if I change the rule
above to read:
><i>ip rule add from 0.0.0.0/0 to 192.168.107.0/24 lookup main prio 110
</I>
then I can ping fine. Thinking that I might be required to specify a mask,
I even tried the following version:
><i>ip rule add from 0.0.0.0/0 to 192.168.107.28/32 lookup main prio 110
</I>
No luck. Does any one know what's going on?
-Andrew
--
<A HREF="mailto:depaan@bibleinfo.com">depaan@bibleinfo.com</A>
--------------------------------------------------------------
Want answers to life's big questions? Visit www.bibleinfo.com.
</PRE>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-12-11 19:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-12-11 19:58 [LARTC] Can't one filter based on a single destination address? Andrew
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.