Default Deny Rule - Where is it ?
-
You need to pass the traffic from OPT1 that you want to let into pfSense to be sent on its way. Look at the rules on LAN.
That OPT is a WAN. https://forum.pfsense.org/index.php?topic=94566.msg525367#msg525367
Plus, 17500/UDP has nothing to do with "cannot ping".
@OP: Dude, stop multiposting and wasting other people's time. Also, upgrade your pfSense to something supported.
-
probably easier if you just said you hadn't got the first clue how to fix it instead of that waffle.
-
Dude. You highlight OPT1 blocks then post LAN rules.
Post your OPT1 rules and, please, read and understand this completely:
https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting
-
Dude. You highlight OPT1 blocks then post LAN rules.
Why don't you just answer the questions on the other thread? And which part of "your unknown ~6 years old pfSense version is NOT supported and not something people are working with, nor anything they base their advise on" is exactly hard to get?
-
probably easier if you just said you hadn't got the first clue how to fix it instead of that waffle.
That might be the douchiest post I've seen this year. The clue bat is directed at you, bro.
-
Also, he's got hell of a mess there, including some prehistoric pfSense version and some complete nonsense set up including the ISP DNS servers on WAN being the OPT1 gateway (probably related to some overlapping multi-NAT.)
-
Also, he's got hell of a mess there, including some prehistoric pfSense version and some complete nonsense set up including the ISP DNS servers on WAN being the OPT1 gateway (probably related to some overlapping multi-NAT.)
can't upgrade its hardware specific.
ISP DNS are NOT the OPT1 gateway. and DNS isnt a problem as OPT1 resolves without issue.
There is no NAT issue.
I have NO OPT1 rules same as I have no WAN rules and WAN works fine.
So BACK to the original problem, can't ping hosts over OPT1.
-
-
Dude. You highlight OPT1 blocks then post LAN rules.
Post your OPT1 rules and, please, read and understand this completely:
https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting
you asked for LAN rules.
-
I said look at the rules on LAN to get you to see what you need to do on OPT1.
And, please, read and understand this completely: https://doc.pfsense.org/index.php/Firewall_Rule_Troubleshooting
-
you asked for LAN rules.
No, he told you to "Look at the rules on LAN" so that you get a clue on what should be set up there. (Of course, without knowing you are wasting everyone's time here with multiposts and not telling anyone that OPT1 is not a LAN interface at all.)
-
Thanks for pointing that out, had overwrite from ISP ticked corrected now.
Made ZERO difference to OPT1.
Maybe just a bug as its an old release, doesn't seem i'm trying to push the limits though just wanting a WAN connection to actually work.
-
you asked for LAN rules.
No, he told you to "Look at the rules on LAN" so that you get a clue on what should be set up there. (Of course, without knowing you are wasting everyone's time here with multiposts and not telling anyone that OPT1 is not a LAN interface at all.)
Why so confrontational I clearly stated in FIRST post of this thread I had 2 WAN's ?
-
OP: What version of pfSense are you running?
-
Thanks for pointing that out, had overwrite from ISP ticked corrected now.
Made ZERO difference to OPT1.Look, ISP DNS servers is something you get via DHCP - on supported pfSense versions, that is. Not something you manually type somewhere. I hope you finally can see the problem with your prehistoric shit. If you are unable to upgrade, you should switch to something else than pfSense or upgrade your HW. Because, the stuff you are using is actually very insecure (and buggy, and people are just not using it, so asking for advise is generally futile.)
-
actually its not
version in 1.2.3-RELEASE
-
version in 1.2.3-RELEASE
dude. piss off.
-
https://doc.pfsense.org/index.php/Versions_of_pfSense_and_FreeBSD
Dude that version came out in 2009.. Update to current and people more than willing to help you setup a dual wan that is a very common, click click setup.
