Created attachment 1435922 [details]
router web gui
I migrated from Ubuntu 17.10 to Fedora 28 KDE spin and now my router does not detect correct MAC address of my PC, which makes it impossible for me to set up static DHCP rules
Created attachment 1437689 [details]
Fedora 28 wireshark
Created attachment 1437690 [details]
Ubuntu 18.04 wireshark
So, I've run wireshark in Fedora 28 live USB and in Ubuntu 18.04 live USB. It works correctly in Ubuntu, works wrong in Fedora 28. Diff is basically this
< Transaction ID: 0x454aa16f
< Seconds elapsed: 0
> Transaction ID: 0xa9c15853
> Seconds elapsed: 3
< Option: (61) Client identifier
> Padding: 000000000000000000000000000000000000000000000000
network-manager in ubuntu: 1.10.6-2ubuntu1
NetworkManager in fedora: 1.10.6
dhcp-client in fedora: 4.3.6
isc-dhcp-client in ubuntu: 4.3.5-3ubuntu7
The only relevant difference is the client-identifier. Can you please check how it looks like on the wire running again tshark with the "-x -V" options?
Created attachment 1438117 [details]
Created attachment 1438119 [details]
Created attachment 1438124 [details]
fedora tshark cold boot
The DHCP client on Fedora sends a RFC4361 client-identifier, which your router wrongly consider as a MAC address. You could try to change the client identifier on the connection to look like a hardware address one, using this command:
nmcli con modify <connection-name> ipv4.dhcp-client-id 01:9c:eb:e8:07:d4:3f
where the last argument is '01:' followed by the interface MAC address. After this, try again to connect.
That solved it. After I rebooted. Until I rebooted, network stopped working.
Should we report this issue to upstream?
(In reply to Gabriel Ostrolucký from comment #9)
> That solved it. After I rebooted. Until I rebooted, network stopped working.
> Should we report this issue to upstream?
I don't think this is a bug. dhclient sends by default a client-identifier as specified by standards (RFC 4361). Apparently for some reason your router extracts the MAC from the client-id instead of looking at the actual MAC address.
In the upcoming version of NM (1.12, not released yet), it will be possible to globally set a mac-based client-id by adding the following:
to NM configuration, or to set it for each connection. See this: