DHCP client list full and cannot be cleared even with factory reset

Product Discussion Pepwave AP & Surf
1

I have a Pepwave Surf SOHO is a very simple configuration at home. I have about ten clients connected to the router, some wired and most wireless with a wired WAN connection. It is running 6.3.3 although I tried version 7 as well and still have the issue.

When attempting to add a new device to the wireless network, it would not get an IP address although it seems to join the network just fine otherwise. I checked the client list on the router and could see the client didn’t receive an IP address and defaulted to a locally assigned address (169.xxx.xxx.xxx). I then checked my computer. Same issue; it could not get an IP address. Thankfully my iPad still had access so I was able to access the router though the iPad.

Before I turned on DHCP debugging, I power cycled the unit. Same issue. I then reset to factory defaults on the web interface. I could barely get access to the unit because it would not serve up an IP address to any host except one. Even setting a static address on the host didn’t work. The SSID did change to the default so I could tell that it did factory reset.

Eventually I pressed the reset button for ten seconds to clear the config and could get one host to access the router. It was still having issues assigning DHCP addresses. I discovered DHCP debugging and checked the logs (see below)

Something isn’t making sense. After a factory reset, the lease pool was still full. My workaround is to add entries to the DHCP server and adjust the scope. I also tried to adjust the DHCP server TTL to 1 minute to clear out the client list. The phantom entries still exist.

Any ideas on how to do a full reset on the router to delete all the clients from the DHCP table?

Jun 07 06:32:17 DHCP Server: 192.168.50.1 lease pool is full
Jun 07 06:32:17 DHCP Server: In server 192.168.50.1, IP 192.168.50.240 is already using
Jun 07 06:32:16 DHCP Server: In server 192.168.50.1, IP 192.168.50.239 is already using
Jun 07 06:32:16 DHCP Server: In server 192.168.50.1, IP 192.168.50.238 is already using
Jun 07 06:32:15 DHCP Server: In server 192.168.50.1, IP 192.168.50.237 is already using
Jun 07 06:32:14 DHCP Server: In server 192.168.50.1, IP 192.168.50.236 is already using
Jun 07 06:32:14 DHCP Server: In server 192.168.50.1, IP 192.168.50.235 is already using
Jun 07 06:32:13 DHCP Server: In server 192.168.50.1, IP 192.168.50.234 is already using
Jun 07 06:32:13 DHCP Server: In server 192.168.50.1, IP 192.168.50.233 is already using
Jun 07 06:32:12 DHCP Server: In server 192.168.50.1, IP 192.168.50.232 is already using
Jun 07 06:32:12 DHCP Server: In server 192.168.50.1, IP 192.168.50.231 is already using
Jun 07 06:32:11 DHCP Server: In server 192.168.50.1, IP 192.168.50.230 is already using
Jun 07 06:32:11 DHCP Server: In server 192.168.50.1, IP 192.168.50.229 is already using
Jun 07 06:32:11 DHCP Server: In server 192.168.50.1, IP 192.168.50.228 is already using
Jun 07 06:32:11 DHCP Server: In server 192.168.50.1, IP 192.168.50.227 is already using
Jun 07 06:32:10 DHCP Server: In server 192.168.50.1, IP 192.168.50.226 is already using
Jun 07 06:32:10 DHCP Server: In server 192.168.50.1, IP 192.168.50.225 is already using
Jun 07 06:32:09 DHCP Server: In server 192.168.50.1, IP 192.168.50.224 is already using
Jun 07 06:32:09 DHCP Server: In server 192.168.50.1, IP 192.168.50.223 is already using
Jun 07 06:32:08 DHCP Server: In server 192.168.50.1, IP 192.168.50.222 is already using
Jun 07 06:32:08 DHCP Server: In server 192.168.50.1, IP 192.168.50.221 is already using
Jun 07 06:32:08 DHCP Server: In server 192.168.50.1, IP 192.168.50.220 is already using
Jun 07 06:32:08 DHCP Server: In server 192.168.50.1, IP 192.168.50.219 is already using
Jun 07 06:32:07 DHCP Server: In server 192.168.50.1, IP 192.168.50.218 is already using
Jun 07 06:32:07 DHCP Server: In server 192.168.50.1, IP 192.168.50.217 is already using
Jun 07 06:32:06 DHCP Server: In server 192.168.50.1, IP 192.168.50.216 is already using
Jun 07 06:32:06 DHCP Server: In server 192.168.50.1, IP 192.168.50.215 is already using
Jun 07 06:32:05 DHCP Server: In server 192.168.50.1, IP 192.168.50.214 is already using
Jun 07 06:32:05 DHCP Server: In server 192.168.50.1, IP 192.168.50.213 is already using
Jun 07 06:32:04 DHCP Server: In server 192.168.50.1, IP 192.168.50.212 is already using
Jun 07 06:31:56 DHCP Server: 192.168.50.1 lease pool is full
Jun 07 06:31:56 DHCP Server: In server 192.168.50.1, IP 192.168.50.211 is already using
Jun 07 06:31:56 DHCP Server: In server 192.168.50.1, IP 192.168.50.210 is already using
Jun 07 06:31:56 DHCP Server: In server 192.168.50.1, IP 192.168.50.209 is already using
Jun 07 06:31:55 DHCP Server: 192.168.50.1 lease pool is full
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.208 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.207 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.205 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.206 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.202 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.204 is already using
Jun 07 06:31:55 DHCP Server: In server 192.168.50.1, IP 192.168.50.203 is already using
Jun 07 06:31:54 DHCP Server: In server 192.168.50.1, IP 192.168.50.201 is already using
Jun 07 06:31:54 DHCP Server: In server 192.168.50.1, IP 192.168.50.200 is already using
Jun 07 06:31:54 DHCP Server: In server 192.168.50.1, IP 192.168.50.199 is already using
Jun 07 06:31:54 DHCP Server: In server 192.168.50.1, IP 192.168.50.198 is already using
Jun 07 06:31:53 DHCP Server: In server 192.168.50.1, IP 192.168.50.195 is already using
Jun 07 06:31:53 DHCP Server: In server 192.168.50.1, IP 192.168.50.197 is already using
Jun 07 06:31:53 DHCP Server: In server 192.168.50.1, IP 192.168.50.196 is already using
Jun 07 06:31:53 DHCP Server: In server 192.168.50.1, IP 192.168.50.194 is already using
Jun 07 06:31:53 DHCP Server: In server 192.168.50.1, IP 192.168.50.193 is already using
Jun 07 06:31:52 DHCP Server: In server 192.168.50.1, IP 192.168.50.192 is already using
Jun 07 06:31:52 DHCP Server: In server 192.168.50.1, IP 192.168.50.191 is already using
Jun 07 06:31:52 DHCP Server: In server 192.168.50.1, IP 192.168.50.188 is already using
Jun 07 06:31:52 DHCP Server: In server 192.168.50.1, IP 192.168.50.190 is already using
Jun 07 06:31:51 DHCP Server: In server 192.168.50.1, IP 192.168.50.189 is already using
Jun 07 06:31:51 DHCP Server: In server 192.168.50.1, IP 192.168.50.186 is already using
Jun 07 06:31:51 DHCP Server: In server 192.168.50.1, IP 192.168.50.187 is already using
Jun 07 06:31:51 DHCP Server: In server 192.168.50.1, IP 192.168.50.185 is already using
Jun 07 06:31:50 DHCP Server: In server 192.168.50.1, IP 192.168.50.184 is already using
Jun 07 06:31:50 DHCP Server: In server 192.168.50.1, IP 192.168.50.183 is already using
Jun 07 06:31:50 DHCP Server: In server 192.168.50.1, IP 192.168.50.180 is already using
Jun 07 06:31:50 DHCP Server: In server 192.168.50.1, IP 192.168.50.182 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.181 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.178 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.179 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.177 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.174 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.176 is already using
Jun 07 06:31:49 DHCP Server: In server 192.168.50.1, IP 192.168.50.175 is already using
Jun 07 06:31:48 DHCP Server: In server 192.168.50.1, IP 192.168.50.173 is already using
Jun 07 06:31:48 DHCP Server: In server 192.168.50.1, IP 192.168.50.172 is already using
Jun 07 06:31:48 DHCP Server: In server 192.168.50.1, IP 192.168.50.171 is already using
Jun 07 06:31:48 DHCP Server: In server 192.168.50.1, IP 192.168.50.170 is already using
Jun 07 06:31:48 DHCP Server: In server 192.168.50.1, IP 192.168.50.168 is already using
Jun 07 06:31:47 DHCP Server: In server 192.168.50.1, IP 192.168.50.169 is already using
Jun 07 06:31:47 DHCP Server: In server 192.168.50.1, IP 192.168.50.167 is already using
Jun 07 06:31:47 DHCP Server: In server 192.168.50.1, IP 192.168.50.165 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.166 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.164 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.163 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.161 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.162 is already using
Jun 07 06:31:46 DHCP Server: In server 192.168.50.1, IP 192.168.50.160 is already using
Jun 07 06:31:45 DHCP Server: In server 192.168.50.1, IP 192.168.50.159 is already using
Jun 07 06:31:45 DHCP Server: In server 192.168.50.1, IP 192.168.50.158 is already using
Jun 07 06:31:45 DHCP Server: In server 192.168.50.1, IP 192.168.50.157 is already using
Jun 07 06:31:45 DHCP Server: In server 192.168.50.1, IP 192.168.50.155 is already using
Jun 07 06:31:45 DHCP Server: In server 192.168.50.1, IP 192.168.50.156 is already using
Jun 07 06:31:44 DHCP Server: In server 192.168.50.1, IP 192.168.50.154 is already using
Jun 07 06:31:44 DHCP Server: In server 192.168.50.1, IP 192.168.50.153 is already using
Jun 07 06:31:44 DHCP Server: In server 192.168.50.1, IP 192.168.50.151 is already using

