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.
First: I had a stroke a few years ago, and I am a perpetual dumba$$... Sorry...
Well. it is my fault.
I did a reinstall of Debian Stable. And it asked for a firmware blob, which I had downloaded from Debian, that I put on a flash drive. For some reason, it refused to autoconfigure DHCP. I said "ignore it, I will fix it later".
Well, it is later and I have no internet access. He!!, I cannot even connect to my own modem!
So, I have been fighting with this since Saturday night, and I cannot know how to configure my eth0 interface, and yes, it is eth0.
Can anyone offer me a suggestion of what to do?
Please!
Thank you for your help.
{{PS: I have already messed with /etc/network/interfaces, ifdown eth0, ifup eth0, and I do have all of the relevant bits from debian. I just don't know how to use these things to get this eth0 interface working.}}
What kind of install did you do? If you installed one of the desktop environments, it should have also installed networkmanager and a frontend for it that you can use.
What hardware are you using? What ethernet devices show up (if any) with the following commands?
Code:
lspci
lsusb
ip link list
ip addr list
Thanks!
I'm just confused because you mention a firmware blob, but my experience is that usually the wired ethernet adapter does NOT require a firmware blob. WiFi is different, and I often get the Debian installer asking for a firmware blob for that. (I never bother with it. I install with wired ethernet and use apt-get afterward if necessary to get wifi working.)
IsaacKuo: I will check on that and tell you later.
Yes, I have a damnable driver, and prior to this reinstall, it HAD worked until Friday's nightmare. (I had initially used (spit) Fedora, but after it crashed and had to reinstall it, I decided that Debian is my best option, and thus started my Saturday night "fun").
It may have worked in the past, but it doesn't work now..... unless my computer guy put a different chip set in my computer "for" me, but it isn't on the work order. I will ask him tomorrow.
IsaacKuo: OK, it may not be a firmware blob, but in the Debian repository it is labelled as a"Binary firmware for Realtek wired and wireless network adapters" and the particular thing had attempted to install is called "rtl_nic/rtl8168g-2.fw".
So, I don't know what it is, but the installer told me that I should install it via a flash drive. It didn't accept it, but I installed it after the system was up and running.
OK, you have public IP address, no NAT router between you and the net. Meaning you cannot set up the IP address by hand, you must use DHCP. Which seems to be working, you got the IP address. What's in /etc/resolv.conf?
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
[...]
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 40:8d:5c:8d:fc:75 brd ff:ff:ff:ff:ff:ff
[...]
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 40:8d:5c:8d:fc:75 brd ff:ff:ff:ff:ff:ff
inet 72.24.169.187/24 brd 72.24.169.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::428d:5cff:fe8d:fc75/64 scope link
valid_lft forever preferred_lft forever
Huh. Well, it looks like the required module is present, loaded, and functional. Not only that, but eth0 appears to be up and has an ip address. Unless you manually configured a static IP setup, it must surely have gotten it via DHCP.
But you say you're not able to connect to the internet? My next guess is to look at /etc/resolv.conf to find out what nameserver(s) the OS is attempting to use. The DHCP server might not be configured properly to feed the client a good nameserver to use, or the OS might have something funny going on where an old nameserver is "stuck".
For example, I've had weird things happen where I started a machine off connected to another computer using "Shared to Other computers"; /etc/resolv.conf was populated (correctly) with "nameserver 10.42.0.1". But this setting seemed to get "stuck" so it was still in place even later when I connected up to a different DHCP server.
I manually edited /etc/resolv.conf to the IP address of the currently attached gateway and my problems went away.
If you have no idea what the IP address of your currently attached gateway is, you can guess it from the results of
Code:
ip neigh list
This will list ip neighbors which have tried to connect to your computer or which your computer has tried to connect to. This will likely be a pretty short list, including the DHCP server (which is likely the gateway you need).
Quick reply to Emerson: I am connected to a router, not directly to the modem. The only thing else is a wireless modem, but WiFi has an inherent upper speed, whereas a wired modem is much faster... I want faster.
I was experimenting with a static, but as of this morning, I switched it back to DHCP.
PS: when I used, I think, "/etc/init.d/dsnmasq restart" it responded with "fail" or "failure"
Also: (spit) Fedora has a connection, as I have installed a small install of (spit) Fedora. However, neither Debian, Ubuntu, nor Mint have an internet connection. It could be an inherent problem with Debian-based kernels, and the last successful kernel compilation was in early 2011, before my stroke. Every attempt at a kernel compilation has resulted in a "kernel panic".
I will get back with that /etc/resolve.conf in about an hour or so.
As an aside... in 2005, I had been distro-hopping and I chose to stick with Debian in mid 2005. It was, ultimately, either Debian or Slackware.
Should I give Slackware a try, see if I have internet connection, and go from there?
Or maybe I should try Arch.
I have had a stroke in 2011, and I am unable to work, unable to get hired. I use the internet to occupy myself. I play an MMORPG called Ryzom, and I use Steam. Steam is a bit "chunky" on (spit) Fedora. Maybe it is the Debian-based kernels. Perhaps if I try Slackware of Arch it will work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.