Forum Replies Created
I don’t understand why you specify /21.
The CIDR notation (Classless Inter-Domain Routing) 172.18.184.106/21 and 172.18.184.107/21 are network address and not host IP address and the problem is that they rappresent the same subnet:
Infact the binary notation of the netmask is:
1111111.1111111.11111000.00000000 (21 ones)
therefore when FreeRADIUS applies the logical AND operation the last byte of both the networks is zero. In other words you have:
Thanks Fulvio, 😀
Ok, I feel like a total N00B now but at least I learned something additional today. I never work with CIDR notation and always just IP/Mask. I completely understand the behavior now. The interface threw me for a loop, I thought the /# was required not optional. When using a subnet calculator to find out my CIDR, I didn’t catch that IP/CIDR corresponds to a subnet not an IP and MASK.
I entered the IPs alone and it’s all set now.
Every thing’s up and working now. I appreciate your time and not just telling me to RTM. Sorry about that. 😳
(Deleted by user)
The more I think about it, if Zeroshell supported external LDAP for authentication it would support AD, Edirectory and many other directories that have native support for LDAP.
At the moment the FreeRadius configured in Zeroshell is only able to authenticate and authorizate by using the local LDAP server.
In the future I’ll try to configure it to use external LDAP and Kerberos 5 servers such as Active Directory.
That would be really sweet. I can support LDAP and Samba 3 will do AD if memory serves which I could also host on my SuSe box. That would allow me to use Zeroshell to authenticate into my existing directory and avoid creating separate users for everyone.
I’ll cross my fingers that you win a lot of money and the support comes out sooner than later. 😀
I haven’t had much feedback about my guide, so it’s great to hear that you got it working without a problem.
It wasn’t easy for me to figure it out, so I thought it would be best to share with the community and perhaps speed up the adoption of zeroshell across the world… 🙂
Well here is my feedback then – THANK YOU!!!! It steered me in the completely right direction. The server side setup covered my setup completely. My client side of course was a little different since I’m using DELL laptops with a different wireless client but I worked around a few minor changes and I now have it all working.
Thank you for zeroshell but I need your help in some problems
I use zeroshell as a hotspot server on my hotel its working but
1- I need to generate more than account in a same time for gust.
2- I need user to use account just one time.
3- I need to edit in login page as my hotel standard.
4- zeroshell documentation.
Not really a response but just to summarize are these correct?
1.) So multiple account creation. (Create multiple accounts at once.)
2.) I assume with a hotel you’d mean an account expiration date/time? Wouldn’t you want them to be able to authenticate until they checked out? That could be accomplished by an account expiry date.
3.) There is some information on the forum about this but it’s not officially supported.
4.) I think documentation would be very beneficial myself. If it wasn’t for Paul’s WPA guide it would have been a lot harder for me to set up my RADIUS/WPA system.