LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 06-05-2004, 04:36 PM   #1
pcj
LQ Newbie
 
Registered: Jun 2004
Posts: 3

Rep: Reputation: 0
SUSE 9.1 network problem: DHCP ???


I have a Netgear DSL modem/router and I have installed SUSE 9.1 on one of my networked pc's - it is installed alongside Win 98v2. The other computer (set as gateway) is running on Win XP.
The installation of SUSE seemed to go OK until I tried the "Connect to internet" test which failed...the ERROR message from feedback is "DHCP client is already running on etho".
I have tried entering IP address etc manually but they are rejected as "incorrect addresses".
I have run another Win XP PC on the same line with no problems.
I am new to Linux and as yet do not even know how to ping from it.
Any advice would be greatly appreciated.
pj
 
Old 06-05-2004, 04:57 PM   #2
rshaw
Senior Member
 
Registered: Apr 2001
Location: Perry, Iowa
Distribution: Mepis , Debian
Posts: 2,692

Rep: Reputation: 45
not sure on this one, have you tried entering the default gateway address.
 
Old 06-05-2004, 06:01 PM   #3
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
I've had similar problem after new SuSE 9 instal but firstly need to check a few things. Is the Netgear modem/router a combined modem and eg 4 port switch? Is it also acting as DHCP server? Do all your PCs plug into it? When you say the WinXP machine is a gateway is it running internet sharing? How is the WinXP machine getting its IP address? Can you check what IP addresses your machines have - WinXP type 'ipconfig /all' in a command box - Linux type 'ifconfig' in a shell (Konsole for KDE) box (but you have to switch to root first - type su at shell prompt then enter root password)

The linux response should be similar to

eth0 Link encap:
inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::260:97ff:fe25:ff65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37539 errors:0 dropped:0 overruns:0 frame:0
TX packets:43299 errors:0 dropped:0 overruns:0 carrier:0
collisions:3491 txqueuelen:100
RX bytes:19933368 (19.0 Mb) TX bytes:29382049 (28.0 Mb)
Interrupt:11 Base address:0xe000

eth1 Link encap:
inet addr:192.168.2.250 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::20c:76ff:fe8f:dabd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:955 errors:0 dropped:0 overruns:0 frame:0
TX packets:340 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:120404 (117.5 Kb) TX bytes:37403 (36.5 Kb)
Interrupt:11 Base address:0xd000

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:6024 errors:0 dropped:0 overruns:0 frame:0
TX packets:6024 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:759095 (741.3 Kb) TX bytes:759095 (741.3 Kb)

except that unless you have two network cards you should only have eth0 and lo.
If you don't get anything apart from lo then your network card is not set up correctly.

Last edited by andrewdodsworth; 06-18-2004 at 02:22 AM.
 
Old 06-06-2004, 07:50 AM   #4
pcj
LQ Newbie
 
Registered: Jun 2004
Posts: 3

Original Poster
Rep: Reputation: 0
I have entered default gateway details but no improvement.

Where do I find the "shell" mentioned...is on the YAST panel?
 
Old 06-06-2004, 12:25 PM   #5
pcj
LQ Newbie
 
Registered: Jun 2004
Posts: 3

Original Poster
Rep: Reputation: 0
Awwwww can't believe the eventual solution was so simple!...having spent hours and hours reinstalling the whole of SUSE - 7 times; zeroing the hard drive to remove every trace of Windows, and trawling every Linux support site I could find (sorry to mention that)...the actual solution was to swap LAN ports at the computer end... and the automatic configuration setup did the business!

The mainboard is an ASUS A7N8X Deluxe and I have been used to using either port when connecting to a Windows machine...however, the top port (as the board sits in a tower case) is a 3COM LAN and lower one is an NVIDIA LAN.

I have had the router plugged into the 3COM LAN and presumably SUSE 9.1 does not support that (or perhaps more accurately 3COM do not support SUSE 9.1)

The result was that the installation process configured the NVIDIA LAN but when DHCP looked for the addresses there was nout coming through because there was no cable connected!!

I did find my way around to do the 'ifconfig' and there was a total lack of address info.

The ERROR message "DHCP client is already running on etho" seems pretty unhelpful to me (although I'm sure it makes sense to those that understand these things)...something like "no connection found" would have given a better clue.

But anyway, I take back all the things I said about LINUX over the last two days (till the next time that is :-)

Many thanks to Andrew for giving the matter some serious thought and providing the helpful info.

Oh, and thank you to the moderator - was the subtext aimed at me personally or what ?
Software advice and psychology all on the same website :-)
 
Old 06-06-2004, 01:14 PM   #6
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Glad you're sorted - my problem was also to do with 2 network cards - one of which was faulty!

I've tried lots of different linux distros in the past and since finding SuSE have stuck with it - mainly because of YaST. Sooner or later though you have to start diving into conf files to get everything you want but it's well worth the effort.

Have fun.
 
Old 06-06-2004, 04:54 PM   #7
bruno buys
Senior Member
 
Registered: Sep 2003
Location: Rio
Distribution: Debian
Posts: 1,509

Rep: Reputation: 46
Hi!
The "dhcp already running on eth0" means that the interface eth0 was already probed for an IP address. The dhcp deamon had tried to put it to work.
My computer routes internet for another win98 station, and when I need to do eth stuff, I launch the console and do:
ifdown ethX (stops the interface)
ifup ethX (starts the interface)
ifconfig (shows info about all interfaces)

