DEBIAN 11 Can't join WAN without rebooting pfSence DHCP service

[matthieu15150]

Hello I'm new to the Proxmox comunity. And I think that I have do something very bad with my configuration. Like in the title I have a network configuration that have a firewall pfSense that do the usual stuff : routing, DHCP, DNS. I have configure it correctly with the web interface (I will post the configuration of the DHCP and network interface bellow).

The thing is that I have a Windows 10 VM and it has no problem with the DHCP. The only thing that I found to make the DEBIAN accept the ip configuration is to reboot the DHCP service (of the pfSense). I have tried to create a new pfSense / DEBIAN VM with different configuration but it is always when I reboot the DHCP service of the VPN that the DEBIAN can access the WAN.

I have tried to put some static IP address to see if the DHCP was not correct but nothing change.

The interresting thing is that when I can access the WAN by rebooting the DHCP service I reboot the DEBIAN VM and I'm stuck again with the same problem and need to reboot the DHCP service.

so this is the configuration of the debian interfaces :

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: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b6:75:71:66:87:98 brd ff:ff:ff:ff:ff:ff
altname enp0s18
inet 192.168.5.200/24 brd 192.168.5.255 scope global dynamic ens18
valid_lft 9547sec preferred_lft 9547sec
inet6 2a05:6e02:1007:aa10:b475:71ff:fe66:8798/64 scope global dynamic mngtmpaddr
valid_lft 85796sec preferred_lft 85796sec
inet6 fe80::b475:71ff:fe66:8798/64 scope link
valid_lft forever preferred_lft forever


and this is the configuration of the pfSense interfaces :

vtnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: WAN
options=800b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
ether 92:7c:38:54:85:e8
inet6 fe80::907c:38ff:fe54:85e8%vtnet0 prefixlen 64 scopeid 0x1
inet 192.168.10.51 netmask 0xffffff00 broadcast 192.168.10.255
media: Ethernet 10Gbase-T <full-duplex>
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
vtnet1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=800b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
ether e6:d1:d9:91:15:e6
inet6 fe80::e4d1:d9ff:fe91:15e6%vtnet1 prefixlen 64 scopeid 0x2
inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255
media: Ethernet 10Gbase-T <full-duplex>
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
enc0: flags=0<> metric 0 mtu 1536
groups: enc
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff000000
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=100<PROMISC> metric 0 mtu 33160
groups: pflog
pfsync0: flags=0<> metric 0 mtu 1500
groups: pfsync

The configuration of the DHCP is like this :
Subnet : 192.168.5.0
Subnet mask : 255.255.255.0
Available range : 192.168.5.1 - 192.168.5.254
Range : 192.168.5.100 To 192.168.5.150

All the VM's except the Windows 10 have a VirtO network adapter. I have tried to change the network adapter but nothing change.

This are the logs from the pfSense DHCP server when I reboot the DEBIAN (screenshot RebootDebian) and when I reboot the DHCP service (sceenshot RebootDHCPServices)

I will send the configuration or the bridges too.

[EDIT] When I use the traceroute commande I can join the pfSense but I can't go any further.

 

[matthieu15150]

Some news, when I change the VMID to be before the pfsense the Debian can access the WAN. But I found nothing to make it work properly.

 

[matthieu15150]

OK I found the reason why I can't have an IP with the DHCP ! The pfSense need tow interfaces BUT when you add one with the hardware menue you need to activate it AND change the boot order in the option menue. The network interfaces need to boot first and the you boot the OS.