This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why doesn't the ANY-ANY-ALLOW-ANY Rule work?!

Yesterday, I tried to open up everything to troubleshoot an ongoing connection issue. I created an ANY-ANY-ALLOW-ANY rule to let everything in on a network with only a single PC having no security requirements.

Despite the ANY-ANY-ALLOW-ANY rule, Packet Filter showed all kinds of stuff still getting dropped. Why did that happen if had the above rule activated and working?

This thread was automatically locked due to age.

Parents

0 BarryG over 20 years ago

Real IPs on INT?

If not,
Got DNAT?
Cancel
Vote Up 0 Vote Down

Cancel
0 digital_1 over 20 years ago in reply to BarryG

Yes, real IPs on the Internet were dropped. IPS was inactive and no DNATing. What else would cause those packets to be dropped?

I can post a sample of the packet filter log if anyone is interested in seeing that.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 digital_1 over 20 years ago in reply to BarryG

Yes, real IPs on the Internet were dropped. IPS was inactive and no DNATing. What else would cause those packets to be dropped?

I can post a sample of the packet filter log if anyone is interested in seeing that.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 BarryG over 20 years ago in reply to digital_1

Sorry, INT is Internal network, not Internet.

My point was, if you're not using real IPs internally, you need Masq and DNAT setup.

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 Simon Shaw over 20 years ago in reply to BarryG

The any-any-any rule is a bit deceptive. It will still block packets to the firewall interfaces.

So try adding Any Any RED (Where RED=external nic)
Cancel
Vote Up 0 Vote Down

Cancel