Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Tetra

#1
General Discussion / Re: WAN out connection Issues
September 06, 2026, 01:30:59 AM
My end goal in the future is to have all my devices besides mobile devices behind OPNsense. Important note the Modem and ISP Router are equipment from Spectrum, so I have very limited control over them.

Modem:
-It has no management address I can find
-No
-I believe Bridge due to the ISP Router having a public IP
-Not that I can see
-The model # is EU2251

ISP Router:
-It doesn't have a explicit management IP, but I used the gateway IP from my desktop directly connected to it and I did get a page directing me you use my mobile app without any other UI options
-Not any true configurations
-I can only add/edit Port forwarding, IP Reservations, DNS Servers, UPnP, and Security Shield
-Preferably I don't want to take my ISP router out topology but if I have to then I will
-Model # is SBE1V1K

Cisco Switch:
-The Switch is connected to OPNsense LAN using a L3 interface. IP routing is enabled
-As of now I only have one VLAN setup on this switch with a SVI(only has a IP and description in config). The IP of the SVI is a 10.11.120.1/24 IP
-The DHCP pool gives the endpoints IPs with a DNS(OPNsense LAN IP) and Gateway(VLAN SVI IP)

OPNsense:
-Routing Table: (Of course these aren't my actual IPs and Subnets)
Internet:
Destination        Gateway        Flags    Netif Expire
default                192.168.1.1        UGS         re0
10.11.110.0/30      Link#2            U               re1
10.11.110.1               Link#3           UHS         lo0
10.11.120.0/24      10.11.110.2         UGS         re1
127.0.0.1                Link#3           UH            lo0
192.168.1.0/24    Link#1            U               re0
192.168.1.101        Link#3           UHS         lo0
-Automatic Source NAT mode (All these rules are auto generated)
 LAN | IPv4 | Source Loopback Network --> Destination Port 500 | Translate Source IP LAN Address
 LAN | IPv4 | Source Loopback Network --> Translate Source IP LAN Address
 WAN | IPv4 | Source Loopback Network --> Destination Port 500 | Translate Source IP WAN Address
 WAN | IPv4 | Source Loopback Network --> Translate Source IP WAN Address
-LAN rules
LAN | IPV4 | Direction: BOTH | ALLOW ANY | (Note: For now this is just for test and will change later)
LAN | IPv4 | Direction: BOTH | ICMP | ALLOW |
#2
General Discussion / Re: WAN out connection Issues
September 05, 2026, 12:48:27 AM
I have applied what you have suggested and sadly no improvements and no new ping/reachability changes. The only custom things I have done (outside of your suggestions) to OPNsense is set up DNS over TLS to cloudflare and a few other DNS servers with firewall rules. I have also created the LAN point to be a routed interface with a /30 IP. The routed interface is pointing to my cisco switch routed port. On that switch I have a DCHP service enabled and the pools give the gateway to the user their respective SVI on that switch. I don't use OPNsense for dhcp services and none of my vlans or dhcp pools are held/conflict with OPNsense. This set up is entirely physical. The WAN interface is getting a IP from the ISP router's DHCP. Both IPv4 and IPv6 gateways with proper addressing are active and online.
#3
General Discussion / Re: WAN out connection Issues
September 04, 2026, 01:28:21 AM
Follow-up: For testing purposes I did some allow any firewall changes and I believe the firewall was blocking the pings from the other devices connected to my ISP router. The OPNsense WAN interface can now ping the ISP Router private not public, while other devices connected to the ISP can ping the public IP. Other devices can also ping the OPNsense WAN interface but the issue still persists where the endpoint can't ping the ISP Router(public or private).
#4
General Discussion / Re: WAN out connection Issues
September 03, 2026, 11:42:21 PM
So on the ISP I still have some of my other personal devices connected and they can ping each other and the ISP Router, but can't ping still the OPNsense WAN interface. I've confirmed that its properly pulling a IP from the router by restarting the interface. All my other devices work just fine connected the ISP router but this OPNsense WAN interface.
#5
General Discussion / Re: WAN out connection Issues
September 03, 2026, 06:29:51 PM
The WAN IP is private and the IP on the ISP is private that I am trying to ping. I have also tried to ping the ISP's public IP but as expected no luck. I have tried to ping the ISP router from OPNsense with no luck.
#6
General Discussion / WAN out connection Issues
September 03, 2026, 03:44:45 AM
I've ran into an issue setting up my personal physical network. I currently can't ping my ISP Router from my endpoint but I can ping the Opnsense WAN from the same endpoint. I believe it might be a routing issue between the WAN and ISP but I'm hopping someone could provide more input. The following is my topology for clarity:

Endpoint --> SVI --> Switch Routed interface --> Opnsense LAN --> Opnsense WAN --X--> ISP Router --> Modem