kouxp 发表于 2020-11-12 12:26:29

AX3000 5G断流因iPhone 12引起

AX3000升级到了最新固件后(当前版本 : 3.0.0.4.384_9923-g94ad322),5G断流严重,发现了个现象。。。

只有设备接近iPhone 12(ax 但是是80M)时,接近的设备和iPhone 12会同时出现断流现象,只要两个设备离开2米以上断流现象消除。。。

同时测试iPhone 6s,6sp,7p,Surface Pro7放在一起同时使用(除了Surface Pro7是ax,使用160MHz,剩下设备都是ac,都是使用80MHz),没有出现任何断流现象。。。

有没有大侠遇到同样情况, 有什么解决方案么?

kouxp 发表于 2020-11-12 12:35:58

系统记录

涵哥 发表于 2020-11-12 14:38:34

kouxp 发表于 2020-11-12 12:35
系统记录

不排除是兼容性问题,但是看到离开之后又能使用,感觉又不是,
如果可以先提供log看看

jtwgxs 发表于 2020-11-12 15:15:36

加厚不锈钢换水果12,P系列可多换1个小号的。

kouxp 发表于 2020-11-12 15:27:43

刚才又测试了下, 发现iPhone 12可以判定为5G断流激发设备,其与surface Pro7放在一块时都是同时断流。。。。咳。。。

kouxp 发表于 2020-11-12 15:28:24

