ka1ifq wrote:
On Friday 16 February 2007 15:26, Peter Breger wrote:
John,
I am afraid that this is not it. The USRobotics router is a cable
router, and connected via ethernet cable to the network card. No USB
involved. Tested the hardware system with windows XP (bart PE) from CD -
perfect, used it even before under win98. The only way it works in Linux
Suse 10.1 is manually deleting the Network card config in Yast, running
through the finishing sequence in Yast, then reconfigurating the network
card with DHCP in Yast, running through the finishing sequence in Yast
---- then it works. After booting - no chance, again no connection.
Tried both network manager and ifup = same behaviour.
Searched through the boot sequence - yes, network is being connected
etc, but cannot get the DHCP address collected.
Question - in the boot sequence, what needs to be installed in what
sequence to allow DHCP etc to be successfull i.e. if maybe one item is
missing or starte din wrong sequence, then network detection, setup etc
is not possible during boot.
Any suggestions how to detect hickups in boot sequence? (Log file is not
very revealing for me, other than to see that DHCP acquisition is not
successful - which I know anyway).
Peter
PS I am posting thsi direct e-mail to the mailinglist in hope of
re-establishing finally a working thread.
You are setting the card to use DHCP, are you running a DHCP server on your
Linux box or your router?
Linux PC is set up as client only, connected via ethernet to a hardware
router which does the DHCP serving
Do you see any errors or warnings when yast is completing its run, or in any
of the log files?
Mmmh - where would I have to find these (you see I am new to Linux...)
... boot.msg has something to say, here is a short summary of what it
has to say on network matters (sorry, cannot actually use file text cut
and paste but have to retype laboriously in this mail on another Windows
PC, [] encloses my own comment)
setting up network interfaces:
lo IP address: 127.0.0.1/8 done
eth0 device: 3Com [and all kinds of bla bla on hardware card]
eth0 configuration: eth-bus-pci-0000:00:0f.0
eth0 (DHCP) . . . . . no IP address yet ... backgrounding.
Warning: could not set up default route via interface.
Command ip route replace to default via 192.168.1.1 returned: .RTNETLINK
answers Network is unreachable
Configuration line. default 192.168.1.1 - -
[then all kinds of other bla bla until it gets back to matter on hand]
eth0 dhcpcd is still waiting for data
waiting
eth0 interface could not be set up until now.
Sounds to me like a problem during boot process which later does not
occur. Where do I start diagnosing that?
How long are you waiting for the connection, can take some time depending on
the speed of the computer or router?
Mmmh - where would I see that? I guess the mutiple dots in boot.msg
correspond to some long waiting. When I am successfull with the manual
setting up the network using YaST the log of NetworkManager shows dhcp
step is un-noticeably fast. (I.e. no long waiting or dots indicated)
Mike
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