If you issue a ifdown and then a ifup, you'll see the dhcp daemon trying to grab an IP for the interface. In yast you can set any interfaces you want to use dhcp.
 
Old 06-14-2004, 01:37 AM   #8
seingoku
Member
 
Registered: Mar 2003
Posts: 34

Rep: Reputation: 15
YEa I have just installed Suse 9.1 and am having the same problem with my eth0 adapter. "DHCP client is already running on etho"I have only one NIC it is a Via-rhine II(on-board lan). I am getting a ip6 addy and not ip4. I have tried to del the ip6 address but when i shutdown the interface and bring it back up the ip6 address is back. I have tried setting a static ip and i still can't ping the gateway.(behind router) The NIC is good. I don't know how to disable ip6 addressing. There is not a place to remove it. It seems from reading that it is suppost to assign an ip6 addy but won't having two addresses bind to the same NIC not allow it to work? OR does in not matter since they are different protocols.
 
Old 06-14-2004, 02:09 AM   #9
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
IPv6 isn't a problem - you should have both IPv4 and IPv6 addresses on the card - you can also have multiple IPs on a card if you really want to.

I experienced similar problem on first instal of 9.1 - I wanted static IP addresses so changed to static IP addresses but still not working. In the end removed network card config in YaST and rebooted machine then set card up again and worked. Not sure why had to reboot machine but obviously some process running that wasn't stopped by just changing card config in YaST.
 
Old 06-14-2004, 09:23 PM   #10
seingoku
Member
 
Registered: Mar 2003
Posts: 34

Rep: Reputation: 15
ok i havd tried removing the card in yast, rebooting then reconfiguring. I try to assign an IP to the card through YaST and ifconfig. I have also tried removing the ipv6 address thru ifcofig. When ever I bring the interface back up the static address is gone and the ipv6 address is back. I have tried to install the card using modprobe. Im stumped.

How can I uninstall the card not just the configuration file? I can't find it inYaST and don't know how at the prompt.
 
Old 06-15-2004, 05:31 AM   #11
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Sounds as though NIC not working, how do you know it is? How are you connecting your computer to the network? Is the cable ok? Do you have any means of running diagnostics on the NIC? In YaST does it show up as available to configure and if so what happens if you select automatic configure using DHCP? What do the results of ifconfig look like?
 
Old 06-16-2004, 07:53 PM   #12
seingoku
Member
 
Registered: Mar 2003
Posts: 34

Rep: Reputation: 15
The NIC is functional. When I had Slack installed it worked just fine. LEDs on router and NIC are green.

YaST finds the NIC and and loads the module. Using YaST or manually the card is loaded but it is not binding to a dhcp address, when I assign it a manual addy it binds but alias it still doesn't work. If I reboot the addy is gone, even taking down and bringing back up the interface the addy is gone.

eth0 Link encap:Ethernet HWaddr 00:60:97:25:FF:65
inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::260:97ff:fe25:ff65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37539 errors:0 dropped:0 overruns:0 frame:0
TX packets:43299 errors:0 dropped:0 overruns:0 carrier:0
collisions:3491 txqueuelen:100
RX bytes:19933368 (19.0 Mb) TX bytes:29382049 (28.0 Mb)
Interrupt:11 Base address:0xe000

Of Course the physical address, ine6 address, are different and the IP address is not even there.

seingoku
 
Old 06-18-2004, 02:07 AM   #13
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
It looks like you've got some kind of conflict somewhere. If YaST finds the card but it won't initialise then it could be down to something else using the same IRQ etc. Have you got any other cards in the machine that could be causing problems? In YaST .. Hardware .. Hardware information what appears under Network card and network interface? Have you checked that the LAN card is enabled in the BIOS? Have you checked boot messages YaST .. Misc .. view start-up log - there should be some hint of what's wrong there. Looking at the lack of response it would probably be better if you started a new thread giving posts of start up logs, ifconfig, dmesg and full description of hardware etc. as someone else may be able to help you more. The more info you give on the problem the better response you'll get.
 
Old 06-18-2004, 03:22 AM   #14
seingoku
Member
 
Registered: Mar 2003
Posts: 34

Rep: Reputation: 15
I guess it apeers I am just retarded. The cable i was using had a broken snap on the end and was a loose conx. Consequently A tiny nudge and in and out it went. Lesson learned here is to double check the conx.
 
Old 06-18-2004, 04:29 AM   #15
andrewdodsworth
Member
 
Registered: Oct 2003
Location: United Kingdom
Distribution: SuSE 10.0 - 11.4
Posts: 347

Rep: Reputation: 30
Glad you're sorted - good luck with SuSE - I've tried other distros and always come back to it - YaST takes a heck of a lot of pain out of automatic configuration. Make sure you do the online update asap as there are quite a few bug fixes - particularly samba client browsing in KDE which doesn't work out of the box.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with network wireless conf dhcp jorfermo Linux - Wireless Networking 0 01-14-2005 03:42 AM
university dhcp network problem mwa Linux - Networking 18 12-08-2003 12:14 AM
network cards dhcp and suse 8.2 spjsm Linux - Hardware 2 05-29-2003 09:33 AM
network cards dhcp and suse 8.2 spjsm Linux - Networking 0 05-28-2003 09:22 AM
DHCP network problem MasterC Linux From Scratch 4 06-10-2002 08:39 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 04:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration