[Bug 2092860] Re: netplan routes issue with static ipv4 and ipv6

Chris Peterson 2092860 at bugs.launchpad.net
Fri Jan 10 21:43:14 UTC 2025


This is a known bug in our UI. We only ever specify the "default" route,
which AFAIU is mutually exclusive with setting individual routes for
IPV4 and IPV6.

For now, if you would like to specify a route for each then the
workaround is to supply the desired netplan config via autoinstall in
the network[1] section.

[1] https://canonical-subiquity.readthedocs-
hosted.com/en/latest/reference/autoinstall-reference.html#network

** Changed in: subiquity (Ubuntu)
       Status: New => Confirmed

** Changed in: subiquity (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2092860

Title:
  netplan routes issue with static ipv4 and ipv6

Status in Netplan:
  Invalid
Status in subiquity package in Ubuntu:
  Confirmed

Bug description:
  root at ub6:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 24.04.1 LTS
  Release: 24.04
  Codename: noble

  =====

  root at ub6:~# apt-cache policy netplan.io
  netplan.io:
    Installed: 1.0.1-1ubuntu2~24.04.1
    Candidate: 1.0.1-1ubuntu2~24.04.1
    Version table:
   *** 1.0.1-1ubuntu2~24.04.1 500
          500 http://ca.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       1.0-2ubuntu1.2 500
          500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages
       1.0-2ubuntu1 500
          500 http://ca.archive.ubuntu.com/ubuntu noble/main amd64 Packages

  ======

  3. I am configuring the ubuntu server on proxmox 8 via gui and setup
  ipv4 and ipv6 manually with their subnet, ip and DHCP gateway.

  a) I edited ipv4 first
  b) I edited ipv6 second

  Installed.

  I was expecting that ipv4 and ipv6 will use their own dhcp server to
  connect however this only set a single DHCP server routes default to
  the Action done on b).

  I am expecting if it should have looked like this as what is working
  for me after manual editing the yaml file.

  [code]

  network:
    version: 2
    ethernets:
      ens18:
        addresses:
          - 192.168.1.102/24
          - fd3b:14ca:3674:5011::102/64
        nameservers:
          addresses:
            - 1.1.1.1
            - 8.8.8.8
            - 2606:4700:4700::1111
            - 2001:4860:4860::8888
          search: []
        routes:
          - to: 0.0.0.0/0
            via: 192.168.1.1
          - to: ::/0
            via: fd3b:14ca:3674:5011::1

  [/code]

  4. Netplan /etc/netplan/50-cloud-init.yaml file looks like this based
  on network setting on ubuntu install via gui.

  a ) setting up ipv4 first, ipv6 second.

  network:
      ethernets:
          ens18:
              addresses:
              - 192.168.1.102/24
              - fd3b:14ca:3674:5011::102/64
              nameservers:
                  addresses:
                  - 1.1.1.1
                  - 8.8.8.8
                  - 2606:4700:4700::1111
                  - 2001:4860:4860::8888
                  search: []
              routes:
              - to: default
                  via: fd3b:14ca:3674:5011::1
      version: 2

  b ) setting up ipv6 first, ipv4 second

  network:
      ethernets:
          ens18:
              addresses:
              - fd3b:14ca:3674:5011::102/64
              - 192.168.1.102/24
              nameservers:
                  addresses:
                  - 2606:4700:4700::1111
                  - 2001:4860:4860::8888
                  - 1.1.1.1
                  - 8.8.8.8
                  search: []
              routes:
              - to: default
                  via: 192.168.1.1
      version: 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2092860/+subscriptions




More information about the foundations-bugs mailing list