Thanks to all who replied. I'm starting to zero in on this now.
A few more details:
To follow up with a few more details:
server1 ------ hub (switch) ------- server 2
|
|
datacenter's router
The hub is a basic $40 gigE switch (not switch/router) from datacenter.
The netblock assignments are:
-------
Your rack space had been set up and your IP block is 207.154.13.32/27:
gateway: 207.154.13.33
netmask: 255.255.255.224
broadcast: 207.154.13.63
useful: 207.154.13.34-62
2nd block - allocated 3/22/07
207.154.59.128/27
Netmask - 255.255.255.224
Gateway - 207.154.59.129
First Usable - 207.154.59.130
Last Usable - 207.154.59.158
----
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
would keep the traffic from reaching the big router, but this is where
I'm just a little shaky on how everything works.
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?
Thanks again,
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
