> tcpdump -netttvvvSXi interfacename
>
> should show you something like
Here it is:
Feb 05 11:59:06.601418 0:b:6:bc:7b:e ff:ff:ff:ff:ff:ff 0806 60: arp
who-has 192.168.0.10 tell 24.145.134.116
0000: 0001 0800 0604 0001 000b 06bc 7b0e 1891 ...........<{...
0010: 8674 0000 0000 0000 c0a8 000a 1102 27b6 .t......@(....'6
0020: c0a8 6401 008a 00bb 0000 2046 4445 @(d....;.. FDE
Feb 05 11:59:06.601500 0:20:78:1f:0:af 0:b:6:bc:7b:e 0806 60: arp reply
192.168.0.10 is-at 0:20:78:1f:0:af
0000: 0001 0800 0604 0002 0020 781f 00af c0a8 ......... x../@(
0010: 000a 000b 06bc 7b0e 1891 8674 1102 27b6 .....<{....t..'6
0020: c0a8 6401 008a 00bb 0000 2046 4445 @(d....;.. FDE
> What is currently in your hostname.* files?
hostname.dc0 (external) is just "dhcp".
hostname.fxp0 (internal) is:
inet 192.168.1.11 255.255.255.0 192.168.1.255
> is it possible that any of your internal hosts have an address
> on the wrong (meaning 192.168.0) subnet?
All the internal hosts are 192.168.1.*
What does 'arp -a' and 'netstat -nr -f inet' output on rock?
