Estou tentando acessar a página da web administrativa de um roteador conectado diretamente ao meu laptop via cabo Ethernet. O roteador (um TP-Link WR700N ) é novo, apenas retirado da caixa. Ele está conectado e a luz de status do LED indica operação normal. O endereço IP padrão da página de administração é 192.168.0.254.
Meu laptop está executando o Linux e o nome da minha interface é eth0. Com o roteador ligado e conectado diretamente ao meu laptop pelo patch cable Ethernet, executei este comando para definir um endereço:
ip addr add 192.168.0.10/24 dev eth0
Eu mostro a interface como UP com o endereço esperado de 192.168.0.10.
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 0a:b9:5b:9a:de:16 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 scope global eth0
valid_lft forever preferred_lft forever
No entanto, quando tento acessar a página de administração do roteador no link , o Firefox diz "Não é possível conectar-se". Quando tento pingar esse endereço, recebo "Destination Host Unreachable".
O comando curl -I http://192.168.0.254 retorna o erro "falha ao conectar-se a 192.168.0.254 porta 80: nenhuma rota para o host".
Para solucionar problemas, eu mudei o cabo e fiz um "reset de fábrica" no roteador (mesmo que seja novo). O LED do roteador passa pelos estágios esperados durante a redefinição.
Eu também tentei configurar a conexão usando o NetworkManager no KDE (endereço IP manual). Nesse caso, ip a fornece esta saída:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 0a:b9:5b:9a:de:16 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 brd 192.168.0.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
No entanto, as mensagens de erro permanecem as mesmas. Finalmente, tentei configurar a conexão usando o NetworkManager no modo automático / DHCP, mas a eth0 não obtém um endereço.
Eu negligenciei algo em fazer a conexão? Eu perdi alguma etapa de solução de problemas? Ou posso concluir que este dispositivo está com defeito?
UPDATE: adicionei tcpdump , ip route e informações adicionais abaixo:
# connect cable:
root@host1 [/home/joe1]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 23:ba:53:24:82:38 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 34:d2:10:2c:2f:12 brd ff:ff:ff:ff:ff:ff
# network manager cannot obtain an IP address, set it manually:
root@host1 [/home/joe1]# ip a add 192.168.0.10/24 brd 192.168.0.255 dev eth0
root@host1 [/home/joe1]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 23:ba:53:24:82:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 34:d2:10:2c:2f:12 brd ff:ff:ff:ff:ff:ff
# device's manual states that 192.168.0.254 is the admin page IP address
root@host1 [/home/joe1]# ping 192.168.0.254
PING 192.168.0.254 (192.168.0.254) 56(84) bytes of data.
From 192.168.0.10 icmp_seq=1 Destination Host Unreachable
From 192.168.0.10 icmp_seq=2 Destination Host Unreachable
From 192.168.0.10 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.254 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 67ms
pipe 4
root@host1 [/home/joe1]# ip route
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.10
root@host1 [/home/joe1]# tcpdump -vvv
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
17:42:45.941767 IP (tos 0x0, ttl 32, id 14813, offset 0, flags [DF], proto UDP (17), length 316)
0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from c4:e9:84:64:a7:b2 (oui Unknown), length 288, xid 0xed64d8be, Flags [Broadcast] (0x8000)
Client-Ethernet-Address c4:e9:84:64:a7:b2 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Parameter-Request Option 55, length 10:
Subnet-Mask, Default-Gateway, Vendor-Option, Netbios-Name-Server
Netbios-Node, Netbios-Scope, Domain-Name-Server, Static-Route
Classless-Static-Route, Classless-Static-Route-Microsoft
Hostname Option 12, length 6: "WR700N"
Vendor-Class Option 60, length 9: "MSFT 98^@_"
Client-ID Option 61, length 7: ether c4:e9:84:64:a7:b2
END Option 255, length 0
17:42:49.941806 IP (tos 0x0, ttl 32, id 14813, offset 0, flags [DF], proto UDP (17), length 316)
0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from c4:e9:84:64:a7:b2 (oui Unknown), length 288, xid 0xed64d8be, secs 4, Flags [Broadcast] (0x8000)
Client-Ethernet-Address c4:e9:84:64:a7:b2 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Parameter-Request Option 55, length 10:
Subnet-Mask, Default-Gateway, Vendor-Option, Netbios-Name-Server
Netbios-Node, Netbios-Scope, Domain-Name-Server, Static-Route
Classless-Static-Route, Classless-Static-Route-Microsoft
Hostname Option 12, length 6: "WR700N"
Vendor-Class Option 60, length 9: "MSFT 98^@_"
Client-ID Option 61, length 7: ether c4:e9:84:64:a7:b2
END Option 255, length 0
17:42:56.941934 IP (tos 0x0, ttl 32, id 14813, offset 0, flags [DF], proto UDP (17), length 316)
0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from c4:e9:84:64:a7:b2 (oui Unknown), length 288, xid 0xed64d8be, secs 11, Flags [Broadcast] (0x8000)
Client-Ethernet-Address c4:e9:84:64:a7:b2 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Parameter-Request Option 55, length 10:
Subnet-Mask, Default-Gateway, Vendor-Option, Netbios-Name-Server
Netbios-Node, Netbios-Scope, Domain-Name-Server, Static-Route
Classless-Static-Route, Classless-Static-Route-Microsoft
Hostname Option 12, length 6: "WR700N"
Vendor-Class Option 60, length 9: "MSFT 98^@_"
Client-ID Option 61, length 7: ether c4:e9:84:64:a7:b2
END Option 255, length 0
17:42:57.480505 IP (tos 0x0, ttl 255, id 59726, offset 0, flags [DF], proto UDP (17), length 73)
host1.mdns > 224.0.0.251.mdns: [bad udp cksum 0xa1f4 -> 0x3289!] 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
17:43:12.942038 IP (tos 0x0, ttl 32, id 14813, offset 0, flags [DF], proto UDP (17), length 316)
0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from c4:e9:84:64:a7:b2 (oui Unknown), length 288, xid 0xed64d8be, secs 27, Flags [none] (0x0000)
Client-Ethernet-Address c4:e9:84:64:a7:b2 (oui Unknown)
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
MSZ Option 57, length 2: 1024
Parameter-Request Option 55, length 10:
Subnet-Mask, Default-Gateway, Vendor-Option, Netbios-Name-Server
Netbios-Node, Netbios-Scope, Domain-Name-Server, Static-Route
Classless-Static-Route, Classless-Static-Route-Microsoft
Hostname Option 12, length 6: "WR700N"
Vendor-Class Option 60, length 9: "MSFT 98^@_"
Client-ID Option 61, length 7: ether c4:e9:84:64:a7:b2
END Option 255, length 0
^C
5 packets captured
5 packets received by filter
0 packets dropped by kernel
UPDATE 2: tcpdump mostra que o dispositivo está solicitando um endereço IP como um cliente DHCP. Então, liguei o cabo Ethernet ao meu servidor dhcp, ele recebeu um endereço, mas não consegui me conectar às páginas de administração usando esse endereço. Claramente, o manual deste dispositivo é errado ou enganoso. Eu tenho dois desses dispositivos, ambos são novos, ambos agora foram "redefinidos de fábrica, e eu não consigo fazer um deles funcionar.
Firefox http://192.168.1.203/
The connection has timed out
The server at 192.168.1.203 is taking too long to respond.
# ping 192.168.1.203
PING 192.168.1.203 (192.168.1.203) 56(84) bytes of data.
64 bytes from 192.168.1.203: icmp_seq=1 ttl=64 time=0.226 ms
64 bytes from 192.168.1.203: icmp_seq=2 ttl=64 time=0.200 ms
Tags networking router ipv4