From owner-freebsd-questions Sun Nov 26 10:58:25 2000 Delivered-To: freebsd-questions@freebsd.org Received: from freeze.org (www.bellnetworks.net [208.177.187.234]) by hub.freebsd.org (Postfix) with ESMTP id 4466937B479 for ; Sun, 26 Nov 2000 10:58:22 -0800 (PST) Received: (from jim@localhost) by freeze.org (8.9.3/8.9.3) id NAA34298; Sun, 26 Nov 2000 13:58:20 -0500 (EST) (envelope-from jim) X-Authentication-Warning: www.bellnetworks.net: Processed from queue /var/spool/alt_queue X-Authentication-Warning: www.bellnetworks.net: Processed by jim with -C /web/siteinfo/freeze/mail/sendmail.cf Date: Sun, 26 Nov 2000 13:58:20 -0500 (EST) From: Jim Freeze X-Sender: jim@www.bellnetworks.net To: cjclark@alum.mit.edu Cc: questions@FreeBSD.ORG Subject: Re: Need help with natd and connecting Windows to LAN In-Reply-To: <20001126105512.A34151@149.211.6.64.reflexcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Crist: My gateway inside nic is a LinkSys network card. The pc nic is a Netgear FA311 card. What other info do you need? Jim On Sun, 26 Nov 2000, Crist J . Clark wrote: > 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 mtu 1500 > > > > inet 24.9.218.175 netmask 0xffffff00 broadcast 24.9.218.255 > > > > ether 00:60:97:4f:aa:a0 > > > > al0: flags=8843 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 > =========================== Jim Freeze jim@freeze.org --------------------------- Am I a webmaster? No. More like a webslave. =========================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message