您尚未登录。

#1 2018-09-11 20:07:31

hayu
会员
注册时间: 2015-07-02
帖子: 14

奇怪的问题:网速超过100Mps就会断网

网络是学校的dhcp环境(1Gps端口),最近一次滚动更新后就发生这样的事情了,只要我网速超过100Mps就会断网分不到ip. 虽然绝大部分时间不会用到这么大的带宽,但是有的时候进行一些内网文件传输还有p2p下载的时候可能超过这个阈值,电脑会马上断网.重启就能恢复.只是重启dhcpcd没有效果.

由于断网了我也没法在网上找一些教程来诊断查找原因,很无解.

离线

#2 2018-09-11 20:44:20

hayu
会员
注册时间: 2015-07-02
帖子: 14

Re: 奇怪的问题:网速超过100Mps就会断网

经过一些搜索之后我发现可能的问题是"Configuring and Troubleshooting Ethernet 10/100/1000Mb Half/Full Duplex Auto-Negotiation",现在安装了个networkmanager,把Auto-Negotiation设置了手动,1Gbps,Duplex Full,问题解决了.不过我任然不懂这个Auto-Negotiation是啥意思,为啥我之前只用开启dhcpcd,使用默认设置没问题,  还有看网上说Auto-Negotiation的设置应该与另一端一致,另一端是哪?交换机吗?

离线

#3 2018-09-11 22:10:30

依云
a.k.a. 百合仙子
所在地: 一个等待妹纸出现的地方
注册时间: 2011-08-21
帖子: 4,836
个人网站

Re: 奇怪的问题:网速超过100Mps就会断网

看一下内核日志。断网的时候看一下接口还在不在,在的话抓一下包。

离线

#4 2018-09-12 12:16:58

hayu
会员
注册时间: 2015-07-02
帖子: 14

Re: 奇怪的问题:网速超过100Mps就会断网

依云 说:

看一下内核日志。断网的时候看一下接口还在不在,在的话抓一下包。

断网的时候没ip没路由. 现在基本确定了就是auto-negotiation的设置问题. 只是我不清楚为啥之前默认的设置能很好的工作,而最近才突然出现这个bug.而且这个功能我也是第一次接触.对这个概念一无所知.

每次启动log里面都会有这么一段,包括我换networkmanager并且设置能正常使用之后,貌似这一段不是导致网络中断的原因.

