> My first question is about captive portal and the protocol that Peter wants
> to build into m0n0. I work regularly win 802.1x compliant devices and it
> seems to me that it's just what Peter looks for. I don't think it's the
> place to explain what 802.1x is (if necessary), but it should be a good
> point to include this in m0n0. And though it's often associated with WIFI,
> this protocole isn't restricted to wireless connection.
The protocol I described earlier is actually trying to solve a completely
different issue to 802.1x. My problem could have been solved by the use of
Radius for authentication, plus some tinkering with Radius accounting. I
think Dinesh and I have bounced this one around a couple of weeks ago (look
in the archive).
However, I decided that the quickest way to a working solution that can be
delivered immediately was the system I described yesterday. This is up and
running and supporting quite a few users.
802.1x is a potential solution for this kind of thing and has a number of
benefits over vanilla Radius, especially in a WiFi environment. However, at
the end of the day, it is simply an authentication + authorisation system.
What I need is accounting as well, and some sort of simple feedback
BUT - I agree with you that an 802.1x solution for m0n0wall would be a 'GOOD
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.