Routing issues between WAN and LAN
-
Routing table looks normal, except for the host route in bold… that looks strange... shouldn't be needed... but who knows... someone chime in and give us an idea if that's normal.
Not at all normal, that's a publicly routable network to a privately routable network and should not be in there.
-
I thought it looked strange too, but he said it was automatically added when he plugged in his modem… so idk... I don't know why it would add a host route like that... doesn't look standard... I checked a couple other routing tables from routers that were connected to cable modems via dhcp and none of them had a route like that. I'm betting there's something to it... but he says it was added automatically, so I gave him the benefit of the doubt.
-
I'd actually be willing to bet that's his problem. If stuff is headed to his gateway with that static route there, it's going to try to push it to that IP which makes absolutely no sense.
OP, please try the following command in your CLI: route del 192.168.1.1 173.81.164.1
After that, try it again and let us know the results. That route should not be there. -
Since it's a fresh install and I didn't have much time put into it yet I did a reset to factory defaults. It is now functioning fine. I checked my current routing table and the aberrant route being discussed is not present. I don't know how it was created but it very well may have been the problem. Thank you all for your help.
-
Hi,
I do have exactly same problem, i tried restoring Pfsense to default settings it didn't help at all…
I can ping 8.8.8.8 from pfsense but not from any computer on my lan. Please help!!
Does some one have any suggestions? Here my route:
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 70.168.57.34 UGS 0 20224 em0
10.4.1.0 link#10 U 0 0 em2_vl
10.4.1.1 link#10 UHS 0 0 lo0
10.5.1.0 link#2 U 0 11485 em1
70.168.57.34/31 link#1 U 0 2482 em0
70.168.57.35 link#1 UHS 0 0 lo0
localhost link#8 UH 0 544 lo0 -
You likely don't have the same exact problem. What is the output of "netstat -rn" on the computer you're trying to ping from? What is the LAN address of your pfSense box?
-
You likely don't have the same exact problem. What is the output of "netstat -rn" on the computer you're trying to ping from? What is the LAN address of your pfSense box?
yes it is
PFSense BOX has WAN 70.168.57.35 routed IP
and gateway 70.168.57.34I also got IP block with 4 IP's and it's own gateway where should this go??
LAN: 10.5.1.1/24
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 10.5.1.1 UGSc 129 16 en4
10.5.1/24 link#7 UCS 2 0 en4
10.5.1.1 0:0:24:d0:6b:59 UHLWIir 144 618 en4 1158
10.5.1.10 127.0.0.1 UHS 0 0 lo0
10.5.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en4
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 2 39766 lo0
127.94.0.1 127.94.0.1 UH 0 21 lo0
127.94.0.2 127.94.0.2 UH 0 161 lo0
169.254 link#7 UCS 0 0 en4 -
anogmus, unless you're double natting, you have a config issue. (I guess that could be another BSD client, but looks like PFsense to me)
we're happy to help, but…Start a new thread, post a network map, post the IP schema for your network and include that routing table.
-
yes it is
Oh, my mistake then.
In the case of this thread, the fix was a factory default. I'd recommend you try that. Good luck! -
You might want to read this to know how to fix it https://forum.pfsense.org/index.php?topic=75495.0
-
Your issue has absolutely no relation to the OP's issue.