OPNsense Forum

English Forums => General Discussion => Topic started by: LVeronaS on June 24, 2024, 01:48:38 AM

Title: OPNsense after ISP Router without Internet connection to LAN Net
Post by: LVeronaS on June 24, 2024, 01:48:38 AM
I just bought J4125 hardware to build my own router. The reasons are that I want to learn more about networking and I'm frustrated with the strict limitations of my ISP-provided router.

Here is my network configuration:

ISP router (192.168.1.1) -> OPNsense WAN (192.168.1.2)
OPNsense LAN (192.168.2.1) -> Notebook (192.168.2.10)

I have a fresh install with a few manual changes (such as setting specific IP addresses, configuring the WAN default gateway, and disabling IPv6).

When testing the setup, I noticed that my notebook doesn't have an Internet connection and is unable to ping or trace to 8.8.8.8 or my ISP router. I am only able to ping/trace to the OPNsense LAN and WAN interfaces.

Using ping/trace from the OPNsense diagnostics tool, I was able to reach my ISP router and 8.8.8.8.

I did some research and found several posts mentioning configurations in NAT, Firewall, and others, but none resolved my issue. Does anyone have any tips or know how to resolve my problem?
I attached the current OPNsense configuration for reference.

As you may guess, I am still learning about networking, so forgive my naivety.

Best regards,
Leo
Title: Re: OPNsense after ISP Router without Internet connection to LAN Net
Post by: newsense on June 24, 2024, 03:12:15 AM
Interfaces - WAN

Disable " Block private networks "
Title: Re: OPNsense after ISP Router without Internet connection to LAN Net
Post by: LVeronaS on June 24, 2024, 05:51:39 AM
Hi newsense,

Thanks for the reply.

Both "Block private networks" and "Block bogon networks" flags are unchecked.

I'm afraid this isn't my solution :(

Regards,
Leo
Title: Re: OPNsense after ISP Router without Internet connection to LAN Net
Post by: LVeronaS on June 28, 2024, 03:56:48 PM
I was able to resolve.

Indeed I need to uncheck the "Block private networks" and "Block bogon networks" flags, but I also had to an additional setting.

My WAN was set as Static IPv4 and the 'IPv4 Upstream Gateway' was set to "Auto-Detect". I changed it from "Auto-Detect" to the only gateway available at my system "WAN_GW - 192.168.1.1" and it works perfectly after that.

Not sure why setting it to "Auto-Detect" would give an error in this circumstance, but it is resolved now.

Issue is done, but I would really appreciate if someone could tell me why this was the root cause.

Tks,
Leo