Date: Tue, 16 Sep 1997 13:19:28 -0400 From: Gary Schrock <root@eyelab.psy.msu.edu> To: Greg Lehey <grog@lemis.com> Cc: freebsd-questions@freebsd.org Subject: Re: arplookup messages Message-ID: <3.0.3.32.19970916131928.007545ac@eyelab.msu.edu> In-Reply-To: <19970915095351.00157@lemis.com> References: <3.0.3.32.19970914115337.007e7440@eyelab.msu.edu> <3.0.3.32.19970913192927.007e4210@eyelab.msu.edu> <Pine.BSF.3.96.970913204208.918A-100000@localhost> <3.0.3.32.19970914115337.007e7440@eyelab.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:53 AM 9/15/97 +0930, you wrote: >Well, the message is correct. Your local network has the address >range 208.25.49.0 to 208.25.49.255. Since it's arp that's >complaining, it would appear that you have non-local hosts on the >network. >Now you might come and say "but Microsoft does it". Yes, that's >right. Microsoft is broken. This Must Not Work. Doesn't really suprise me. Unfortunately, we don't always have control over how a network is put together. I've got another machine that I get the same type of messages where I *know* that there are non-local hosts on it, so I kinda suspected from the start that that's what was causing this. >In other words, both 208.25.49.5 and 205.138.224.173 are behind >144.228.147.22, which is probably another interface for >gatekeeper.inreach.com (208.25.49.1), which is on your local net. Yeah, it does look like 144.228.147.22 an 208.25.49.1 are the same machines: anguish:/etc$ traceroute 144.228.147.22 traceroute to 144.228.147.22 (144.228.147.22), 30 hops max, 40 byte packets 1 gatekeeper.inreach.com (205.138.224.1) 0.944 ms * 1.078 ms >I'd guess that 144.228.147.22 is doing proxy arp, and it's incorrectly >configured. Can you ping the host? Can you traceroute? If this is >the only other machine on the net, as the netstat -nr output suggests, >then just disable proxy arp. Yup, I can ping and traceroute it. I have to admit that I'm not real familiar with arp, and honestly don't know how to disable proxy arp, any suggestions for where to look? And, I'm also curious what one should do if you are on a net that does have other machines on it (the machine in my lab that gets similar message is on a net that they're running 3 different ip ranges on): # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 35.8.64.1 UGSc 94 855 ed1 35.8.64/24 link#1 UC 0 0 35.8.64.1 0:0:c:1:85:b4 UHLW 93 0 ed1 1199 35.8.64.37 0:c0:4f:d4:96:59 UHLW 0 0 ed1 1110 35.8.64.81 0:aa:0:30:ed:10 UHLW 0 0 ed1 1146 35.8.64.143 0:60:8:34:5:8a UHLW 1 71570 ed1 892 35.8.64.179 2:60:8c:38:76:77 UHLW 2 227098 lo0 35.8.64.180 0:c0:4f:d7:18:b3 UHLW 4 285096 ed1 1121 35.8.64.255 ff:ff:ff:ff:ff:ff UHLWb 2 34943 ed1 127.0.0.1 127.0.0.1 UH 0 9786 lo0 (I've sliced a few out to keep the list length down). This particular net also has 35.8.110.* and 35.8.194.* running on it, so needless to say I get arplookup messages here too. Thanks, Gary Schrock root@eyelab.msu.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19970916131928.007545ac>