iKuai爱快流控路由

标题: 爱快2.7.11 AP 用其他品牌的，DHCP不能分配地址，求解？？ [打印本页]
作者: wghl2003    时间: 2017-9-12 15:01
标题: 爱快2.7.11 AP 用其他品牌的，DHCP不能分配地址，求解？？
本帖最后由 wghl2003 于 2017-9-12 15:26 编辑

爱快2.7.11 AP 用其他品牌的，DHCP不能分配地址，求解？？

2.7.10 也存在这个问题，导致企业版不敢往上升了。

网络环境：lan1 有线网络，lan2 下接POE交换机，再通过poe交换机链接到各终端AP

查看dhcp日志如下：
2017-09-12 14:59:55
DHCPDISCOVER from 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.180 to 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:55
DHCPDISCOVER from 90:67:1c:c2:21:9f (android-18d07c20ad66839d) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.182 to 90:67:1c:c2:21:9f (android-18d07c20ad66839d) via lan2
2017-09-12 14:59:55
DHCPDISCOVER from f0:1b:6c:14:43:c8 (android-1c1b0a0315b0efa3) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.251 to f0:1b:6c:14:43:c8 (android-1c1b0a0315b0efa3) via lan2
2017-09-12 14:59:55
DHCPDISCOVER from e4:47:90:d0:51:ab (android-5ee9e66785e947b0) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.135 to e4:47:90:d0:51:ab (android-5ee9e66785e947b0) via lan2
2017-09-12 14:59:55
DHCPDISCOVER from 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.139 to 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:55
DHCPDISCOVER from 28:e1:4c:38:66:d7 (iPhone) via lan2
2017-09-12 14:59:55
DHCPOFFER on 172.16.7.204 to 28:e1:4c:38:66:d7 (iPhone) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.139 to 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from c0:07:8b:8c:7f:51 (android-5417becfca9b3609) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.132 to c0:07:8b:8c:7f:51 (android-5417becfca9b3609) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from b8:37:65:db:9e:51 (android-151fccd20df2adc9) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.240 to b8:37:65:db:9e:51 (android-151fccd20df2adc9) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from dc:6d:cd:79:6b:1f (android-7fbe4c78ff2239bf) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.131 to dc:6d:cd:79:6b:1f (android-7fbe4c78ff2239bf) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from 64:b0:a6:c7:cd:38 (iPhone-2) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.185 to 64:b0:a6:c7:cd:38 (iPhone-2) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from b8:37:65:bd:2b:5d (android-96bb1c0ac1fc6a79) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.183 to b8:37:65:bd:2b:5d (android-96bb1c0ac1fc6a79) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from 10:41:7f:8b:7e:6e (iPhone-101) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.173 to 10:41:7f:8b:7e:6e (iPhone-101) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from 18:e2:9f:c8:a5:dd (vivo-Y55A) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.175 to 18:e2:9f:c8:a5:dd (vivo-Y55A) via lan2
2017-09-12 14:59:52
DHCPDISCOVER from 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2
2017-09-12 14:59:52
DHCPOFFER on 172.16.7.137 to 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 28:e1:4c:38:66:d7 (iPhone) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.204 to 28:e1:4c:38:66:d7 (iPhone) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from c0:07:8b:8c:7f:51 (android-5417becfca9b3609) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.132 to c0:07:8b:8c:7f:51 (android-5417becfca9b3609) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 18:e2:9f:c8:a5:dd (vivo-Y55A) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.175 to 18:e2:9f:c8:a5:dd (vivo-Y55A) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.139 to 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 64:a5:c3:c3:c9:34 (iPhone-8) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.174 to 64:a5:c3:c3:c9:34 (iPhone-8) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from cc:2d:83:0b:d3:ab (android-f0838df66b8bc67a) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.134 to cc:2d:83:0b:d3:ab (android-f0838df66b8bc67a) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.180 to 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.137 to 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.139 to 40:33:1a:a1:f1:39 (iPhone) via lan2
2017-09-12 14:59:49
DHCPDISCOVER from 74:23:44:2e:6f:d0 (MIMAX-xiaomishouji) via lan2
2017-09-12 14:59:49
DHCPOFFER on 172.16.7.138 to 74:23:44:2e:6f:d0 (MIMAX-xiaomishouji) via lan2
2017-09-12 14:59:46
DHCPDISCOVER from 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:46
DHCPOFFER on 172.16.7.180 to 00:b3:62:a9:e8:46 (iPhone) via lan2
2017-09-12 14:59:46
DHCPDISCOVER from b8:37:65:ae:c4:17 (android-2e93c2f9adda6c06) via lan2
2017-09-12 14:59:46
DHCPOFFER on 172.16.7.176 to b8:37:65:ae:c4:17 (android-2e93c2f9adda6c06) via lan2
2017-09-12 14:59:46
DHCPREQUEST for 192.168.1.118 from 8c:0d:76:af:c4:ae via lan2: wrong network.
2017-09-12 14:59:46
DHCPNAK on 192.168.1.118 to 8c:0d:76:af:c4:ae via lan2
2017-09-12 14:59:46
DHCPDISCOVER from 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2
2017-09-12 14:59:46
DHCPOFFER on 172.16.7.137 to 8c:0d:76:af:c4:ae (HUAWEI_P9_Plus) via lan2

