Configuring IPv6 (static) causes the IPv4 (static) default route to not exist in the netplan config after install on 22.10.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Confirmed
|
Undecided
|
Unassigned | ||
subiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When configuring the network on Ubuntu Server 22.04 with subiquity 22.10.1, configuring IPv6 (manual) causes the IPv4 (manual) default gateway to be lost and only the static IPv6 default gateway persists in the generated netplan configuration after install. This also affects the installer's network connectivity too and is noticeable when trying to import SSH keys from GitHub (what still is IPv4 only it appears, wow). Entering a shell and running `ip route` and `ip -6 route` shows the default IPv6 route but no default v4 route, this persists between the installer and the install after booting into it.
his was tested on a Proxmox VE (7.2-11) virtual machine with a virtio network adapter, not yet tested with other configs/hardware but I'll do more testing when I get home.
Changed in subiquity (Ubuntu): | |
status: | New → Confirmed |
Changed in subiquity: | |
status: | New → Confirmed |
Forgot to remove SLAAC from the title, getting an IPv6 address via DHCPv6 or SLAAC does not overwrite the IPv4 manually assigned gateway, only if both IPv4 and IPv6 is manually assigned