|
YES!
Ian, i love you!
haha, yeah, this was exactly the problem. the gateway is a router that i
don't have direct access to, and the real servers couldn't arp request it
since they're not on a network it's attached to. if i add the arp entries
manually, everything works properly.
many thanks for the info and suggestion.
-tcl.
On Tue, 18 Jul 2000, Ian S. McLeod wrote:
> I believe this is the key problem. You don't seem to be getting any
> response from the ARP of the GW address.
>
> 1) Can you verify that the ARP requests for 64.208.49.1 are actually
> reaching the gateway machine? (BTW-Is this a router or another Linux
> box?)
>
> 2) The gateway may be ignoring these arp requests because it doesn't know
> how get the reply back to 192.168.100.98. You may have to hard code the
> MAC address of the gateway using the arp command. Try:
>
> # arp -s 64.208.49.1 <mac>
>
> Where <mac> is the gateway MAC address in colon separated hex.
>
> -Ian
>
> > real server:
> > 12:17:52.999514 eth1 B arp who-has 64.208.49.1 tell 192.168.100.98
> > 12:17:52.999521 eth2 B arp who-has 64.208.49.1 tell 192.168.100.98
> > 12:17:53.550585 eth1 > 192.168.100.99 > 64.208.49.132: icmp: host
> > 208.219.36.67 unreachable [tos 0xc0]
> > 12:17:53.550598 eth1 > 192.168.100.99 > 64.208.49.132: icmp: host
> > 208.219.36.67 unreachable [tos 0xc0]
> >
> >
> > other real server:
> > 12:17:55.251106 eth1 B arp who-has 64.208.49.1 tell 192.168.100.99
> > 12:17:55.251114 eth2 B arp who-has 64.208.49.1 tell 192.168.100.99
> > 12:17:56.124482 eth1 < 208.219.36.67.62374 > 64.208.49.132.www: S
> > 98091686:98091686(0) win 32120 <mss 1460,sackOK,timestamp 161199526
> > 0,nop,wscale 0> (DF)
> > 12:17:56.199872 eth1 > 192.168.100.98 > 64.208.49.132: icmp: host
> > 208.219.36.67 unreachable [tos 0xc0]
>
>
>
>
>
>
|
