wan and gateways on different networks,

MyKroFt

100% pack loss, even tho internet is up, but cant update dyn

this happened after a isp upgrade about 2.5 months ago and have not been able to resolve it

any suggestions, thanks

MyKroFt

This post is deleted!

MyKroFt

if i ping from my win11 or router, it has correct ip and comes back, but pfsense can not lookup the ip

patient0

@MyKroFt your DynDNS name is visiable in your first post and therefore your public IP, which does resolve correct when I dig <your name>.dyndns.org. You may want to remove the second picture of your first post, or re upload it with the first part of the FQDN blurred. I'd choose blur instead of one line strikethrough (which is still kinda readable).

If your gateway shows down then you have to fix that first.

I can't ping your gateway and maybe the gatway can't be pinged. A gateway doesn't have to be ping-able.

In System / Routing / Gateways, in your WANGW (or whatever you called it) set Monitor IP to something like 1.1.1.1 or 9.9.9.9.

Btw: what pfSense version are you using?

MyKroFt

@patient0

am using the latwstr when i updated last weekend

my internet is up, that gatewat is what is coming from isp

also found this

Dec 31 22:42:51 php-fpm 507 /services_dyndns.php: Dynamic DNS () Could not determine the request IP address (using "wan", "igb0"): gateway not online
Dec 31 22:42:52 php-fpm 507 /services_dyndns.php: Dynamic DNS: updatedns() starting
Dec 31 22:42:51 php-fpm 507 /services_dyndns.php: Dynamic DNS: updatedns() starting

gateway status

it looks like the gateway is coming back from isp is not reachable, changed moinitor to 1.1.1.1 and now dyn is working as the dyn updated and turned green with correct ip

thanks!

patient0

@MyKroFt excellent, glad it works.

Btw: your title "wan and gateways on different networks". I'm not sure what your are referring to but your gateway is in the same subnet as your WAN IP, it's just a bigger subnet.

The subnet mask is 255.255.240.0 or /20 which results in:

$ sipcalc 47.5.16.1/20
-[ipv4 : 47.5.16.1/20] - 0

[CIDR]
Host address		- 47.5.16.1
Host address (decimal)	- 788860929
Host address (hex)	- 2F051001
Network address		- 47.5.16.0
Network mask		- 255.255.240.0
Network mask (bits)	- 20
Network mask (hex)	- FFFFF000
Broadcast address	- 47.5.31.255
Cisco wildcard		- 0.0.15.255
Addresses in network	- 4096
Network range		- 47.5.16.0 - 47.5.31.255
Usable range		- 47.5.16.1 - 47.5.31.254

MyKroFt

@patient0

correct, previously before isp update was ip and gatewas had first 3 the same with 4 being different

MyKroFt

dam, cant type tonight, sorry

johnpoz

@MyKroFt said in wan and gateways on different networks,:

ip and gatewas had first 3 the same with 4 being different

Well if your old IP started with 69 from your ddns info you posted. Seems like they changed the IP range you are connected too is all. As @patient0 pointed out your IP and its gateway are in the same network.

47.5.16.1 - 47.5.31.254

Doesn't really matter what the 2 IPs are, as long as they are in that range they are the same network.

Your old gateway most likely answered ping, your new one in this 47 network does not it seems.