Wireless client disconnect frequently



  • dear all,
    i am running captive portal of version pfsense 2.2.6, i have come up with probelm that my wireless clients disconnect frequently, i check the dhcp logs and there are repeated ip request for same clients this happens to some clients and other are workong fine. clients disconnect sometimes within second and sometime after some minutes

    most devices are mobiles.

    need help to sort out this probelm.



  • Apr 16 22:55:39 dhcpd: DHCPREQUEST for 172.16.17.150 (172.16.1.1) from e0:2c:b2:cf:cb:6d via re1
    Apr 16 22:55:09 dhcpd: DHCPACK on 172.16.17.199 to 54:40:ad:26:7b:33 via re1
    Apr 16 22:55:09 dhcpd: DHCPREQUEST for 172.16.17.199 from 54:40:ad:26:7b:33 via re1
    Apr 16 22:55:05 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:05 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:05 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:05 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:05 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:05 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPACK on 172.16.17.105 to f4:0e:22:e1:f5:ed via re1
    Apr 16 22:55:04 dhcpd: DHCPREQUEST for 172.16.17.105 from f4:0e:22:e1:f5:ed via re1
    Apr 16 22:54:49 dhcpd: DHCPACK on 172.16.17.210 to e0:cb:ee:32:96:b5 via re1



  • Apr 16 23:58:36 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:36 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:31 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:31 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:28 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:28 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:24 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:24 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:20 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:20 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:17 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:17 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:13 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:13 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:08 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:08 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:04 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:58:04 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:57 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:57 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:53 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:53 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:43 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:43 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:38 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:38 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:34 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:34 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:30 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:30 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:26 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:26 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:21 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:21 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:16 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:16 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:11 dhcpd: DHCPACK on 172.16.17.244 to b0:47:bf:3f:06:9e via re1
    Apr 16 23:57:11 dhcpd: DHCPREQUEST for 172.16.17.244 from b0:47:bf:3f:06:9e via re1



  • after update from 2.2.6 to 2.3 again the same probelm
    screen shot is attached

    ![DHCP logs.jpg_thumb](/public/imported_attachments/1/DHCP logs.jpg_thumb)
    ![DHCP logs.jpg](/public/imported_attachments/1/DHCP logs.jpg)



  • The problem is on your network, not the firewall. It's answering the clients' requests, and it appears those don't get back to the client. It also appears there is something else odd going on. There are multiple requests per second from one host 172.16.17.105. No normally functioning DHCP client is going to send more than one request a second. Something inside your network duplicating packets possibly.



  • @cmb:

    The problem is on your network, not the firewall. It's answering the clients' requests, and it appears those don't get back to the client. It also appears there is something else odd going on. There are multiple requests per second from one host 172.16.17.105. No normally functioning DHCP client is going to send more than one request a second. Something inside your network duplicating packets possibly.

    any idea what it would be… i am unable to figure out


Log in to reply