Strange Networking Behavior On Debian WiFi
Hi. I work at a Windows shop, but I setup my laptop to dual boot into Debian 8, with Gnome 3. I had to install the iwlwifi package to get Gnome to see the WiFi networks. I also had to adjust the netmanager config slight to get the ethernet managed. Other than that, I think it is a default system.
The networking seems to be fine on ethernet, but when on WiFi, connected to any of our routers, I see some weird behavior that prevents practical use. Here is a summary: 1. I can see all wireless networks, both with gnome and with iwlist. And I can connect successfully to any of them. 2. I can ping both localhost wlan0 ip address, as well as the gateway router. I can make dns requests to the gateway router. 3. I cannot ping anything past the gateway router, such as the next hop past the gateway router, or ip addresses on the Internet. 4. When booted into Windows, I have full connectivity using the same WiFi routers. I checked, and I have the same MAC address under both windows and Linux. I can't understood how the WiFi routers would be discriminating against me based on my OS (that should be transparent). Maybe some issue with the routing configuration on my system...? Code:
me@echo:~$ ip addr |
Welcome to LinuxQuestions.
Yes, it looks like a routing problem. If you look at the output of the ping command you will see it is using eth0 versus wlan0 when trying to communicate outside the LAN. Quote:
Post the output of the command: ip route https://en.wikipedia.org/wiki/Link-local_address |
Code:
me@echo:~$ ip route The part that I adjusted was in the /etc/NetworkManager/NetworkManager.conf file, pasted into my first post. I adjust the "managed" line from "false" to "true". I changed it earlier because when i first started Gnome, it said that the ethernet connection was unmanaged, so I gave that a try, blindly following some Web page article I found. |
I tried deleting the NetworkManager.conf, and reinstalling network-manager and gnome-network-manager from Debian wheezy. But the eth0 default route still gets added after about 1 or 2 minutes, even if ethernet is never plugged in. I'm not sure how to proceed, so I'm just using the workaround command
Code:
ip route del default dev eth0 |
I'm not sure what is happening either. I only suspect that the dhcp client is trying to get an address on eth0 and times out to a link-local address.
|
For posterity, I think it was this line in /etc/network/interfaces causing the "problem":
Code:
# The primary network interface |
All times are GMT -5. The time now is 02:47 PM. |