Can't access SSH server when it's on a wireless laptop.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Last night I tested to see how long a connection would last (once they find each other). I was able to stay SSH'ed in for six hours or so before I went to bed. I have been knocked off the SSH connection in the past but I wouldn't characterize the connection as tenuous once made.
running arping on the laptop didn't make the PC aware of it. They still can't see each other until they are both pinging each other.
I did have to use a lowercase 'u' instead of a capital 'U' for arping
results:
(117 is laptop, 116 is pc)
Code:
# arping -u -c 2 192.168.1.117
arping: Um.. lo looks like the wrong interface to use. Is it? (-i switch)
arping: using it anyway this time
ARPING 192.168.1.117
--- 192.168.1.117 statistics ---
2 packets transmitted, 0 packets received, 100% unanswered (0 extra)
# arping -u -c 2 192.168.1.116
ARPING 192.168.1.116
--- 192.168.1.116 statistics ---
2 packets transmitted, 0 packets received, 100% unanswered (0 extra)
root@modef:~#
Did you ever sort this out? I have exactly the same problem on my network. I cannot ping any Linux machines that are wirelessly connected to my router unless they are first pinged by a windows machine, after which time it can be accessed for about a minute before being pinged again. Please help.....
Your router may be isolating wireless connections only allowing internet traffic. Wireless can be tricky. My router will stop wireless authentication. I found that this only happens when my laptop is connected on the wired side. Strangely, this still happens after switching to the Tomato firnware!
Thank you Schiwal, with that tip I believe I have found the problem.
My Linksys Router has a feature on it (which is apparently common) called AP isolation. It isolates wireless devices so they can only communicate to the router, not each other.
It took forever to find, because in my router's settings, it was set to off. However it was indeed on, and toggling that setting on and off was needed to fully disable it.
Since the toggle I haven't had any issues connecting via wireless.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.