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 question - I am stumped

OK, so I have ASL configured with 2 NICS, and everything on the private side can get out. I have rules allowing outbound traffic from 192.168.2.0 network to the internet (DHCP address from ATT). AT&T has blocked http inbound on port 80. I have a Axis camera at 192.168.2.16, port 81 to serve live video. I want to allow inbound on port 81 to this address, but cannot get ASL to allow inbound traffic on 81. I have defined the network, service, and rules to allow it, yet I see in the syslog port 81 being dropped. Any examples would help...

This thread was automatically locked due to age.

0 YuppieScum over 23 years ago

Two things:

1. All the rules are processed in order, so if "reject all" is before "allow port 81", it'll fail.
2. If the packet filter is active, you'll need a rule for this too!
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_C over 23 years ago in reply to YuppieScum

The rule is #1, This is what is so puzzleing. I have everything in place as it should be, and yet it doesn't work.
Cancel
Vote Up 0 Vote Down

Cancel
0 Heinz Wittenbecher over 23 years ago in reply to Mike_C

I had to add a service for port 5051 and tried S-Port/Client 5051 and D-Port/Server 5051. That didn't work.

Changed S-Port/Client to 1024:65535 and it works.

Unfortunately I'm not sure what it does and if I did it right as I assumed if I only need 5051 it would go in both columns but when it didn't work I followed Telent service as an example and it works.

HTH - Heinz
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_C over 23 years ago in reply to Heinz Wittenbecher

Thanks, followed the FAQ on FTP, and your suggestion, and now it works. Beats me, I did all this last night. Must have missed something.
Cancel
Vote Up 0 Vote Down

Cancel