For testing purposes I changed the ssh rule to:
-A TCP -p tcp -m tcp --dport 22 -j ACCEPT
-A TCP -p tcp -m tcp -s 0.0.0.0/0 -d 192.168.2.5 --dport 22 -j DROP
And still no go. As mentioned before, everything works fine until I
try to close up the rest of the ports not opened up in the chains
UDP
On 21/05/2013 18:01, Nick Khamis wrote:
For testing purposes I changed the ssh rule to:
-A TCP -p tcp -m tcp --dport 22 -j ACCEPT
-A TCP -p tcp -m tcp -s 0.0.0.0/0 -d 192.168.2.5 --dport 22 -j DROP
And still no go. As mentioned before, everything works fine until I
try to close up the
Neal,
As for the --sport flag for OUTPUT, should it not be left arbitrary?
The SSH daemon should use unprivileged ports between 1024 and 65535.
The only daemon I know thus far that does not is NTP which is
hardwired to 123 both ways.
Thanks Guys,
Nick.
On Tue, May 21, 2013 at 12:53 PM, Nick Khamis sym...@gmail.com wrote:
Neal,
As for the --sport flag for OUTPUT, should it not be left arbitrary?
The SSH daemon should use unprivileged ports between 1024 and 65535.
The only daemon I know thus far that does not is NTP which is
hardwired to
Anyone advocating stateless firewalls in 2013 deserves scrutiny. I would be
asking for some evidence there is a performance issue, and that the best
solution to the problem is to turn off stateful inspection.
Adam Carter adamcarter3 at gmail.com writes:
Anyone advocating stateless firewalls in 2013 deserves scrutiny. I would
be asking for some evidence there is a performance issue, and that the
best solution to the problem is to turn off stateful inspection.
There are lots of tools and
6 matches
Mail list logo
