Re: no remote access to smoothwall ?

"Adam Pavelec" <apavelec-be0aN53zdcR+u43qRgrggVaTQe2KTcn/@public.gmane.org> Tue, 28 Sep 2004 08:53:14 -0400
Newsgroups gmane.comp.security.firewalls.smoothwall.general
Message-ID <003201c4a55a$21fd3ae0$2027a8c0@PAVELECA>
On Tuesday, September 28, 2004 7:16 AM [GMT-5=EST], you wrote:

> I don't think this is the normal sort of remote access issue, I have
> set up the ports in the external access table (ports 441 and 222) and
> set the services/remote access to ssh and not mset ath allow access
> from valid referrals.
>
> I have also tried port forwarding to an internal PC for Port 80.
>
> I can set up a VPN, and am getting access to the smoothwall this way,
> however any other connection to the smoothwall via its public IP
> address results in a timeout. The port forwarding also fails, (I have
> an number of working smoothwalls with the same configuration... they
> all work)
>
> I have spoken to the ISP providing the connection who say that they
> are not blocking access to the smoothie.
>
> A port scan shows no open ports
>
> I can ping the smoothie.

From what I can see, everything you have done should allow SSH/HTTPS remote 
management to work (*as long as your ISP is truthful about not blocking 
access to the well-known ports).  Here are a few additional things I would 
check:

1) Make sure Services>Remote Access>SSH is enabled.

2) Do a netstat -a from the shell.  You should see at least the following 
entries:

[root@smoothwall root]# netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 smoothwall:800          *:*                     LISTEN
tcp        0      0 *:81                    *:*                     LISTEN
tcp        0      0 *:441                   *:*                     LISTEN
tcp        0      0 *:222                   *:*                     LISTEN

If for some reason ports 441 or 222 are not in the listening state, they 
probably are not running.  The simplest thing would be to level your 
SmoothWall and reinstall, for it would probably take more time to figure out 
why this is occurring than to start fresh.  If they /are/ listed, your ISP 
has probably been untruthful.  I can do a quick scan from a few different 
external perspectives -- send me a message off list if you're interested.

-Adam 
_______________________________________________
gpl mailing list
[email protected]
http://lists.smoothwall.org/mailman/listinfo/gpl

SmoothWall Stash - Buy Our Stuff! http://cafepress.com/smoothwall