Hello Jeff, Wednesday, October 1, 2014, 12:14:53 PM, you wrote:
J> It sounds like "ping -I" is what I was looking for, but when I use it, it seems J> to be sending out the packet with the right source address, but sending it to J> the wrong interface.....are there any tricks here? J> Here's some data (edited) to show what I'm seeing: J> fxp0: inet 10.16.100.1 netmask 0xfffffff0 broadcast 10.16.100.15 J> fxp1: inet 192.168.243.152 netmask 0xffffff00 broadcast 192.168.243.255 J> when I try "ping -I 192.168.243.152 ucla.edu", I see the following: J> tcpdump -i fxp0 icmp and host ucla.edu J> tcpdump: listening on fxp0, link-type EN10MB J> 13:06:36.478450 192.168.243.152 > 128.97.27.37: icmp: echo request J> 13:06:37.483393 192.168.243.152 > 128.97.27.37: icmp: echo request J> 13:06:38.493244 192.168.243.152 > 128.97.27.37: icmp: echo request J> The routing table shows: J> 10.16.100.0/28 link#1 UC 4 0 - 4 fxp0 J> 192.168.243/24 link#2 UC 1 0 - 4 fpx1 The output of "route -n get ucla.edu" would be helpful. It seems like you need more knowledge about routing, otherwise there is a very big chance you "shoot yourself in the foot" messing around this. Been there, probably still is. -- Best regards, Boris mailto:bo...@twopoint.com