2

Sounds to me like you might have a device on the network with some sort of virus, constantly dropping and then requesting a new IP address from the DHCP server.

You should look at your client list and the MAC addresses associated with all of those leases…

3

Thanks for the feedback. The client list only has the ten devices I expect to be on the network. Even if a device were to request a new IP address via DHCP, it would just get the same address unless it changed it’s MAC address but nothing looks suspicious there.

4

To add one more thing, after the two hard resets, I only connected one host to the router and it was still having trouble getting an IP address from DHCP. While the host could have been the device acting up, it seems to work just fine on the other Pepwave Surf SOHO I have at work so I doubt that is the case.

Is there any reason why a factory reset would not wipe everything from the router?

5

A factory reset does wipe everything that’s why this makes no sense. Are you starting with a factory default config or are you uploading a saved one to it?

I would start from scratch by unplugging the WAN altogether and factory reset it and confirm it is working.

1 Like
6

The first time I did a reset, I recovered my config after I could get access again. The next time I unplugged everything and did a reset by holding down the button with a toothpick for 10+ seconds. They yielded the same results. I will do it again and let you know if the results are any different.

7

Please try press and hold at least 20 seconds.

Hope this help.

1 Like
8

Hi

Was there a solution for this.

We seem to have a similar problem where a lot of hosts are unable to recieve a DHCP address. Particular is that these are all windows computers. Mac and Raspberry seem to have no problem at all. Some windows computers receive an address though. We are in the middle of a production and cannot just do a full reset.

Thanks

Arne