ATT Internet AIr

[ahole4sure]

@tman222 @stephenw10
Thanks guys
For an Orthopedic surgeon this is a humbling process!! -- sure am thankful for your expertise

Here is what I have
I am able to ping 192.168.2.1 but not reach the gateway interface

[stephenw10]

The translation address in the outbound NAT rule needs to be the VIP not the WAN address. And that needs to be on the WAN. It's applied to traffic as it leaves the WAN interface.

That rule you have above it seems odd, that shouldn't ever be required. Those are manually added outbound NAT rules?

[ahole4sure]

@stephenw10
Yes that is manually created based on the suggestions that I needed to create a outbound rule

Is my VIP created correctly? My gateway says on the front that I can access the settings page by going to http://192.168.2.1 (so it would insinuate that it is infact accesible)

Can you tell me how to create the outbound rule correctly - clearly I am not thinking about things correctly

[stephenw10]

The VIP is good as long as the Nighthawk is using a different IP in the 192.168.2.0/24 subnet.

[ahole4sure]

@stephenw10
So the Nighthawk is using 192.168.2.1
So my VIP needs to be somehting differnet in that subnet , like 192.168.2.10 ?

Then I gotta figure out the outbound rule thing

[ahole4sure]

@stephenw10
Should the VIP be setup on the WAN or the LAN interface??
Sorry probably sounds dumb

[ahole4sure]

@stephenw10 ok this finally worked --- look ok??

[stephenw10]

Yup exactly like that.

[stephenw10]

Though the source port should be empty because that's the port the client uses to connect from which is usually some high numbered random port.

Also you should se https (or both) if the router supports it.

[ahole4sure]

@stephenw10
So freaking weird
I made the change of the source port and then I could no longer access http://192.168.2.1
I can still ping the address

So weird - I tried changing it back and it still wouldn't work
hitting my head lol

[stephenw10]

Hmm, odd. Try removing the ports entirely. There's no real reason to specify a port there, all traffic between LAN and the modem would need to be NAT'd.

[ahole4sure]

@stephenw10 Well I tried to remove all the port entries and still no success

Whats really odd is that if I activate my Wireguard VPN into my network -- viola , I have access to http://192.168.2.1. (notice in my settings for the tunnel I have allowed IP ranges including 192.168.2.0/24

[stephenw10]

Hmm, almost sounds like that NAT rule is actually breaking the connection. Since with the source port set to 80 it would not have been matching the traffic.

Try disabling the rule.

[ahole4sure]

@stephenw10 OMG!! That worked - after all that

Thanks again

[ahole4sure]

@stephenw10 Oddly I changed back to "Auto Mode" for Outbound NAT and it still worked

[stephenw10]

Hmm, interesting! That still using 192.168.2.1 to access it? It seems like the Nighthawk has a route to the public IP then. In which case that's no problem.

[ahole4sure]

@stephenw10 yes still using 192.168.2.1

[stephenw10]

Should be fine then. Some modems do not require a NAT rules and can use the public IP on WAN to reply to.

[ahole4sure]

@stephenw10
Now that I have survived that ordeal , lol (with you help) - I have to replicate the process at our second location.

My pfsense device at that location only has 4 ethernet ports just like the one I have at location 1 - however, at location 2, I have all 4 ports used as per the pics. 2 are for security camera ports, one for and eero wifi and 1 for my NAS.

I have them on differnt networks.

What would be the best way to salvage my current equipment and still setup a failover internet (second WAN)? since my ports are filled

[ahole4sure]

@ahole4sure