[Closed] System and network slow, DHCP problem??
-
It has bin about two weeks that the system run without any errors, >> https://forum.pfsense.org/index.php?topic=99673.0
Yesterday late they let me know, the wifi is not stable from time to time.
This morning the network and system itself was very slow, only after restarting the DHCP the system get the speed back.
At this point I have no idea whats going on.The network setup is as follows:
2.2.4-RELEASE (amd64)
Intel(R) Core(TM)2 Duo CPU E7300 @ 2.66GHz
2 CPUs: 1 package(s) x 2 core(s)Wan - Ziggo connection
Lan - 192.168.1.x - Lan and private wifi
OPT1 - 192.168.2.x - Guest WiFi with captive portal (only a access point on this interface)The wifi is used upstairs and the guest wifi in the cafe.
Here the DHCP log, please let me know what I can do to lookup this problem.
Oct 8 11:53:05 Gateway dhcpd: Wrote 23 leases to leases file. Oct 8 11:53:33 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:53:33 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:53:43 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:53:43 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:10 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:10 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:14 Gateway dhcpd: DHCPREQUEST for 192.168.1.130 from 34:64:a9:82:3a:68 (HP823A68) via re1 Oct 8 11:54:14 Gateway dhcpd: DHCPACK on 192.168.1.130 to 34:64:a9:82:3a:68 (HP823A68) via re1 Oct 8 11:54:42 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1 Oct 8 11:54:42 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:54:46 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 via re2 Oct 8 11:54:46 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:48 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:54:50 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:55:04 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:55:04 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:55:52 Gateway dhcpd: DHCPREQUEST for 192.168.1.159 (192.168.1.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:55:52 Gateway dhcpd: DHCPACK on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:57:20 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 via re2 Oct 8 11:57:20 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:57:22 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 11:58:26 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1 Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:26 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 11:58:27 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:27 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:27 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:55 Gateway dhcpd: DHCPREQUEST for 192.168.1.159 (192.168.1.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:55 Gateway dhcpd: DHCPACK on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:59 Gateway dhcpd: DHCPREQUEST for 192.168.1.159 (192.168.1.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:58:59 Gateway dhcpd: DHCPACK on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:59:01 Gateway dhcpd: DHCPREQUEST for 192.168.1.159 (192.168.1.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 11:59:01 Gateway dhcpd: DHCPACK on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:01:12 Gateway dhcpd: DHCPREQUEST for 10.238.242.28 from 00:12:40:39:2c:33 via re2: wrong network. Oct 8 12:01:12 Gateway dhcpd: DHCPNAK on 10.238.242.28 to 00:12:40:39:2c:33 via re2 Oct 8 12:01:14 Gateway dhcpd: DHCPDISCOVER from 00:12:40:39:2c:33 via re2 Oct 8 12:01:14 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:01:15 Gateway dhcpd: DHCPOFFER on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:01:46 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:01:46 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:02 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:02 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPDISCOVER from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPOFFER on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPDISCOVER from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:36 Gateway dhcpd: DHCPOFFER on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:40 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:40 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:42 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:42 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPDISCOVER from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPOFFER on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPDISCOVER from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPOFFER on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:45 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:02:45 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:02:47 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:47 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:51 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:51 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:53 Gateway dhcpd: DHCPREQUEST for 192.168.2.254 (192.168.2.1) from 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:53 Gateway dhcpd: DHCPACK on 192.168.2.254 to 00:12:40:39:2c:33 (android-d97f6cf10246ce75) via re2 Oct 8 12:02:53 Gateway dhcpd: DHCPDISCOVER from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:53 Gateway dhcpd: DHCPOFFER on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:02:53 Gateway dhcpd: DHCPDISCOVER from 00:22:58:2f:7a:14 via re1 Oct 8 12:02:53 Gateway dhcpd: DHCPOFFER on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:03:16 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 (192.168.1.1) from 00:22:58:2f:7a:14 via re1 Oct 8 12:03:16 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:03:16 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:03:23 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 (192.168.1.1) from 00:22:58:2f:7a:14 via re1 Oct 8 12:03:23 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:03:44 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 (192.168.1.1) from 00:22:58:2f:7a:14 via re1 Oct 8 12:03:44 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPREQUEST for 192.168.1.138 (192.168.1.1) from 00:22:58:2f:7a:14 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPACK on 192.168.1.138 to 00:22:58:2f:7a:14 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPDISCOVER from 74:da:38:35:38:51 via re1 Oct 8 12:04:09 Gateway dhcpd: DHCPOFFER on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:04:15 Gateway dhcpd: DHCPREQUEST for 192.168.1.157 (192.168.1.1) from 74:da:38:35:38:51 via re1 Oct 8 12:04:15 Gateway dhcpd: DHCPACK on 192.168.1.157 to 74:da:38:35:38:51 via re1 Oct 8 12:11:20 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:11:20 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:07 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:07 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:17 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:17 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:21 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:21 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:23 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:23 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:23 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:23 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:12:25 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1 Oct 8 12:12:25 Gateway dhcpd: uid lease 192.168.1.159 for client 78:4b:87:dd:aa:24 is duplicate on 192.168.1.0/24 Oct 8 12:12:29 Gateway dhcpd: DHCPREQUEST for 192.168.1.147 from 78:4b:87:dd:aa:24 via re1 Oct 8 12:12:29 Gateway dhcpd: DHCPACK on 192.168.1.147 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:12:29 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:12:36 Gateway dhcpd: DHCPREQUEST for 192.168.1.147 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2: wrong network. Oct 8 12:12:36 Gateway dhcpd: DHCPNAK on 192.168.1.147 to 78:4b:87:dd:aa:24 via re2 Oct 8 12:12:38 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re2 Oct 8 12:12:38 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:13:36 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:13:36 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:02 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:02 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:06 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:06 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:08 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:08 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:14:10 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2 Oct 8 12:22:48 Gateway dhcpd: DHCPREQUEST for 192.168.1.158 (192.168.1.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:22:48 Gateway dhcpd: DHCPACK on 192.168.1.158 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:15 Gateway dhcpd: DHCPREQUEST for 192.168.1.158 (192.168.1.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:15 Gateway dhcpd: DHCPACK on 192.168.1.158 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:24 Gateway dhcpd: DHCPREQUEST for 192.168.1.158 (192.168.1.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:24 Gateway dhcpd: DHCPACK on 192.168.1.158 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:45 Gateway dhcpd: DHCPREQUEST for 192.168.1.158 (192.168.1.1) from bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:23:45 Gateway dhcpd: DHCPACK on 192.168.1.158 to bc:e5:9f:6b:b5:9f (android-e83e37de1cbfd561) via re1 Oct 8 12:26:18 Gateway dhcpd: Internet Systems Consortium DHCP Server 4.2.8 Oct 8 12:26:18 Gateway dhcpd: Copyright 2004-2015 Internet Systems Consortium. Oct 8 12:26:18 Gateway dhcpd: All rights reserved. Oct 8 12:26:18 Gateway dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Oct 8 12:26:18 Gateway dhcpd: Internet Systems Consortium DHCP Server 4.2.8 Oct 8 12:26:18 Gateway dhcpd: Copyright 2004-2015 Internet Systems Consortium. Oct 8 12:26:18 Gateway dhcpd: All rights reserved. Oct 8 12:26:18 Gateway dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Oct 8 12:26:18 Gateway dhcpd: Wrote 26 leases to leases file. Oct 8 12:26:35 Gateway dhcpd: Listening on BPF/re2/10:fe:ed:06:ad:da/192.168.2.0/24 Oct 8 12:26:35 Gateway dhcpd: Sending on BPF/re2/10:fe:ed:06:ad:da/192.168.2.0/24 Oct 8 12:26:35 Gateway dhcpd: Listening on BPF/re1/10:fe:ed:06:b2:62/192.168.1.0/24 Oct 8 12:26:35 Gateway dhcpd: Sending on BPF/re1/10:fe:ed:06:b2:62/192.168.1.0/24 Oct 8 12:26:35 Gateway dhcpd: Sending on Socket/fallback/fallback-net Oct 8 12:29:08 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:29:08 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:29:20 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:29:20 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:29:25 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:29:25 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:30:00 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:30:00 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:35:27 Gateway dhcpd: DHCPREQUEST for 192.168.1.128 from 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:27 Gateway dhcpd: DHCPACK on 192.168.1.128 to 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:31 Gateway dhcpd: DHCPREQUEST for 192.168.1.128 from 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:31 Gateway dhcpd: DHCPACK on 192.168.1.128 to 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:35 Gateway dhcpd: DHCPREQUEST for 192.168.1.128 from 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:35 Gateway dhcpd: DHCPACK on 192.168.1.128 to 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:37 Gateway dhcpd: DHCPREQUEST for 192.168.1.128 from 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:35:37 Gateway dhcpd: DHCPACK on 192.168.1.128 to 20:16:d8:a6:15:8a (Nicole) via re1 Oct 8 12:36:51 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1 Oct 8 12:36:51 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:36:51 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:36:51 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:36:51 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:36:51 Gateway dhcpd: unexpected ICMP Echo Reply from XX.XX.XX.X Oct 8 12:36:52 Gateway dhcpd: DHCPOFFER on 192.168.1.147 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:36:54 Gateway dhcpd: DHCPREQUEST for 192.168.1.147 (192.168.1.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:36:54 Gateway dhcpd: DHCPACK on 192.168.1.147 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1 Oct 8 12:41:00 Gateway dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:00 Gateway dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:02 Gateway dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:02 Gateway dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:06 Gateway dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:06 Gateway dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:13 Gateway dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:13 Gateway dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:31 Gateway dhcpd: DHCPREQUEST for 192.168.1.133 from 00:d0:b8:0c:c5:9e via re1 Oct 8 12:41:31 Gateway dhcpd: DHCPACK on 192.168.1.133 to 00:d0:b8:0c:c5:9e via re1 Oct 8 12:51:16 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:51:16 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:51:18 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:51:18 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:51:20 Gateway dhcpd: DHCPREQUEST for 192.168.1.154 from 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:51:20 Gateway dhcpd: DHCPACK on 192.168.1.154 to 70:18:8b:4b:93:c9 (Romee) via re1 Oct 8 12:52:53 Gateway dhcpd: DHCPREQUEST for 192.168.1.130 from 34:64:a9:82:3a:68 (HP823A68) via re1 Oct 8 12:52:53 Gateway dhcpd: DHCPACK on 192.168.1.130 to 34:64:a9:82:3a:68 (HP823A68) via re1Diagnostics: System Activity
last pid: 30910; load averages: 0.00, 0.03, 0.00 up 0+16:03:00 13:01:24 139 processes: 3 running, 118 sleeping, 18 waiting Mem: 18M Active, 143M Inact, 123M Wired, 40M Buf, 1676M Free Swap: 4096M Total, 4096M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 155 ki31 0K 32K RUN 0 955:26 100.00% [idle{idle: cpu0}] 11 root 155 ki31 0K 32K CPU1 1 958:15 99.85% [idle{idle: cpu1}] 30202 root 20 0 223M 31756K piperd 0 0:00 0.10% php-fpm: pool lighty (php-fpm) 0 root -92 0 0K 176K - 0 1:05 0.00% [kernel{dummynet}] 12 root -60 - 0K 288K WAIT 1 1:00 0.00% [intr{swi4: clock}] 0 root -16 0 0K 176K swapin 0 0:54 0.00% [kernel{swapper}] 12 root -56 - 0K 288K WAIT 0 0:44 0.00% [intr{swi5: fast taskq}] 6 root -16 - 0K 16K pftm 1 0:16 0.00% [pf purge] 15 root -16 - 0K 16K - 1 0:12 0.00% [rand_harvestq] 24015 root 20 0 12456K 2124K select 0 0:04 0.00% /usr/local/sbin/apinger -c /var/etc/apinge 53973 root 52 20 17136K 2408K wait 1 0:03 0.00% /bin/sh /var/db/rrd/updaterrd.sh 21 root 16 - 0K 16K syncer 0 0:02 0.00% [syncer] 42186 nobody 20 0 30264K 4352K select 1 0:02 0.00% /usr/local/sbin/dnsmasq --all-servers --re 94287 root 20 0 28204K 18088K select 0 0:02 0.00% /usr/local/sbin/ntpd -g -c /var/etc/ntpd.c 4 root -16 - 0K 32K - 0 0:02 0.00% [cam{doneq0}] 50682 root 20 0 227M 40812K accept 1 0:01 0.00% /usr/local/bin/php 4 root -16 - 0K 32K - 0 0:01 0.00% [cam{scanner}] 20889 root 20 0 16804K 2292K bpf 0 0:01 0.00% /usr/local/sbin/filterlog -i pflog0 -p /vaStatus: System logs: General
Oct 7 21:00:02 syslogd: kernel boot file is /boot/kernel/kernel Oct 7 21:01:40 php-fpm[50839]: /index.php: User logged out for user 'XXXXXXXX' from: xx.xx.xxx.xx Oct 7 21:23:57 lighttpd[45562]: (request.c.1125) POST-request, but content-length missing -> 411 Oct 8 12:13:21 php-fpm[50839]: /index.php: Successful login for user 'XXXXXXXX' from: xx.xx.xxx.xx Oct 8 12:13:21 sshlockout[53945]: sshlockout/webConfigurator v3.0 starting up -
you do know machines tend to do stuff in the background even if your not actively having a browser session open.. I would track down some of the public IPs to who owns them, and look on your machines specifically for what processes have those connections open if your worried look on 0.1 and 1.12 for that they might be doing..
-
You are still getting DHCP requests from the same MAC address on re1 and re2 nearly simultaneously. As I said before, diagram your network. You have something seriously hosed. Probably at layer 2 (switching and wifi APs.)
Oct 8 12:12:07 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:07 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:17 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 (192.168.2.1) from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:17 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:21 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:21 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:23 Gateway dhcpd: DHCPREQUEST for 192.168.2.150 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:23 Gateway dhcpd: DHCPACK on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:23 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:23 Gateway dhcpd: DHCPOFFER on 192.168.2.150 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2
Oct 8 12:12:25 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re1
Oct 8 12:12:25 Gateway dhcpd: uid lease 192.168.1.159 for client 78:4b:87:dd:aa:24 is duplicate on 192.168.1.0/24
Oct 8 12:12:29 Gateway dhcpd: DHCPREQUEST for 192.168.1.147 from 78:4b:87:dd:aa:24 via re1
Oct 8 12:12:29 Gateway dhcpd: DHCPACK on 192.168.1.147 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1
Oct 8 12:12:29 Gateway dhcpd: DHCPOFFER on 192.168.1.159 to 78:4b:87:dd:aa:24 (android-737119de387638b0) via re1
Oct 8 12:12:36 Gateway dhcpd: DHCPREQUEST for 192.168.1.147 from 78:4b:87:dd:aa:24 (android-737119de387638b0) via re2: wrong network.
Oct 8 12:12:36 Gateway dhcpd: DHCPNAK on 192.168.1.147 to 78:4b:87:dd:aa:24 via re2
Oct 8 12:12:38 Gateway dhcpd: DHCPDISCOVER from 78:4b:87:dd:aa:24 via re2 -
You have something seriously hosed. Probably at layer 2 (switching and wifi APs.)
Yes, this.
Restarting DHCP did absolutely nothing to any kind of slowness. DHCP either works, or it doesn't. Systems are either online and have an IP, or they don't. There is no in between, DHCP can't make things slow, they either work or they don't.
The logs from DHCP are quite telling though, you have something seriously wrong on your network from the looks of it.
-
My guess is re1 and re2 are connected to the same unmanaged switch, but that's just a guess. A diagram would tell the tale.
-
My guess is re1 and re2 are connected to the same unmanaged switch, but that's just a guess.
They're somehow interconnected where they shouldn't be, for sure. Hard to say how or where without knowing more.
-
Oke, I will check all the cabling, and change the private wifi pass.
But still I think it's strange that something works for 16 days and then decides to stop working.My guess is re1 and re2 are connected to the same unmanaged switch, but that's just a guess. A diagram would tell the tale.
This is not possible, re2 is directly connected to the guest wifi
re1 is connected to a switch and then goes upstairs to the wifi there.No repeaters, extenders or anything.
[Added]
Decided to try something differed and switch the private wifi to re2
To see what happens and that the owners have no problems switching from one to the other. -
One nice thing about IP networking is there is no guesswork necessary. It is what it is.
I can never understand why people just "try things" to see if it works. Find the fault and fix it.
-
I can never understand why people just "try things" to see if it works. Find the fault and fix it.
I'm not just trying, I have the same type of network at home and that runs fine.
and here we do need a guest wifi, we do not wand the payment terminal and POS system on the same network as the guests.
But yes, I'm not a pro… I do this for "fun" but this is getting annoying.The problems started after a power outish.
At the power restore the old cases power supply and mainboard broke. -
Do you have the same SSIDs on the two wifi APs?
(I also don't understand why someone would hire someone who does this for "fun" when the problem is as important as PoS segmentation from guest networks, but that's probably just me.)
-
Do you have the same SSIDs on the two wifi APs?
Nope both have differed names and the private one has a WPA2 pass
Guest is open.
But the owners do switch between booth.(I also don't understand why someone would hire someone who does this for "fun" when the problem is as important as PoS segmentation from guest networks, but that's probably just me.)
They don't hire me, that ask of i know a solution for there request.
as there friend I showed them my setup and ask me to get it installed.Everything was running fine for almost two years. until the blackout.
-
Back on topic, re2 is now both wifi networks and for now everything seems to be working.
let's hope it will stay this way.
-
Umm. So your private and guest networks are now on the same subnet? Thought you wanted them isolated.
Since you refuse to provide requested details and just want to plug things into different ports instead of actually design it in a correct, secure manner, I guess a "good luck" is in order.
-
Umm. So your private and guest networks are now on the same subnet? Thought you wanted them isolated.
Only the wifi, lan is still a separate on and on there is the POS and Payment gateway.
And it should be temporarilySince you refuse to provide requested details and just want to plug things into different ports instead of actually design it in a correct, secure manner, I guess a "good luck" is in order.
I may have missed something, but I do not see any data requests in this topic.
Else I would post them no problem, I want to fix this.I think I'm misunderstood, I do not want to " just plug things into different ports" I do what to fix this, but the Lan is working fine so I can't just shutdown the network for the day. They are open all day and I'm trying to work without giving them problems.
Also I did check the lan today everything is fine, from the music pc to the pos everything is connected the right way.
So no, I have no idea why a phone would request a ip on both networks ate the same time.Again, If I can provide you some information that can make the situwation or problem more clear,
let me know and I will post it. -
Yeah. Make a diagram.
If you have both wifi networks on the same subnet, one open and one with WPA, they might as well both be open. They're the same network.
-
Guess I missed that one, but here you go.
This how is was this morning!
-
Back on topic, re2 is now both wifi networks and for now everything seems to be working.
So you moved your private wifi to re2? Now it's the same network as your guest wifi. Might as well not have a WPA passphrase on it.
And how did you do that without adding a switch to re2?
-
Back on topic, re2 is now both wifi networks and for now everything seems to be working.
So you moved your private wifi to re2? Now it's the same network as your guest wifi. Might as well not have a WPA passphrase on it.
And how did you do that without adding a switch to re2?
Yes I did, but once again it's temporarily.
I did add one, the image is the situation before moving the wifi.
aka the situation the problems started. -
BTW, I still see this
Oct 9 22:12:09 dhcpd: DHCPREQUEST for 192.168.2.18 from 20:16:d8:a6:15:8a (Nicole) via re2 Oct 9 22:12:09 dhcpd: DHCPACK on 192.168.2.18 to 20:16:d8:a6:15:8a (Nicole) via re2 Oct 9 22:12:09 dhcpd: DHCPREQUEST for 192.168.2.18 from 20:16:d8:a6:15:8a (Nicole) via re2 Oct 9 22:12:09 dhcpd: DHCPACK on 192.168.2.18 to 20:16:d8:a6:15:8a (Nicole) via re2Should be just one request and one pack right?
-
Don't know why the client is requesting twice. Either the client is requesting it twice or your network is sending it to the DHCP interface twice (like there's a layer 2 loop or something.)
