No internet access - not Getting IP for WAN via DHCP

Started by P195, November 29, 2023, 12:21:14 PM

Previous topic - Next topic
Hi all,

I've switched my ISP's [modem/router/ap] into bridge mode and have connected a cable from the WAN port on the back to the first port on my OPNsense router. The ports on the OPNsense router are labelled ETH0,ETH1,ETH2,ETH3. When installing OPNsense I configured the ports - the available options in the list were igc0,igc1,igc2,igc3 so I set WAN as igc0 and LAN as igc1. So... WAN from bridged ISP router into WAN (igc0/ETH0).

I've connected my PC into the LAN port and am able to access the OPNsense GUI where I have run through the wizard and have set WAN as DHCP and have specified DNS servers as 9.9.9.9 and alternative as 1.1.1.1. I have left the two checkmarks on (for the blocking of bogon and the other one).

From the video's I've seen, I should be able to access the internet off the bat but I can't. I've rebooted both the ISP modem and the OPNsense router. When the OPNsense router has finished booting it shows my LAN IP as 192.168.1.1/24 but for the WAN IP it shows 0.0.0.0/8 and I assume this is why I can't access the internet.

I went into the ISP routers GUI, but most of the configurable settings have been disabled due to being in bridge mode. I've also tried fiddling about with the TCP/IPv4 properties for the network interface on my PC, but to no avail.

The cables I've used are straight thru patch cables RJ45 pinout T-568B and have tried several which haven't worked, so I don't think the cables are the issue. I do not yet have a managed network switch, I've plugged my PC directly to the LAN port on the OPNsense router, does that matter?

Any tips on what I could try get a WAN IP detected by OPNsense from my ISP's router in bridge mode please?
Also please bear in mind that I'm a networking beginner so simple explanations would be helpful.

Many Thanks!
P195

Quote from: P195 on November 29, 2023, 12:21:14 PM
I've switched my ISP's [modem/router/ap] into bridge mode and have connected a cable from the WAN port on the back to the first port on my OPNsense router. The ports on the OPNsense router are labelled ETH0,ETH1,ETH2,ETH3. When installing OPNsense I configured the ports - the available options in the list were igc0,igc1,igc2,igc3 so I set WAN as igc0 and LAN as igc1. So... WAN from bridged ISP router into WAN (igc0/ETH0).

You should connect the WAN port of your OpnSense to (one of) the LAN port(s) of your bridge. It still bridges from whatever connection technology it supports to ethernet. If it has a WAN port, then it is destined to be used with another bridge, like an ONT, which you do not have, instead of its internal modem.

The numbering of physical interfaces is somewhat arbitrary. Are you sure that the correct WAN port of your OpnSense is connected to bridge? You can at least check if the interface is up, regardless up its IP. There shoul be only two interfaces that are up, namely the LAN and the WAN. If you see other physical interfaces up (igcX), then use those.

Quote
I've connected my PC into the LAN port and am able to access the OPNsense GUI where I have run through the wizard and have set WAN as DHCP and have specified DNS servers as 9.9.9.9 and alternative as 1.1.1.1. I have left the two checkmarks on (for the blocking of bogon and the other one).

From the video's I've seen, I should be able to access the internet off the bat but I can't. I've rebooted both the ISP modem and the OPNsense router. When the OPNsense router has finished booting it shows my LAN IP as 192.168.1.1/24 but for the WAN IP it shows 0.0.0.0/8 and I assume this is why I can't access the internet.

Same thing here: Do you see that only on the console or can you access the web GUI from your PC?

Quote
The cables I've used are straight thru patch cables RJ45 pinout T-568B and have tried several which haven't worked, so I don't think the cables are the issue. I do not yet have a managed network switch, I've plugged my PC directly to the LAN port on the OPNsense router, does that matter?

No.
Intel N100, 4 x I226-V, 16 GByte, 256 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Thank you for your response. This evening I have connected from the LAN port on the ISP router instead of the WAN port as you suggested.

QuoteAre you sure that the correct WAN port of your OpnSense is connected to bridge?

When I booted the OPNsense router the loading console showed that igc0 and igc1 were UP. To ensure that these corresponded to ETH0 and ETH1 as labelled on the device, I went through the interface setup again but this time I disconnected both WAN and LAN connections to the OPNsense router and used the auto detect function, plugged in the WAN cable to ETH0 and it detected this as igc0. Then I plugged in the LAN cable into ETH1 and it detected this as igc1, so this is how I had it configured before and I believe this is all correct.

I rebooted both ISP router and OPNsense router just in case it required this. After rebooting I noticed that during the console configuration stage, many of the other configuration steps (e.g firewall, Lagg, VLAN, LAN etc etc) said done very quickly but when it got to the configuring WAN, it took about 25 seconds before it said ....Done. Is that normal behavior?

Once at the login in the console, I noticed the WAN IP is still showing as V4:DCHPv4 0.0.0.0/8

QuoteDo you see that only on the console or can you access the web GUI from your PC?

I was able to access the web GUI at 192.168.1.1 and login (both yesterday and today). The IP shown in the web GUI for WAN also (still) shows 0.0.0.0 for WAN. I have attached some snips of some web GUI sections (filenames named accordingly).

I'm obviously missing something. Any ideas?

Many Thanks
P195

I just found the following thread: https://community.plus.net/t5/My-Router/Hub-2-Bridging-Mode/td-p/1848842

I've currently got my WAN set as DHCP, the accepted fix in this thread suggests I need to use PPPoE for the WAN interface, and input my broadband login credentials so I'll give that a go this evening and hopefully that'll do the trick!