Sep 11 17:15:59 ARCH406 kernel: ------------[ cut here ]------------
Sep 11 17:15:59 ARCH406 kernel: NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 timed out
Sep 11 17:15:59 ARCH406 kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x21a/0x220
Sep 11 17:15:59 ARCH406 kernel: Modules linked in: cfg80211 8021q mrp intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_g>
Sep 11 17:15:59 ARCH406 kernel:  crc16 mbcache jbd2 fscrypto sd_mod hid_generic ata_generic pata_acpi usbhid hid ata_piix ehci_pci xhci_pci crc32c_intel libata xhci_>
Sep 11 17:15:59 ARCH406 kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.18.6-arch1-1-ARCH #1
Sep 11 17:15:59 ARCH406 kernel: Hardware name: System manufacturer System Product Name/P8B75-M LX PLUS, BIOS 0701 02/05/2013
Sep 11 17:15:59 ARCH406 kernel: RIP: 0010:dev_watchdog+0x21a/0x220
Sep 11 17:15:59 ARCH406 kernel: Code: 49 63 4c 24 e8 eb 8c 4c 89 ef c6 05 eb ea aa 00 01 e8 5a eb fc ff 89 d9 4c 89 ee 48 c7 c7 38 dc 8f a6 48 89 c2 e8 40 a7 a2 ff <>
Sep 11 17:15:59 ARCH406 kernel: RSP: 0018:ffff92579ea03e78 EFLAGS: 00010286
Sep 11 17:15:59 ARCH406 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000103
Sep 11 17:15:59 ARCH406 kernel: RDX: 0000000000000103 RSI: 00000000000000f6 RDI: 00000000ffffffff
Sep 11 17:15:59 ARCH406 kernel: RBP: ffff925794c0445c R08: 0000000000000001 R09: 0000000000000320
Sep 11 17:15:59 ARCH406 kernel: R10: 0000000000000004 R11: 0000000000000000 R12: ffff925794c04478
Sep 11 17:15:59 ARCH406 kernel: R13: ffff925794c04000 R14: 0000000000000001 R15: ffff925792e9ae80
Sep 11 17:15:59 ARCH406 kernel: FS:  0000000000000000(0000) GS:ffff92579ea00000(0000) knlGS:0000000000000000
Sep 11 17:15:59 ARCH406 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 11 17:15:59 ARCH406 kernel: CR2: 00002143adf34000 CR3: 000000001220a003 CR4: 00000000001606f0
Sep 11 17:15:59 ARCH406 kernel: Call Trace:
Sep 11 17:15:59 ARCH406 kernel:  <IRQ>
Sep 11 17:15:59 ARCH406 kernel:  ? qdisc_reset+0xe0/0xe0
Sep 11 17:15:59 ARCH406 kernel:  ? qdisc_reset+0xe0/0xe0
Sep 11 17:15:59 ARCH406 kernel:  call_timer_fn+0x2b/0x150
Sep 11 17:15:59 ARCH406 kernel:  ? qdisc_reset+0xe0/0xe0
Sep 11 17:15:59 ARCH406 kernel:  expire_timers+0x99/0x110
Sep 11 17:15:59 ARCH406 kernel:  run_timer_softirq+0x8a/0x160
Sep 11 17:15:59 ARCH406 kernel:  ? sched_clock+0x5/0x10
Sep 11 17:15:59 ARCH406 kernel:  ? sched_clock_cpu+0xe/0xd0
Sep 11 17:15:59 ARCH406 kernel:  __do_softirq+0x10d/0x30d
Sep 11 17:15:59 ARCH406 kernel:  irq_exit+0xd9/0xf0
Sep 11 17:15:59 ARCH406 kernel:  smp_apic_timer_interrupt+0x87/0x170
Sep 11 17:15:59 ARCH406 kernel:  apic_timer_interrupt+0xf/0x20
Sep 11 17:15:59 ARCH406 kernel:  </IRQ>
Sep 11 17:15:59 ARCH406 kernel: RIP: 0010:cpuidle_enter_state+0xb7/0x2e0
Sep 11 17:15:59 ARCH406 kernel: Code: e8 3e ef ad ff 80 7c 24 03 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 fb 01 00 00 31 ff e8 90 e2 b3 ff fb 66 0f 1f 44 00 00 <>
Sep 11 17:15:59 ARCH406 kernel: RSP: 0018:ffffffffa6a03e78 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
Sep 11 17:15:59 ARCH406 kernel: RAX: ffff92579ea00000 RBX: 000000ef7959eb94 RCX: 000000000000001f
Sep 11 17:15:59 ARCH406 kernel: RDX: 000000ef7959eb94 RSI: ffffffffa688051e RDI: ffffffffa68884ed
Sep 11 17:15:59 ARCH406 kernel: RBP: 0000000000000004 R08: 000003034d703380 R09: 0000000000002075
Sep 11 17:15:59 ARCH406 kernel: R10: 0000000000002178 R11: ffff92579ea20a68 R12: ffff92579ea2bb38
Sep 11 17:15:59 ARCH406 kernel: R13: ffffffffa6aaecb8 R14: 000000ef78892600 R15: 00000000b9ee5c6e
Sep 11 17:15:59 ARCH406 kernel:  ? cpuidle_enter_state+0x92/0x2e0
Sep 11 17:15:59 ARCH406 kernel:  do_idle+0x20a/0x240
Sep 11 17:15:59 ARCH406 kernel:  cpu_startup_entry+0x6f/0x80
Sep 11 17:15:59 ARCH406 kernel:  start_kernel+0x515/0x535
Sep 11 17:15:59 ARCH406 kernel:  secondary_startup_64+0xa5/0xb0
Sep 11 17:15:59 ARCH406 kernel: ---[ end trace fa82a1040e64e9f4 ]---

这部分是日志中dhcpcd相关的部分

