No routing to class C WAN
-
Ok, spent Christmas with the family, now back to debugging.
As said, everything seems to work: I can ping nodes on the intermediate network on the WAN side. I can even visit the fiberglass router's webpages from the LAN side.Routing from WAN to LAN works just fine. The only thing that doesn't work, is forwarding traffic for neither network to a default gateway. And I think I've found something.When connected to the cable modem (in bridge mode), my gateways look like this:
But when connected to the fiberglass router (not capable of bridge mode), they look like this:
The WANGW setting seems to be fixed, hard-coded. And it is configured as the IPv4 default gateway.I can easily fix it, but I do not like hard-coded settings that are normally received over DHCP. Because if my ISP changes something, my internet connections stops working, and the searching game is on.
Does anybody know what the WANGW setting is for? I do have ntopng installed.
-
@zak-mckracken you created a gateway by hand - remove it you should only have the wan_dhcp gateway.
Click the little trash can next to the wangw
-
@johnpoz said in No routing to class C WAN:
@zak-mckracken you created a gateway by hand - remove it you should only have the wan_dhcp gateway.
Click the little trash can next to the wangw
I leaned towards that conclusion too, but this is really not something I would do, because I'm just not knowledgeable enough to be comfortable with settings like that.
So at first I thought it was the result of some other setting, or some package that I had installed. But that doesn't make sense.
So I went through my posting history here on the forum, because I've probably consulted people here about this setting, and I've found this post:
https://forum.netgate.com/post/993975
Apparently, I had overridden my WAN IP address, netmask and default gateway to work around a provider-problem. Later, I reverted back the WAN IP address and netmask, but most likely neglected to revert the default gateway override.Does that make sense, or could it still be a package or another setting that's responsible for WANGW?
-
@zak-mckracken clearly your not going to be using isp A ip address with isp B clearly the wants was added by hand you have dhcp delete it
-
@johnpoz said in No routing to class C WAN:
@zak-mckracken clearly your not going to be using isp A ip address with isp B clearly the wants was added by hand you have dhcp delete it
Well, I was considering to change it to the new intermediate network gateway, but that doesn't make sense: The added gateway is identical to the DHCP gateway, kind'a confirming it was added manually due to the problem I described in the other thread.
So you're right; It has to go!
And so it went, nothing seems to break down with it.
Thanks for all the help, guys!
