Messages

Hey everyone, thanks for the attempts at repairing this!  I think we can mark this as CLOSED.

After reading Nero's message, I went down that route, as there didn't seem to be anything blatantly wrong on my end.  Called in to activate the modem again and the ISP made it seem like they forgot something and put me on hold for awhile.  Came back, said everything should be good.  Still didn't have internet access.

So I decided to just put the ISP's modem/router/switch/AP combo unit back in and called to reactivate - the rest of the family was getting too upset at the lack of internet access during troubleshooting.  SAME ISSUE occurs with this one.  Call again, new person gets on, says they need to 'send an additional signal' (likely this portal activation part Nero mentioned) and now it is finally working and I have access.  It seems that they just don't try very hard when it's a customer device instead of one they control (I cannot change settings to their device through the web GUI nor SSH - I have to install an app on my phone to get access.  absolutely insane).  So i plan to just slap it in bridge mode and hook the rest of my network back up like before

System > Routing > Gateways has a gateway IP

Check status is Online, Pending, or Offline

Interfaces > WAN  Confirm IPv4 Configuration Type is DHCP

Check the actual default route   




These all appear to be correct and set up.

netstat -rn -f inet | head -20

This looks like it knows where to go, it's just not making it out for some reason.  Is there something beyond just activating the new modem with the ISP that they must do for it to function properly?  If so, why would I already have public IP coming from it?  i assumed these are provided by ISP.

Could the issue be related to DNS servers (or lack thereof)?  I would assume there's no need to set them up manually on a fresh install.

Check if the MB8611 is in bridge mode if your ISP requires it
The web admin for this modem is status only, though from poking around online, it appears it only functions in bridge mode.  Shouldn't have any weird double-NAT shenanigans as it has no routing capabilities.

Thanks for the response, here are the outputs:

ping -c 3 1.1.1.1
ping -S <WAN_IP> -c 3 1.1.1.1
netstat -rn | head -20

no route to address apparently?


Check System > Routing > Gateways to see whether the WAN gateway is online.

This looks good to me

post the WAN interface settings

appears okay, though of course i can't confirm the public ips

check Firewall > Log Files > Live View while trying to ping 1.1.1.1



Sorry for all the phone pics - the OPNsense network is offline, so I am working off of hotspot to post.

Additional information on system setup:

I recently set up a new OPNsense box running an i226-V dual nic.  The WAN is connected to an MB8611 modem, the LAN is connected to a RealHD managed switch (currently no VLANs or other changes made on the switch), which has an Omada AP and laptop attached to different ports.  My issue is that I cannot reach any public addresses from any machine on the network.

• WAN port is receiving IP from modem, modem is showing connected/bonded
• LAN DHCP is running properly and all devices can reach other without issue
• devices on LAN can ping the modem and access its webGUI, implying traffic is flowing from LAN to WAN properly
• devices on LAN cannot ping 1.1.1.1, 8.8.8.8, etc.  Console of OPNsense box as well as OPNsense GUI are also unable to ping these public addresses

I cannot seem to figure out what is causing this issue.  NAT rules appear correct, gateway setup is (I assume) correct.  I've fresh installed a handful of times.  Called ISP to activate new modem, power cycled to break MAC bonding, etc.  Any pointers on what might be blocking my ability to get to the outside world??

Thanks