• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Networking in Linux? (SuSE 8.0)

N

NTB

Diamond Member
I can't get SuSE to recognize my little home network. It did find my network card (built-in SIS ethernet), but I can't get through the Linksys router at all. It's like I'm not even connected to the network. DHCP isn't working right for some reason; I can tell because as it goes through the boot sequence - and the steps come up on the screen - it hangs on getting an IP address by DHCP for a second before it says "(backgrounding)" and goes through the rest of the boot. What I can't figure out is exactly what isn't working right. I know this setup does work, thouhg; I've never had a problem under Windows XP. Any suggestions? Thanks!

Nate
 


<< Got the DHCP daemon running? service dhcpcd start >>



"Cannot run this command" is all I get when I type that in the RUN dialog box. The program is there though; I searched for the dhcpd files. And like I said; it's obviously running something when it boots up; the problem is that whatever is running isn't working right - I never get an IP address. Any other suggestions? Sorry about asking so much, but I'm new to this; it's the first time I've given an alternate OS a serious shot. So far this is the only thing I've found that hasn't worked.

Nate
 
forget the "run" dialog.

open a terminal and type:
tail -f /var/log/sys.log
or
tail -f /var/log/messages
(whichever exists on a suse system)

open another terminal and type:
dhcpcd -d

any interesting output?
 


<< forget the "run" dialog.

open a terminal and type:
tail -f /var/log/sys.log
or
tail -f /var/log/messages
(whichever exists on a suse system)

open another terminal and type:
dhcpcd -d

any interesting output? >>



The results:

linux:~ # tail -f /var/log/messages
May 7 00:01:56 linux kernel: parport0: Printer, HEWLETT-PACKARD DESKJET 710C
May 7 00:01:56 linux kernel: lp0: using parport0 (polling).
May 7 00:01:56 linux kernel: lp0: compatibility mode
May 7 00:02:01 linux /usr/sbin/cron[1005]: (CRON) STARTUP (fork ok)
May 7 00:02:03 linux /etc/hotplug/net.agent[759]: No HW description found ... exiting
May 7 00:02:18 linux kdm[1066]: pam_unix2: session started for user root, service xdm
May 7 00:02:32 linux modprobe: modprobe: Can't locate module sound-slot-1
May 7 00:02:33 linux modprobe: modprobe: Can't locate module sound-service-1-0
May 7 00:02:33 linux modprobe: modprobe: Can't locate module sound-slot-1
May 7 00:02:33 linux modprobe: modprobe: Can't locate module sound-service-1-0
 
looks like dhcpcd is either not in your PATH (unlikely)
or it's just dying at startup
Are you sure your nic is being recognized?
you can check with:
dmesg | grep eth
or
lsmod (if it's loaded as a module)
or you'll get an unknown device error if you try to bring up the interface:
ifconfig eth0 10.0.0.1
 
If I'm reading these correctly, it is identifying my network card. Something must be wrong with DHCP:

linux:~ # dmesg | grep eth
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xc400, IRQ 10, 00:07:95:a7:38:79.
eth0: Media Link On 100mbps full-duplex
eth0: Media Link On 100mbps full-duplex
eth0: no IPv6 routers present

linux:~ # lsmod
Module Size Used by Not tainted
snd-pcm-oss 45152 0 (autoclean)
snd-mixer-oss 11136 0 (autoclean)
parport_pc 25448 1 (autoclean)
lp 5824 0 (autoclean)
parport 21856 1 (autoclean) [parport_pc lp]
snd-seq-midi 4480 0 (autoclean) (unused)
snd-emu10k1-synth 5504 0 (autoclean)
snd-emux-synth 28480 0 (autoclean) [snd-emu10k1-synth]
snd-seq-midi-emul 4560 0 (autoclean) [snd-emux-synth]
snd-seq-virmidi 3720 0 (autoclean) [snd-emux-synth]
snd-seq-oss 24128 0 (autoclean)
snd-seq-midi-event 2664 0 (autoclean) [snd-seq-midi snd-seq-virmidi snd-seq-oss]
snd-seq 39596 2 (autoclean) [snd-seq-midi snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event]
snd-emu10k1 62820 0 [snd-emu10k1-synth]
snd-pcm 58528 0 [snd-pcm-oss snd-emu10k1]
snd-timer 11456 0 [snd-seq snd-pcm]
snd-hwdep 4736 0 [snd-emu10k1]
snd-util-mem 1472 0 [snd-emux-synth snd-emu10k1]
ipv6 123424 -1 (autoclean)
snd-rawmidi 13536 0 [snd-seq-midi snd-seq-virmidi snd-emu10k1]
snd-seq-device 4336 0 [snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-seq-oss snd-seq snd-emu10k1 snd-rawmidi]
snd-ac97-codec 24196 0 [snd-emu10k1]
snd 31720 0 [snd-pcm-oss snd-mixer-oss snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event snd-seq snd-emu10k1 snd-pcm snd-timer snd-hwdep snd-util-mem snd-rawmidi snd-seq-device snd-ac97-codec]
soundcore 3268 10 [snd]
isa-pnp 27816 0 (unused)
hid 17824 0 (unused)
joydev 5728 0 (unused)
evdev 3904 0 (unused)
input 3072 0 [hid joydev evdev]
st 25844 0 (autoclean) (unused)
sg 23620 0 (autoclean)
usb-ohci 18880 0 (unused)
usbcore 55136 1 [hid usb-ohci]
af_packet 11528 0 (autoclean)
sis900 11972 1
lvm-mod 58016 0 (autoclean)
ide-scsi 7648 0
reiserfs 158816 1

linux:~ # ifconfig eth0 10.0.0.1
linux:~ #

running that last one - ifconfig - did nothing at all; no error messages, nothing.

Nate
 


<< can u dl Suse for free? >>



Nope. There is a "Live Eval" version of 7.3 at linuxiso.org but a)it's older and b) I don't think it's a full version of the OS, just a demo.

