Default incusbr0 seems to be capped at 8 leases?

IncusOS
1

Hi, second post here. I’m trying to add an 8th container to my IncusOS system. So far, they’ve all been on incusbr0, and it assigns each of them an IPv4 through DHCP.

incusbr0 currently has 8 leases on it: 7 containers and the gateway lease (incusbr0.gw). I just added an 8th container, and for some reason, no matter how hard I try, I can’t get it to lease an IP from incusbr0??

I’ve tried re-creating the container, using a different name, making sure the settings are correct, and it still won’t work.

Any help would be greatly appreciated. With my luck, it’s something stupidly simple that I’m totally missing.

2

Hey :slight_smile:

Please give the output of incus network show incusbr0 as well as incus network list.

3 
incus network show incusbr0
config:
  ipv4.address: 10.242.58.1/24
  ipv6.address: none
description: Local network bridge (NAT)
name: incusbr0
type: bridge
used_by:
  - /1.0/instances/adguard
  - /1.0/instances/ddns
  - /1.0/instances/debian
  - /1.0/instances/family-backup
  - /1.0/instances/nginx
  - /1.0/instances/samba
  - /1.0/instances/unbound
  - /1.0/instances/wg-easy
  - /1.0/profiles/default
managed: true
status: Created
locations:
  - none
project: default

incus network list -f yaml
- config:
    ipv4.address: 10.242.58.1/24
    ipv6.address: none
  description: Local network bridge (NAT)
  name: incusbr0
  type: bridge
  used_by:
    - /1.0/profiles/default
    - /1.0/instances/nginx
    - /1.0/instances/samba
    - /1.0/instances/unbound
    - /1.0/instances/wg-easy
    - /1.0/instances/adguard
    - /1.0/instances/ddns
    - /1.0/instances/debian
    - /1.0/instances/family-backup
  managed: true
  status: Created
  locations:
    - none
  project: default
- config:
    parent: enp42s0
  description: ""
  name: macvlan0
  type: macvlan
  used_by:
    - /1.0/instances/nginx
    - /1.0/instances/samba
  managed: true
  status: Created
  locations:
    - none
  project: default
- config: {}
  description: ""
  name: enp42s0
  type: bridge
  used_by:
    - /1.0/networks/macvlan0
    - /1.0/instances/adguard
  managed: false
  status: ""
  locations: []
  project: default
4

Hmm nothing obvious, try something like

incus network set ipv4.dhcp.ranges=10.242.58.2-10.242.58.254

Please also give incus version

5

Not running into this problem here. I just used a clean IncusOS system from our demo (try-it) service and ran 50 Debian 13 containers on it using the default incusbr0:

bash-5.2# for i in $(seq -w 50); do incus launch images:debian/13 c$i; done
bash-5.2# incus list -fcsv -cn4
c01,10.103.250.176 (eth0)
c02,10.103.250.196 (eth0)
c03,10.103.250.83 (eth0)
c04,10.103.250.147 (eth0)
c05,10.103.250.109 (eth0)
c06,10.103.250.38 (eth0)
c07,10.103.250.64 (eth0)
c08,10.103.250.254 (eth0)
c09,10.103.250.27 (eth0)
c10,10.103.250.113 (eth0)
c11,10.103.250.222 (eth0)
c12,10.103.250.13 (eth0)
c13,10.103.250.230 (eth0)
c14,10.103.250.49 (eth0)
c15,10.103.250.239 (eth0)
c16,10.103.250.7 (eth0)
c17,10.103.250.39 (eth0)
c18,10.103.250.63 (eth0)
c19,10.103.250.103 (eth0)
c20,10.103.250.231 (eth0)
c21,10.103.250.20 (eth0)
c22,10.103.250.155 (eth0)
c23,10.103.250.228 (eth0)
c24,10.103.250.82 (eth0)
c25,10.103.250.127 (eth0)
c26,10.103.250.167 (eth0)
c27,10.103.250.148 (eth0)
c28,10.103.250.193 (eth0)
c29,10.103.250.195 (eth0)
c30,10.103.250.235 (eth0)
c31,10.103.250.181 (eth0)
c32,10.103.250.253 (eth0)
c33,10.103.250.189 (eth0)
c34,10.103.250.73 (eth0)
c35,10.103.250.15 (eth0)
c36,10.103.250.2 (eth0)
c37,10.103.250.96 (eth0)
c38,10.103.250.135 (eth0)
c39,10.103.250.129 (eth0)
c40,10.103.250.232 (eth0)
c41,10.103.250.247 (eth0)
c42,10.103.250.173 (eth0)
c43,10.103.250.136 (eth0)
c44,10.103.250.190 (eth0)
c45,10.103.250.238 (eth0)
c46,10.103.250.131 (eth0)
c47,10.103.250.6 (eth0)
c48,10.103.250.168 (eth0)
c49,10.103.250.240 (eth0)
c50,10.103.250.8 (eth0)
7

Is macvlan use an issue?

8

I thought about that as well I don’t think incusbr0 is bridged to enp42s0

EDIT: No “parent enp42s0” that means it is bridged @perfectkirkle ?

9

Sorry for the late reply. Yes, incusbr0 does not have enp42s0 as a parent, plus I don’t think bridges can have parents.

I will try removing the macvlan device I created earlier, just to see if it does anything.

incusbr0 shouldn’t be modified from the original values, other than disabled ipv6.

I also tried setting the DHCP range manually, it didn’t change anything.

EDIT: I just noticed that by default, ipv4 NAT is overridden to “true” in incusbr0, but I must have removed that override. I feel like this was after my issues started, but I will also try that and see if that fixes anything.

10

Please make it possible that your community members can seen what you can see.

bridges do have members. What I see on laptop with hostname messer.

stappers@messer:~
$ ip -brief link | cut -b -28
lo               UNKNOWN    
enp0s31f6        DOWN       
wlp0s20f3        UP         
lxcbr0           DOWN       
incusbr-1000     UP         
incusbr0         DOWN       
veth1848bc43@if8 UP         
veth9f0505eb@if10 UP        
stappers@messer:~
$ ip link show master incusbr-1000
9: veth1848bc43@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master incusbr-1000 state UP mode DEFAULT group default qlen 1000
    link/ether 76:87:de:fe:11:73 brd ff:ff:ff:ff:ff:ff link-netnsid 0
11: veth9f0505eb@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master incusbr-1000 state UP mode DEFAULT group default qlen 1000
    link/ether 66:3a:44:ad:5e:51 brd ff:ff:ff:ff:ff:ff link-netnsid 1
stappers@messer:~
$ bridge link show master incusbr-1000
-bash: bridge: opdracht niet gevonden
stappers@messer:~
$ sudo bridge link show master incusbr-1000
9: veth1848bc43@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master incusbr-1000 state forwarding priority 32 cost 2 
11: veth9f0505eb@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master incusbr-1000 state forwarding priority 32 cost 2 
stappers@messer:~
$