Thanks for the reply. Bering 1.2 does not have the "netstat -ln"
command. Has this been replaced with another command in Bering? The inetd
service is running when I do a 'ps' command. I have gone back through all
the Shorewall config files, the hosts.allow and hosts.deny files and also
the weblet config files and everything seems to be in order. So I am a bit
baffled at what is different. I even set shorewall in allow in and out
everything via the policies and it still did not work. It seems that the
system is not denying the packets, it seems that the service is not there on
that port ??? Something strange that I have noticed is that when I go to a
windows machine and try and call up the firewall web page I see network
activity out to the internet? Whether this is just IE doing a search I do
not know.
What I am going to try is to build another system from scratch and
see if it works. From monitoring the list there seems that no one else is
having any problems. So it must be something different that I am doing. I
will let you know if I have any success.
Regards,
Robert.
-----Original Message-----
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]
Sent: Saturday, 24 May 2003 6:15 AM
To: Robert McRostie
Cc: [EMAIL PROTECTED]
Subject: Re: [leaf-user] Problem with Weblet...
Robert McRostie wrote:
> Now the questions.
>
> 1. How do I know that the web service is running? (It does load the .lrp
> file and also sets up the directory etc)
Run "netstat -ln", and look for something listening on port 80.
The web-server used by weblet is sh-httpd, and is started by inetd (the
"super-server daemon". You can look for inetd in your process list
"ps ax", and verify the contents of your /etc/inetd.conf file.
> 2. Is there a way of manually starting it?
Start or re-start inetd, although this should happen automatically at boot.
> 3. Is there any thing else that I should be checking for or can do? Eg the
> little gotcha's that people can fall into.
If you changed IP's, there are at least 3 layers of security you need to
verify are configured correctly:
- Shorewall
- tcpd (/etc/hosts.allow and /etc/hosts.deny)
- weblet itself, which can be configured to deny access to all but
specific IP ranges (weblet and/or sh-httpd config file(s) in /etc, whose
name escapes me at the moment)
--
Charles Steinkuehler
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
