Cannot ping opt1 interface or router connected to opt1 (wan2) interface from lan
-
I've done a state reset but cannot ping. I'll attach other pics, in case something is wrong with the config.
-
This happens when i tracert from lan: opt1(wan2) - wan - opt2(DMZ)
It seems that when i ping the opt1(wan2) pfsense int from lan, it tries to reach it going out to internet instead to just replying from the firewall itself!
Strange!
-
This is my loadbalancer config:
-
::)…. any suggestions?? Or do i better reset to defaults: rules, nat and loadbalancer and see if i resolve and start over the config step by step?
Thanks.
-
Disable the manual advanced outbound nat and set it to automatic again. Retest. Does it work now?
-
tried… :-\ but no ping.... is aon worse than using automatic?
If tracerouting opt1 pfsense int from lan, give me back wan gateway as this:
C:>tracert -d 10.0.0.9
Rilevazione instradamento verso 10.0.0.9 su un massimo di 30 punti di passaggio
1 <1 ms <1 ms <1 ms 85.35.156.x -----> this is default gateway on pfsense wan int
2 85.35.141.x rapporti: Rete di destinazione non raggiungibile. (Network unreachable)
|
|--> This is next op routerRilevazione completata.
does it mean that it is trying to find a reply from opt1 going out to internet, instead of just replying from its internal int?
.... ???
-
It means that for some reason it skips your first new created firewallrule. Don't know why though. Maybe reboot.
-
already rebooted….what other factor can lead to such a problem? only loadbalancing or i've to check also other configurations such trafficshaping (but i don't think so) anyway just to be sure!
do you think that if i remove loadbalancing and failover conf i'll solve the issue? Thanks.
-
Only firewallrules and outbound nat can cause problems here. You don't have any static routes configured, right?
-
no static routes. do you need more info on my conf? i can provide you with all the settings? I have the same problem on another pfsense 1.2 box also with dual wan. Everything works fine, but i cannot ping opt1 int from lan nor router attached to that interface. What can be the problem :-\
-
Try to rebuild the config step by step and see where it breaks. I guess that'S the easiest way to find the issue atm.
-
ok thanks a lot, I'll post the result if i succeed!
-
Yes, I'm interested to see where the problem is as well :)
-
You could try with my setup.
-
you mean the localnet entry?
-
No. What ip address i you trying from?
-
i'm trying to ping from internal server 192.168.100.10/24 to pfsense op1 (wan2) interface 10.0.0.10 or router behind it 10.0.0.9 but do not ping. Those rules you mention, was there to let both internal server not being restricted by the last rule "blockall". Do you mean that those rules are blocking pings?
-
Yes if you first 192.168.100.10 rules has the gateway * or 10.0.0.9 it should work imo.
-
!!SOLVED!! Perry found the problem! ;) The rules under LAN that i put to let 192.168.100.10 go out without being filtered by the last rule, had the gateway not to default one but specified to use opt1 default gateway, so when pinging from lan from that ip, it didn't look at the defaut routing tables causing the problem! Thanks a lot Perry. I suppose that the other rule to let the same internal host go out via opt1 using opt1 default gw is ok. Because i so not want to filter that host when going out from opt1.
-
;)
Rules:
Rules are processed from top to down.
If a rule catches the rest of the rules is no longer considered.
Per default a "block all" rule is always in place (invisible below your own rules).Traffic is filtered on the Interface on which traffic comes in.
So traffic comming in on the LAN-Interface will only be processed from the rules you define on the LAN tab.If you have a private subnet on your WAN: uncheck the "Block private networks" checkbox on your WAN-config page.
http://forum.pfsense.org/index.php/topic,7001.0.html