I downloaded and applied the full update 1.0-BETA1-TESTING-SNAPSHOT-2-2-06 I turned on HTTPS on the portal and I get no login screen. This time around TCP 8000 is closed below is the scan. It still works perfectly with http for the portal login and then TCP 8000 is open for the logout button.
Starting nmap 3.81 ( http://www.insecure.org/nmap ) at 2006-02-02 21:25 Centra Standard Time Interesting ports on pfgate01.rkkz.msft (90.x.x.x): (The 1661 ports scanned but not shown below are in state: filtered) PORT STATE SERVICE 53/tcp open domain 443/tcp open https MAC Address: 00:10:B5:F9:AE:CF (Accton Technology) Nmap finished: 1 IP address (1 host up) scanned in 22.341 seconds -----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Thursday, February 02, 2006 5:07 PM To: support@pfsense.com Subject: Re: [pfSense Support] RE: *SPAM*[pfSense Support] HTTPS Captive Portal Fixed as of today. This came back after syncing with m0n0wall 1.21. On 2/2/06, Ronald Henriksen <[EMAIL PROTECTED]> wrote: > I installed the full update still no go if I turn on HTTPS for the portal > login I get "The page cannot be displayed". Also TCP 8001 is not open to > except the HTTPS connection. Is there a daemon not starting? > > Starting nmap 3.81 ( http://www.insecure.org/nmap ) at 2006-02-02 06:35 > Central > Standard Time > Interesting ports on pfgate01.rkkz.msft (90.X.X.X): > (The 1660 ports scanned but not shown below are in state: filtered) > PORT STATE SERVICE > 53/tcp open domain > 443/tcp open https > 8000/tcp open http-alt > MAC Address: 00:10:B5:F9:AE:CF (Accton Technology) > > Nmap finished: 1 IP address (1 host up) scanned in 22.100 seconds > > > -----Original Message----- > From: Holger Bauer [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 01, 2006 1:11 AM > To: support@pfsense.com > Subject: AW: [pfSense Support] RE: *SPAM*[pfSense Support] HTTPS Captive > Portal > > Please try the latest snapshot: > http://pfsense.com/~sullrich/1.0-BETA1-TESTING-SNAPSHOT-1-29-06/ > beta1 already is more than 1 month behind developement. > > Holger > > > -----Ursprüngliche Nachricht----- > > Von: Ronald Henriksen [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 1. Februar 2006 05:43 > > An: support@pfsense.com > > Betreff: RE: [pfSense Support] RE: *SPAM*[pfSense Support] > > HTTPS Captive > > Portal > > > > > > I am running beta 1 using radius authenticaton when I > > activate https for the > > portal and I get "The page cannot be displayed" it works > > perfectly when it > > not https for the login. Also it redirects to port TCP 8001 > > it's never open > > to allow a connection to it. I ran an nmap scan on the inside > > interface > > which has the portal on it. > > > > Starting nmap 3.81 ( http://www.insecure.org/nmap ) at > > 2006-01-31 22:29 > > Central > > Standard Time > > Interesting ports on pfgate01.rkkz.msft (90.X.X.X): > > (The 1660 ports scanned but not shown below are in state: filtered) > > PORT STATE SERVICE > > 53/tcp open domain > > 443/tcp open https > > 8000/tcp open http-alt > > MAC Address: 00:10:B5:F9:AE:CF (Accton Technology) > > > > Nmap finished: 1 IP address (1 host up) scanned in 22.280 seconds > > > > > > > > > > -----Original Message----- > > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, January 31, 2006 10:13 AM > > To: support@pfsense.com > > Subject: Re: [pfSense Support] RE: *SPAM*[pfSense Support] > > HTTPS Captive > > Portal > > > > That's not true. I fixed the problems myself. > > > > if(isset($config['captiveportal']['httpslogin'])) { > > $cert = > > base64_decode($config['captiveportal']['certificate']); > > $key = > > base64_decode($config['captiveportal']['private-key']); > > } > > > > So please test it out and let me know. > > > > On 1/31/06, Ronald Henriksen <[EMAIL PROTECTED]> wrote: > > > It's been broken since release 94.10 I had a support ticket > > 725 for the > > > issue but nothing seemed to happen to fix the problem. > > > > > > -----Original Message----- > > > From: HOFMAN Stéphane [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, January 31, 2006 2:52 AM > > > To: support@pfsense.com > > > Subject: *SPAM*[pfSense Support] HTTPS Captive Portal > > > > > > Hi, > > > > > > Can someone explain how to configure an HTTPS Captive > > Portal with PFSENSE > > ? > > > My captive portal is OK with HTTP (and RADIUS > > authentification), but I > > don't > > > understand with HTTPS. > > > > > > Thanks a lot > > > > > > Stephane HOFMAN > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > ____________ > Virus checked by G DATA AntiVirusKit > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
