Hi Sven,

> I had some problems with the ssl, but now it works fine. I made the
> certificate as described in thr README file and placed the ntop-cert.pem in
> the /usr/local/etc/ntop folder. I didn't have the folder so I created it.

That's what I did, too.

> The ssl still won't start with the service daemon but if I start ntop
> manually it work. But I use -w 80 -W 443 parameters...
> 
> Maybe you should try to run ntop as these (default) ports?!?

No, I found out that it runs with other ports, too, but only when I
enable access for all (nothing in /etc/hosts.deny). I've got
tcpwrapper-support enabled, as you see. When I say "ntop:ALL" in
hosts.allow or even "ALL:<my local subnet>" in hosts.allow, then ntop
doesn't work with SSL. 
The error message from Netscape is "A network error occured while
Netscape was receiving data. (Network Error: Connection reset by peer)
Try connecting again."

Only when I say "ALL:ALL" in hosts.allow or when I delete the entries in
hosts.deny, then ntop works with SSL. Without SSL, the tcpwrapper works
fine.

I use the snapshot ntop-01-11-20 which should be actual.

CU,

Michael
-- 
Michael Weidel, University of Ulm, Computing Center
EMAIL:         [EMAIL PROTECTED]
WWW (PGP-KEY): http://www.weidel.org/
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listmanager.unipi.it/mailman/listinfo/ntop

Reply via email to