I’m running two hotspot interfaces on the same RB - one serving an ethernet connection to a PC and the other serving a wireless interface. Both authenticate against ‘tickets’ issued by a User-Manager running on the same box.
The weirdness is that according to the ‘active user’ tab the wireless interface is allocating addresses from the PC-pool to wireless log-ons despite the fact that its server profile is quite definitely set to the wireless pool, as is DHCP for that interface - and DHCP records the allocation of an address to the wireless laptop’s MAC from the correct pool in its ‘leased’ list as well as the allocation of an address from the PC pool to the same MAC. Wireless clients are able to connect to the hotspot and log-on but then nothing happens as it’s on the wrong network.
I’m baffled. Any suggestions as to where I might look for answers?
there no bridge across any of the interfaces is there?
secondly, confirm each server profile has it own unique IP pool and they aren’t using the same one.
Are you able to paste your hotspot config (removing any private data of course)?
/ip hotspot export
See below.
I’ve spent several hours trying to get to the bottom of this and believe I know what’s happening.
There are two hotspots - PublicPC (ethernet) and Wireless. Both authenticate against User-Manager on the same machine. Each has its own IP pool = hs-pool-2 (PC) and hs-pool-6 (wireless). If I create an individual wireless user in User-Manager I can specify the hs-pool to use (Pool Name) so I set it to hs-pool-6 and can log-on to the wireless hs without problem. However a BATCH creation of wireless hotspot users does not have the facility to specify the address pool to use and as a result when wireless users are authenticated by User-Manager they are allocated an address from the first pool - the PC pool - and don’t get a usable connection.
As a result I’ve had to instruct the client to manually add the correct pool name to all wireless users created by batch, which is a nuisance and shouldn’t be necessary.
If I’m correct it is clearly an inadequacy in User-Manager, and the facility to point batch-created users at a particular pool is required.
ip hotspot profile
set default dns-name=“” hotspot-address=0.0.0.0 html-directory=hotspot
http-cookie-lifetime=3d http-proxy=0.0.0.0:0 login-by=cookie,http-chap
name=“default” rate-limit=“” smtp-server=0.0.0.0 split-user-domain=no
use-radius=no
add dns-name=“” hotspot-address=192.168.20.1 html-directory=hotspot
http-proxy=0.0.0.0:0 login-by=http-chap,http-pap name=“PublicPC”
nas-port-type=ethernet radius-accounting=yes radius-default-domain=“”
radius-interim-update=received radius-location-id=“”
radius-location-name=“PublicPC” rate-limit=“128k/512k”
smtp-server=xxx.xxx.xxx.xxx split-user-domain=no use-radius=yes
add dns-name=“” hotspot-address=10.6.50.1 html-directory=hotspot
http-cookie-lifetime=3d http-proxy=0.0.0.0:0 login-by=cookie,http-chap
name=“hsprof1” nas-port-type=wireless-802.11 radius-accounting=yes
radius-default-domain=“” radius-interim-update=received
radius-location-id=“” radius-location-name=“” rate-limit=“256k/512k”
smtp-server=xxx.xxx.xxx.xxx split-user-domain=no use-radius=yes
/ip hotspot user profile
set PublicPC address-pool=hs-pool-1 advertise=no idle-timeout=none
keepalive-timeout=2m name=“PublicPC” open-status-page=http-login
rate-limit=“128k/512k” session-timeout=5m shared-users=1
status-autorefresh=1m transparent-proxy=yes
add address-pool=hs-pool-6 idle-timeout=none keepalive-timeout=2m
name=“Wireless” shared-users=1 status-autorefresh=1m transparent-proxy=no
/ip hotspot
add address-pool=hs-pool-1 addresses-per-mac=2 disabled=no idle-timeout=5m
interface=ether1 keepalive-timeout=none name=“Public PC” profile=PublicPC
add address-pool=hs-pool-6 addresses-per-mac=2 disabled=no idle-timeout=5m
interface=“Wireless Hotspot” keepalive-timeout=none name=“hs-Wireless
Hotspot” profile=hsprof1
/ip hotspot service-port
set ftp disabled=no ports=21
Am I right or is there something I’ve missed?
In the new User Manager (which is currently beta and new version will be released very soon) the IP Pool is specified per Profile. Each User has then one ore multiple profiles assigned. To change IP Pool to a batch of users, just IP Pool of the Profile has to be changed.
In the current version, it is not possible right now to specify IP Pool in User Batch-Add form. But we will add this feature (IP Pool in Batch-Add form) in the next release (v3.25).