Pfsense, No internet when it is said "You are connected".
-
@gertjan which one should I give url??
-
The issue discussed in this thread : https://github.com/pfsense/pfsense/pull/4031
Dono where you took your patch URL from (except that it is something proposed by @jimp last September, so ... old).
-
@abuledi please use https://github.com/pfsense/pfsense/compare/master...Augustin-FL:patch-captivportal-reconfigure-no-configbump.diff as "URL/Commit ID"
-
@gertjan yes... Same issue I am facing but I am new here so mentioned patch is not compliang I have to execute this could please send me url so I can sync this patch to my box..
-
What are the messages when you "Test" the patch ?
-
The patch applies fine for me against 2.4.4p2:
I suspect you have entered the wrong URL.
Steve
-
@stephenw10 please share that url thanks in advance...
-
It's this, the link that free4 posted above, twice:
https://github.com/pfsense/pfsense/compare/master...Augustin-FL:patch-captivportal-reconfigure-no-configbump.diffSteve
-
@stephenw10 https://github.com/pfsense/pfsense/commit/4573641589d50718b544b778cea864cfd725078a.patch
I already use that url and you share also same but no luck for me..
-
And you are running 2.4.4p2 ?
What does the first "detail" links tell ypu ?
Use
to highlight the code.
/usr/bin/patch --directory=/ -t -p2 -i /var/patches/5c3c2026af1e2.patch --check --forward --ignore-whitespace Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/etc/inc/captiveportal.inc b/src/etc/inc/captiveportal.inc |index 9b4856f774..b08bd350e0 100644 |--- a/src/etc/inc/captiveportal.inc |+++ b/src/etc/inc/captiveportal.inc -------------------------- Patching file etc/inc/captiveportal.inc using Plan A... Hunk #1 succeeded at 225. Hunk #2 succeeded at 233. Hunk #3 succeeded at 371. Hunk #4 succeeded at 391. Hunk #5 succeeded at 415. Hunk #6 succeeded at 563. Hunk #7 succeeded at 605. Hunk #8 succeeded at 698. Hunk #9 succeeded at 911. Hunk #10 succeeded at 967. Hunk #11 succeeded at 1101. Hunk #12 succeeded at 1219. Hunk #13 succeeded at 1234. Hunk #14 succeeded at 1683. Hunk #15 succeeded at 1706. Hunk #16 succeeded at 2208. Hunk #17 succeeded at 2431. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/etc/inc/globals.inc b/src/etc/inc/globals.inc |index 6d082a01d7..f1cc340192 100644 |--- a/src/etc/inc/globals.inc |+++ b/src/etc/inc/globals.inc -------------------------- Patching file etc/inc/globals.inc using Plan A... Hunk #1 succeeded at 69. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/etc/inc/system.inc b/src/etc/inc/system.inc |index 73b1acbcac..d55adeea07 100644 |--- a/src/etc/inc/system.inc |+++ b/src/etc/inc/system.inc -------------------------- Patching file etc/inc/system.inc using Plan A... Hunk #1 succeeded at 2113. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/etc/inc/upgrade_config.inc b/src/etc/inc/upgrade_config.inc |index 97fb3d6a3e..51398ca6cb 100644 |--- a/src/etc/inc/upgrade_config.inc |+++ b/src/etc/inc/upgrade_config.inc -------------------------- Patching file etc/inc/upgrade_config.inc using Plan A... Hunk #1 succeeded at 5921 (offset -13 lines). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/services_captiveportal.php b/src/usr/local/www/services_captiveportal.php |index ccdc6152af..69875d12a3 100644 |--- a/src/usr/local/www/services_captiveportal.php |+++ b/src/usr/local/www/services_captiveportal.php -------------------------- Patching file usr/local/www/services_captiveportal.php using Plan A... Hunk #1 succeeded at 151. Hunk #2 succeeded at 354. Hunk #3 succeeded at 635. Hunk #4 succeeded at 1187. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/status_captiveportal.php b/src/usr/local/www/status_captiveportal.php |index bdfd441f5a..3963fd2ed5 100644 |--- a/src/usr/local/www/status_captiveportal.php |+++ b/src/usr/local/www/status_captiveportal.php -------------------------- Patching file usr/local/www/status_captiveportal.php using Plan A... Hunk #1 succeeded at 268. done -
If you're using the same settings as I posted above then it would only not apply if the files have already been modified or it's not 2.4.4p2 (so the files are different).
You see the same error details?
Steve
-
I just upgraded to 2.4.4-RELEASE-p3 and now I'm experiencing this issue. Has the fix not made it into released versions, yet?
-
@ohbobva no...sadly, Netgate didn't included the fix in 2.4.4-p3 :/
-
The real cause of this problem is that when the cellphone/laptop become out of wifi signal range
for example you login to the captive portal page [there is internet connection]
but when you turn off the wifi of cellphone/laptop then you re-open it
it will reconnected but there is no internet, when you look at
pfsense gui still connected but the cellphone has no internet,
i am hoping they fix this bug
i downgrade my pfsense to version 2.3.2 [no bug] -
Going to need more than "has no internet."
-
We have over 100 pfsense deployments in the field and are encountering this issue as well.
-
Really you have 100 installs of pfsense in the field and the most you can add to the information about the problem is
+1
WTF??????
Sorry but BS!!!
-
Um, yeah, waaay more info required.
I assume you mean you log into the captive portal and it reports you are connected but you are still unable to reach external sites?
And you have tried the suggestions here?:
https://docs.netgate.com/pfsense/en/latest/book/captiveportal/troubleshooting-captive-portal.htmlSteve
-
@johnpoz this is the whole problem with pf now. Unfortunately we do indeed have many of these. We do use these for CP. Users Macs/iPhones/androids all get the error that indeed says just that. Now we have another revision that feels like we are beta testing software and troubleshooting.
I indeed have more information about this is related to users that have logged in before and try again. The only difference on these boxes is the firmware update.
Instead of believing customers and helping solve their issues. Just saying BS. Why would we login to lie about an issue? This is an unfortunate turn.
-
@MTNet and the browers says you are connected but never by passes it and no internet if you close it. It’s the same problem detailed above..
