Date: Sun, 26 Nov 2000 10:55:12 -0800 From: "Crist J . Clark" <cjclark@reflexnet.net> To: Jim Freeze <jim@freeze.org> Cc: questions@FreeBSD.ORG Subject: Re: Need help with natd and connecting Windows to LAN Message-ID: <20001126105512.A34151@149.211.6.64.reflexcom.com> In-Reply-To: <Pine.BSF.4.21.0011261307440.33771-100000@www.bellnetworks.net>; from jim@freeze.org on Sun, Nov 26, 2000 at 01:16:47PM -0500 References: <20001125235823.F12190@149.211.6.64.reflexcom.com> <Pine.BSF.4.21.0011261307440.33771-100000@www.bellnetworks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 26, 2000 at 01:16:47PM -0500, Jim Freeze wrote:
>
> > If you do a 'tcpdump -eni al0' while you try both the ping from the
> > gateway to the Win98 box and the other way, what do you see?
>
> Here is what I get when pinging from W98(192.168.1.2) to
> FreeBSD(192.168.1.1) - W98 ping reports "Request timed out" as before:
>
> root@eeyore1 ('tty') /usr/home/jfreeze 1 -> tcpdump -eni al0
> tcpdump: listening on al0
> 13:15:16.269835 19:2:16:8:1:2 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
> 192.168.1.1 tell 192.168.1.2
> 13:15:16.269892 ff:ff:ff:ff:ff:ff 19:2:16:8:1:2 0806 60: arp reply
> 192.168.1.1 is-at ff:ff:ff:ff:ff:ff
> 13:15:20.553363 19:2:16:8:1:2 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
> 192.168.1.1 tell 192.168.1.2
> 13:15:20.553390 ff:ff:ff:ff:ff:ff 19:2:16:8:1:2 0806 60: arp reply
> 192.168.1.1 is-at ff:ff:ff:ff:ff:ff
> 13:15:25.052420 19:2:16:8:1:2 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
> 192.168.1.1 tell 192.168.1.2
> 13:15:25.052442 ff:ff:ff:ff:ff:ff 19:2:16:8:1:2 0806 60: arp reply
> 192.168.1.1 is-at ff:ff:ff:ff:ff:ff
> 13:15:29.551832 19:2:16:8:1:2 ff:ff:ff:ff:ff:ff 0806 60: arp who-has
> 192.168.1.1 tell 192.168.1.2
> 13:15:29.551857 ff:ff:ff:ff:ff:ff 19:2:16:8:1:2 0806 60: arp reply
> 192.168.1.1 is-at ff:ff:ff:ff:ff:ff
There is something pretty funky going on here. The first thing, and I
think it is the cause of the problem, is what I pointed out in the
previous mail. It looks like your al0 NIC seems to believe that its
MAC address is ff:ff:ff:ff:ff:ff, the broadcast address. And it looks
like the Win98 machine is not buying that. Now, the Win98
machine... what kind of card does it have? I can't seem to find a
manufacturer who has the 19:02:16 prefix. Something weird is going on.
All of this is a problem at the data layer and has nothing to do with
your IP settings, NAT, etc.
> On Sat, 25 Nov 2000, Crist J . Clark wrote:
>
> > On Sun, Nov 26, 2000 at 01:06:51AM -0500, Jim Freeze wrote:
[snip]
> > The configs look OK. But...
> >
> > > root@eeyore1 ('tty') ~ 17 -> ifconfig -a
> > > vx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > inet 24.9.218.175 netmask 0xffffff00 broadcast 24.9.218.255
> > > ether 00:60:97:4f:aa:a0
> > > al0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > > inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
> > > ether ff:ff:ff:ff:ff:ff
> > ^^^^^^^^^^^^^^^^^
> > This does not look at all right.
--
Crist J. Clark cjclark@alum.mit.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001126105512.A34151>