can't access computer on LAN from ubuntu laptop while wireless but works wired
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.
can't access computer on LAN from ubuntu laptop while wireless but works wired
The problem: I can't seem to access other computers on my home LAN with my ubuntu laptop while connected wirelessly but it works fine on a wired connection.
Note: I am however able to access the internet wirelessly.
My router: linksys WRT54G v8 (dhcp disabled) (wpa2 personal enabled)
I am trying to ssh into my ubuntu desktop from my ubuntu laptop. The desktop is wired to the router along with a mac (also wired).
I can ssh into the ubuntu deskop from the mac and the laptop when wired but not wirelessly. After a long pause the connection simply times out.
I have adjusted my desktop firewall to let both my wireless and wired ips for my laptop through.
laptop ifconfig output:
eth0 Link encap:Ethernet HWaddr **hidden**
inet addr:192.168.1.102 Bcast:192.168.1.255
Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17
Are you running a firewall program in ubuntu ? Perhaps the wireless (eth1) is in the list of interfaces with port 22 (ssh) blocked.
(Easiest way to check it is connect to internet via wireless and then visit grc.com and do a ShieldsUP! test. It will tell you which ports are closed and open.)
I am running firestarter on both the laptop and the desktop. I assume that you are referring to the laptop.
On the laptop I have the default policy that blocks all incoming traffic (except port 80, etc) and allows all outgoing traffic.
On the desktop (hosts the ssh server) I have opened port 22 only to my internal ip addresses for my mac machine, and both laptop (eth0 and eth1) interfaces.
Shields up shows all stealth from all my computers on a port scan (even if I disabled firestarter, the router contains a firewall that should block port 22 from the internet).
Correct me if I am wrong but I do not believe I have to open my incoming port 22 on the laptop so the laptop can act as an ssh client.
I disabled the firewall on the laptop (confirmed by iptables -L) and tried to ssh into the desktop using the wireless connection and got the following message:
Code:
ssh: connect to host 192.168.***.*** port 22: No route to host
I am still able to connect to the internet with this setup.
I turned the laptop firewall on and tried to ssh the desktop and it just times out without connecting.
For those that might have a similar problem in the future, here is what I think was going on.
The network manager (system->administration->network) had both my wired and wireless network loading by default.
When trying to ssh into another computer on my network, the computer was choosing to use the ip address of the wired nic instead of the wireless nic address.
I caught the error by looking in my messages log (system->administration->system log->messages. When I attempted to ssh into another computer I noticed that the source address was the wired ip instead of the wireless ip.
To fix the problem, I set two profiles in my network manager. One for wireless only access and one for wired access. I set the wireless profile to the default and rebooted the computer (you could probably just restart the networking system but I don't know how to do that off the top of my head). After the reboot, sshing into a computer on the local network works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.