Quantcast
Channel: Active questions tagged 22.04 - Ask Ubuntu
Viewing all articles
Browse latest Browse all 4669

Netplan 'ignore-carrier' option doesn't work on 22.04 Ubuntu

$
0
0

So I have a machine running 22.04 ubuntu with a RJ45 ethernet card with two ports. One port has a cable plugged in, the other doesn't. The ideal situation is that I can configure both ports with an IP addr, static or assigned, carrier or no carrier. I've successfully produced this behavior on 20.04 ubuntu using the ignore-carrier option in my netplan yaml. However, this doesn't seem to translate to 22.04 for some reason. I can set a static IP or have dhcp assign an IP to the port that has a carrier, so I don't think addressing is a problem. Has anyone been able to get this feature to work on 22.04?

Here's my netplan config:

network:  version: 2  renderer: networkd  ethernets:    enp26s0f0:      dhcp4: true      ignore-carrier: yes      link-local: [ ipv4 ]

And the resultant logs from networkd:

● 2: enp26s0f0                                                                 >                     Link File: /usr/lib/systemd/network/99-default.link                  Network File: /run/systemd/network/10-netplan-enp26s0f0.netwo>                          Type: ether                         State: no-carrier (configuring)                  Online state: offline             Alternative Names: eno0                          Path: pci-0000:1a:00.0                        Driver: i40e                        Vendor: Intel Corporation                         Model: Ethernet Connection X722 for 10GBASE-T                    HW Address: a4:bf:01:6d:8a:e4 (Intel Corporate)                           MTU: 1500 (min: 68, max: 9702)                         QDisc: mq  IPv6 Address Generation Mode: none          Queue Length (Tx/Rx): 64/64              Auto negotiation: no                         Speed: n/a             Activation Policy: up           Required For Online: yesSep 04 02:55:04 ta systemd-networkd[918]: enp26s0f0: DHCPv6 lease lostSep 04 02:57:14 ta systemd-networkd[918]: enp26s0f0: Re-configuring with /run/s>Sep 04 02:57:14 ta systemd-networkd[918]: enp26s0f0: Re-configuring with /run/s>Sep 04 02:58:16 ta systemd-networkd[37387]: enp26s0f0: Link UPSep 04 02:59:16 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>Sep 04 02:59:16 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>Sep 04 03:01:19 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>Sep 04 03:01:19 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>Sep 04 03:02:20 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>Sep 04 03:02:20 ta systemd-networkd[37387]: enp26s0f0: Re-configuring with /run>

These logs and the netplan apply --debug logs don't tell me much, any more info would be much appreciated! My backup plan is to use ifconfig to manually set the static IP for this port. This command works but it's major downside is that the assignment gets randomly lost at times and always lost on reboots.


Viewing all articles
Browse latest Browse all 4669

Trending Articles