I have a couple of instances where it appears that several hotspot clients are being assigned the same IP address as the gateway as well as a normal IP. the result is that the client can not connect until i delete the hosts entry under the hotspot winbox management.

MTRouter/Hotspot
Address:
# ADDRESS NETWORK BROADCAST INTERFACE
0 192.168.0.1/24 192.168.0.0 192.168.0.255 wlan1

IP Pool:
# NAME RANGES
0 hs-pool-1 192.168.0.128-192.168.0.254

DHCP-Server:
# NAME INTERFACE RELAY ADDRESS-POOL LEASE-TIME ADD-ARP
0 dhcp1 wlan1 hs-pool-1 1h yes

HOTSPOT:
# NAME INTERFACE ADDRESS-POOL PROFILE IDLE-TIMEOUT
0 hotspot-1 wlan1 hs-pool-3 hsprof2 none

HOTSPOT PROFILE:
1 name="hsprof2" hotspot-address=192.168.0.1 dns-name=""
html-directory=hotspot rate-limit="" http-proxy=0.0.0.0:0
smtp-server=000.000.000.000 login-by=mac,cookie,http-chap,https,http-pap
mac-auth-password="" http-cookie-lifetime=3d ssl-certificate=none
split-user-domain=no use-radius=yes radius-accounting=yes
radius-interim-update=received nas-port-type=wireless-802.11
radius-default-domain="" radius-location-id="" radius-location-name=""
radius-mac-format=XX:XX:XX:XX:XX:XX

FAULT IN HOSTS: (from what i remember)
Flags: S - static, H - DHCP, D - dynamic, A - authorized, P - bypassed
# MAC-ADDRESS ADDRESS TO-ADDRESS SERVER IDLE-TIMEOU
35 P XX:XX:XX:XX:XX:XX 192.168.0.1 192.168.0.1 hotspot-1
36 P XX:XX:XX:XX:XX:XX 192.168.0.149 192.168.0.149 hotspot-1

The MAC addresses for 35 and 36 are the same.

Try extending the leas time to at least 1 day, personaly i do 3 days.

are they offered by dhcp? can't see 'H' flags...

Thanks, I will try this however this does not explain why such a thing happens as that address is not part of the pool and is excluded/denied in the hotspot bindings table.

Regards
Andrew

Chupaka: Yes they should be as i can see no other way for these IP's to be handed out and they are not static. There are a couple of HA tags in the /ip hotspot host print however these are not for this customer.

There is only a P flag for him.

Regards
Andrew

Andrew, Did you ever find the reason why the client got assigned the gateways ip address? How did you solve this issue? We see the same thing on one of our spots now. 2 Clients get assigned the gateways ip address by dhcp. I might try to downgrade to 2.9.51 to see if it is related to ROS 3.22
ip-pool
0 VLAN471-Student-Pool/22 10.17.100.100-10.17.100.250
10.17.101.2-10.17.101.254
10.17.102.2-10.17.102.254
10.17.103.2-10.17.103.254
1 VLAN1-Admin-Pool 172.20.11.245-172.20.11.249
2 VLAN844-Office-Pool 192.168.1.100-192.168.1.170

DHCP-SERVER
Flags: X - disabled, I - invalid
# NAME INTERFACE RELAY ADDRESS-POOL LEASE-TIME ADD-ARP
0 dhcp-student vlan471 VLAN471-Student-Pool 6h yes

# ADDRESS GATEWAY DNS-SERVER WINS-SERVER DOMAIN
0 ;;; Student Network
10.17.100.0/22 10.17.100.1 10.17.100.1
208.67.220.220
1 ;;; Admin Network VLAN1 static
172.20.11.0/24 172.20.11.1 172.20.11.1
2 ;;; Eth1 Local management
192.168.10.0/24 192.168.10.1 192.168.10.1
193.162.153.164


[admin] /ip hotspot ip-binding> print
Flags: X - disabled, P - bypassed, B - blocked
# MAC-ADDRESS ADDRESS TO-ADDRESS SERVER
0 X 10.59.1.0/24
1 X 192.168.1.0/24
2 X 10.17.102.0/24
3 ;;; D-Link- DHCP Alert
00:13:46:42:14:81 10.17.100.177 10.17.100.177 hs-student
4 P ;;; bgm6615 - 7874
00:17:F2:2B:30:71 10.17.101.86 10.17.101.86 hs-student
5 P 00:16:D4:E3:48:89 10.17.103.130 10.17.103.130 hs-student
6 ;;; Belkin DHCP Alert
00:17:3F:DE:78:C8 10.17.100.120 10.17.100.120 hs-student
7 B 00:17:3F:DE:78:C8 10.17.100.1 10.17.101.57 hs-student
8 B 00:16:D4:E3:48:89 10.17.100.1 10.17.100.109 hs-student

I have blocked the MAC addresss which get the gateways ip address 10.17.100.1 because it seems this 2 clients are eating slowly all unleased dhcp addresses from our pools.

I have not seen this issue before, so if you did find a solution which explain why they are getting the gateways please post id.

Kenneth