23.7.7 No WAN IP On Reboot

[jaskerx]

Installed OPNsense 23.7.4 and set it up from scratch it was working perfectly and have since updated to 23.7.5 and 23.7.6 without issue but now with 23.7.7 and having to reboot I have no WAN IP. I am able to work around this two ways I can either just go to the WAN interface and hit save or I can go to Interface Overview and hit reload under DHCP on the WAN, both are inconvenient as they require my manual intervention. Looking around the various forums on the net I find that this is a common issue in fact while I was running pfSense I reloaded my config and ran into this same problem but was able to work around it by setting my speed and duplex on the WAN to 100baseTX-full duplex. That same solution does not seem to work here.

My config is somewhat advanced as I have three OpenVPN connections set up into a gateway group all with priority 255 while the WAN_DHCP has 100. When I boot not having an WAN IP the gateway section says that WAN_DHCP is defunct and VPN3 is active. I do not have default gateway switching enabled and setting WAN_DHCP as upstream gateway does not work either. Have tried adding 8.8.8.8 as monitor IP to default ipv4 gateway which also didn't work.

I also have this in my logs:

Code: [Select]


/usr/local/etc/rc.bootup: The command '/sbin/dhclient -c '/var/etc/dhclient_wan.conf' -p '/var/run/dhclient.igb0.pid' 'igb0'' returned exit code '1', the output was 'igb0: no link .............. giving up'



Code: [Select]


ifconfig igb0

igb0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
description: WAN (wan)
options=4e0002b<RXCSUM,TXCSUM,VLAN_MTU,JUMBO_MTU,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
ether MAC ADDRESS
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>



Code: [Select]


netstat -rn

Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
127.0.0.1             link#6             UH          lo0
192.168.10.0/24    link#2             U          igb1
192.168.10.1       link#2             UHS         lo0
192.168.20.0/24    link#10            U        vlan02
192.168.20.1       link#10            UHS         lo0
192.168.30.0/24    link#11            U        vlan03
192.168.30.1       link#11            UHS         lo0
192.168.40.0/24    link#12            U        vlan04
192.168.40.1       link#12            UHS         lo0
192.168.100.0/24   link#9             U       vlan010
192.168.100.1      link#9             UHS         lo0

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::1                                       link#6                        UHS         lo0
fe80::%lo0/64                     link#6                        U              lo0
fe80::1%lo0                        link#6                        UHS         lo0


Starting to wonder if this could be an issue with the DSL modem itself? I have been told at one point to try to insert a switch between the modem and the router but I don't have an extra so have not been able to try this.

Looking through Github all the other similar issues have been merged into https://github.com/opnsense/core/issues/2517 here. Nothing there has led to any solutions so I wondering if anyone here might be able to offer assistance. Please let me know what other logs you might need.

[franco]

> media: Ethernet autoselect (100baseTX <full-duplex>)

This seems a bit low. How is the OPNsense WAN port connected?

Maybe the thing in front works better in half-duplex mode. You can change it from the WAN settings.


Cheers,
Franco

[jaskerx]

It's only a 50 Mbit connection that's what the port always auto-negotiates at even under pfSense. I will give that a try but I doubt it will make any difference.

EDIT: Guess I should add that the NIC is an Intel I350-T4, WAN is igb0 and LAN is igb1. WAN is connected to DSL modem in bridge mode.

[CJ]

Have you tried a different cable?  What do other devices show when connected to the modem?

Being DSL I wouldn't be surprised if it only has a 100m port but without knowing the model number it's impossible to know for sure.

[jaskerx]

OMG I'm so dumb...years ago when I wired up the internet in the house I used a power brick with Ethernet surge protection and was running through that still. Now that I run from the modem straight to the router the problem is gone, and the port is even negotiating at 1000baseT (not that it's using it). Still I wonder why it wasn't an issue when I installed OPNsense? Sorry to waste every ones time, going to go jump in a lake now! 

[franco]

Hehe, no worries. Glad you could solve it.


Cheers,
Franco

[CJ]

I remember running into that problem when connections started getting faster.

I'm not sure if any companies ever updated their products with gig or higher capable surge protection.