On Wednesday 11 January 2006 12:17, Tom Eastep wrote:
> On Wednesday 11 January 2006 12:11, Jim Ford wrote:
> > On Wednesday 11 January 2006 10:45, Robert K Coffman Jr - Info From Data
> >
> > wrote:
> > > It appears that you are misunderstanding what those commands do. See
> > > http://www.s
On Wednesday 11 January 2006 12:11, Jim Ford wrote:
> On Wednesday 11 January 2006 10:45, Robert K Coffman Jr - Info From Data
>
> wrote:
> > It appears that you are misunderstanding what those commands do. See
> > http://www.shorewall.net/starting_and_stopping_shorewall.htm#id2507868
> > fo
On Wednesday 11 January 2006 10:45, Robert K Coffman Jr - Info From Data
wrote:
> It appears that you are misunderstanding what those commands do. See
> http://www.shorewall.net/starting_and_stopping_shorewall.htm#id2507868 for
> more detail.
And for port knocking with Shorewall 2.x, yo
On Wednesday 11 January 2006 10:45, Robert K Coffman Jr - Info From Data
wrote:
> It appears that you are misunderstanding what those commands do. See
> http://www.shorewall.net/starting_and_stopping_shorewall.htm#id2507868 for
> more detail.
And for port knocking with Shorewall 2.x, you should
11, 2006 1:27 PM
To: leaf-user
Subject: [leaf-user] Port Knocking Shorewall command?
With the view of including Shorewall commands to open and close the ssh port
25 when accessed from the internal network, I tried the following line from
a command prompt:
shorewall allow 192.168.11.0/24:25
With the view of including Shorewall commands to open and close the ssh port 25
when accessed from the internal network, I tried the following line from a
command prompt:
shorewall allow 192.168.11.0/24:25
Which evoked the response from shorewall: Not dropping or rejecting from
192.168.11.0/24