Sep 11 16:58:55 ARCH406 systemd[1]: Starting dhcpcd on all interfaces...
Sep 11 16:58:55 ARCH406 dhcpcd[350]: dev: loaded udev
Sep 11 16:58:55 ARCH406 dhcpcd[350]: forked to background, child pid 370
Sep 11 16:58:55 ARCH406 systemd[1]: Started dhcpcd on all interfaces.
Sep 11 16:58:56 ARCH406 dhcpcd[370]: enp3s0: waiting for carrier
Sep 11 16:58:59 ARCH406 dhcpcd[370]: enp3s0: carrier acquired
Sep 11 16:58:59 ARCH406 dhcpcd[370]: DUID 00:01:00:01:22:99:10:f2:60:a4:4c:cb:f3:4f
Sep 11 16:58:59 ARCH406 dhcpcd[370]: enp3s0: IAID 4c:cb:f3:4f
Sep 11 16:58:59 ARCH406 dhcpcd[370]: enp3s0: adding address fe80::4824:**.**.**
Sep 11 16:59:00 ARCH406 dhcpcd[370]: enp3s0: soliciting an IPv6 router
Sep 11 16:59:00 ARCH406 dhcpcd[370]: enp3s0: rebinding lease of 222.**.**.**
Sep 11 16:59:00 ARCH406 dhcpcd[370]: enp3s0: probing address 222.**.**.**/24
Sep 11 16:59:01 ARCH406 dhcpcd[370]: enp3s0: Router Advertisement from fe80::da67:**.**.**
Sep 11 16:59:01 ARCH406 dhcpcd[370]: enp3s0: adding address 2001:da8:**.**.**/64
Sep 11 16:59:01 ARCH406 dhcpcd[370]: enp3s0: adding route to 2001:da8:**.**.**::/64
Sep 11 16:59:01 ARCH406 dhcpcd[370]: enp3s0: adding default route via fe80::da67:**.**.**
Sep 11 16:59:06 ARCH406 dhcpcd[370]: enp3s0: leased 222.**.**.** for 259200 seconds
Sep 11 16:59:06 ARCH406 dhcpcd[370]: enp3s0: adding route to 222.**.**.**/24
Sep 11 16:59:06 ARCH406 dhcpcd[370]: enp3s0: adding default route via 222.**.**.**
Sep 11 17:19:17 ARCH406 dhcpcd[370]: enp3s0: fe80::da67:**.**.** is unreachable, expiring it
Sep 11 17:19:37 ARCH406 sudo[4285]:    xiayu : TTY=pts/0 ; PWD=/home/xiayu ; USER=root ; COMMAND=/usr/bin/systemctl restart dhcpcd.service
Sep 11 17:19:37 ARCH406 systemd[1]: Stopping dhcpcd on all interfaces...
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: sending signal TERM to pid 370
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: waiting for pid 370 to exit
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: sending signal TERM to pid 370
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: waiting for pid 370 to exit
Sep 11 17:19:37 ARCH406 dhcpcd[370]: received SIGTERM, stopping
Sep 11 17:19:37 ARCH406 dhcpcd[370]: enp3s0: removing interface
Sep 11 17:19:37 ARCH406 dhcpcd[370]: dhcpcd exited
Sep 11 17:19:37 ARCH406 systemd[1]: Stopped dhcpcd on all interfaces.
Sep 11 17:19:37 ARCH406 systemd[1]: Starting dhcpcd on all interfaces...
Sep 11 17:19:37 ARCH406 dhcpcd[4290]: dev: loaded udev
Sep 11 17:19:37 ARCH406 dhcpcd[4290]: forked to background, child pid 4291
Sep 11 17:19:37 ARCH406 systemd[1]: Started dhcpcd on all interfaces.
Sep 11 17:19:37 ARCH406 dhcpcd[4291]: DUID 00:01:00:01:22:99:10:f2:60:a4:4c:cb:f3:4f
Sep 11 17:19:37 ARCH406 dhcpcd[4291]: enp3s0: IAID 4c:cb:f3:4f
Sep 11 17:19:38 ARCH406 dhcpcd[4291]: enp3s0: soliciting an IPv6 router
Sep 11 17:19:38 ARCH406 dhcpcd[4291]: enp3s0: rebinding lease of 222.**.**.**
Sep 11 17:19:43 ARCH406 dhcpcd[4291]: enp3s0: DHCP lease expired
Sep 11 17:19:43 ARCH406 dhcpcd[4291]: enp3s0: soliciting a DHCP lease
Sep 11 17:19:50 ARCH406 dhcpcd[4291]: enp3s0: no IPv6 Routers available

17:19:17 这个位置应该是断网开始的时间,之后我试着重启了一次dhcpcd没效果.

这是这个时间点附近的日志文件

