Hi -
Is there anyone that has done policy routing with iproute2 on this list?
If so, I am having problems with the traceroute command, such that packets
originated from from a host that has many interfaces and different
policies for each. Other commands such as ping, apache, and others seem to
work fine.
Specifics. Consider 4 interfaces 192.168.1.{1,2,3,4}/24 represented by
eth0, eth0:{1,2,3} respectively. The rules I have are:
0: from all lookup local
32761: from 192.168.1.1 lookup path1
32762: from 192.168.1.2 lookup path2
32763: from 192.168.1.3 lookup path3
32764: from 192.168.1.4 lookup path4
32766: from all lookup main
32767: from all lookup default
The table specific routes are defined by:
path1: default via 192.168.1.251 dev eth0
path2: default via 192.168.1.252 dev eth0
path3: default via 192.168.1.253 dev eth0
path4: default via 192.168.1.254 dev eth0
If I sniff the wire and run "ping -I eth0:3 hostname" the policy route
appears to be used. Likewise, if I point my browser at http://192.168.1.4/
again the policy seems fine. Unfortunately, when I run the command
"traceroute -s 192.168.1.4 hostname" the policy is NOT used. Changing to
"traceroute -I -s 192.168.1.4 hostname" has no effect either.
Does anyone have suggestions about how I might rectify this? Answers like
"change to freebsd and use ipfw" sadly aren't acceptable, though yes, I
have proven that it does in fact work fine.
Thanks in advance - Marc
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
