I don't usually file anything as a blocker, but this is big. dhcpcd has been reporting the wrong mac addresses to both my school and my home network. My school employs the use of a mac filter to force students to register their adapter on the network. There are two gentoo users I know that use the network, myself and a friend (he goes by the nickname Vanquisher on Freenode). During the Spring 2007 semester we were able to connect to the network. Fall 2007 however we would recieve an ip, but the router would block all traffic to us.. we assumed they found a way to block linux users as all windows users were able to access fine (including myself with a dual-boot). We found dhclient worked to access the network. I found the cause because of house issues. I have a server, a desktop, and a laptop all running gentoo and all kept up to date with 3.1.7 (though this problem existed with stable 3.1.5). My local ip's are 192.168.0.104, 192.168.0.100, and varying, respectively. I used to use static dhcp on the router, but the router still continued to assign the wrong ip's to the server and desktop. Looking at what mac addresses the router saw... was interesting. Currently the server's mac is shown as: 00-30-f1-02-bf-2f (looks normal) Well, the laptop's mac is shown as: 00000004000100010EA7FE6F0080C8B2 (what is that supposed to be?!?!) Laptop shows 00:80:C8:B2:43:B9 in ifconfig. The server and desktop show this crap after the lease expires and dhcpcd goes to renew. The router sees this vomit and goes "aww hell no, that's not his ip, that's 00-30-f1-02-bf-2f's ip" and I end having to hunt for the box.. this is bad for a nfs server especially since the systems using it need to then be rebooted. I can't believe this, I'm seeing these problems across 4 machines now, but it took months to figure out that incorrect mac addresses were causing the headache. I can't find when it started, but it had to be sometime between June and September. Reproducible: Always Steps to Reproduce: 1. use dhcpcd 2.check router 3.try to figure out what kind of crap "00000004000100010EA7FE6F0080C8B2" is Actual Results: Vomits a mess of letters and numbers instead of a mac address. Expected Results: Report the correct mac address in ifconfig. Sorry for the messy report, I'll send more information if requested. Current version of dhcpcd is 3.1.7, but I saw this issue long before.
Please read the docs, or at least the ebuilds messages. This is a feature and not any bug, and your router is broken, not dhcpcd. <snip> ewarn "You have installed dhcpcd with DUID support." elog "This means that we will generate a DUID in /var/lib/dhcpcd/dhcpcd.duid" elog "This is generated from a MAC address of the card and a timestamp." elog "It will be used in every subsequent DHCP transaction, along with a IAID" elog "in the ClientID option. This is required by RFC 4361." ewarn "Some DHCP server implementations require a MAC address only in the" ewarn "ClientID field. These DHCP servers should be updated to be RFC" ewarn "conformant. If you cannot do this, you can revert to the old" ewarn "behaviour by using the -I '' option OR building dhcpcd with the" ewarn "vram USE flag enabled." </snip>
