Capitve Portal not showing on LAN but internet works [Solution]



  • I have installed pfsense in virtualbox and made a simple configuration for internet and cp .
    Internet work fine specially on dns forwarder , then when i enable cp i can't access it or the internet .

    The solution i found that makes it work is to disable ipv6 on all interfaces , it seems their is something wrong with it .

    [Update]
    It seems that it not because ipv6 , because after i rebooted pfsense the issue came again ! .. So i discovered that i have to modify any thing in the wan interface so the cp to found it !

    It seems that the cp need to run before initialization of the interfaces not after .

    [Update2]

    I tried another approach by going to :
    status >> interfaces >> WAN >> release
    then renew

    it came with the same result , the CP won't work until the WAN interface has reloaded , we can argue about this all night long , but this is a fact that i have found , at least some body try it .

    [Update3]

    I have found a final solution , it's easy and simple :

    1 - backup configuration
    2 - edit the xml file
    3 - add the following line below and above

    <shellcmd>/etc/rc.interfaces_wan_configure</shellcmd>

    4 - save the xml file
    5 - restore the xml file

    And the CP will always show

    [Solved]



  • IPv6 isn't used when it concerns the captive portal.

    [Update]
    It seems that it not because ipv6 , because after i rebooted pfsense the issue came again ! .. So i discovered that i have to modify any thing in the wan interface so the cp to found it !

    It seems that the cp need to run before initialization of the interfaces not after .

    Keep looking - keep as much to default. I do not understand what the problem is.

    Initializing the captive portal, which means loading ipfw rules etc, can not be done without having an active interface.

    Keep in mind: use the captive portal on a dedicated NIC (Interface) will simplify the setup.



  • @Gertjan:

    IPv6 isn't used when it concerns the captive portal.

    [Update]
    It seems that it not because ipv6 , because after i rebooted pfsense the issue came again ! .. So i discovered that i have to modify any thing in the wan interface so the cp to found it !

    It seems that the cp need to run before initialization of the interfaces not after .

    Keep looking - keep as much to default. I do not understand what the problem is.

    Initializing the captive portal, which means loading ipfw rules etc, can not be done without having an active interface.

    Keep in mind: use the captive portal on a dedicated NIC (Interface) will simplify the setup.

    After i disable or enable ipv6 or other thing and hit apply changs in the WAN interface , the capitve portal work fine , that's what i'm trying to say .


  • Banned

    Let me say it again: You cannot have IPv6 on the CP interface.



  • @doktornotor:

    Let me say it again: You cannot have IPv6 on the CP interface.

    Guys , did you read my update ?
    What happened with me is that the wan interface have to be " reload " in order to CP to work .
    This is what i wrote this post for [possible solution] , i just need any one to confirm the " reload" issue .


  • Banned

    No such issue here. Then again, I'm NOT using the CP on LAN (absolutely the worst place you can put CP on.)



  • @doktornotor:

    No such issue here. Then again, I'm NOT using the CP on LAN (absolutely the worst place you can put CP on.)

    Ok , that's interesting , this info i did not know .
    Can you tell me how to config CP to the LAN clients without using it on LAN interface ?


  • Banned

    @shark74:

    Can you tell me how to config CP to the LAN clients without using it on LAN interface ?

    That is really simple. You don't do any such thing. CP just does not go to interface assigned to LAN. :P



  • @doktornotor:

    That is really simple. You don't do any such thing. CP just does not go to interface assigned to LAN. :P

    :(



  • LAN : a set of devices that you trust.
    Captive Portal : a set of devices that you do not trust, you do not share anything with them (you should even stop sharing between these invited devices), the captive portal has been invented to give 'strangers' an Internet Access - which is the only thing you share with them : 'Internet Access'.

    It is possible that there are no devices are present on the LAN interface, just ones in a while a device (your PC) to a administer pfSense.
    For that matter, captive portal (interface) users (clients) should not have access to pfSense port 80, 443 and 22 on its interface (OPTx).
    Normally, in a perfect world, a captive portal is hooked up to an OPT1 (third interface - NIC) , OPT2 (fourth interface - NIC), etc.

    Seems all normal, right ?! ;)

    Now, have a look at the publicity on top of this page. Click on it? And you'll see boxes that can run pfSense: they all have 3 more NIC's ….. ;)

    I guess a captive portal on LAN (second interface) can be done. I never tried it ...



  • @Gertjan:

    LAN : a set of devices that you trust.
    Captive Portal : a set of devices that you do not trust, you do not share anything with them (you should even stop sharing between these invited devices), the captive portal has been invented to give 'strangers' an Internet Access - which is the only thing you share with them : 'Internet Access'.

    It is possible that there are no devices are present on the LAN interface, just ones in a while a device (your PC) to a administer pfSense.
    For that matter, captive portal (interface) users (clients) should not have access to pfSense port 80, 443 and 22 on its interface (OPTx).
    Normally, in a perfect world, a captive portal is hooked up to an OPT1 (third interface - NIC) , OPT2 (fourth interface - NIC), etc.

    Seems all normal, right ?! ;)

    Now, have a look at the publicity on top of this page. Click on it? And you'll see boxes that can run pfSense: they all have 3 more NIC's ….. ;)

    I guess a captive portal on LAN (second interface) can be done. I never tried it ...

    After reloading WAN interface , CP work on LAN like charm .  ;)



  • I hope that one of the experts will explain what actually happened  ;)


Log in to reply