Ubuntu
subiquity package

Installation manual network config fails with "x.x.x.x is not in contained in x.x.x.x/yy"

Asked by Leon Castellanos

1) lsb_release -rd

Description: Ubuntu 20.04.1 LTS
Release: 20.04

2) Package version
Unknown. Whatever version is part of ubuntu-20.04.1-live-server-amd64.iso 2020-07-31 17:35

3) What I expected

For valid manual network settings to work.

4) What happened instead

Manual network configuration fails saying:

"'xxx.xxx.17.114' is not contained in '255.255.254.0/23'"

With network settings:

Subnet: 255.255.254.0/23
Address: xxx.xxx.17.114
Gateway: xxx.xxx.16.1

Subnet certainly contains xxx.xxx.16.1 - xxx.xxx.17.254

We attempted to define /23 on Address instead, but that is not allowed.

I work for NASA GSFC and we're having to proceed without network and then manually edit /etc/netplan/*.yaml after install.

If this is an error on our part, can you please clarify what we were supposed to enter for subnet? Since Subnet line requires an entry in CIDR form with error "should be in CIDR form (xx.xx.xx.xx/yy)"

Manual network config works fine with:

# This is the network config written by 'subiquity'
network:
  version: 2
  renderer: networkd
  ethernets:
    enp49s0f1:
      dhcp4: no
      addresses:
        - xxx.xxx.17.114/23
      gateway4: xxx.xxx.16.1
      nameservers:
          addresses: [xxx.xxx.10.134, xxx.xxx.50.17]

**IPs redacted for security purposes

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu subiquity Edit question
Assignee:
No assignee Edit question
Solved by:
Leon Castellanos
Solved:
Last query:
Last reply:

This question was originally filed as bug #1910155.

Revision history for this message
Leon Castellanos (leoncastellanos) said : 		#1

Figured out it's not looking for the subnet MASK but just the net cidr (xxx.xxx.16.0/23 in my case)

IMHO this is the stupidest way to do this.

I don't understand why you have chosen to do this in a completely unintuitive way to how every other operating system is configured using the netmask.

Revision history for this message
Bernard Stafford (bernard010) said : 		#2

It might let you range the IPs like in this exmple.
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.1, 192.168.1.2;
option domain-name "mydomain.example";

subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.100;
range 192.168.1.150 192.168.1.200;
}

Revision history for this message
Bernard Stafford (bernard010) said : 		#3

could it be defined as subnet-mask 255.255.255.0.023

Revision history for this message
Leon Castellanos (leoncastellanos) said : 		#4

Hi, I already stated in my comment that the solution is entering the subnet CIDR "xx.xx.16.0/23" and not the subnet mask.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#5

Don't confuse "subnet mask" and "subnet address"!

Revision history for this message
Leon Castellanos (leoncastellanos) said : 		#6

You're making it sound like I missed something obvious.

The prompt doesn't say "Subnet ADDRESS". It just says "Subnet: ".

Every other OS (UNIX/Linux) I've installed in my 30 years of sysadmin experience has requested a "Subnet MASK".

This is the first time I've seen an installer request a COMPLETELY UNINTUITIVE subnet address...

It's just dumb and it unnecessarily confuses people.

My colleagues here at NASA Goddard Space Flight Center said "WTF" once we figured out what it was asking for.

The prompt should say "Subnet Address" at the very least.

Revision history for this message
ranasab (ranasab) said : 		#7

Avoid mixing up "subnet mask" with "subnet address