On Thu, May 6, 2010 at 10:12 PM, Miles Fidelman <mfidel...@meetinghouse.net> wrote: > Thanks to all who replied. I'm starting to zero in on this now. > > A few more details: > [snip]
> > on server 1: > eth0: inet addr:207.154.13.48 Bcast:207.154.13.63 Mask:255.255.255.224 > (first netblock) > server1:/home/milesf# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > localnet * 255.255.255.224 U 0 0 0 eth0 > default 207.154.13.33 0.0.0.0 UG 0 0 0 eth0 > server1:/home/milesf# arp -a > ? (207.154.13.33) at 00:d0:03:b3:18:00 [ether] on eth0 > > on server 2: > eth0: net addr:207.154.59.130 Bcast:207.154.59.159 Mask:255.255.255.224 > (2nd netblock) > server2:/home/milesf# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > localnet * 255.255.255.224 U 0 0 0 eth0 > default 207.154.59.129 0.0.0.0 UG 0 0 0 eth0 > server2:/home/milesf# arp -a > ? (207.154.59.129) at 00:d0:03:b3:18:00 [ether] on eth0 > > from box 1 -> box 2 > traceroute to 207.154.59.130 (207.154.59.130), 30 hops max, 40 byte packets > 1 207.154.13.33 (207.154.13.33) 0.418 ms 0.429 ms 0.481 ms > 2 server2.neighborhoods.net (207.154.59.130) 0.299 ms 0.317 ms 0.309 ms > > from box 2 -> box 1 > server2:/home/milesf# traceroute 207.154.13.48 > traceroute to 207.154.13.48 (207.154.13.48), 30 hops max, 40 byte packets > 1 207.154.13.33 (207.154.13.33) 0.352 ms 0.369 ms 0.436 ms > 2 server1.neighborhoods.net (207.154.13.48) 0.292 ms 0.295 ms 0.302 ms > > The traffic is definitely going through the datacenter's router > (207.154.13.33). > > I'm thinking that adding something like: > > server 1: route add -net 207.154.13.128 netmask 255.255.255.244 dev eth0 > server 2: route add -net 207.154.13.32 netmask 255.255.255.244 dev eth0 why not just limit it to the ip address you want currently only 2 server 1: ip route add 207.154.59.130 dev eth0 src 207.154.13.48 server 2: ip route add 207.154.13.48 dev eth0 src 207.154.59.130 just put in routing statements for the ip's that you need > > > One of the machines is a production machine, so I want to be fairly sure of > this before starting to play with the routing table. > > Any more comments? > > And... anybody know if the "route" command persists across reboots, and if > so, where it store the information? iproute is the new route place them in /etc/network/interfaces as post-up command don't forget || true at the end of the command > > Thanks again, answered agan > > Miles > > -- > In theory, there is no difference between theory and practice. > In<fnord> practice, there is. .... Yogi Berra > > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject > of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/4be2b248.7080...@meetinghouse.net > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/u2w836a6dcf1005062058qd3b61a7dx5fb98b79a7423...@mail.gmail.com