Captive Portal turned on but not working
-
There are some issues with VLANs and CP under some specific circumstances - but I don't know what those circumstances are. Haven't had time to look at it, and I can't personally replicate it. It works fine for quite a few people, but there are at least a handful who it doesn't work for. It's not related to authentication settings or authenticated vs. non-authenticated, those who see this don't even get the portal screen, it just gets passed through.
-
I had time to upgrade to 1.2.3-PRERELEASE-TESTING-VERSION built Feb 7 and am still having the problem. I started with a fresh config and built it from scratch to make sure it wasnt an issue with my backup…
Peter
-
I had time last night to setup and test 1.2.3-PRERELEASE-TESTING-VERSION built on Sat Mar 7 09:51:09 EST 2009 with Captive Portal on one of my VLANs - I'm seeing the same issue others have reported where its just allowing direct access to the internet… I'll trying to do some more testing and report back with any additional info (just to make sure its not me).
Not sure if its any help, but...
I'm using the embedded version with Alix hardware. I'm using VLAN tags 3, 8 and 10 (CP is running on vlan tag 10). They are all VLANs on the LAN interface and the LAN interface is
configured with a network / IP but its not really used. The rest of the VLAN functionality seem to be working correctly. -
Provide this output:
ipfw list
/tmp/rules.debug
/conf/config.xml
sysctl net.inet.pfil
ifconfig -
Having failed to get it working, I had to go for an alternative config, I'll try and set it up again and post the config.
Unfortunately this is at a charity where I just help out in my own time so it may take me a few days to sort.Thanks for your help.
Nick -
What is the status on these issues?
I am planing on a major reconfiguration and will probably use only VLAN internally and need to know it's working. And I will also use captive portal and it will surely be on a VLAN interface.
Also, it's apparent reading through different areas in the forum that 1.2.2 seems to have broken a lot of stuff, I've seen a number of posts dealing with packages that no longer works after 1.2.2 upgrade etc and I have personally experienced (and reported) a number of problematic package issues on 1.2.2.
Cheers,
-
ermal -
Where do I need to input this into to get the info you need the shell? Do I enter each line individually or all together as one? Sorry for the newb question….Peter
-
I'm having pretty much this same behavior, but in 1.2-RELEASE with no vlan's as stated in my thread from a few days ago. Maybe there's something else at play here?
-
Just give the output of the commands i have asked above.
-
The problem arises when you use the untagged interface at the same time as a tagged one… ipfw forwards the packet for the untagged interface witch contains the tagged interface.