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.
My PC has a dual boot, debian 8.2 which is my favourite and Windows 7. Since two days ago I am suffering a pretty weird issue: I cannot reach 192.168.0.1 (the router) and I have no Internet. But, if I boot W7, it works OK.
I'm connecting to the router using an ethernet wire.
The WiFi connection has worked OK, son I think it's not a router problem.
Everything has worked perfectly for years. I cannot think of any changes I might have done, I've checked the files and they have not been modified lately.
I use DHCP but debian has a static IP adress (192.168.0.2).
Now I'm writing from W7 so I cannot attach any configuration file.
UGH! I had typed a detailed reply, and got a "Bad Request" error from NginX when submitted... all lost!
Did you recently do an upgrade? Specifically, do you remember if there was a kernel upgrade involved?
What is the output of lspci -v? This will tell you what hardware you have and what driver is loaded. For example, from my laptop that I am using right now:
Code:
anthony@serenity: ~ $ lspci -v | grep -A 6 -i net
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
Subsystem: AzureWave Device 1186
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f7d00000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at f7d80000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath9k
--
03:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10)
Subsystem: ASUSTeK Computer Inc. Device 200f
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f7c00000 (64-bit, non-prefetchable) [size=256K]
I/O ports at e000 [size=128]
Capabilities: <access denied>
Kernel driver in use: alx
(Note that -A 6 was just used as I knew how many lines of output I needed for this example, you may want to start with a few lines more.)
If it's a Realtek, Atheros, or one of some others, there's likely firmware involved. If lspci lists no kernel driver in use, I'd likely bet that is your problem. The firmware was not installed in the kernel upgrade, you'll have to install it again. I go through this every kernel upgrade as both my ethernet and wireless adapters require firmware.
If no driver is in use, you can also check the output of dmesg. It may indicate why the driver was not loaded at boot time (for example "bad or missing firmware" or some such error).
If you can't figure it out, feel free to post the relevant output of those commands here. I understand you're visiting the site from Windows 7, so save a text file on that partition with the output so you have access to it. It really will help us to help you better.
Last edited by goumba; 09-24-2015 at 07:46 AM.
Reason: Noticed the Win7 part.
# ip addr show dev eth0
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:26:18:7b:27:52 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.2/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
My mistake, I saw the IP address, thought you were up and running now. I had taken it early you weren't even getting that.
Are you using NetworkManager? What does /etc/network/interfaces look like? If you're using network manager (GNOME for instance), there wouldn't be an entry for eth0, but if you're not, you want to make sure it has something like.
Code:
allow-hotplug eth0
iface eth0 inet dhcp
If you're using another DE, you may want to consult the network management app's manual page to see if you need to modify /etc/network/interfaces.
Something had to have changed, and you just don't realize it. Debian wouldn't suddenly stop working for no reason. Have you tried resetting the router? Have you checked the router's logs? Can you ping the router?
I use DHCP but debian has a static IP adress (192.168.0.2).
What does that mean? Debian is configured to use dhcp but you have a rule in the router that always pairs its mac address with that IP? Or you use dhcp for everything else and you've configured debian with static? If the latter, what is the dhcp address range in the router?
Also, what's the output of "ip route"?
Last edited by suicidaleggroll; 09-25-2015 at 02:18 PM.
My mistake, I saw the IP address, thought you were up and running now. I had taken it early you weren't even getting that.
Are you using NetworkManager? What does /etc/network/interfaces look like? If you're using network manager (GNOME for instance), there wouldn't be an entry for eth0, but if you're not, you want to make sure it has something like.
Code:
allow-hotplug eth0
iface eth0 inet dhcp
If you're using another DE, you may want to consult the network management app's manual page to see if you need to modify /etc/network/interfaces.
Something had to have changed, and you just don't realize it. Debian wouldn't suddenly stop working for no reason. Have you tried resetting the router? Have you checked the router's logs? Can you ping the router?
I'm using KDE. This is my /etc/networks/interface file
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# IP dinámica
# iface eth0 inet dhcp
# IP Fija
iface eth0 inet static
address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
broacast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1
Router works OK under W7. Under debían it cannot be reached. Ping fails, no matter I'm connected through a Ethernet cable.
What does that mean? Debian is configured to use dhcp but you have a rule in the router that always pairs its mac address with that IP? Or you use dhcp for everything else and you've configured debian with static? If the latter, what is the dhcp address range in the router?
Also, what's the output of "ip route"?
The DHCP server runs on the router, but I force the PC to get a static IP (some P2P software requirement). W7 gets a dinamic IP. I can disable this to give a try
This is the output of ip route
Code:
root@bossanova:/etc/network# ip route
default via 192.168.0.1 dev eth0
default via 192.168.0.1 dev eth0 proto static metric 1024
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2
I'm using KDE. This is my /etc/networks/interface file
Code:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# IP dinámica
# iface eth0 inet dhcp
# IP Fija
iface eth0 inet static
address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
broacast 192.168.0.255
gateway 192.168.0.1
dns-nameservers 192.168.0.1
Router works OK under W7. Under debían it cannot be reached. Ping fails, no matter I'm connected through a Ethernet cable.
You misspelled "broadcast"
Also just remove that line and a couple of others. Leave address, netmask, and gateway, remove the rest. Are you sure your router can function as a dns server? You can just stick 8.8.8.8 in /etc/resolv.conf to use google's.
---------- Post added 09-26-15 at 08:28 AM ----------
Quote:
Originally Posted by bocabits
The DHCP server runs on the router, but I force the PC to get a static IP (some P2P software requirement).
You misspelled "broadcast"
Also just remove that line and a couple of others. Leave address, netmask, and gateway, remove the rest. Are you sure your router can function as a dns server? You can just stick 8.8.8.8 in /etc/resolv.conf to use google's.
I've followed your advice, using Google's DNS and the following interfaces file
Code:
root@bossanova:~# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
# IP dinámica
# iface eth0 inet dhcp
# IP Fija
auth eth0
iface eth0 inet static
address 192.168.0.2
netmask 255.255.255.0
gateway 192.168.0.1
Code:
root@bossanova:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:26:18:7b:27:52
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)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6176 (6.0 KiB) TX bytes:6176 (6.0 KiB)
root@bossanova:~# ping 192.168.0.1
connect: Network is unreachable
Quote:
Originally Posted by suicidaleggroll
---------- Post added 09-26-15 at 08:28 AM ----------
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
