The essence of the problem, you need to somehow get the client mac in order to become attached to it and sift out the unwanted. freeradius and for the NAS stands mikrotik. When you try to login, a request is sent to the radius of the server and from there you can get mac from Calling-Station-Id, but here’s the problem, the registration page on the server, i.e. it does not receive data from the NAS. There is a thought on the registration button to hang up that thread that will send an authorization request and I will receive the cherished Calling-Station-Id, but what code to insert into the login page of the microtic has no thoughts yet. The authorization system is spinning on django + postgresql. And how do you get client mac?
- is the registration page on the server available prior to authorization on freeradius? - Igor
- something like this, the server is added to the walled garden. If you manually register the address of the registration page, it will also open - slayerus
- from the internal network we learn IP, by IP we recognize mac. From the external methods I don’t know normal, it’s not normal to run java or activex components on the user's computer and transfer them. - Igor
|
1 answer
Mikrotik can turn out a lot, including transmitting poppy and so on. http://wiki.mikrotik.com/wiki/HotSpot_external_login_page
and no crutches in the form of tearing poppy on ip or fake authorization.
|