Unexpected IP value leased from router DHCP

djarvo

New Member
Jan 13, 2024
2
0
1
Hello! I have a pretty simple home network configuration, where my isp router acts as DHCP leasing IPs in range 192.168.100.2 - 192.168.100.254.

Screenshot 2024-01-13 141934.png
On the screenshot you cah see DHCP config with a single allocated IP for my wifi AP.

So I also have a Proxmox Host on 192.168.100.3, but this is a static binding on my router:
1705144928494.png

What I try to do is to create a CT in Proxmox with enabled DHCP. I expect that the CT will get an IP within DHCP range 192.168.100.2 - 192.168.100.254 (like 192.168.100.4). But the result is different. This is what "ip a " says in CT:
Code:
root@CT101:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether bc:24:11:2e:ef:16 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.30.83.214/19 metric 1024 brd 10.30.95.255 scope global dynamic eth0
       valid_lft 3570sec preferred_lft 3570sec
    inet6 fe80::be24:11ff:fe2e:ef16/64 scope link 
       valid_lft forever preferred_lft forever

I see that IP 10.30.83.214 was allocated, but I can't get where it was leased from.
This is "ip a" from proxmox host:
Code:
root@pve:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether b4:2e:99:cc:3c:a3 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b4:2e:99:cc:3c:a3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.3/32 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::b62e:99ff:fecc:3ca3/64 scope link
       valid_lft forever preferred_lft forever
28: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether fe:0f:cd:1a:16:d1 brd ff:ff:ff:ff:ff:ff link-netnsid 0
29: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether de:46:7d:42:2d:cb brd ff:ff:ff:ff:ff:ff
30: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 06:74:9b:ac:93:ed brd ff:ff:ff:ff:ff:ff
31: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether de:46:7d:42:2d:cb brd ff:ff:ff:ff:ff:ff
32: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether fe:5f:9d:f3:ba:73 brd ff:ff:ff:ff:ff:ff link-netnsid 1
33: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 4e:dc:68:65:b3:aa brd ff:ff:ff:ff:ff:ff
34: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 7e:0e:a8:17:13:05 brd ff:ff:ff:ff:ff:ff
35: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether 4e:dc:68:65:b3:aa brd ff:ff:ff:ff:ff:ff

Can someone give me a hint what is wrong with my config?
 

Attachments

  • 1705144748220.png
    1705144748220.png
    51.9 KB · Views: 0
  • 1705145027008.png
    1705145027008.png
    23.8 KB · Views: 0
After some diggin into my router configuration I found out that lan port where proxmox is plugged was configured in WAN DHCP mode (whatever it means). Changing it to LAN fixed the IP distribution.
1705150514578.png
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!