11 Dec
2017
11 Dec
'17
3:28 p.m.
Hello Nges!
Can you try the "Connect using IPv6 link local" section in the
troubleshooting guide?
It's quite a complex way to access the router but if we manage to get it
working should allow you to ignore the mess that hinders the connection
via IPv4 :)
Ciao,
Ilario
P.S.: seems that both your PC (as shown by "ip -4 address show scope
global") and your router (as can be seen by "netdiscover" output, which
shouldn't include your own IP) have the same IP 10.5.5.55. This is
weird. Maybe you set this static IP somewhere on your PC? Let's ignore this.
P.P.S.: also seems that there's a DHCP attempt going on on your PC,
indicated by the 169.254.0.0/16 line in "ip -4 route show". Weird stuff.
Let's ignore this.
On 12/06/2017 06:37 AM, Nges B wrote:
Hello all. Sorry for my late response to this mail. I
was out of the
country . I just resumed work this week.
Bellow is an attachment with the output of the above commands. Please
take a look at them.
On Nov 7, 2017 5:07 PM, "Ilario Gelmetti" <iochesonome(a)gmail.com
<mailto:iochesonome@gmail.com>> wrote:
On 11/07/2017 11:00 AM, Nges B wrote:
No that is the IP of the router.
I got that from the netdiscover command which was tied to the TP link
router.
Ok, that's great! Netdiscover is a very useful command :)
But for being sure that the IP you saw is not another client, can you
run it again and wait until it ends?
Then please save the output and send it to this mailing list (remember
to disconnect from any other network apart from the WDR3600 one,
preferably by ethernet cable, before running netdiscover)?
Additionally, while connected to the router, can you save the output of
these commands and then send the output to this mailing list?
ip -4 address show scope global
ip -4 route show
cat /etc/resolv.conf
ping -c 3 10.5.5.55
ping -c 3 10.5.0.1
ping -c 3 10.13.0.1
telnet 10.5.5.55
ssh root(a)10.5.0.1 <mailto:root@10.5.0.1>
telnet 10.5.0.1
Thanks!
Ilario