Am Montag, 2. Juni 2003 10:37 schrieb Adam Niedzwiedzki:
I also ran an nmap scan on my firewall IP.
Port State Service
22/tcp openssh
113/tcpclosed auth
135/tcpclosed loc-srv
I'm have no idea why 113 and 135 are showing as open. These are my
On Mon, 2 Jun 2003 18:48:04 +0200, K.-P. Kirchdörfer [EMAIL PROTECTED]
wrote:
Am Montag, 2. Juni 2003 10:37 schrieb Adam Niedzwiedzki:
I also ran an nmap scan on my firewall IP.
Port State Service
22/tcp openssh
113/tcpclosed auth
135/tcpclosed loc-srv
On Mon, 2 Jun 2003 18:37:10 +1000, Adam Niedzwiedzki [EMAIL PROTECTED]
wrote:
I have a couple of question about shorewall and stuff I'm running
version 1.3 from on the base install of bering.
I was reading the shorewall help and have a question about this line.
You know, there is an entire web
On Tue, 3 Jun 2003 08:24:41 +1000, Adam Niedzwiedzki [EMAIL PROTECTED]
wrote:
But I was asking on how to restrict SSH to only answer on one of my LIVE
ips and for shorewall to ONLY allow ssh connections on that LIVE ip.
Due to me only being on a dynamic IP (my DSL provider is a real PIG they
On Tue, 3 Jun 2003 09:52:47 +1000, Adam Niedzwiedzki [EMAIL PROTECTED]
wrote:
On Tue, 3 Jun 2003 08:24:41 +1000, Adam Niedzwiedzki
[EMAIL PROTECTED]
wrote:
But I was asking on how to restrict SSH to only answer on one of my
LIVE ips and for shorewall to ONLY allow ssh connections on that LIVE
Hi all,
I'm running a bering firewall on my production system (after upgrading
from eigerstien).
And very impressed with Bering great job.
I managed a complete system upgrade from eigerstein, using wget, and all
done remote via ssh, LOT's of planning ahead, *fingers crossed on the
first reboot*,
