Gateway down, can't allocate LLInfo
-
Hey guys. I know this question has been asked countless times before, but the existing Topics on this forum didn't really help me.
Suppose this: https://www.dropbox.com/s/d24ix11ba4gdmac/Screenshot%202016-01-15%2009.41.06.png?dl=0
Now, ISP1 is my standard WAN interface (DHCP) - This works fine.
ISP2 is my second WAN interface, on another subnet (X.X.3.2). This works fine now, too, after resetting the link state and re-entering the static route.
ISP3 however, is my 3rd WAN, which is connected to my PFSense via a Fritz!Box (TKom) - This does not work. It used to in the beginning, but the Router on this subnet can no longer be pinged (X.X.4.2)I figured this would be a routing problem as well. Now, when I try to change it (or fiddle with it in general, really) I get the message "The gateway '192.168.4.2' is a different Address Family as network '192.168.4.2'." - this does not occur on my other route, which works in a similar scheme just on a different subnet.
Does anyone have an idea how to fix this? I read on the Documentation that "Address Family" describes IPv4 and IPv6 - the networks are both IPv4 however. I don't even know where to start looking
-
Interfaces>Wan3
Make sure block private network is NOT selected
-
First of all, thanks for your reply. :)
It is not.
This is the info page on the affected WAN interface:
https://www.dropbox.com/s/j9mjy2iyr0ggdk4/Screenshot%202016-01-27%2010.40.21.png?dl=0Only thing missing is the name and the checked "Enable Interface" box.
I've been thinking though. Maybe I'm looking at the problem from the wrong end - PFSense can't talk to the router behind the interface, sure, but maybe it's just that the router there doesn't answer. Which would be weird since that one does not have a firewall (or really any other capabilities) enabled, but it's definitely something I will have to look into.