|
Julian,
> Then I assume eth0/forward_shared is 1.
No, actually its not. Enabling it now and seeing what happens
> Yes, no ARP flux expected, until you use 65.88.136.62 to
>talk to other hosts on the LAN through both eth0 and eth1. You have to
>tell us whether this is a persistent problem or happens in rare cases.
It seems to happen to all users who are trying to hit our site with Road
Runner, and with a few rare others on LANs (State of Ohio Government
Organizations)
>Also you better to monitor the ARP tables with arp -an. You can also show
>us all IP addresses and routes in director or everything is shown in the
>first posting?
ARP Tables:
? (65.88.136.33) at 00:50:73:22:0B:5B [ether] on eth0
? (65.88.136.55) at 00:50:04:71:E0:61 [ether] on eth0
? (65.88.136.58) at 00:50:8B:EE:27:36 [ether] on eth0
? (65.88.136.59) at 00:50:8B:F1:D4:AD [ether] on eth0
? (65.88.136.56) at 00:04:76:CA:01:BA [ether] on eth0
? (65.88.136.57) at 00:A0:CC:5A:64:E2 [ether] on eth0
Routes:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
gatekeeper-Insi * 255.255.255.255 UH 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
65.88.136.0 * 255.255.255.0 U 0 0 0 eth0
default router 0.0.0.0 UG 0 0 0 eth0
gatekeeper-Insi = VIP = 65.88.136.60
All the IP address in the director from the first posting are all that are
on the director.
|
