Re: SuseFirewall2 open one TCP port for (both in and out datatransfer)

From: mtcobra (mtcobra_at_gmx.de)
Date: 09/30/03 

Date: 30 Sep 2003 03:48:09 -0700

As far as I know, a forwarded port doesn't appear as "open port"...
I have several ports forwarded to other servers in my homenetwork the
way you did it.
Everything works fine, though they aren't listet as "open ports" if
you portscan my firewall-server.

Markus

"Martin" <contact@knives.at> wrote in message news:<3f70809b$0$52018$91cee783@newsreader02.highway.telekom.at>...
> Hi!
>
> I use Suse 8.2 and the SuseFirewall2.
>
> I made the standard installation through yast2 and internet, e-mail, ftp
> work perfect
>
> Now I want to open the tcp port 15595 (for in and out data transfer)
>
> I changed now the following lines:
> -
> FW_SERVICES_EXT_TCP="15595"
>
> FW_FORWARD_MASQ="0/0,192.168.0.15,tcp,15595"
> -
> and made a restart (these two changes I founded at google)
>
> 192.168.0.15 is the Internal IP Address from the PC which need a open 15595
> port.
>
> But the firewall port is closed.
>
> I tried the port at http://grc.com and this port is closed.
> -
> Results from probe of port: 15595
>
> 0 Ports Open
> 1 Ports Closed
> 0 Ports Stealth
> ---------------------
> 1 Ports Tested
>
> THE PORT tested was found to be: CLOSED.
>
> TruStealth: FAILED - NOT all tested ports were STEALTH,
> - NO unsolicited packets were received,
> - A PING REPLY (ICMP Echo) WAS RECEIVED.
>
> Anybody know what I forgot?
>
> Thank you for any help!
>
> Best regards
>
> Martin