Sep 11 17:15:59 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:16:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:16:22 ARCH406 env[372]: 2018/09/11 17:16:22 tcp:127.0.0.1:41354 accepted tcp:clients4.google.com:443
Sep 11 17:16:29 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:16:41 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:16:53 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:17:02 ARCH406 env[372]: 2018/09/11 17:17:02 tcp:127.0.0.1:41680 accepted tcp:www.google.com:443
Sep 11 17:17:04 ARCH406 env[372]: 2018/09/11 17:17:04 [Warning] [4014975058] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: operation was canceled] > Retry: all retry attempts failed
Sep 11 17:17:05 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:17:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:17:29 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:17:37 ARCH406 env[372]: 2018/09/11 17:17:37 tcp:127.0.0.1:41962 accepted tcp:clients4.google.com:443
Sep 11 17:17:41 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:17:44 ARCH406 env[372]: 2018/09/11 17:17:44 [Warning] [449836142] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: operation was canceled] > Retry: all retry attempts failed
Sep 11 17:17:53 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:18:05 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:18:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:18:19 ARCH406 env[372]: 2018/09/11 17:18:19 [Warning] [3713900026] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: operation was canceled] > Retry: all retry attempts failed
Sep 11 17:18:29 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:18:41 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:18:46 ARCH406 env[372]: 2018/09/11 17:18:46 tcp:127.0.0.1:42516 accepted tcp:clients4.google.com:443
Sep 11 17:18:53 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:19:05 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:19:17 ARCH406 dhcpcd[370]: enp3s0: fe80::da67:d9ff:fe70:e941 is unreachable, expiring it
Sep 11 17:19:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:19:28 ARCH406 env[372]: 2018/09/11 17:19:28 [Warning] [3038312972] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: operation was canceled] > Retry: all retry attempts failed
Sep 11 17:19:29 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:19:37 ARCH406 sudo[4285]:    xiayu : TTY=pts/0 ; PWD=/home/xiayu ; USER=root ; COMMAND=/usr/bin/systemctl restart dhcpcd.service
Sep 11 17:19:37 ARCH406 systemd[1]: Stopping dhcpcd on all interfaces...
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: sending signal TERM to pid 370
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: waiting for pid 370 to exit
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: sending signal TERM to pid 370
Sep 11 17:19:37 ARCH406 dhcpcd[4288]: waiting for pid 370 to exit
Sep 11 17:19:37 ARCH406 dhcpcd[370]: received SIGTERM, stopping
Sep 11 17:19:37 ARCH406 dhcpcd[370]: enp3s0: removing interface
Sep 11 17:19:37 ARCH406 dhcpcd[370]: dhcpcd exited
Sep 11 17:19:37 ARCH406 systemd[1]: Stopped dhcpcd on all interfaces.
Sep 11 17:19:37 ARCH406 systemd[1]: Starting dhcpcd on all interfaces...
Sep 11 17:19:37 ARCH406 dhcpcd[4290]: dev: loaded udev
Sep 11 17:19:37 ARCH406 dhcpcd[4290]: forked to background, child pid 4291
Sep 11 17:19:37 ARCH406 systemd[1]: Started dhcpcd on all interfaces.
Sep 11 17:19:37 ARCH406 dhcpcd[4291]: DUID 00:01:00:01:22:99:10:f2:60:a4:4c:cb:f3:4f
Sep 11 17:19:37 ARCH406 dhcpcd[4291]: enp3s0: IAID 4c:cb:f3:4f
Sep 11 17:19:38 ARCH406 dhcpcd[4291]: enp3s0: soliciting an IPv6 router
Sep 11 17:19:38 ARCH406 dhcpcd[4291]: enp3s0: rebinding lease of 222.**.**.**
Sep 11 17:19:43 ARCH406 dhcpcd[4291]: enp3s0: DHCP lease expired
Sep 11 17:19:43 ARCH406 dhcpcd[4291]: enp3s0: soliciting a DHCP lease
Sep 11 17:19:50 ARCH406 dhcpcd[4291]: enp3s0: no IPv6 Routers available
Sep 11 17:19:59 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:21:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:22:47 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:24:35 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:26:17 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:29:11 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:37:47 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 17:47:35 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 18:07:53 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 18:27:11 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 18:38:41 ARCH406 kernel: r8169 0000:03:00.0 enp3s0: link up
Sep 11 18:42:45 ARCH406 env[372]: 2018/09/11 18:42:45 tcp:127.0.0.1:42810 accepted tcp:mtalk.google.com:5228
Sep 11 18:42:45 ARCH406 env[372]: 2018/09/11 18:42:45 tcp:127.0.0.1:42812 accepted tcp:accounts.google.com:443
Sep 11 18:42:45 ARCH406 env[372]: 2018/09/11 18:42:45 tcp:127.0.0.1:42816 accepted tcp:ssl.google-analytics.com:443
Sep 11 18:42:46 ARCH406 env[372]: 2018/09/11 18:42:46 tcp:127.0.0.1:42818 rejected  Proxy|Socks: insufficient header > EOF
Sep 11 18:42:47 ARCH406 env[372]: 2018/09/11 18:42:47 [Warning] [794481948] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:42:48 ARCH406 env[372]: 2018/09/11 18:42:48 tcp:127.0.0.1:42820 accepted tcp:accounts.google.com:443
Sep 11 18:42:50 ARCH406 env[372]: 2018/09/11 18:42:50 [Warning] [2884927300] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:42:52 ARCH406 env[372]: 2018/09/11 18:42:52 tcp:127.0.0.1:42826 accepted tcp:accounts.google.com:443
Sep 11 18:42:54 ARCH406 env[372]: 2018/09/11 18:42:54 [Warning] [1526209081] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:43:02 ARCH406 env[372]: 2018/09/11 18:43:02 tcp:127.0.0.1:42828 accepted tcp:accounts.google.com:443
Sep 11 18:43:04 ARCH406 env[372]: 2018/09/11 18:43:04 [Warning] [1503182418] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:43:10 ARCH406 env[372]: 2018/09/11 18:43:10 tcp:127.0.0.1:42830 accepted tcp:mtalk.google.com:443
Sep 11 18:43:12 ARCH406 env[372]: 2018/09/11 18:43:12 [Warning] [1275083374] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:43:12 ARCH406 env[372]: 2018/09/11 18:43:12 tcp:127.0.0.1:42832 rejected  Proxy|Socks: insufficient header > EOF
Sep 11 18:43:31 ARCH406 env[372]: 2018/09/11 18:43:31 tcp:127.0.0.1:42834 accepted tcp:accounts.google.com:443
Sep 11 18:43:33 ARCH406 env[372]: 2018/09/11 18:43:33 [Warning] [1389235354] App|Proxyman|Outbound: failed to process outbound traffic > Proxy|VMess|Outbound: failed to find an available destination > Retry: [dial tcp 35.**.**.**:11023: connect: network is unreachable] > Retry: all retry attempts failed
Sep 11 18:44:04 ARCH406 env[372]: 2018/09/11 18:44:04 tcp:127.0.0.1:42836 accepted tcp:mtalk.google.com:5228
Sep 11 18:44:05 ARCH406 env[372]: 2018/09/11 18:44:05 tcp:127.0.0.1:42838 rejected  Proxy|Socks: insufficient header > EOF

