Hello

I'm in the process of installing Suse 9.0 personal edition. During the install, Suse auto-detects the NIC card and network setup. Then the user is prompted to test the Internet connection. Each time I test the connection, I get an error.

I have a Dell Inspiron 1150 with a Broadcom 440x 10/100 Integrated Controller. Suse auto-detects this. My computer is connected to a (linksys) router that's connected to a cable modem. Suse sets the NIC to obtain IP automatically from the router (DHCP).

If I leave the settings that Suse sets up automatically, I get the following error when testing the connection: DHCP Client is already running on eth0.

I tried assigning a static IP (192.168.1.100) and net mask (255.255.255.0) AND I tried manually entering the routing information. When I do this, I get the following error when I test the connection: (Something to the effect of) Cannot resolve address ht tp://www . suse . de....

Does anyone have any suggestions as to what I can in order to access the Internet? I download a driver from Broadcom, but I haven't compiled it yet -- I'm not sure that I need to since Suse auto-detects the NIC card.

I've been trying to get the Internet working with Suse for 2 weeks. This is the third time I've reinstalled Suse in an attempt to get it working. Any help would be *Greatly* appreciated!!

apatia

I want to begin with a question:
Is the cable in working order, can you test the router by using another computer.

If everything is in working order start by using Yast(2) to setting the nic to receiving its setting thru from a dhcp server and reboot your machine.

Use lspci to look for the name of your ethernet controller

Use
dmesg | more
to for look for remark in reference to your nic

Use
ifconfig
to show it configuration and error

Use
route -n
to display the route of

Use
cat /etc/resolv.conf
to show the name of your dns servers on the net

On the link below I found out that some broadcom nic's you better use the tg3 drivers
You can test it by

insmod tg3

if that works
You add te following line to the /etc/modules.conf
alias eth0 tg3

http://lists.suse.com/archive/suse-l...-Jun/2837.html

Here's the output from the actions you suggested:

[ifconfig]
eth0 Link encap:Ethernet HWaddr 00:0F:1F:17:AC:3A
inet6 addr: fe80::20f:1fff:fe17:ac3a/64 Scope:Link
UP BROADCAST NOTRAILERS 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:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe000 Memory:fcffe000-fcfff080

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

[dmesg | more -- specific blurbs]

NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
cryptoapi: loaded

Broadcom 4401 Ethernet Driver bcm4400 ver. 1.0.1 (08/26/02)
eth0: Broadcom BCM4401 100Base-T found at mem fcffe000, IRQ 11, node addr 000
f1f17ac3a
bcm4400: eth0 NIC Link is Down
eth0: no IPv6 routers present

[route -n]
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

[resolv.conf]
search local

[insmod tg3]
Using /lib/modules/2.4.21-99-default/kernel/drivers/net/tg3.o
/lib/modules/2.4.21-99-default/kernel/drivers/net/tg3.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg

I'm going to try installling the tg3 driver. But I have Suse 9.0 and I'm not sure I have the option to install a specific driver.

Have you tried finishing the install and than testing the Internet using a browser. From my experience there seems to be a glitch with the network connection test in the installer for SuSE 9.1. I never got the test to work but when the install was finished I was instantly on the Internet. If you haven't finished the install because of that issue, Finish it and try your connection I'd bet it is working, and if it's not YaST will let you change your setting to make it work.

What I see is that your eth0 has a inet6 address instead of an inet4 address, can you remeber where you choose to support inet6 I have no experiance with inet6 implemetations

It appears that your NIC driver IS installed correctly.

There could be a number of reasons why you get an error like "DHCP client already running." You can try this: kill the dhcpcd process and restart networking by issuing commands like this (be root):

user@linux# ps -e |grep dhcpcd

You should get an output similar to this:

359 ? 0:00:00 dhcpcd

This is the dhcpdc (DHCP client daemon) process. It's process ID is 359. Kill it with:

user@linux# kill -HUP 359

That will HUP (hangup) the process. Now restart networking with:

user@linux# /etc/init.d/network restart

See if you can ping www.yahoo.com or something out on the internet.

- OR - just give the device a static IP like you did below:

"I tried assigning a static IP (192.168.1.100) and net mask (255.255.255.0) AND I tried manually entering the routing information. When I do this, I get the following error when I test the connection: (Something to the effect of) Cannot resolve address ht tp://www . suse . de...."

You were almost there... all you needed to do was to make some entries in /etc/resolv.conf so that you can resolve hostnames via DNS. Get the IP addresses of the DNS servers from your router and add them to your /etc/resolv.conf so that the file looks like this:

search is.chrysler.com
nameserver 192.168.256.256
nameserver 192.168.257.257

...with the nameservers being the IP addresses of your DNS servers.

Of course, you'll also need to set your route manually with:

user@linux# route add -net 0.0.0.0 gw 192.168.1.1

...assuming your router's IP address is 192.168.1.1

I've completed the SuSe install (this is actually my third reinstall). When I login after the install, I try launching the Konqueror browser and loading the SuSe hompage. I get an error.

