Captive portal manual logout page address
-
$timeout = 0; if (!empty($config['captiveportal'][$cpzone]['timeout']) && is_numeric($config['captiveportal'][$cpzone]['timeout'])) { $timeout = time() + $config['captiveportal'][$cpzone]['timeout'] * 60; setcookie("cookie_portal", $sessionid, $timeout); } else setcookie("cookie_portal", $sessionid, $timeout);Dont know if this works…i only have
setcookie("cookie_portal", $sessionid)"log out page" some times appears and some time not
It should give you a logout page when u revisit 192.168.100.1:8002 and when u have a cookie.
So no cookie = no logout.
But I can recall "log out page" by entering address "192.168.100.1:8002" in url anytime and it also gets disconnected if hit logout button so its working.
This is the opposit of what you stated above….
Only 1 problem is left "log out page" gets redirected after entering user name and password so it does not appear always as it should.
So your logout page shows up right after u logged in?
-
"log out page" some times appears and some time not
By this I want to say that after log in via CP, log out page does not appear as it should, rather I am redirected to intended site. Like if I start to use internet and want to browse google, CP page comes in, I log in , now log out page should appear but it does not, I am redirected to google site and when I need to log out I has to recall log out page. but sometimes I dont get redirected to intended site instead log out page remains.
cookies are enabled in my browser by default. but log out page should come if cookies are disabled too. is int it?Thanks & Regards
amitaussie -
By this I want to say that after log in via CP, log out page does not appear as it should, rather I am redirected to intended site.
This is ok and normal.
That's why I tell about it on my login page -
Btw: as said before, the original patches were valid for 2.1.5.
To make them work on 2.2 you just can't copy entire functions drom (my) pastbin.org - you should have putting in the replacements. The is because other stuff changed also, remember 2.1.5 is not 2.2 - many lines have changed.
By putting in 2.1.5 functions, you downgraded your 2.2 - and that can give strange results, or worse.
I should have post diff files on pastebin - or files for each version.….
cookies are enabled in my browser by default. but log out page should come if cookies are disabled too. is int it?Not possible.
No cookie = logout page can't pop up.
Just check the code yourself : the cookie has to be found.
The cookie contains your sessionid
The sessionsid is looked up in the users database.
If its found, a logout page is produced and you can see it.Btw: IF your are logged in - and you accept cookies, the visiting this page 192.168.100.1:8002 (on your pfSEnse box) will produce the logout page.
This:
$timeout = 0; if (!empty($config['captiveportal'][$cpzone]['timeout']) && is_numeric($config['captiveportal'][$cpzone]['timeout'])) { $timeout = time() + $config['captiveportal'][$cpzone]['timeout'] * 60; setcookie("cookie_portal", $sessionid, $timeout); } else setcookie("cookie_portal", $sessionid, $timeout);is the nearly same thing as this:
setcookie("cookie_portal", $sessionid, 0);The difference is that I test first if a hard timeout is set on the portal interface (in minutes).
If it exists, its used to set the max live of the cookie, because, the user will be disconnected after that time. No need to keep the cookie alive after that. It will die by itself.
If the hard timeout isn't set, then a normalsetcookie("cookie_portal", $sessionid, 0);will be used, which is the same as:
setcookie("cookie_portal", $sessionid);Anyway, since I discovered that CNA is bugging all this severely, I'm still trying to mix up "IP/MAC and cookie" logout …. works is still in progress.
-
Hi Gertjan!
Thanks for the explanation.
It would be better if it can work on 2.2 too.
Thanks & Regards!
amitaussie
-
It does work on 2.2. Just do the same thing. But dont copy the whole files…just insert the needed parts.
If you want to be redirected to the logout page right after you logged in you can simply enter the redirected url in the GUI.
I use this to be redirected to the coporate website.
-
Hi!
Yes, it is working in 2.2!
But I found a problem I dont know if I am right?
I am browsing internet after log in via CP login page, I want to log out, I recall log out page 192.168.100.1:8002, it comes, but if I close the browser without logging out and later on when I try to log out by recalling log out page, I am redirected to CP Login page and after entering credentials then only I am redirected to log out page.
Problem is if I am already logged in and I want to log out by recalling 192.168.100.1:8002, then log out page should come, not CP log in page. isnt it?
-
I am browsing internet after log in via CP login page, I want to log out, I recall log out page 192.168.100.1:8002, it comes, but if I close the browser without logging out and later on when I try to log out by recalling log out page, I am redirected to CP Login page and after entering credentials then only I am redirected to log out page.
This is by design ;)
I already talked about setcookie() and how the browser handles cookies.
Read again: http://php.net/manual/en/function.setcookie.php
And this time, see what the THIRD parameter does: expire.Remember :
setcookie("cookie_portal", $sessionid);is the same thing as
setcookie("cookie_portal", $sessionid, 0);What you described in your question:
The time the cookie expires. This is a Unix timestamp so is in number of seconds since the epoch. In other words, you'll most likely set this with the time() function plus the number of seconds before you want it to expire. Or you might use mktime(). time()+606024*30 will set the cookie to expire in 30 days. If set to 0, or omitted, the cookie will expire at the end of the session (when the browser closes).
So => closing browser == cookie destroyed == no more log out page.
This means you have to walk through the login again to get a cookie to be able to logout.
Exactly as you found out.A solution might:
setcookie("cookie_portal", $sessionid, time()+strtotime("+1 day"));This cookie will be persistent for one day.
-
Hi Gertjan!
This solution is perfect now, I hope! working great in 2.2!
setcookie("cookie_portal", $sessionid, time()+strtotime("+1 day"));
For one day it is ok.
Testing it further to see if there's anything to improve (hopefully nothing :))Thanks & Regards
-
….
Testing it further to see if there's anything to improve (hopefully nothing :))Ok, good.
I conclude that you do not use any smartphones like Androids en iDevices (iPhone, iPads) on your portal network ?
Because they use CNA 'navigator' which will discard the cookie on login …..
This means that, as you said already, people have to re-login with their 'real' browser to get a cookie - to be able to log out .... -
Hi!
Well…
People do use smartphones to browse internet in my network. So you mean to say they won't be able to access log out page...oh! ok. If it can be solved then its great! Otherwise not a big issue as everyone uses his own smartphone etc. and if they are not served a log out page.
Thanks & Regards!
-
So you mean to say they won't be able to access log out page…oh! ok. If it can be solved then its great! Otherwise not a big issue as everyone uses his own smartphone etc. and if they are not served a log out page.
No, no, no… you misunderstood that issue. They will be logged out as soon as they've logged in via the crippled CNA "browser". They need to use their real browser to log in if they want to continue browsing.
-
Hi!
oh ! Is this CNA browser feature offered by Apple IOS only ? As I have checked with my Samsung mobile, i am offered my CP login page and after log in, I am able to browse and recall log out page. Its working in Samsung mobile.
Do i have to install any other browser in Apple devices to bypass this CNA feature, like chrome etc.?
Thanks & Regards!
amitaussie
-
Do i have to install any other browser in Apple devices to bypass this CNA feature, like chrome etc.?
Will not help. The only way to avoid this junk is to avoid CP detection altogether.
-
No, no, no… you misunderstood that issue. They will be logged out as soon as they've logged in via the crippled CNA "browser". They need to use their real browser to log in if they want to continue browsing.
When i login via CNA everything works fine. I just use the less secure IP/MAC solution.
-
I just use the less secure IP/MAC solution.
Yeah, so what exactly does this have to do with the manual logout page?
-
No, no, no… you misunderstood that issue. They will be logged out as soon as they've logged in via the crippled CNA "browser". They need to use their real browser to log in if they want to continue browsing.
They won't be logout…they r just not getting the cookie (or am I missing something). So I use the IP/MACso users can use CNA or browser.
-
This entire thread has been discussing how to log out people by using a cookie. So yeah, you can use CNA just fine if you not using logout, just don't get why are you discussing this on a CP manual logout thread…
-
This entire thread has been discussing how to log out people by using a cookie. So yeah, you can use CNA just fine if you not using logout, just don't get why are you discussing this on a CP manual logout thread…
No its not. It been discussed using IP/MAC too at the first page..and this does work with CNA. Im just stating this since the cookie solution is troublesome for phones/tablets.
-
doktornotor, you joined in with the "cookie issue with CNA" which, by the way, destroyed half the fun, not because it was true but because I thought it was working good, or all prove was there that it wasn't ;) CNA f*cked that up.
It was lsense, who told use that he uses cookies https://forum.pfsense.org/index.php?topic=77143.msg421812#msg421812
I wasn't doing so, before. I used a lookup with IP and MAC which I found secure enough because my portal uses https. (But, for some reason, it seems to me that most of us don't)Anyway, who cares :D
Maybe I should write-up a cookie+(MAC/IP) …. but what I realy need it the answer to his first:
https://forum.pfsense.org/index.php?topic=77143.msg478165#msg478165
Last "Btw":
@lsense:modify capture of 1.1.1.1 in ipfw : it gets always redirected, even if authenticated
"Could you detail this please ? What is de ipfw rule ? Injected where ?"
(Ok, I know where, but what ipfw rule ? I'm an iptables man)I'd like to know how to make a short simple easy-to-remember logout URL, like "logme.out" or even "logout" that get redirected to the captive portal web server.
Any ideas ?Byw: It's easy to circumvent the CNA login culprit.
Just connect to the Wifi network.
The CNA pops up.
Shut it down ! (iDevice: hit de home button).
Open the real browser, like Safari or whatever you have on your iDevice.
Login.
The cookie will be there.
Tested and works every time on an iDevice. -
I use a NAT rule: IP of CP port 80 redirect to 8002.
And a DNS record: logout.me with ip of the CP.
I bet Isense redirect 1.1.1.1 to CP IP:800x