最近编辑记录 hayu (2018-09-12 12:19:59)

离线

#5 2018-09-12 14:29:18

依云
a.k.a. 百合仙子
所在地: 一个等待妹纸出现的地方
注册时间: 2011-08-21
帖子: 4,836
个人网站

Re: 奇怪的问题:网速超过100Mps就会断网

为什么没有 link down 却有那么多 link up?
造成此问题的最初原因是突然之间发送不了数据了。结合你手动设置 1Gbps 速率能使用,考虑是(你或者对端的)网卡驱动或者固件有问题。
对了,你自动协商出来的速率是多少?难不成和对端的不一样?
对端就是网线另一端,你顺着网线找过去就能找到。应当是交换机。

离线

#6 2018-09-12 17:40:12

hayu
会员
注册时间: 2015-07-02
帖子: 14

Re: 奇怪的问题:网速超过100Mps就会断网

依云 说:

为什么没有 link down 却有那么多 link up?
造成此问题的最初原因是突然之间发送不了数据了。结合你手动设置 1Gbps 速率能使用,考虑是(你或者对端的)网卡驱动或者固件有问题。
对了,你自动协商出来的速率是多少?难不成和对端的不一样?
对端就是网线另一端,你顺着网线找过去就能找到。应当是交换机。

我装好networkmanager默认是ignore自动协商,不调整配置问题依然存在,我直接手动设置了个1Gps全双工模式,发现就ok了,没有再测试自动或者其他设置了.

有可能是以前是默认自动协商,某次更新后默认设置变成了忽略.

这是现在的信息

Settings for enp3s0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: yes

离线

#7 2018-09-27 12:15:03

hayu
会员
注册时间: 2015-07-02
帖子: 14

Re: 奇怪的问题:网速超过100Mps就会断网

问题的根源总算找到了,我是r8168网卡,但是内核自动加载了r8169驱动,这是个已知的问题
https://wiki.archlinux.org/index.php/Ne … 11.2F8168B

离线

页脚