I tried installing the new(er) Broadcom 440x driver. I had v.1.0.1; now I have v3.0.7. It didn't help.

Have a look at this thread

Look at the display from the first ifconfig listing, there you can see only an ipv6 entry, now look at the last ifconfig listing there is an ipv4 and an ipv6 entry.
Must have found the solution in the middle.


http://www.linuxquestions.org/questions/history/210265

I tried killing the dhcpcd process, restarting it and pinging an address. Here are the results:


moose:/usr # ping www.yahoo.com
ping: unknown host www.yahoo.com

moose:/usr # ping 192.168.1.1
connect: Network is unreachable

moose:/usr # ping 192.168.1.100
connect: Network is unreachable

moose:/usr # ping 192.168.1.101
connect: Network is unreachable


I tried inserting the tg3 module again (i updated my kernel). But i got the same results:

moose:/usr # insmod tg3
Using /lib/modules/2.4.21-238-default/kernel/drivers/net/tg3.o
/lib/modules/2.4.21-238-default/kernel/drivers/net/tg3.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg


This is so frustrating.

Thank you everyone who offered suggestions:

arno
HenchmenResourc
jpdixon

I finally was able to access the internet from Suse. I did what jpdixon suggested and forced the NIC card to a static IP, set the net mask, dns server and default gateway. And that did it.

Again, thank you everyone!!

LAN connection won't stay configured after reboot.

SuSE 9.1 Personal.
Toshiba A45-S130 /
Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller /
Askey AR5212 802.11abg NIC

BellSouth DSL - Bridged Ethernet
CheckPoint Safe@Office 4port Firewall - DHCP server

PROBLEM: On boot, Kontact won't recognize mail settings; Konqueror won't bring up any URLs.
WORKAROUND - after boot, "dhcpcd -k", then "dhcpcd -n" ALWAYS gets me back.

I've tried with / w/o / and various iterations of settings on the DSL modem / CheckPoint FW
It Used to Work. ~ 2 months.
================================
With the SuSE 9.1 Personal full install, I set

Control Center -> Yast2 Modules -> Network Devices -> Network Card -> Change > Edit
to the
"Network address setup" screen.

'Host Name and Server' bar -> [click modify if message popup occurs] brings up
"Host name and name server configuration" screen.

I have used all manner of entries here... For Name Server & Domain Search, 1,2,...
I've used "update...via DHCP" ,
I've used w/o "update...via DHCP",
I've used 198.162.1.1,
I've used the static entries provided by BellSouth.

Regardless - after boot, "dhcpcd -k", then "dhcpcd -n" ALWAYS gets me back.
===============================
NOTE: this problem began after I went to the local coffee shop to browse their free WLAN. The above process in YaST2 configured my WLAN right away. Came home, now LAN connection won't stay configured after reboot. Even w/ disabling WLAN. btw: there's an open AP in the neighborhood, if I leave the WLAN card active (there's a HW toggle switch on the LapTop), the above workaround authenticates me to the AP.
===============================
I'm responding to this post because the /etc/init.d/network restart was what I thought would help... but after running I get new DHCP addresses but lose my route.
===============================
the following excerpt from the start up log seems to say the eth0 recv'd a DHCP address...
this is with the WLAN (ath0) disbaled...

<notice>start services (network)
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done ath0 device: Unknown device 168c:0013 (rev 01)
ath0 configuration: wlan-id-00:90:96:84:3d:1b
ath0 warning: using NO encryption
ath0 (DHCP) . . . . modprobe: FATAL: Error inserting hw_random (/lib/modules/2.6.5-7.104-default/kernel/drivers/char/hw_random.ko): No such device


. no IP address yet... backgrounding.
waiting
eth0 device: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 83)
eth0 configuration: eth-id-00:08:0d:ef:63:d4
<notice>checkproc: /sbin/dhcpcd 1910
eth0 (DHCP) . . . . . IP/Netmask: 192.168.1.11 / 255.255.255.0
done<notice>checkproc: /sbin/dhcpcd 2562<notice>checkproc: /sbin/dhcpcd 1910

Hopefully I can help you out. I've wrestled with all kind of Linux problems before and I know how frustrating it can be. Anyway...

From what I can gather from your post, it seems that you want to be able to use your wired LAN connection at home, but the default route won't stick on reboot. I'm assuming that your DSL router is 192.168.1.1.

Do you get an IP address on eth0 when you reboot? It looks like dhcpcd is doing something funky when you reboot, like getting a command line parameter from somewhere (i.e 'dhcpcd 1910'). If doing dhcpcd-k and dhcpcd -n fixes the problem, you could of course go for the quick-n-dirty fix by adding these commands to /etc/init.d/boot.local or your .bashrc.

Can you send the output of 'ifconfig' and '/etc/sysconfig/network/ifcfg-eth0' ?

jp, thanx for the quick reply...

...From what I can gather from your post, it seems that you want to be able to use your wired LAN connection at home, but the default route won't stick on reboot.
that seems to be it???

