No route from LAN-WAN through new update? Help please.
-
So I just updated my firmware.. and now I've suddenly bumped into a strange problem - which I'm, not 100% certain is caused by the upgrade itself..
Anyways… I'm running:
2.0-BETA4 (i386)
built on Sun Nov 14 17:23:12 EST 2010
FreeBSD 8.1-RELEASE-p1You are on the latest version.
So here's the situation...
If I go to the console on the firewall, I can ping everything but WAN and LAN wise
If I go to a computer on the LAN, I can't ping anything but whats on the same internal switch by IP.
I can't ping ANY DNS names
I can't ping the firewall itself (192.168.1.1)
But if I go to a browser and type in the firewall's IP (192.168.1.1) I'm able to access the admin interface...What on earth could be the problem here?
Hoping someone can help me.. because I can't use the internet at home atm...
Br,
Amelsen -
Its just that the default antilockout rule has been tightened to only tcp protocol and ssh and webGUI ports.
Before you LAN was wide open to anything coming to it which is not always secure! -
Well unable to solve it, what I did was actually do a complete reset to defaults… this seemed to solve the issue without coming on the net internally. Now I just need to set up all my configurations again.
-
How do I set it up so I'm allowed and able to ping everything internally and get a response? Is there something specific I need to do then?
I'd rather not be prohibited internally on the LAN.
-
The default rule which allows all outbound traffic from the LAN subnet will also let you ping, resolve DNS, etc, against the router's IP.
If you altered that rule, restricted local traffic in any way, you may have cut that access off.
Access to your local LAN is not restricted by the firewall, but access to the firewall's IP and beyond may be.
