From owner-freebsd-questions Thu Dec 21 4:14:25 2000 From owner-freebsd-questions@FreeBSD.ORG Thu Dec 21 04:14:24 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from bryden.apana.org.au (bryden.apana.org.au [203.3.126.129]) by hub.freebsd.org (Postfix) with ESMTP id 3FA3337B400 for ; Thu, 21 Dec 2000 04:14:21 -0800 (PST) Received: from dougy (dougy.apana.org.au [203.3.126.131]) by bryden.apana.org.au (8.9.3/8.9.3) with ESMTP id WAA12317 for ; Thu, 21 Dec 2000 22:20:32 +1000 (EST) (envelope-from dougy@bryden.apana.org.au) Date: Thu, 21 Dec 2000 22:23:33 +1000 (E. Australia Standard Time) From: Doug Young To: Subject: SSL timeout / error 408 Message-ID: X-X-Sender: dougy@[203.3.126.129] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've compiled & installed the current snapshot version of ntop & have a few "features" to sort out. I'm getting ntop started OK in either / or / both regular webmode / SSL mode When I point a browser at the correct URL" http://:3000", everything appears to work fine When I point the browser at the correct SSL address "https://:3001" I get "Error 408 The request was timed-out" I don't believe the problem is with Open SSL since Webmin works perfectly on the same machine at "https://:10000" A different ntop issue on which I'd appreciate advice is that of configuring password access control. The earlier versions of ntop used a ".ntop" file in home directories to limit access, however that idea was apparently dropped later & replaced by something different ... (presumably in the interests of security) but that has not been documented. Is there a practical way to implement some form of password access control or user IP address access control to either http://:3000 or https://:3001 ?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message