Apparently hotspot users keepalive-timeout will be set to 2m regardless of the value set in hotspot definition. I’ve tested both 4.4 and 4.6 versions, and results are the same. The bad thing is, users are logging out by reason “logged out: keepalive timeout” even though they are active. Isn’t it possible to set the keepalive-timeout in these versions? Or is this a bug?
[admin@Mik-1] /ip hotspot> print detail
Flags: X - disabled, I - invalid, S - HTTPS
0 name=“hotspot1” interface=Ether1 profile=hsprof1 idle-timeout=6h keepalive-timeout=6h proxy-status="running
[admin@Mik-1] /ip hotspot active> print detail
Flags: R - radius, B - blocked
0 R server=hotspot1 user=“guest” address=172.16.25.9 mac-address=00:0F:F8:BA:9C:8A login-by=“http-pap” uptime=56m51s keepalive-timeout=2m
1 R server=hotspot1 user=“guest” address=172.16.24.10 mac-address=00:0F:F8:BA:9C:8A login-by=“http-pap” uptime=3h23m46s keepalive-timeout=2m
The keep-alive timeout is actually set on a per profile basis. Change it in the User Profile under Hotspot to what you want it to be, or set it by Radius when they sign into the network.
What radius attribute is used for setting keepalive-timeout. It’s obvious for idle-timeout but I couldn’t find anything on keepalive-timeout.
BTW, setting default profile in user applied for radius authenticated users too. thanks it was a great help.
Lists all of the available Radius Attributes. The Default profile is just that, the default settings, unless it is told otherwise by something else(ie Radius server), that will be assigned to someone.