今天测试所产生的记录
Nov 12 00:03:48 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 00:03:48 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 00:31:33 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 7C:B2:7D:AD:9C:3D, status: 0, reason: Unspecified reason (1)
Nov 12 04:04:21 WATCHDOG: retrieve firmware information
Nov 12 04:04:21 WATCHDOG: no need to upgrade firmware
Nov 12 04:04:51 WATCHDOG: retrieve firmware information
Nov 12 04:04:51 WATCHDOG: no need to upgrade firmware
Nov 12 08:11:11 kernel: eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link Up at 10 mbps full duplex
Nov 12 08:11:12 kernel: eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link DOWN.
Nov 12 08:11:17 kernel: eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link Up at 1000 mbps full duplex
Nov 12 08:11:36 kernel: eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link DOWN.
Nov 12 08:11:39 kernel: eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link Up at 1000 mbps full duplex
Nov 12 08:18:02 miniupnpd: upnp_event_process_notify: connect(192.168.50.195:2869): Connection timed out
Nov 12 08:18:02 miniupnpd: upnp_event_process_notify: connect(192.168.50.195:2869): Connection timed out
Nov 12 09:25:54 miniupnpd: PCP MAP: added mapping UDP 5353->192.168.50.156:5353 'PCP MAP aa36d443a504761339f06361'
Nov 12 09:45:30 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 8A:5E:B8:BE:85:AA, status: 0, reason: Disassociated due to inactivity (4)
Nov 12 10:14:18 wlceventd: wlceventd_proc_event(499): eth6: Auth 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 10:14:18 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 10:27:49 wlceventd: wlceventd_proc_event(499): eth6: Auth 7C:B2:7D:AD:9C:3D, status: Successful (0)
Nov 12 10:27:49 wlceventd: wlceventd_proc_event(509): eth6: ReAssoc 7C:B2:7D:AD:9C:3D, status: Successful (0)
Nov 12 10:28:24 wlceventd: wlceventd_proc_event(499): eth5: Auth 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 10:28:24 wlceventd: wlceventd_proc_event(527): eth5: Assoc 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 10:28:28 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind 24:05:0F:1A:F5:DC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 12 10:28:48 wlceventd: wlceventd_proc_event(499): eth5: Auth 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 10:28:48 wlceventd: wlceventd_proc_event(527): eth5: Assoc 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 10:28:52 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind 24:05:0F:1A:F5:DC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 12 10:31:40 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 10:31:40 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 10:35:16 wlceventd: wlceventd_proc_event(499): eth5: Auth 88:94:7E:A7:E5:81, status: Successful (0)
Nov 12 10:35:16 wlceventd: wlceventd_proc_event(527): eth5: Assoc 88:94:7E:A7:E5:81, status: Successful (0)
Nov 12 10:44:49 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3E:4C:79:64:D5:AE, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Nov 12 10:44:49 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 3E:4C:79:64:D5:AE, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 10:44:50 wlceventd: wlceventd_proc_event(499): eth6: Auth 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 10:44:50 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 11:03:26 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind 88:94:7E:A7:E5:81, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 12 11:07:01 wlceventd: wlceventd_proc_event(499): eth5: Auth 62:56:C3:B0:7B:A0, status: Successful (0)
Nov 12 11:07:01 wlceventd: wlceventd_proc_event(527): eth5: Assoc 62:56:C3:B0:7B:A0, status: Successful (0)
Nov 12 11:13:47 wlceventd: wlceventd_proc_event(481): eth5: Disassoc 62:56:C3:B0:7B:A0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:13:47 wlceventd: wlceventd_proc_event(481): eth5: Disassoc 62:56:C3:B0:7B:A0, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:13:47 wlceventd: wlceventd_proc_event(499): eth6: Auth 1A:60:1D:8F:C2:FF, status: Successful (0)
Nov 12 11:13:47 wlceventd: wlceventd_proc_event(527): eth6: Assoc 1A:60:1D:8F:C2:FF, status: Successful (0)
Nov 12 11:31:28 wlceventd: wlceventd_proc_event(499): eth6: Auth 8A:5E:B8:BE:85:AA, status: Successful (0)
Nov 12 11:31:28 wlceventd: wlceventd_proc_event(527): eth6: Assoc 8A:5E:B8:BE:85:AA, status: Successful (0)
Nov 12 11:36:27 wlceventd: wlceventd_proc_event(499): eth5: Auth 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 11:36:27 wlceventd: wlceventd_proc_event(527): eth5: Assoc 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 11:36:31 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind 24:05:0F:1A:F5:DC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 12 11:36:52 wlceventd: wlceventd_proc_event(499): eth5: Auth 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 11:36:52 wlceventd: wlceventd_proc_event(527): eth5: Assoc 24:05:0F:1A:F5:DC, status: Successful (0)
Nov 12 11:36:56 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind 24:05:0F:1A:F5:DC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 12 11:38:06 wlceventd: wlceventd_proc_event(499): eth6: Auth C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:38:06 wlceventd: wlceventd_proc_event(527): eth6: Assoc C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:40:04 wlceventd: wlceventd_proc_event(499): eth5: Auth C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:40:04 wlceventd: wlceventd_proc_event(481): eth6: Disassoc C8:F7:33:A2:26:23, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:40:04 wlceventd: wlceventd_proc_event(481): eth6: Disassoc C8:F7:33:A2:26:23, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:40:04 wlceventd: wlceventd_proc_event(527): eth5: Assoc C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:41:12 wlceventd: wlceventd_proc_event(499): eth6: Auth C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:41:12 wlceventd: wlceventd_proc_event(527): eth6: Assoc C8:F7:33:A2:26:23, status: Successful (0)
Nov 12 11:41:12 wlceventd: wlceventd_proc_event(481): eth5: Disassoc C8:F7:33:A2:26:23, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:41:12 wlceventd: wlceventd_proc_event(481): eth5: Disassoc C8:F7:33:A2:26:23, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 12 11:41:28 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind C8:F7:33:A2:26:23, status: 0, reason: Unspecified reason (1)
Nov 12 11:42:42 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 9) Link DOWN.
Nov 12 12:39:15 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 12:39:19 miniupnpd: upnp_event_process_notify: connect(192.168.50.75:2869): Connection timed out
Nov 12 12:55:53 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3E:4C:79:64:D5:AE, status: 0, reason: Disassociated due to inactivity (4)
Nov 12 12:57:08 wlceventd: wlceventd_proc_event(499): eth6: Auth 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 12:57:08 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3E:4C:79:64:D5:AE, status: Successful (0)
Nov 12 13:06:02 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 9) Link Up at 1000 mbps full duplex
Nov 12 13:06:03 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 9) Link DOWN.
Nov 12 13:06:31 kernel: eth1 (Int switch port: 1) (Logical Port: 1) (phyId: 9) Link Up at 1000 mbps full duplex
Nov 12 13:07:46 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3E:4C:79:64:D5:AE, status: 0, reason: Disassociated due to inactivity (4)
Nov 12 13:35:14 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind D2:A3:C8:A9:1B:62, status: 0, reason: Disassociated due to inactivity (4)
Nov 12 13:54:36 kernel: eth2 (Int switch port: 2) (Logical Port: 2) (phyId: a) Link Up at 100 mbps full duplex
Nov 12 13:54:42 kernel: eth2 (Int switch port: 2) (Logical Port: 2) (phyId: a) Link DOWN.
Nov 12 13:54:44 kernel: eth2 (Int switch port: 2) (Logical Port: 2) (phyId: a) Link Up at 100 mbps full duplex
Nov 12 13:59:58 kernel: eth2 (Int switch port: 2) (Logical Port: 2) (phyId: a) Link DOWN.
Nov 12 15:13:16 miniupnpd: PCP MAP: added mapping UDP 5353->192.168.50.251:5353 'PCP MAP ea479a351ec2b25b0982ba92'
Nov 12 15:13:19 miniupnpd: PCP MAP: added mapping UDP 5354->192.168.50.32:5353 'PCP MAP 56d6d88bae0d196e52d4f9bc'


Dr.Antenna 发表于 2020-11-12 15:34:13

kouxp 发表于 2020-11-12 15:27
刚才又测试了下, 发现iPhone 12可以判定为5G断流激发设备,其与surface Pro7放在一块时都是同时断流。。。 ...
真的是重大发现啊:victory:

kouxp 发表于 2020-11-12 15:49:37

Dr.Antenna 发表于 2020-11-12 15:34
真的是重大发现啊

5G偶尔还是会出现断流的, 只是一碰到这个激发器立马断流。。。
这个发现对以后测试路由器应该还是很有效的吧。。。。呵呵

Dr.Antenna 发表于 2020-11-12 15:59:48

kouxp 发表于 2020-11-12 15:49
5G偶尔还是会出现断流的, 只是一碰到这个激发器立马断流。。。
这个发现对以后测试路由器应该还是很有效 ...

赶紧联系苹果官方,有重大发现会给奖金的;P

ray5460 发表于 2020-11-16 16:19:36

看不懂,但表示牛逼。
页: [1] 2
查看完整版本: AX3000 5G断流因iPhone 12引起