...I'm assuming that your DSL router is 192.168.1.1.
the Checkpoint FW is 192.168.1.1; the DSL (bridged ethernet) is 192.168.1.254.

...Do you get an IP address on eth0 when you reboot?
No, not unitl I run dhcpcd -k/-n. (no UG in the route output either).

=======================
since posting, i made a change (of course),
i renamed the /etc/sysconfig/network/ifcfg-nnn files and re-ran YaST2 as above...

this created a new /etc/sysconfig/network/ifcfg-nnn for the eth0 (WLAN off)...
2 reboots - LAN ip and route config'd automatically on reboot...
=======================
seems there is some interaction w/ two net cards / eth0 (LAN) & ath0 (WLAN)
config'd via YaST2 that i'd love to understand...
=======================
here's the latest...(after change noted above since previous post)

linux:/etc/sysconfig/network # ll
total 71
drwxr-xr-x 6 root root 632 Aug 22 21:34 .
drwxr-xr-x 7 root root 1464 Aug 8 21:07 ..
-rw-r--r-- 1 root root 118 Aug 22 16:19 OLDifcfg-eth-id-00:08:0d:ef:63:d4
-rw------- 1 root root 461 Aug 22 16:19 OLDifcfg-wlan-id-00:90:96:84:3d:1b
-rw-r--r-- 1 root root 6712 Aug 16 20:59 config
-rw-r--r-- 1 root root 6343 Aug 22 21:34 dhcp
drwxr-xr-x 2 root root 48 Apr 6 12:04 if-down.d
drwxr-xr-x 2 root root 48 Aug 22 15:57 if-up.d
-rw-r--r-- 1 root root 118 Aug 22 21:34 ifcfg-eth-id-00:08:0d:ef:63:d4
-rw-r--r-- 1 root root 126 Apr 7 09:40 ifcfg-lo
-rw-r--r-- 1 root root 225 Jun 7 09:08 ifcfg-ppp0
-rw-r--r-- 1 root root 5723 Apr 7 09:40 ifcfg.template
-rw-r--r-- 1 root root 239 Apr 7 09:40 ifroute-lo
drwx------ 2 root root 80 Aug 22 15:27 providers
-rw-r--r-- 1 root root 0 Aug 20 21:14 routes
-rw-r--r-- 1 root root 25 Aug 20 21:14 routes.YaST2save
drwxr-xr-x 2 root root 1272 Aug 22 15:54 scripts
-rw------- 1 root root 109 May 29 18:47 update-log
-rw------- 1 root root 168 May 29 18:47 update-log.debug
-rw-r--r-- 1 root root 5471 May 29 20:17 wireless


linux:/etc/sysconfig/network # cat ifcfg-e*
BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='75Hn.FBHF3fNyZJ7'
_nm_name='bus-pci-0000:01:08.0'


linux:/etc/sysconfig/network # ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:0D:EF:634
inet addr:192.168.1.93 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::208:dff:feef:63d4/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4228 (4.1 Kb) TX bytes:6178 (6.0 Kb)

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

linux:/etc/sysconfig/network # route -vn
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
======================
and here's the old ifcfg files... 1st the LAN, then the WLAN...

linux:/etc/sysconfig/network # cat OLD*
BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='75Hn.FBHF3fNyZJ7'
_nm_name='bus-pci-0000:01:08.0'


BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='ul7N.tUUwRYkMFJ2'
WIRELESS_AP=''
WIRELESS_BITRATE='auto'
WIRELESS_CHANNEL=''
WIRELESS_ESSID=''
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
_nm_name='bus-pci-0000:01:05.0'
WIRELESS_AUTH_MODE='open'
WIRELESS_DEFAULT_KEY='0'
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'

=========================
=========================
philosphically, i'd get more people to convert from m$ to lx
if i could do most, if not all from the gui configs...

i.e., m$ makes setting up simple... but nothing works
v. lx which setting up can be a chore v. everything works going forward...

i'll note the shell changes because i did not know where to insert that...
my at&t unix days are a little rusty ;(

thanx for any further feedback.

Is the problem solved? I can't understand from your post.

I'm curious about the FW and DSL setup you have tho. You have an IP for the DSL modem and the firewall? Shouldn't the DSL modem be arranged behind the firewall?

no, my original problem is un-resolved... no LAN GW/routing/DNS automaticaly on reboot... but now it seems to be narrowed down a little more... WORKAROUND #2... delete the WLAN ifcgfg file. (This problem began after I 1st config'd the WLAN adapter. Prior to that, I used LAN eth0 exclusively).

my setup...
Bellsouth DSL incoming to Westel modem (ip 192.168.1.254), set to bridged ethernet, into WAN in port on CheckPoint FW (ip 192.168.1.1), which has a DHCP server built in. CheckPoint FW appliance has 4 standard LAN out ports for the LAN. I believe what this does is make the DSL modem a 'passthru' device(?).

something in the SuSE handling of two net cards is causing a conflict. when WLAN is config'd, LAN won't re-initialize automatically on reboot. they both work fine, it's just that eth0 needs to be kick started on reboot if WLAN is config'd.