Pfsense, No internet when it is said "You are connected".
-
This :
@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
Unfortunately there's still no internet connection after I logged in
is your problem, right ?
This :
@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
disabled interfaces (WAN/LAN) tx offloading.
isn't portal related.
De-activate the portal : the interface gives an Internet access ?This is where everything goes down hill :
@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
defined DNS servers.....
Quick solution : don't. Out of the box, things work. Then people try hard to break their DNS. DNS, is, for the captive portal, must work as a clock.
So, no (not your defined) DNS, Just the Resolver as it was set out out of the box. Check for yourself that the portal works right away.
Now start breaking things, and then undo your last setting to get a stable situation.with corresponding gateways for my WAN & LAN
What ?
Screen capture please ?@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
disabled DNS Resolver
Why ??
(although, this might be part of a solution that could work)@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
enabled DNS Forwarder
Forwarder ? Ok, but why ? You sold your DNS requests to some company ?
(What, you give this information to them for free ?? )@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
enabled DNS override to disable localhost (127.0.0.1) as DNS server.
Coool !!! Now pfSense itself can't even check for updates, package info etc.
@bLitZerg said in Pfsense, No internet when it is said "You are connected".:
enabled captive portal.
Try this : take a pfSense setup with default settings - and make work WXAN (only WAN !).
Now, set up the captive portal as the video, there are 3 official vidoes => Youtube => Netgate.
Enjoy this for some time.Then, before continuing, explain us what you are trying to do with DNS , Why should it change ?
Btw : the most know issue, of course, is people mssng up their DNS :
Also : your question has nothing to do with this thread : subject : Pfsense, No internet when it is said "You are connected".
-
I can confirm this behavior.
In my current setup at an office we only use de Accept Terms login (no password or ticket involved), when an employee leaves the office at the end o f his work time, the next they they would come to find the "you are connected" message. The only bypass I could find is to set the client expiration time to 10 hours, enough so everybody would have to re-accept terms next day, and if after that the issue still happens I just go to the CP Status page and delete the client, then disconnect their wifi and reconnect.Ive got no clue why this is happening, the issue with this problem is that you cant create a totally unattended setup.
-
@jvelez88 said in Pfsense, No internet when it is said "You are connected".:
The only bypass I could find
There are two others ways to bypass the issue :
- The most easy one : stop saving the portal config. Do not change the configuration => the firewall doesn't get reset => all is well.
- Apply the patch.
-
I have similar issue, i'm using v. 2.4.4 p3. how effective this patch? what are the expected issue may occur? Thanks.
-
It is effective if that is actually the issue you're hitting.
Steve
-
@stephenw10 sorry don't know where to find the System \ Patches page.
-
@sox1600 said in Pfsense, No internet when it is said "You are connected".:
don't know where to find the System \ Patches page.
Really???
I take it you get bit by a lot of snakes, since you don't see them ;)
-
@johnpoz need to install it under the Package Manager :-) I got this error:
"Patch Fetch Failed" i used this URL: https://github.com/pfsense/pfsense/compare/master...Augustin-FL:patch-captivportal-reconfigure-no-configbump.diff -
I suggest you actually read the instructions again ;) Not sure where you got the idea that was the patch url??
-
@johnpoz i read the earlier post, but i tried the one: https://github.com/pfsense/pfsense/pull/4042.diff, successfully got the patch. Do I have to reboot or just restart the CP service?
-
@sox1600 please read the instructions again. the correct url to use is
https://github.com/pfsense/pfsense/compare/RELENG_2_4_4...Augustin-FL:fix-reconfig-for-2-4-4.diff
the instructions can be found here : https://forum.netgate.com/topic/137824/pfsense-no-internet-when-it-is-said-you-are-connected/13
-
@jurhein
hi, that is the issue, when a user connect to my wifi network and he/she left the place with their device (disconnect from wifi) and came back and connect again to wifi ( get same ip address) they see "you are connected" message in their browser but not really access the internet resource. -
@soheil-amiri yes.
-
This post is deleted! -
Still unsolved, I have to disconnect user manually after rebooting
Version 2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10 -
@dhmyess yup, it's normal
it's currently only fixed in development versionit will be fixed in stable version when pfsense 2.5.0 will be out
in the meantime you could install the patch ! -
@dhmyess said in Pfsense, No internet when it is said "You are connected".:
Still unsolved, I have to disconnect user manually after rebooting
Hummm.
You posted here, in this thread. So you must have read this thread.
What you mean with "unsolved" is that, after finding the problem, finding this thread, concluding that you have the same problem, applying the solution, you still have a problem which is : users show connected in Status > Captive Portal > [ZONE] after a reboot ?edit : well, in that case : you are correct.
I logged in to my portal.
Saw that I showed up in Status > Captive Portal > [ZONE]
Also, I checked that I was listed into the two ipgw tables :ipfw table cpzone1_auth_down list ipfw table cpzone1_auth_up list( my zone is called cpzone1 )
I reboot pfSense.
After the Status > Captive Portal > [ZONE] still showed I was logged in.
The ipfw table where empty ....
So, I saw the "You are connected." ...... again.The solution :
Look (search) this part in the file /etc/inc/system.inc :function system_reboot_cleanup() { global $config, $cpzone, $cpzoneid;Right after 'global', add " $g, "
function system_reboot_cleanup() { global $g, $config, $cpzone, $cpzoneid;Btw :
@free4 : you confirm ?
This issue is fixed upstream. I guess was created when it was backported ?In this function system_reboot_cleanup(), the global "{$g['vardb_path']}" is used.
The result (before adding the $g) is that deleting the captive portal logged in database is NOT deleted with
unlink_if_exists("{$g['vardb_path']}/captiveportal{$cpzone}.db");
because "{$g['vardb_path']}" is empty (non defined). So the command tries to delete something inexistant, the captive portal user database survives the reboot ... -
I was add $g like you said and reboot, but user still logged in captive portal, my captive portal zone name is 'cp', and strangely everytime i save change or when i click disconnect all users interface that i selected on captive portal will be freeze and i must reboot the router to make it work again.
-
When you add the "$g, ", the logged-in user data base is destroyed - when pfSense reboots, it won't show show any logged in users - because the 'list' is deleted.
Did you 'really' edited the file /etc/inc/system.inc ?
(and before, apply the patch stated above ? )@dhmyess said in Pfsense, No internet when it is said "You are connected".:
when i click disconnect all users interface that i selected on captive portal will be freeze and i must reboot the router to make it work again.
Freeze ?
Logs ?
Other user ?
ipfw table list ? (see https://docs.netgate.com/pfsense/en/latest/captiveportal/captive-portal-troubleshooting.html )
Can you detail ? -
@Gertjan Yes, I've ready apply this patch and then edited the file /etc/inc/system.inc but no changes.
Am I use wrong patch??
sorry for slow respon, I have to wait for users not using the network to work, I do not want to get complaints from them because of my trial.
For freezing issues it's probably due to motherboard problems or bios bugs, because other machines aren't affected.
