31
General Discussion / Re: No internet access - not Getting IP for WAN via DHCP
« on: November 30, 2023, 01:15:15 am »
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.
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
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
Quote
Are 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
Quote
Do 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

