您尚未登录。

#1 2013-10-11 09:14:47

Kelei
会员
注册时间: 2013-10-11
帖子: 21

安装完archlinux 2013.10.01之后突然无法上网

第一次安装arch。校园网,windows下是用pppoe用户名+密码连接的。用光盘安装,刚开始的时候不能上网,后来在wiki里找到一段和我网卡完全一样的:
8e70d792gw1e9gyfsm240j20wk07s3zv.jpg
按它的操作步骤配置好再用dhcpcd+pppoe-setup/pppoe-start就可以上网了。

成功完装完成之后,用同样的方法(启动dhcpcd+配置pppoe-setup)可以顺利连接网络,然后就用pacman安装了openbox等一些需要用到的软件。某次重启之后,进入系统就无法上网。
开始以为是系统的问题,但发现:即使我启动光盘的系统,用先前同样的方法,在live系统里面也变得无法上网了(dhcpcd始终报错)。也就是现在在live系统和安装好的系统里都无法上网。

ip link的结果是:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
    link/ether c8:0a:a9:69:86:30 brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:26:c7:44:d7:06 brd ff:ff:ff:ff:ff:ff

我的dhcpcd.conf里面是这样的:

hostname
duid
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
require dhcp_server_identifier
nohook lookup-hostname
noipv4ll

dpcpcd enp9s0运行结果是:
8e70d792gw1e9gygckwpuj21kw0w0h2u.jpg

尝试在dhcpcd.conf里加上

noipv6rs

之后,dhcpcd enp9s0的结果是:
8e70d792gw1e9gyg1zgehj21kw0w0h30.jpg

另外,wiki里提到dhcpcd里连接失败的可以尝试使用dhclient,由于我装好的系统里还没有安装这个,所以没法尝试。但在光盘live系统里,使用dhclient没有报任何错误,pppoe-start同样但无法上网。

现在是怎么都连不上网络了,请问有谁可以帮帮我?谢谢

离线

#2 2013-10-11 11:01:24

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

有 tcpdump 不?

离线

#3 2013-10-11 18:49:55

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:

有 tcpdump 不?

tcpdump -i enp9s0 -v

有这样的输出:

