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

HTTP through Packet Filters..

This would seem pretty straightforward, however, all attempts at making this work has failed. Even in the Live Log, it shows the packets being accepted, yet the page fails to load. To avoid excessive filters for DNS, I am simply trying to browse to a webserver via IP.

Packet filter: Any --> External network, anyservice, logallow.

No joy. Ive tried adding a second filter reversing the path in case these filters arent stateful. Still No joy.

External network is defined as our Class C Ipaddress block with a webserver assigned a routeable IP from the block.

Please tell me Im missing something simple.

Regards,
Jones

This thread was automatically locked due to age.

Parents

0 Overnet over 21 years ago

If you have a http server behind ASL you must also have a dnat for webserver.

Lokk in here for set up a dnat for you webserver dnat

Hope it helps you [:)]
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Overnet over 21 years ago

If you have a http server behind ASL you must also have a dnat for webserver.

Lokk in here for set up a dnat for you webserver dnat

Hope it helps you [:)]
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Dr_Jones over 21 years ago in reply to Overnet

Thanks for the response. The webserver Im using isnt behind ASL. Packet filters arent working for anykind of HTTP browsing whatsoever. I was just using our own webserver so I could browse via IP instead of messing with DNS filters, thus further complicating the problem.
Cancel
Vote Up 0 Vote Down

Cancel