退回2.7.8版本，无线上网正常。

作者: wghl2003    时间: 2017-9-12 15:08
选一个mac地址，查看其全部记录如下：
2017-09-12 15:06:58
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:58
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:49
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:49
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:43
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:06:43
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:06:43
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:43
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:40
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:06:40
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:06:25
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:25
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:15
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:15
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:12
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:06:12
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:06:12
DHCPDISCOVER from bc:3a:ea:13:86:35 via lan2
2017-09-12 15:06:12
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:06:06
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:06:06
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:51
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:51
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:45
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:45
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:42
DHCPOFFER on 172.16.7.82 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:39
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:05:39
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:39
DHCPDISCOVER from bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:36
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:05:36
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:21
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:21
DHCPOFFER on 172.16.7.81 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:12
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:12
DHCPOFFER on 172.16.7.81 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:09
DHCPDISCOVER from bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:09
DHCPOFFER on 172.16.7.81 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:05:06
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:05:06
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:05:03
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:05:03
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:04:47
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:47
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:41
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:41
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:35
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:04:35
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:04:35
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:35
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:32
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:04:32
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:04:17
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:17
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:08
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:08
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:04:05
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:04:05
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:04:05
DHCPDISCOVER from bc:3a:ea:13:86:35 via lan2
2017-09-12 15:04:05
DHCPOFFER on 172.16.7.217 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:59
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:03:59
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:03:47
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:47
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:37
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:37
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:31
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:03:31
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:03:31
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:31
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:28
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:03:28
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:03:13
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:13
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:04
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:04
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:01
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:03:01
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:58
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:02:58
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:02:55
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:02:55
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:02:40
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:40
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:34
DHCPDISCOVER from bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:34
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:28
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:02:28
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
2017-09-12 15:02:28
DHCPDISCOVER from bc:3a:ea:13:86:35 via lan2
2017-09-12 15:02:28
DHCPOFFER on 172.16.7.143 to bc:3a:ea:13:86:35 (android-4cb7204588c3ddc7) via lan2
2017-09-12 15:02:25
DHCPREQUEST for 192.168.1.100 from bc:3a:ea:13:86:35 via lan2: wrong network.
2017-09-12 15:02:25
DHCPNAK on 192.168.1.100 to bc:3a:ea:13:86:35 via lan2
作者: 476969516    时间: 2017-9-12 15:41
爱快加TP没事路过
作者: 85619001    时间: 2017-9-12 15:44
没遇到过   我小路由AP模式 用爱快DHCP分配 正常的很
作者: somalia    时间: 2017-9-12 15:44
同样的问题 2.7.9开始出问题，2.7.8是正常的。
作者: wghl2003    时间: 2017-9-12 16:03
somalia 发表于 2017-9-12 15:44
同样的问题 2.7.9开始出问题，2.7.8是正常的。

