cryptography - captive portal authentication theory -
i'm little confused on how captive portal authentication works. in implementations, after user authenticated login page, ip , mac address whitelisted , allowed connect through gateway. has problem of people spoofing mac addresses gain access. if portal sets session between , client, mean every piece of traffic client requests internet must go through portal's server?
generally, security in captive portal not considered particularly important. however, there solutions lock mac first port use , disallow use of mac on additional port. similar techniques can used wirelessly, ap refuse pair additional client using same mac address existing client. requires enterprise authentication unique key negotiated each attached device.
it's not clear me mean "the portal's server". generally, once mac address authorized , wired port configured or wireless connection established, nothing further needs done portal. traffic authenticated connections routed/natted normally.
Comments
Post a Comment