Captive Portal Slow in Google Chrome



  • Hello,

    Does anyone else experience slow load times with captive portal enabled and using google chrome? When I open google chrome and try and browse to a webpage, it takes about 30-45 seconds for the captive portal login page to appear. If i do the same thing using Internet Explorer, the login page comes up right away. I have yet to try with firefox.

    I searched around but only came across the tip to add the gw to the allowed ip's in captive portal settings, but this didn't make any difference.

    Any help would be good.

    I did a packet capture and I see that the machine using chrome is trying to get to google by a whole bunch of different IP's then it finally loads the login page, but only in a different tab?



  • Don't worry about that.
    Chrome is a relative young browser, he hasn't had much experience yet, and he still has a lot to learn.
    Think about it, it took years for Microsoft to put a usable browser on the market (Netscape was for more superior back then)
    Firefox was always ahead …. (and the source code is for free if you want to make it better).

    Chrome is and rest more some kind of marketing device (that feeds Google with all kind of usable information for them, so they can do all kind of stuff with it, as "making a big business out of what you do when you surf" **

    I tend to say that when people start to know what a browser does with YOUR info, then Chrome isn't (anymore) on their PC ....

    ** I've nothing against that, of course ...

    All this with a big  ;) of course.

    (I don't know why, but I bet that pfSense dev's do not use Chrome to test a lot .... I wonder why ..... or not. )

    PS : Chrome works fin on my portal, but it tend to smart-browse ***, something that complely fails when it's behind a portal .... because the connection isn't oen yet and Chrome can't call "home" (now, where should that be ?? ;) ) and it goes wacko.

    *** Or what ever it does that other browsers don't do.

    Ok, a last one before bed time: Chrome wasn't being build for the end-user. It is a harvesting tool, and the crop, that's you.
    As you said yourself:
    @envoys:

    …....
    I did a packet capture and I see that the machine using chrome is trying to get to google by a whole bunch of different IP's then it finally loads the login page, but only in a different tab?

    E.T. can't call home so it does strange things ….



  • Thanks for the reply. I will just forget about it for now. I figured it was just a google calling home thing. Thanks again.


Log in to reply