OPNSense cannot get WAN IP via DHCP from ISP on host boot

[PikachuEXE]

I've read many posts and tried different solutions and I only find workarounds (e.g. cron scripts etc.)

My setup: 4 nic mini PC for OPNSense VM (and a few other VMs like pi-hole)
Only 2 nics are used, IPv4 only, no vLAN

Current workaround is either replug the WAN cable or run `ip link set nic3 down && ip link set nic3 up`

Relevant Proxmox `ip a`:

2: nic0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 60:be:b4:12:b1:30 brd ff:ff:ff:ff:ff:ff
    altname enx60beb412b130
5: nic3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
    link/ether 60:be:b4:12:b1:33 brd ff:ff:ff:ff:ff:ff
    altname enx60beb412b133
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether xx:xx:xx:xx:b1:30 brd ff:ff:ff:ff:ff:ff
    inet 192.168.5.1/16 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 ???/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether xx:xx:xx:xx:b1:33 brd ff:ff:ff:ff:ff:ff
    inet6 ???/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

Proxmox /etc/network/interfaces

auto lo
iface lo inet loopback

iface nic0 inet manual
#LAN Actual

iface nic1 inet manual

iface nic2 inet manual

iface nic3 inet manual
#WAN Actual

auto vmbr0
iface vmbr0 inet static
        address 192.168.5.1/16
        gateway 192.168.5.2
        bridge-ports nic0
        bridge-stp off
        bridge-fd 0
#LAN

auto vmbr1
iface vmbr1 inet manual
        bridge-ports nic3
        bridge-stp off
        bridge-fd 0
#WAN

source /etc/network/interfaces.d/*

OpnSense VM network devices:

• net0 virtio=xx:xx:xx:xx:77:86,bridge=vmbr0,queues=8
• net1 virtio=xx:xx:xx:xx:A8:A3,bridge=vmbr1,queues=8

OpnSense config:

• LAN
  • Interface xx:xx:xx:xx:77:86
  • IP address static 192.168.5.2
• WAN
  • Interface xx:xx:xx:xx:A8:A3
  • Using DHCP
  • Block priovate networks checked
  • Block bogon networks checked

 

[JohnnieKF]

On a failed boot, from the Proxmox host run:

tcpdump -ni nic3 -e port 67 or port 68

If DISCOVERs are going out and nothing comes back, it's upstream. If they never leave nic3, it's the bridge/VM side.

 

[PikachuEXE]

Thanks
I do see some `BOOTP/DHCP, Request from xxx` lines but no reply like `BOOTP/DHCP, Reply` until I manually restart nic via `ip link set` workaround
So I guess upstream is unable to update the connected state for some reason, gonna search more around it

 

[JohnnieKF]

It's worth knowing what's behind your PVE machine also, if you have a modem in bridge mode or an ONT for example. I had a similar setup a couple of years ago and depending how these are configured it can mess with your setup.