你想办法解决了没？ 我现在郁闷死哒 。
作者: wghl2003    时间: 2017-9-12 16:08
更奇葩的问题出现了，跟踪了下IP获取记录、、、、居然是这样的，难道是有个什么判断没有写，导致一直在发现，获取IP????? 详细看日志：
2017-09-12 16:06:55
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:55
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:52
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:52
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:49
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:49
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:43
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:30
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:30
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:24
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:24
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:18
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:18
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:12
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:12
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:09
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:09
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:03
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:03
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:06:00
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:51
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:51
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:42
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:42
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:36
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:36
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:33
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:33
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:27
DHCPDISCOVER from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:27
DHCPOFFER on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:24
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:24
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:21
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:21
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:18
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 via lan2
2017-09-12 16:05:18
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:18
DHCPREQUEST for 172.16.4.141 (172.16.0.1) from 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
2017-09-12 16:05:18
DHCPACK on 172.16.4.141 to 84:9f:b5:a2:ee:32 (HUAWEI_Mate_9) via lan2
作者: 10000    时间: 2017-9-12 16:09
LAN2是172网段吧？
作者: somalia    时间: 2017-9-12 16:12
wghl2003 发表于 2017-9-12 16:03
你想办法解决了没？ 我现在郁闷死哒 。

我现在不管是企业版 还是免费版 都停留在2.7.8  不敢升了
作者: 爱快技术支持10    时间: 2017-9-12 17:32
楼主你好
DHCPREQUEST for 192.168.1.118 from 8c:0d:76:af:c4:ae via lan2: wrong network.
根据这个报错看你本地应该有其他的DHCP导致地址下发异常
作者: wghl2003    时间: 2017-9-12 17:47
wghl2003 发表于 2017-9-12 16:03
你想办法解决了没？ 我现在郁闷死哒 。

降级就正常了，用2.7.8就正常
作者: wghl2003    时间: 2017-9-12 17:49
爱快技术支持10 发表于 2017-9-12 17:32
楼主你好
DHCPREQUEST for 192.168.1.118 from 8c:0d:76:af:c4:ae via lan2: wrong network.
根据这个报错 ...

已经确认不是本地有DHCP的问题，因为降级到2.7.8就正常了，同样的环境，不修改任何配置。 用路由检测DHCP服务正常。

SO  ,还是请爱快检查下DHCP吧。。。 呵呵。。
我的环境是  lan2--poe交换机---AP---客户端，客户端总在获取IP，但是不能获得任何IP
作者: 爱快技术支持10    时间: 2017-9-12 17:54
wghl2003 发表于 2017-9-12 17:49
已经确认不是本地有DHCP的问题，因为降级到2.7.8就正常了，同样的环境，不修改任何配置。 用路由检测DHCP ...

你好，现在你联系下我们QQ4008773227，提供现场我们找开发看下
作者: wghl2003    时间: 2017-9-12 18:36
爱快技术支持10 发表于 2017-9-12 17:54
你好，现在你联系下我们QQ4008773227，提供现场我们找开发看下

网络环境，lan2-poe交换机--AP 使用2.7.8 版本时，终端可以通过AP直接获得IP，2.7.10和2.7.11版本，同样配置下，不能获得IP 。  AP不是爱快品牌，原来已经装好的，更换AP也很麻烦。。。。  2.7.11环境下，有 个奇怪的问题出现了，我拿爱快的AP接入该POE交换机，终端可以正常获取IP了。。。。  而非爱快品牌的就显示网络故障，请技术指导指导。  

你们的400很难接入哦。



欢迎光临 iKuai爱快流控路由 (https://bbs.ikuai8.com/) Powered by Discuz! X3.3