02:45:53.825610 IP (tos 0x0, ttl 64, id 5546, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.241.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:53.839243 IP (tos 0x0, ttl 4, id 2777, offset 0, flags [none], proto UDP (17), length 200)
    192.168.10.1.simp-all > 239.255.255.250.ssdp: UDP, length 172
02:45:53.839337 IP (tos 0x0, ttl 4, id 2778, offset 0, flags [none], proto UDP (17), length 200)
    192.168.10.1.simp-all > 239.255.255.250.ssdp: UDP, length 172
02:45:53.997836 IP (tos 0x0, ttl 64, id 2677, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:53.998815 IP (tos 0x0, ttl 64, id 1403, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.063191 IP (tos 0x0, ttl 64, id 488, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.093565 IP (tos 0x0, ttl 6, id 1175, offset 0, flags [none], proto UDP (17), length 161)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 133
02:45:54.094077 IP (tos 0x0, ttl 6, id 1176, offset 0, flags [none], proto UDP (17), length 160)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 132
02:45:54.094546 IP (tos 0x0, ttl 64, id 1404, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.102724 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.103 tell 192.168.1.26, length 46
02:45:54.123536 IP (tos 0x0, ttl 64, id 1405, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.195359 IP (tos 0x0, ttl 64, id 6415, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.361763 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell 192.168.2.120, length 46
02:45:54.425702 IP (tos 0x0, ttl 64, id 1852, offset 0, flags [none], proto UDP (17), length 78)
    169.254.120.192.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.470903 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.2.1 tell 192.168.2.113, length 46
02:45:54.505747 IP (tos 0x0, ttl 64, id 490, offset 0, flags [none], proto UDP (17), length 229)
    192.168.137.1.netbios-dgm > 192.168.137.255.netbios-dgm: NBT UDP PACKET(138)
02:45:54.507160 IP (tos 0x0, ttl 1, id 2678, offset 0, flags [none], proto UDP (17), length 161)
    192.168.137.174.59603 > 239.255.255.250.ssdp: UDP, length 133
02:45:54.510601 IP (tos 0x0, ttl 64, id 491, offset 0, flags [none], proto UDP (17), length 229)
    192.168.137.1.netbios-dgm > 192.168.137.255.netbios-dgm: NBT UDP PACKET(138)
02:45:54.590024 IP (tos 0x0, ttl 64, id 5547, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.241.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.638509 IP (tos 0x0, ttl 1, id 1357, offset 0, flags [none], proto UDP (17), length 161)
    169.254.117.207.51883 > 239.255.255.250.ssdp: UDP, length 133
02:45:54.660009 IP6 (hlim 1, next-header UDP (17) payload length: 86) fe80::85ec:d534:8e23:4d1.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=22bf21 (elapsed-time 3100) (client-ID hwaddr/time type 1 time 368364877 0023ae2a5d78) (IA_PD IAID:234890158 T1:0 T2:0) (Client-FQDN) (vendor-class))
02:45:54.752271 IP (tos 0x0, ttl 64, id 2679, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.763302 IP (tos 0x0, ttl 64, id 1406, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.828255 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.59520 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:54.828404 IP (tos 0x0, ttl 1, id 492, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.58138 > 224.0.0.252.llmnr: UDP, length 24
02:45:54.856861 IP (tos 0x0, ttl 64, id 1407, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.936867 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.59520 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:54.936880 IP (tos 0x0, ttl 1, id 493, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.58138 > 224.0.0.252.llmnr: UDP, length 24
02:45:54.945538 IP (tos 0x0, ttl 64, id 6416, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:54.975113 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.103 tell 192.168.1.26, length 46
02:45:55.139898 IP (tos 0x0, ttl 64, id 494, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.240520 IP (tos 0x0, ttl 64, id 655, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.378876 IP6 (hlim 1, next-header UDP (17) payload length: 154) fe80::4553:bc85:cdbb:78c0.54580 > ff02::c.ssdp: [udp sum ok] UDP, length 146
02:45:55.501906 IP (tos 0x0, ttl 64, id 2681, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.621302 IP (tos 0x0, ttl 64, id 1408, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.717916 IP (tos 0x0, ttl 64, id 6417, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.732553 IP (tos 0x0, ttl 255, id 495, offset 0, flags [none], proto UDP (17), length 158)
    192.168.137.1.mdns > 224.0.0.251.mdns: 0 [3q] [1au] PTR (QM)? _apple-mobdev._tcp.local. PTR (QM)? 4c1e0576._sub._apple-mobdev2._tcp.local. PTR (QM)? _sleep-proxy._udp.local. (130)
02:45:55.903982 IP (tos 0x0, ttl 64, id 496, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.960195 IP (tos 0x0, ttl 64, id 308, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.145.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:55.973539 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.103 tell 192.168.1.26, length 46
02:45:55.990390 IP (tos 0x0, ttl 64, id 656, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.095203 IP (tos 0x0, ttl 6, id 1177, offset 0, flags [none], proto UDP (17), length 161)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 133
02:45:56.095519 IP (tos 0x0, ttl 6, id 1178, offset 0, flags [none], proto UDP (17), length 160)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 132
02:45:56.125968 IP (tos 0x0, ttl 64, id 48046, offset 0, flags [none], proto UDP (17), length 68)
    169.254.60.231.1004 > 255.255.255.255.1004: UDP, length 40
02:45:56.215419 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::8532:8485:5fcb:6312.52534 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:56.215635 IP (tos 0x0, ttl 1, id 34, offset 0, flags [none], proto UDP (17), length 52)
    169.254.99.18.59894 > 224.0.0.252.llmnr: UDP, length 24
02:45:56.251987 IP (tos 0x0, ttl 64, id 2683, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.312874 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::8532:8485:5fcb:6312.52534 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:56.312888 IP (tos 0x0, ttl 1, id 35, offset 0, flags [none], proto UDP (17), length 52)
    169.254.99.18.59894 > 224.0.0.252.llmnr: UDP, length 24
02:45:56.344171 IP (tos 0x0, ttl 1, id 2008, offset 0, flags [none], proto UDP (17), length 48)
    169.254.245.190.6555 > 239.255.255.239.6555: UDP, length 20
02:45:56.401497 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::7d73:c1ea:a3ee:a90b.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=87411a (elapsed-time 1500) (client-ID hwaddr/time type 1 time 368390088 485d6078e590) (IA_NA IAID:347909829 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:56.467400 IP (tos 0x0, ttl 64, id 6418, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.515769 IP (tos 0x0, ttl 64, id 36, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.560141 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::a0da:25d9:e7fc:2957.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=628fd3 (elapsed-time 0) (client-ID hwaddr/time type 1 time 382022356 e89a8ff2e421) (IA_NA IAID:266902159 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:56.634094 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.1 tell 192.168.1.198, length 46
02:45:56.668386 IP (tos 0x0, ttl 64, id 499, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.724173 IP (tos 0x0, ttl 64, id 310, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.145.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.740239 IP (tos 0x0, ttl 64, id 657, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.823610 IP (tos 0x0, ttl 64, id 658, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:56.946495 IP (tos 0x0, ttl 64, id 659, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.003718 IP (tos 0x0, ttl 64, id 2686, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.018642 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::41ad:b34e:68a6:84b9.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=4bfff8 (elapsed-time 6400) (client-ID hwaddr/time type 1 time 431512331 2c59e5a3ed8e) (IA_NA IAID:237787621 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:57.098096 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.100 tell 192.168.1.26, length 46
02:45:57.212191 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::1845:f3bf:cdd1:bf9f.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=51c0e6 (elapsed-time 1500) (client-ID hwaddr/time type 1 time 368625771 00127b60b7a4) (IA_NA IAID:400583061 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:57.217561 IP (tos 0x0, ttl 64, id 6419, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.280029 IP (tos 0x0, ttl 64, id 37, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.427505 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.52456 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:57.427690 IP (tos 0x0, ttl 1, id 500, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.54996 > 224.0.0.252.llmnr: UDP, length 24
02:45:57.488594 IP (tos 0x0, ttl 64, id 311, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.145.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.507469 IP (tos 0x0, ttl 1, id 2688, offset 0, flags [none], proto UDP (17), length 161)
    192.168.137.174.59603 > 239.255.255.250.ssdp: UDP, length 133
02:45:57.526736 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.52456 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:57.526749 IP (tos 0x0, ttl 1, id 501, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.54996 > 224.0.0.252.llmnr: UDP, length 24
02:45:57.532483 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.1 tell 192.168.1.198, length 46
02:45:57.573341 IP (tos 0x0, ttl 64, id 660, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.582493 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::a0da:25d9:e7fc:2957.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=628fd3 (elapsed-time 100) (client-ID hwaddr/time type 1 time 382022356 e89a8ff2e421) (IA_NA IAID:266902159 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:57.651735 IP (tos 0x0, ttl 1, id 1358, offset 0, flags [none], proto UDP (17), length 161)
    169.254.117.207.51883 > 239.255.255.250.ssdp: UDP, length 133
02:45:57.696365 IP (tos 0x0, ttl 64, id 661, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.727171 IP (tos 0x0, ttl 64, id 502, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.753033 IP (tos 0x0, ttl 64, id 2689, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:57.970368 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.100 tell 192.168.1.26, length 46
02:45:58.003792 IP (tos 0x0, ttl 64, id 662, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.004405 IP (tos 0x0, ttl 64, id 6420, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.044370 IP (tos 0x0, ttl 64, id 38, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.096510 IP (tos 0x0, ttl 6, id 1179, offset 0, flags [none], proto UDP (17), length 161)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 133
02:45:58.096830 IP (tos 0x0, ttl 6, id 1180, offset 0, flags [none], proto UDP (17), length 160)
    192.168.2.120.63845 > 239.255.255.250.ssdp: UDP, length 132
02:45:58.197030 IP (tos 0x0, ttl 64, id 1409, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.323429 IP (tos 0x0, ttl 64, id 663, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.379010 IP6 (hlim 1, next-header UDP (17) payload length: 154) fe80::4553:bc85:cdbb:78c0.54580 > ff02::c.ssdp: [udp sum ok] UDP, length 146
02:45:58.446452 IP (tos 0x0, ttl 64, id 664, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.483263 IP (tos 0x0, ttl 64, id 505, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.503099 IP (tos 0x0, ttl 64, id 2692, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.532516 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.1 tell 192.168.1.198, length 46
02:45:58.616563 PPPoE PADI [Service-Name] [Host-Uniq 0x240000000000000047000000]
02:45:58.753158 IP (tos 0x0, ttl 64, id 665, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.753579 IP (tos 0x0, ttl 64, id 6421, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.809444 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::8532:8485:5fcb:6312.49290 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:58.809668 IP (tos 0x0, ttl 1, id 39, offset 0, flags [none], proto UDP (17), length 52)
    169.254.99.18.50655 > 224.0.0.252.llmnr: UDP, length 24
02:45:58.917917 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::8532:8485:5fcb:6312.49290 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:45:58.917931 IP (tos 0x0, ttl 1, id 40, offset 0, flags [none], proto UDP (17), length 52)
    169.254.99.18.50655 > 224.0.0.252.llmnr: UDP, length 24
02:45:58.959788 IP (tos 0x0, ttl 64, id 1410, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:58.968762 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.194 tell 192.168.1.26, length 46
02:45:58.968774 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.100 tell 192.168.1.26, length 46
02:45:59.121225 IP (tos 0x0, ttl 64, id 41, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.247600 IP (tos 0x0, ttl 64, id 506, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.256803 IP (tos 0x0, ttl 64, id 2693, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.417733 IP (tos 0x0, ttl 64, id 1472, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from b8:70:f4:3a:6c:a3 (oui Unknown), length 300, xid 0x19a3e8ec, secs 7168, Flags [Broadcast]
      Client-Ethernet-Address b8:70:f4:3a:6c:a3 (oui Unknown)
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        Client-ID Option 61, length 7: ether b8:70:f4:3a:6c:a3
        Hostname Option 12, length 7: "win7-PC"
        Vendor-Class Option 60, length 8: "MSFT 5.0"
        Parameter-Request Option 55, length 12:
          Subnet-Mask, Domain-Name, Default-Gateway, Domain-Name-Server
          Netbios-Name-Server, Netbios-Node, Netbios-Scope, Router-Discovery
          Static-Route, Classless-Static-Route, Classless-Static-Route-Microsoft, Vendor-Option
02:45:59.502966 IP (tos 0x0, ttl 64, id 666, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.503708 IP (tos 0x0, ttl 64, id 6422, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.582647 IP6 (hlim 1, next-header UDP (17) payload length: 103) fe80::a0da:25d9:e7fc:2957.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=628fd3 (elapsed-time 300) (client-ID hwaddr/time type 1 time 382022356 e89a8ff2e421) (IA_NA IAID:266902159 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:45:59.724247 IP (tos 0x0, ttl 64, id 1411, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:45:59.885304 IP (tos 0x0, ttl 64, id 42, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.007144 IP (tos 0x0, ttl 64, id 2694, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.012460 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.64011 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:46:00.012614 IP (tos 0x0, ttl 1, id 507, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.52339 > 224.0.0.252.llmnr: UDP, length 24
02:46:00.101780 IP (tos 0x0, ttl 64, id 487, offset 0, flags [none], proto UDP (17), length 229)
    192.168.1.26.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
02:46:00.121175 IP6 (hlim 1, next-header UDP (17) payload length: 32) fe80::5115:7a46:cb63:8c14.64011 > ff02::1:3.llmnr: [udp sum ok] UDP, length 24
02:46:00.121247 IP (tos 0x0, ttl 1, id 508, offset 0, flags [none], proto UDP (17), length 52)
    192.168.137.1.52339 > 224.0.0.252.llmnr: UDP, length 24
02:46:00.201596 IP6 (hlim 1, next-header UDP (17) payload length: 94) fe80::e1cd:e170:603b:1749.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=a738a1 (elapsed-time 0) (client-ID hwaddr/time type 1 time 395072146 e89a8f06335a) (IA_NA IAID:48798351 T1:0 T2:0) (Client-FQDN) (vendor-class) (option-request DNS-search-list DNS-server vendor-specific-info Client-FQDN))
02:46:00.313650 IP (tos 0x0, ttl 64, id 6423, offset 0, flags [none], proto UDP (17), length 78)
    192.168.2.64.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.324466 IP (tos 0x0, ttl 64, id 509, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.1.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.490738 IP (tos 0x0, ttl 64, id 1412, offset 0, flags [none], proto UDP (17), length 78)
    169.254.169.11.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.596460 IP (tos 0x0, ttl 64, id 669, offset 0, flags [none], proto UDP (17), length 78)
    169.254.194.131.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.649714 IP (tos 0x0, ttl 64, id 43, offset 0, flags [none], proto UDP (17), length 78)
    169.254.99.18.netbios-ns > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
02:46:00.757278 IP (tos 0x0, ttl 64, id 2695, offset 0, flags [none], proto UDP (17), length 78)
    192.168.137.174.netbios-ns > 192.168.137.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

离线

#4 2013-10-11 18:59:43

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

Kelei 说:
百合仙子 说:

有 tcpdump 不?

tcpdump -i enp9s0 -v

有这样的输出:

...

既然你有,而且能把结果弄出来:

tcpdump -i enp9s0 -s 0 -vv -w log.pcap

然后把生成的 log.pcap 文件放出来。记得先开 tcpdump,然后再 dhcpcd。

离线

#5 2013-10-11 19:01:45

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:
Kelei 说:
百合仙子 说:

有 tcpdump 不?

tcpdump -i enp9s0 -v

有这样的输出:

...

既然你有,而且能把结果弄出来:

tcpdump -i enp9s0 -s 0 -vv -w log.pcap

然后把生成的 log.pcap 文件放出来。记得先开 tcpdump,然后再 dhcpcd。


哦好的稍等!开了tcpdump再开dhcpcd的话dhcpcd就不会自动退出吗?还有,运行到dhcpcd退出了就可以还是等tcpdump自己完成?

最近编辑记录 Kelei (2013-10-11 19:11:32)

离线

#6 2013-10-11 21:03:06

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:
Kelei 说:
百合仙子 说:

有 tcpdump 不?

tcpdump -i enp9s0 -v

有这样的输出:

...

既然你有,而且能把结果弄出来:

tcpdump -i enp9s0 -s 0 -vv -w log.pcap

然后把生成的 log.pcap 文件放出来。记得先开 tcpdump,然后再 dhcpcd。


按你的提示运行了一下,但dhcpcd运行了不久之后连接不上就自动退出了。输出我不知道怎么放附件。。放了去度盘。。

log.pcap: http://pan.baidu.com/s/1gOvQr

另外,我怕文件太大了,我重新运行了一次,打算dhcpcd死掉就关掉log。没想到这次dhcpcd竟然没有死掉,但依然无法上网,无法ping任务网站,这次的日志是:

log2.pcap: http://pan.baidu.com/s/166NeI

8e70d792gw1e9hk8krrfsj21kw0w0k81.jpg

最近编辑记录 Kelei (2013-10-11 21:27:35)

离线

#7 2013-10-11 22:07:28

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

Kelei 说:

按你的提示运行了一下,但dhcpcd运行了不久之后连接不上就自动退出了。输出我不知道怎么放附件。。放了去度盘。。

log.pcap: http://pan.baidu.com/s/1gOvQr

另外,我怕文件太大了,我重新运行了一次,打算dhcpcd死掉就关掉log。没想到这次dhcpcd竟然没有死掉,但依然无法上网,无法ping任务网站,这次的日志是:

log2.pcap: http://pan.baidu.com/s/166NeI

8e70d792gw1e9hk8krrfsj21kw0w0k81.jpg

DHCP 正常,DNS 正常,但是 ping 没有回应。你 ping 你的网关(192.168.137.174)呢?wget baidu.com 呢?

离线

#8 2013-10-11 22:14:38

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:
Kelei 说:

按你的提示运行了一下,但dhcpcd运行了不久之后连接不上就自动退出了。输出我不知道怎么放附件。。放了去度盘。。

log.pcap: http://pan.baidu.com/s/1gOvQr

另外,我怕文件太大了,我重新运行了一次,打算dhcpcd死掉就关掉log。没想到这次dhcpcd竟然没有死掉,但依然无法上网,无法ping任务网站,这次的日志是:

log2.pcap: http://pan.baidu.com/s/166NeI

http://ww4.sinaimg.cn/mw690/8e70d792gw1 … 0w0k81.jpg

DHCP 正常,DNS 正常,但是 ping 没有回应。你 ping 你的网关(192.168.137.174)呢?wget baidu.com 呢?

现在又不行了,这两天自动上不了之后,dhcpcd就没有成功连过,一直time out然后死掉。就刚刚那一次可以。

离线

#9 2013-10-11 22:16:53

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

离线

#10 2013-10-11 22:22:51

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

网络我不是很懂,就校园网,只知道我们这里是一个账号可以多台电脑一起拨号用的……。请问我可以怎样知道我的网络环境啊?另外,意思是因为有人扫描,导致了DHCP服务器没有响应我的请求吗?

最近编辑记录 Kelei (2013-10-11 22:24:09)

离线

#11 2013-10-11 22:47:10

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

Kelei 说:
百合仙子 说:

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

网络我不是很懂,就校园网,只知道我们这里是一个账号可以多台电脑一起拨号用的……。请问我可以怎样知道我的网络环境啊?另外,意思是因为有人扫描,导致了DHCP服务器没有响应我的请求吗?

你们校园网不需要特别的客户端就可以用吗?

看上去是 DHCP 服务器出了问题的样子呢。别人上网都没问题?你在没有问题的系统上抓个联网过程的包看看呢?

离线

#12 2013-10-11 22:49:27

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:
Kelei 说:
百合仙子 说:

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

网络我不是很懂,就校园网,只知道我们这里是一个账号可以多台电脑一起拨号用的……。请问我可以怎样知道我的网络环境啊?另外,意思是因为有人扫描,导致了DHCP服务器没有响应我的请求吗?

你们校园网不需要特别的客户端就可以用吗?

看上去是 DHCP 服务器出了问题的样子呢。别人上网都没问题?你在没有问题的系统上抓个联网过程的包看看呢?

不用。听说其它栋的需要锐捷,我们这里只要pppoe。我这里win7也一直没有任何问题。现在抓!

--------------

好了!就这个:win.pcap

http://pan.baidu.com/s/13jaXs

最近编辑记录 Kelei (2013-10-11 23:02:29)

离线

#13 2013-10-11 23:32:03

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

Kelei 说:
百合仙子 说:
Kelei 说:
百合仙子 说:

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

网络我不是很懂,就校园网,只知道我们这里是一个账号可以多台电脑一起拨号用的……。请问我可以怎样知道我的网络环境啊?另外,意思是因为有人扫描,导致了DHCP服务器没有响应我的请求吗?

你们校园网不需要特别的客户端就可以用吗?

看上去是 DHCP 服务器出了问题的样子呢。别人上网都没问题?你在没有问题的系统上抓个联网过程的包看看呢?

不用。听说其它栋的需要锐捷,我们这里只要pppoe。我这里win7也一直没有任何问题。现在抓!

--------------

好了!就这个:win.pcap

http://pan.baidu.com/s/13jaXs

哦,我想起来了!PPPoE 的话,连上之后会出现一个 ppp 的网络接口(比如 ppp0)。你看看你有没有 ppp*,如果它没有 IP 地址的话你再给它 DHCP。

离线

#14 2013-10-11 23:34:40

Kelei
会员
注册时间: 2013-10-11
帖子: 21

Re: 安装完archlinux 2013.10.01之后突然无法上网

百合仙子 说:
Kelei 说:
百合仙子 说:
Kelei 说:
百合仙子 说:

前边那个记录中开头部分,有人在进行 ARP 扫描。DHCP 服务器没有回应你的请求。

另外,你这网络里至少有两个网段啊,是什么网络环境呢?

网络我不是很懂,就校园网,只知道我们这里是一个账号可以多台电脑一起拨号用的……。请问我可以怎样知道我的网络环境啊?另外,意思是因为有人扫描,导致了DHCP服务器没有响应我的请求吗?

你们校园网不需要特别的客户端就可以用吗?

看上去是 DHCP 服务器出了问题的样子呢。别人上网都没问题?你在没有问题的系统上抓个联网过程的包看看呢?

不用。听说其它栋的需要锐捷,我们这里只要pppoe。我这里win7也一直没有任何问题。现在抓!

--------------

好了!就这个:win.pcap

http://pan.baidu.com/s/13jaXs

哦,我想起来了!PPPoE 的话,连上之后会出现一个 ppp 的网络接口(比如 ppp0)。你看看你有没有 ppp*,如果它没有 IP 地址的话你再给它 DHCP。

你说的是在dhcpcd和pppoe-start都连上之后吗?前几天能连上的时候连上了我有用ip link看过,是有的。但具体输出是什么不记得了。现在是我dhcpcd连不上……更不用说pppoe-start了,所有我看不到ppp*有没有IP或其它输出。

最近编辑记录 Kelei (2013-10-11 23:37:06)

离线

#15 2013-10-12 00:02:26

依云
会员
所在地: a.k.a. 百合仙子
注册时间: 2011-08-21
帖子: 7,100
个人网站

Re: 安装完archlinux 2013.10.01之后突然无法上网

Kelei 说:

你说的是在dhcpcd和pppoe-start都连上之后吗?前几天能连上的时候连上了我有用ip link看过,是有的。但具体输出是什么不记得了。现在是我dhcpcd连不上……更不用说pppoe-start了,所有我看不到ppp*有没有IP或其它输出。

dhcpcd 之前、pppoe-start 之后。

离线

页脚