Well...yes. Look, I wasn't the one that came up with this setup. It is the setup that I have to work with at this time, however. Although you & I know that it's not very secure, the folks who are using it either a) don't know or b) don't care.
Although I do appreciate you pointing out that I'm doomed (no sarcasm - it has made me look around), I'd like to get back to my original question(s)... 1. Is is possible to do "fall through" on SQL-based user tables, so that RADIUS will look at the whole table for a match before deciding whether there's a match or not? 2. Is it possible to rewrite a null attribute, either with attr_rewrite or some other mechanism? 3. Are there any other attributes besides ==, <=, >=, and =* that could solve this issue for me, or can I do something different with those operators that will make this work? Thank you very much for your help - I really do appreciate it. Sincerely, Brian > > Oh boy, it's the CLIENT that you're trying to authenticate. > The AP only sends the MAC of the client, so that's about the > only thing you > can check to distinguish the users. > > -- > Regards, > > Thor Spruyt > E: [EMAIL PROTECTED] > W: www.thor-spruyt.com > M: +32 (0)475 67 22 65 > Bestel nu uw exemplaar van Operationele verkoop (Walter Spruyt - > Liesbeth Huysmans) via www.salesguide.be Ontdek de Telenet Hotspot > service op www.telenet.be/hotspots > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
