Hi,
i'm using opnsense the last years without any issue, but now i've got a problem i can't handle.
I've got an pppoe as WAN (Telekom VDSL - working flawless for years) and just want to add an second WAN connection for failover (Vodafone cable) which uses DHCP. Everything is working, but if i reboot the opnsense while the Vodafone dhcp-server is not reachable (modem offline), the WAN2 interface get's 0.0.0.0 as IP and so its not possible to set the default route for opnsense -> no traffic from LAN to WAN.
In "Interfaces / Overview" i can see, dhcp for WAN2 is marked "UP" - if i "renew" dhcp lease on WAN2 it is marked "down", the 0.0.0.0 on WAN2 is gone and i can setup an default route via pppoe.
It seems to be a problem with dhcp lease on startup - any idea? Am i doing something wrong?
opnsense 17.7.6
wfr
Michael
Hi Michael,
Some modems can give out faulty leases. You can find out which IP this doing this and add it to the blacklist under Interface: [WAN]: "Reject Leases From".
Cheers,
Franco
Hi Franco,
faulty leases could be an option, but in my case the new vodafone modem is still "offline". There's nothing connected to the wan2-opnsense-interface - nevertheless after an reboot the DHCP is marked "up" with ip "0.0.0.0"
Michael
uncheck block private IPs from the interface WAN and try if you get an ipadress from the 192.168.100.x block
The Vodafone (KD) Modems often have a webinterface on 192.168.100.1
Is the bridgemode activated for the cablemodem? else you allways get private ips from the cable modem
Hi Nils,
bridge mode is activated and i'm not getting an ip in the Range 192.168.x.x. The problem still exists even if the modem ist powered off -> no change to get a wrong answer by the modem.
Michael