Nate
 
awwwww nutz!

anyone else recommend a linux distribution besides RH and mandrake for free DL? Im losing my pipe in 2 weeks and wanna play around with linux during the summer
 
NTB,

To check that your network interface is recognized by the kernel, run

/sbin/ifconfig

I believe I saw another recent post in these forums (OS or Networking) where a user complained that DHCP didn't work w/ their onboard LAN and Linux (same as you). Can you try static addressing as a base case?

If I can find the thread, I'll refer to it here. Searching is difficult without a subscription because we don't get full-text searches.
 
/sbin/ifconfig did turn up something this time, but being a n00b, I can't make heads or tails of it, I don't think. If I am reading it correctly, it is sending and recieving data - so why can't I connect to anything?

linux:~ # /sbin/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:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1956 (1.9 Kb) TX bytes:1956 (1.9 Kb)

linux:~ #

Nate
 
From your last post it looks like the NIC is recognized & running. But no IP address has been assigned.

Is your router set up as DHCP (It probably is) that may be your problem. There can only be one DHCP server on the network.

if disabling the DHCP daemond & see what happens.

Another option is to assign IPs to everything. Not too difficult but eliminates the need for the DHCP server.

Just some thought. Hope they help

AlricTheMad
 
NTB, read the Net HOWTO when you get a chance. It's a nice comprehensive networking primer.

Okay, ifconfig reports that the only network interface you have is lo. This is the loopback interface, which is a virtual interface within the kernel that loops back to your host.

If Ethernet was being properly detected and setup, you would see an eth0 device as well. So that's why the DHCP client has no work to do; the network interface isn't up yet.

You can try to use the ifconfig command to manually bring up eth0, to establish that it's possible. You're certain that Yast2 has one Ethernet device setup?
 
Yes - Yast2 lists an SiS900 ethernet connection, and I've got it configured for DHCP. On bootup, the log shows:

lo
Eth0
(DHCP). . . .(No IP; backgrounding). . .

or something to that effect. I can post that part of the bootlog if you want to see exactly what it says.

Nate
 
I know what you mean by the bootup log, and while somewhat informational, those lines don't mean much (besides reporting success or failure).

Like my previous analysis said, what appears to be happening is that the Ethernet network interface is not being established. To try it manually, as root:

# ifconfig eth0 up
# ifconfig

That attempts to bring the interface up, and then queries all the interfaces. Verify that eth0 is listed (as opposed to previously). If it is listed, that's a sign of progress. Once the interface is up, the remaining steps are to configure the TCP/IP stack (ideally done by DHCP automatically) and to add suitable entries to the routing table.

Now normally, all these steps are done automatically by script, but apparently something needs diagnosis/fixing with your situation. Good luck.

If anyone has subscription access, he can try to do a full-text search for the person with the same problem as you (installing Linux on a system w/ onboard LAN). IIRC, someone mentioned southbridge in a reply. I also believe Nothinman replied in that thread. I don't remember exactly which forum topic that thread is in, but it was fairly recent (i.e. within 2 weeks).
 
Now I'm getting somewhere, I think:

linux:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:07:95:A7:38:79
inet6 addr: fe80::207:95ff:fea7:3879/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:120 (120.0 b) TX bytes:288 (288.0 b)
Interrupt:10 Base address:0xc400

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

Next step is to fire up dhcpd, but that spits out an error message telling me that it can't find dhcpd.conf. So I typed out the example in the helpfile (and manual) and saved it in the /etc directory, as told:

default-lease-time 600;
max-lease-time 7200;

option domain-name "kosmos.all";
option domain-name-servers 192.168.1.1, 192.168.1.2;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option subnet-mask 255.255.255.0;

subnet 192.168.1.0 netmask 255.255.255.0
{
range 192.168.1.10 192.168.1.20;
range 192.168.1.100 192.168.1.200;
}

start dhcpd again, and get this:

linux:~ # dhcpd start
Internet Software Consortium DHCP Server V3.0.1rc6
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

** You must add a ddns-update-style statement to /etc/dhcpd.conf.
To get the same behaviour as in 3.0b2pl11 and previous
versions, add a line that says "ddns-update-style ad-hoc;"
Please read the dhcpd.conf manual page for more information. **

Open dhcpd.conf, add that line, save, start dhcpd again, and get this:

linux:~ # dhcpd start
Internet Software Consortium DHCP Server V3.0.1rc6
Copyright 1995-2001 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
can't parse standard ddns updater!

now what? my guess is to change that last line from ad-hoc to something else, but what? or is it something completely different?

Thanks!

Nate
 
NTB,

Try assigning IP's to your devices, even if temporarily. At least you will know if the network is working.

I still think that you may have conflicts with the DHCP server on the router unless it has been disabled. Then I don't think it will accept an assigned IP

Another thing you can try is to connect the PC you are working on direct to your internet gateway. Once again this may help you isolate the proplem.

<EDIT> I just noticed that you used ip address 192.168.1.1. & 1.2 for your DNS servers. Are you running your own DNS servers at home? that may be why DHCP is having some of it's problem. <EDIT>

AlricTheMad
 
That's the DHCP server, not the DHCP client. You don't need to run this for basic networking.

In SuSE 7.2, the DHCP client is in package dhcpcd

To manually invoke it, as root:

# rcdhclient start

While it does have some minimal configuration possibilities, it's configured out of the box and ready to go.

If that doesn't work, you can try static addressing as a base case. man ifconfig to find out how
 
w00t! posting from Konquerer right now. Thanks for all the help. Here's what I finally used to get up and going:

# ifup eth0

Nate🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top