KT3 Wi-Fi issue

[nasser]

Thanks to an old tutorial by knc1, I was able to set up wi-fi access from PC to PW1, PW3 and KT3. Using shared keys, no need for password too.

However, I face a peculiar issue with KT3. I'm unable to access KT3 from my PC(netbook running Ubuntu 14.04). Any pings to KT3's I.P don't succeed.

As a workaround, I open kterm on KT3 and from there, ping the PC's I.P - which works. After this, I'm able to ping/connect to KT3 from PC.

This reminds me of similar things I used to do on old PCs at my workplace.

I suppose there must a simple (or profound ) reason for this behaviour?

[hius07]

Originally Posted by nasser

Thanks to an old tutorial by knc1

could you give a link please

[nasser]

Originally Posted by hius07

could you give a link please

https://www.mobileread.com/forums/sho...d.php?t=204450

[knc1]

Originally Posted by nasser

Thanks to an old tutorial by knc1, I was able to set up wi-fi access from PC to PW1, PW3 and KT3. Using shared keys, no need for password too.

However, I face a peculiar issue with KT3. I'm unable to access KT3 from my PC(netbook running Ubuntu 14.04). Any pings to KT3's I.P don't succeed.

As a workaround, I open kterm on KT3 and from there, ping the PC's I.P - which works. After this, I'm able to ping/connect to KT3 from PC.

This reminds me of similar things I used to do on old PCs at my workplace.

I suppose there must a simple (or profound ) reason for this behaviour?

Strange indeed.
Please mention which Kindle firmware version that was happening on.

That was written when the PW-1 was new, but I can't think of what difference that should make.
Nor why an outgoing connection would fix it.

Note: There are variations to the specifics of that series of posts for the newer than when-written models.
But the over-all procedure is the same.

[nasser]

Originally Posted by knc1

Strange indeed.
Please mention which Kindle firmware version that was happening on.

That was written when the PW-1 was new, but I can't think of what difference that should make.
Nor why an outgoing connection would fix it.

Note: There are variations to the specifics of that series of posts for the newer than when-written models.
But the over-all procedure is the same.

G000KA, 5.8.0

Before posting now, I did some more trials. If I wait long enough, eventually the KT3 does respond to pings from my PC. It appears that the KT3 takes more time than compared to PW1 or PW3, to become visible on the network. But an outgoing ping makes it visible quicker! Almost weirdly like, when you're searching for somebody in a crowd.. If they wave at you, you locate them faster..

[knc1]

Originally Posted by nasser

G000KA, 5.8.0

Before posting now, I did some more trials. If I wait long enough, eventually the KT3 does respond to pings from my PC. It appears that the KT3 takes more time than compared to PW1 or PW3, to become visible on the network. But an outgoing ping makes it visible quicker! Almost weirdly like, when you're searching for somebody in a crowd.. If they wave at you, you locate them faster..

That is a problem with the kernel's handling of its arp cache.

What kernel version on each of the devices?

[nasser]

Originally Posted by knc1

That is a problem with the kernel's handling of its arp cache.

What kernel version on each of the devices?

1. PW1: 2.6.31-rt11-lab126
2. PW3: 3.0.35-lab126
3. KT3: 3.10.53-lab126

They seem to be changing the version in every model!

[knc1]

Originally Posted by nasser

1. PW1: 2.6.31-rt11-lab126
2. PW3: 3.0.35-lab126
3. KT3: 3.10.53-lab126

They seem to be changing the version in every model!

I no longer follow the kernel mailing list,
But I could check kernel.org repo to see if there where problems with the arp cache 3.0 -> 3.10

3.10.103 is one of the 'long term support' kernel versions, neither of the other two are (now, they where at one time).

[Yourcat]

A tcpdump on Linux should show what's happening. Without a network trace one can only guess, while arp issues could be indeed the cause for this problem.