Suse 10: No Dhcp, no internet, no fun
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) linux:~ # ifconfig 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:2031 errors:0 dropped:0 overruns:0 frame:0 TX packets:2031 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:132036 (128.9 Kb) TX bytes:132036 (128.9 Kb) linux:~ # ifup 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: batch committing... SuSEfirewall2: Firewall rules successfully set linux:~ # ifstatus eth0 eth0 device: nVidia Corporation MCP55 Ethernet (rev a2) eth0 configuration: eth-id-00:16:17:42:99:af eth0 is up 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:16:17:42:99:af brd ff:ff:ff:ff:ff:ff inet 192.168.1.102/24 brd 192.168.1.255 scope global eth0 inet6 fe80::216:17ff:fe42:99af/64 scope link valid_lft forever preferred_lft forever eth0 IP address: 192.168.1.102/24 Configured routes for interface eth0: default 192.168.1.1 - - 169.254.0.0 - 255.255.0.0 eth0 Active routes for interface eth0: 192.168.1.0/24 proto kernel scope link src 192.168.1.102 169.254.0.0/16 scope link default via 192.168.1.1 1 of 2 configured routes for interface eth0 up linux:~ # ifstatus eth0 eth0 device: nVidia Corporation MCP55 Ethernet (rev a2) eth0 configuration: eth-id-00:16:17:42:99:af eth0 dhcpcd is still waiting for data eth0 is up 3: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:16:17:42:99:af brd ff:ff:ff:ff:ff:ff inet6 fe80::216:17ff:fe42:99af/64 scope link valid_lft forever preferred_lft forever linux:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:16:17:42:99:AF inet6 addr: fe80::216:17ff:fe42:99af/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:820 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1209 (1.1 Kb) TX bytes:0 (0.0 b) Interrupt:233 Base address:0x6000 linux:~ # ifup eth0 eth0 device: nVidia Corporation MCP55 Ethernet (rev a2) eth0 configuration: eth-id-00:16:17:42:99:af DHCP client is already running on eth0 linux:~ # dhcpcd eth0 Reloading name server BIND server reload successful ..done linux:~ # ifup eth0 eth0 device: nVidia Corporation MCP55 Ethernet (rev a2) eth0 configuration: eth-id-00:16:17:42:99:af Starting DHCP Client Daemon on eth0... . . . . . no IP address yet... backgrounding. |
try this:
Dear Vcount!
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. |
Quote:
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. Thanks, though. |
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 |
All times are GMT -5. The time now is 08:30 PM. |