From owner-freebsd-questions Sat Dec 2 14:36:30 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 5BE0237B400 for ; Sat, 2 Dec 2000 14:36:26 -0800 (PST) Received: (from jim@localhost) by freeze.org (8.9.3/8.9.3) id RAA61771; Sat, 2 Dec 2000 17:35:41 -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: Sat, 2 Dec 2000 17:35:41 -0500 (EST) From: Jim Freeze X-Sender: jim@www.bellnetworks.net To: Cliff Sarginson Cc: questions@freebsd.org Subject: Re: Is NIC with MAC = ff:ff:ff:ff:ff:ff OK? In-Reply-To: <00120223213100.02062@buffy> 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 Thanks, but each machine is a dedicated machine. I did pull the NIC from FBSD and put it in W98 to check to MAC. It does have a valid MAC. I then put it back in the FBSD box and did the following on W98 arp -s 192.168.0.1 ff-ff-ff-ff-ff-ff (They are separated by '-' on the pc. duh) Then tried to ping the FBSD box. No luck. Also tried arp -s 192.168.0.1 mac-address-read-from-pc and tried the ping. Still no luck. I think, unless someone else has a suggestion, that I am at the end of my rope and have run out of spare cord. Does anyone else have a simple gateway/LAN setup. And if so, what is the MAC on the inside NIC? Also, my current path is a dead end, then I only see hope by getting a new NIC. Can anyone suggest a inexpensive NIC? I don't won't to spend $100 for a 3COM. Thanks Jim On Sat, 2 Dec 2000, Cliff Sarginson wrote: > On Saturday 02 December 2000 22:08, Jim Freeze wrote: > > Windows does not seem to like a MAC of all ff's. > > Can someone help out here? > > > > On Sat, 2 Dec 2000, Jim Freeze wrote: > > > > > % dmesg | grep al0 > > > > > al0: rev 0x11 int a irq 5 on pci0.11.0 > > > > > al0: Ethernet address: ff:ff:ff:ff:ff:ff > > > > > al0: autoneg complete, link status good (full-duplex, 100Mbps) > > > > > al0: promiscuous mode enabled > > > > > > > > Having never seen this before, are both NICs on your LAN set for > > > > > > and > > > > > > > running at full-duplex? Does "dmesg" make a difference if you stop your > > > > "tcpdump", as I think that's why the NIC is showing in promiscous mode. > > > > > > I'm not sure what you mean. > > > The second NIC has always had ff:ff... as its MAC. > > > > > > Is there anyway to change that? > > > > > > > That's where my knowledge ends as I've never heard of a NIC showing a > > > > > > MAC > > > > > > >>address of all ff's. Any one else know what's going on? > > > > Jim > > > I HAVE seen this before. > On a dual boot PC (Linux/Windows98). > It has two NICS. > Scenario: > Boot windows 98 ... > "Soft" reboot from 98 to Linux (point is PC is NOT powered off) > Both NICS Have "FFF..." as MAC. > NIC drivers complain like billio about too many interrupts etc .. > > A hard reboot (i.e. with poweroff) and problem is no problem. > Tested in all combinations of scenarios. > Conclusion: Windows 98 is leaving NICs in this state, that a soft reboot > does not fix. > {Presumable Windows 98 on exit does not clean up after itself .. god knows.. > > Hope this helps > > Cliff > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > ==================================================== Jim Freeze jim@freeze.org --------------------------------------------------- ** http://www.freeze.org ** ==================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message