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.
I've got a fresh install of Suse 10 x86_64 dual booting on my computer, and the DHCP won't work. I've gone into YAST and tried to start DHCP server there, and it gets to the point where it is supposed to start it and gets an error saying it wasn't started, do I want to continue with changes. If I say yes, it just takes me back and we get to repeat the cycle. If I say no, it stays not started.
Okay, well maybe I don't need DHCP for internet. I have a linksys wireless router working as a hub, and two gigabit LAN ports on the back of my computer. I made sure both of them were hooked up, went into windows (where the internet works just fine, and how I'm typing this now) and got the default gateway, subnet mask, and IP addresses for both of the connections. I went back into Suse, and after about an hour and a half of fiddling with different entries (ipforwarding checked or unchecked, DNS ip put in or not, etc), I finally got the internet to work.
For 5 glorious minutes.
Or so it would seem, because happy that I got it to work and tired from beating my head against it for hours, I signed off the computer then. I sign back on today, and nothing works. Maybe the IP's have been reassigned? Nope, I checked. So, I come to you, linux forums. You're my only hope here. I'd PREFER to get the DHCP working, if possible, because the IP's DO change once every couple of days and it's a pain to keep reentering them. But at this point I'd be happy with having any sort of internet access at all.
One interesting thing that I thought I'd mention. I've installed two linux distros to this machine. When the hard drive is fresh, ie doesn't have windows installed on it, both Suse and Ubuntu have no problems DHCP'ing and finding a network connection during the install. As soon as I installed windows so I could have a dual-boot, both Ubuntu and Suse lost DHCP and couldn't find the network during install, and had trouble like this afterwards. I've been unable to fix either.
Here are some ifconfig, ifup, ifstatus from my last attempt to get internet working, just in case they help at all. This is using the first LAN connection, which is an integrated LAN on an MSI K9N motherboard. It is using the forcedeth module.
linux:~ # ifdown eth0
eth0 device: nVidia Corporation MCP55 Ethernet (rev a2)
eth0 configuration: eth-id-00:16:17:42:99:af
SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: Warning: no interface active
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
linux:~ # ifconfig -v
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:16436 Metric:1
RX packets:1959 errors:0 dropped:0 overruns:0 frame:0
TX packets:1959 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:127394 (124.4 Kb) TX bytes:127394 (124.4 Kb)
I don't think you need a DHCP server for using the internet. Just go to the network card configuration tool in YaST, and there set your IP to DHCP and not static. This should work. You don't need to bother the DHCP server config tool, since you're not making a server as I read. Just the IP adress must be changed to DHCP. Thats all.
I don't think you need a DHCP server for using the internet. Just go to the network card configuration tool in YaST, and there set your IP to DHCP and not static. This should work. You don't need to bother the DHCP server config tool, since you're not making a server as I read. Just the IP adress must be changed to DHCP. Thats all.
Oh, man, this is not what I want to hear. Nobody has any other ideas on my problem? It came set to DHCP, and never worked. I tried to get it to find the network during install and it never worked. I tried for hours changing settings in YAST for the network cards and it didn't work.
So, I've tried just setting the IP to DHCP. Indeed, you could say that was the very first thing I tried, because that was the default setting that didn't work in the first place, leading me to try everything else.
You only need to have one of the 2 ports plug in. Try with just one port plugged in. I have the same board (suse 10.1) and I am using the plug closes to the mouse port.
Note: You may need to delete your network definition and rediscover the one that is pluged in.
-- Good luck
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
try this:
