Page MenuHomeVyOS Platform

Reboots fail with eapol WAN interface
Closed, ResolvedPublicBUG

Description

Took the time to upgrade a router I had with an eapol configured WAN interface using vif 0 from a 1.4 rolling release, specifically 1.4-20230714, to the release candidate. During this reboot, the device failed to boot properly as eth0.0 wasn't yet a valid interface. In the 1.4 rolling release, I was able to rectify boot issues by affixing hw-id, but in this rc, the hw-id seems irrelevant.

I beleive there are some existing bug reports around interface ordering and configuration at boot time, but given this was eapol specific, I wanted to open a seperate bug report here.

The specific service that appears to cause the config to fail here is the dynamic dns client.

Dec 22 18:35:31 sudo[1733]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/sh -c '/usr/sbin/vyshim /usr/libexec/vyos/conf_mode/dns_dynamic.py'
Dec 22 18:35:31 sudo[1733]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Dec 22 18:35:31 vyos-configd[767]: Received message: {"type": "init"}
Dec 22 18:35:32 vyos-configd[767]: config session pid is 1555
Dec 22 18:35:32 vyos-configd[767]: Received message: {"type": "node", "data": "/usr/libexec/vyos/conf_mode/dns_dynamic.py"}
Dec 22 18:35:32 vyos-configd[767]: Interface "eth0.0" does not exist!
Dec 22 18:35:32 vyos-configd[767]: Sending response 2

Details

Version
1.4.0-rc1
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Event Timeline

Hi @lclements0,

can you please attach your configuration used for both eth0 and dns dynamic?

c-po renamed this task from VyOS 1.4.0-rc1 reboots fail with eapol WAN interface to Reboots fail with eapol WAN interface.Dec 25 2023, 4:56 PM
c-po added a project: VyOS 1.5 Circinus.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
c-po changed Issue type from Unspecified (please specify) to Bug (incorrect behavior).

This is actually caused by a missing priority value from ddclient. This is an ancient bug indeed.

Reason is the VLAN interface is not yet created, when ddclient tries to consume it during boot.

c-po changed the task status from Open to In progress.Dec 28 2023, 8:27 PM
c-po triaged this task as Normal priority.
c-po edited a custom field.

@c-po apologies for the delay, missed this over the holidays.

ethernet eth0 {
        description WAN
        eapol {
            ca-certificate root_system
            certificate cert
        }
        hw-id 00:e2:69:63:f5:7a
        mac 78:6A:1F:B4:2C:B1
        vif 0 {
            address dhcp
            address dhcpv6
            dhcpv6-options {
                duid 00:02:00:00:0D:E9:30:30:31:45:34:36:2D:52:39:31:56:4A:31:46:47:32:30:35:35:32:39
                pd 0 {
                    interface bond0.100 {
                        address 1
                        sla-id 0
                    }
                    interface bond0.888 {
                        address 1
                        sla-id 1
                    }
                    length 60
                }
            }
            mac 78:6A:1F:B4:2C:B1
        }
    }
service {
  dns {
    dynamic {
      address eth0.0 {
       service noip {
         host-name "XXXXX"
         password "XXXXX"
         protocol "dyndns2"
         server "dynupdate.noip.com"
         username "XXXXX"
     }
 }
}
}
}
c-po moved this task from Open to Finished on the VyOS 1.4 Sagitta board.
c-po moved this task from Open to Finished on the VyOS 1.5 Circinus board.
c-po moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.6) board.