coreos / bugs

Issue tracker for CoreOS Container Linux
https://coreos.com/os/eol/
147 stars 30 forks source link

DUIDType=link-layer shows "Operation not supported" #2413

Open jorgelon opened 6 years ago

jorgelon commented 6 years ago

Issue Report

We need to send the mac as client identifier in IPV6 but when i enable the DUIDType=link-layer option in a .network file I get a "Operation not supported" error

Container Linux Version

NAME="Container Linux by CoreOS" ID=coreos VERSION=1688.5.3 VERSION_ID=1688.5.3 BUILD_ID=2018-04-03-0547 PRETTY_NAME="Container Linux by CoreOS 1688.5.3 (Rhyolite)" ANSI_COLOR="38;5;75" HOME_URL="https://coreos.com/" BUG_REPORT_URL="https://issues.coreos.com" COREOS_BOARD="amd64-usr"

Environment

Vmware environment. 1and1 cloud.

Expected Behavior

The dhcpcp client must send the mac as client identifier in dhcpv6

Actual Behavior

When the coreos vm starts i get an "Operation not supported" error and no ip is given.

Reproduction Steps

  1. I configure the ipv4 static or dynamic. No changes here
  2. My ipv6 setup [DHCP] DUIDType=link-layer
    1. In logs I get sd-netlink: callback failed: Operation not supported
    2. No ipv6 received and no ipv4

Other Information

lucab commented 6 years ago

I may be misreading the documentation, but it looks like you also need to set a corresponding meaningful value in DUIDRawData. Does your configuration stanza have it?

jorgelon commented 6 years ago

Yes but if I use that field, not only the mac address is sent "The DUID that is sent is composed of the DUID type specified by DUIDType= and the value configured here"

jorgelon commented 6 years ago

The point is i need to add DUIDType=link-layer in the .network file and start dhcpcd.service to get it working. I dont know why networkd is not able to do the same without starting dhcpcd.service.

lucab commented 6 years ago

I'm not familiar with this feature, so I don't know if it is a bug or just a lack in documentation/checks. I'd suggest to try to run the same configuration with current alpha, which has systemd-v238, and if you still experience the same behavior then report this directly upstream to the systemd bug-tracker.