I’m trying to set up two hotspot interfaces and two usermanager customers on the same router. Each hotspot has its own set of HTML pages, and each customer has its own set of profiles (speed, time limits, prices, etc). I’m using ROS 6.3
Design:
ether1=hotspot1
ether2=hotspot2
usermanager customers:
admin (parent): router = 127.0.0.1
->customer1 (owner, child of admin [own customers, own profiles, own limitations, inherit parent’s router])
---->user: test (belongs to customer1, profile 1M/512K)
->customer2 (owner, child of admin [own customers, own profiles, own limitations, inherit parent’s router])
---->user: test (belongs to customer2 profile 2M/256K)
I’m able to get both hotspots up and running without a problem. I can create two users (via usermanager) belonging to each customer with the same login without a problem.
I can log in with the newly created user on customer1, but when I try to log in with the same user using hotspot2 I get a “not more sessions allowed message”. It appears as though the usermanager is ignoring the the source of the hotspot login when looking up users. I can verify that the profile information is being provided by customer1, and customer2 is being ignored. If I set “shared users” to 2 on hotspot1, I am now able to log in using hotspot2, but the profile information (e.g. rate limits) is definitely coming from customer1.
How do I associate requests from a particular hotspot to a corresponding usermanager customer? The only way I can see at the moment is to remove the admin customer, set up “customer1” and “customer2” as standalone customers and assign routers to each. The problem with that is each rouer IP needs to be unique, and since all radius requests coming from the hotspots originate from 127.0.0.1, this isn’t possible. If I remember correctly, usermanager 3.x used a special “user-prefix” to differentiate between users on hotspots/customers, but usermanager 5.x+ made this redundant.
Is it possible to run multiple hotspots and multiple customers on the same router? If so, how? Is there some sort of field that needs to be included in the radius requests coming from the hotspots? Thanks.