Strange networking problems after update 5.2.1->5.3

GerritKühn gerrit at pmp.uni-hannover.de
Tue Jan 4 01:17:11 PST 2005


On Tue, 4 Jan 2005 06:30:26 +1100 Peter Jeremy
<PeterJeremy at optushome.com.au> wrote about Re: Strange networking problems
after update 5.2.1->5.3:


PJ> >ed0: flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
PJ> >	inet 130.75.117.37 netmask 0xffff0000 broadcast 130.75.255.255
PJ> >	ether 01:d4:ff:03:00:20

PJ> That's a multicast MAC address (the LSB of the first byte is 1).  More

Ok, I didn't know about this. Can you recommend any online resource where
those special things are documented?

PJ> intelligent NICs will have an internal list of multicast MAC addresses
PJ> that they have been programmed to respond to and will ignore all other
PJ> multicast addresses (for dumber NICs, this checking should be in the
PJ> driver).  This would explain the peculiar behaviour you are seeing.

For sure.

PJ> Firstly, I presume you're not attempting to change the MAC address.

Correct, I even don't know how to do this. ;-)

PJ> Secondly, the MAC address should be reported as part of the ed0 probe
PJ> message - can you have a look back through your messages file and
PJ> report the ed0 probe messages for both 5.2.1 and 5.3.

Ok, 5.2.1 reported the following

Dec 28 10:15:05 lonestar kernel: ed1: <Dual Speed 10/100 Port Attached PC
Card> at port 0x100-0x11f
irq 11 function 0 config 16 on pccard1
Dec 28 10:15:05 lonestar kernel: ed1: address 00:e0:98:a2:a7:33, type
Linksys (16 bit)
Dec 28 10:15:05 lonestar kernel: miibus0: <MII bus> on ed1


With 5.3 it says

Dec 29 15:48:15 lonestar kernel: ed1: <Dual Speed 10/100 Port Attached PC
Card> at port 0x100-0x11f
irq 11 function 0 config 16 on pccard1
Dec 29 15:48:15 lonestar kernel: ed1: [GIANT-LOCKED]
Dec 29 15:48:15 lonestar kernel: ed1: Ethernet address: 01:d4:ff:03:00:20
Dec 29 15:48:15 lonestar kernel: ed1: if_start running deferred for Giant
Dec 29 15:48:15 lonestar kernel: type NE2000 (16 bit)


I admit that I've got no clue where this new MAC is coming from. :)


cu
  Gerrit


More information about the freebsd-stable mailing list