John Andersen wrote:

On Friday 16 February 2007, Peter Breger wrote:

...

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.

And you are SURE there is no firewall blacking dhcp?

Good question John - how do I check status of firewall without starting something running? Certainly /var/boot.msg has no reference to firewall and starting YaST shows on firewall tab that service start is set to manual, firewall is not running and offers the button to start it. So that seems ok to me then. While I am on subject of boot.msg, 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, [] 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? Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan wrote:

* Peter Breger [02-18-07 09:29]:

...

... 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.

I have similar problems on occasion, my router looses dhcp and my local network goes down including access outside.

Unplug the power cord from your router for > 2 minutes. Reconnect and issue as root, rcnetwork restart.

ping an outside connection to check status, ping yahoo.com

Thanks Patrick, but the router is correctly keeping all other PCs happy on the network, I cannot interrupt other peoples use of network by fiddling with the router everytime I switch on my Linux pc . (You just try and boot the family of the net...Teenage wrath will be unleashed instantaneously on unsuspecting dad ... ;-) ) It is the boot process on the Linux that is at fault, being the only process which is not successful. Manual YaST setup succeeds. (Same as simultaneous use on other computers running windows does not show any problems at all). Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. wrote:

On Sunday 18 February 2007 09:09, Peter Breger wrote:

...

but the router is correctly keeping all other PCs happy on the network, ... It is the boot process on the Linux that is at fault, being the only process which is not successful. Manual YaST setup succeeds. (Same as simultaneous use on other computers running windows does not show any problems at all).

Hi Peter,

Have you tried to setup static address for your connection? This will either solve your problem or make possible to cut and paste text direct from Linux box to continue DHCP troubleshooting :-)

You need some local address that is not used by router as DHCP range. By now all routers, that I have configured, don't use range between 192.168.x.201 and 192.168.x.254. The default route is your router 192.168.1.1 (I guess). The name server is the same as default route. Subnet Mask is usually 255.255.255.0

In YaST -- Network Devices -- Network Card use for this time Traditional Method with ifup. In Network Address Setup window mark: x Static Address Setup

IP Address Subnet Mask 255.255.255.0

Click on Host and Name Server. It will pop up the window with warning, click on Modify. For now leave Hostname and Domain Name fields unchanged. Name Server 1 is <you-router IP> for instance 192.168.1.1 and you don't need any other entry on local network, router is taking care of that. Click OK.

Now you have to configure Routing that is hidden under the same name button. Enter in the field Default Gateway <you-router IP> ie. 192.168.1.1 Click OK. Click Next and Finish.

Thanks Rajko! I am afraid that did not do it either. In fact I had tried it before, but with your suggested IP range, I had another go at it. The assignment of IP address worked, however the Ping 192.168.1.1 then resulted in Destination Host unreachable. Had to first go through a full cycle with YaST : deleting card configuration ... then entering YaST again editing card configuration with static address --- voila it works while in the session -- BUT NOT AFTER REBOOT! So the behaviour is the same as with DHCP. It is possible to delete Network card configuration, then in a new YaST run edit it to connect successfully. But never on reboot (of course I use ON CABLE CONNECT in YasT for manual start of connection and ON BOOT for preparing a rebooting. Another snippet - after rebooting, the card has no IP address (previously set static 192.168.1.202). I then use ifconfig eth0 down. THEN type ifconfig eth0 192.168.1.202. THEN ifconfig eth0 up -- it works again. But not after reboot. What is it that is missing in the boot sequence??? Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Breger wrote:

Peter Breger wrote:

...

Rajko M. wrote:

...

On Sunday 18 February 2007 09:09, Peter Breger wrote:

...

...

but the router is correctly keeping all other PCs happy on the network, ... It is the boot process on the Linux that is at fault, being the only process which is not successful. Manual YaST setup succeeds. (Same as simultaneous use on other computers running windows does not show any problems at all).

Hi Peter,

Have you tried to setup static address for your connection? This will either solve your problem or make possible to cut and paste text direct from Linux box to continue DHCP troubleshooting :-)

You need some local address that is not used by router as DHCP range. By now all routers, that I have configured, don't use range between 192.168.x.201 and 192.168.x.254. The default route is your router 192.168.1.1 (I guess). etc etc

Thanks Rajko! I am afraid that did not do it either. In fact I had tried it before, but with your suggested IP range, I had another go at it.

The assignment of IP address worked, however the Ping 192.168.1.1 then resulted in Destination Host unreachable. Had to first go through a full cycle with YaST : deleting card configuration ... then entering YaST again editing card configuration with static address --- voila it works while in the session -- BUT NOT AFTER REBOOT! So the behaviour is the same as with DHCP.

It is possible to delete Network card configuration, then in a new YaST run edit it to connect successfully. But never on reboot (of course I use ON CABLE CONNECT in YasT for manual start of connection and ON BOOT for preparing a rebooting.

Another snippet - after rebooting, the card has no IP address (previously set static 192.168.1.202). I then use ifconfig eth0 down. THEN type ifconfig eth0 192.168.1.202. THEN ifconfig eth0 up -- it works again. But not after reboot.

What is it that is missing in the boot sequence???

Regards, Peter

Had another go at things - installed Suse 10.2 after speaking to Suse people at FOSDEM - no luck!

Already in text mode level 3, I cannot succeed to get to the network. rcnetwork restart does not help either

Although it seems illogical since it can be got to work manually (no longer in suse 10.2 yet), I am using a ethernet cable to a powerline plug -- anybody with experience if this use of a powerline network needs another setup item? Router and windows pcs do not sem to care about teh powerline conversion inbetween, since the output from pc or router is simply ethernet cable.

Forever hopeful, Peter

Ok - I admit it was the powerline networking. I should have known better .. sigh ... Went out and bought xxx m of ethernet cable for up and down the stairs across the corridors - now pc boots with DHCP no problem. Question now: What do I need to get the powerline converter working in linux? (Ethernet cable to powerplug converter is from ACER) Thanks to those that tried helping before ! Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. wrote:

On Saturday 03 March 2007 09:25, Peter Breger wrote: ....

...

Ok - I admit it was the powerline networking. I should have known better .. sigh ... Went out and bought xxx m of ethernet cable for up and down the stairs across the corridors - now pc boots with DHCP no problem.

Question now: What do I need to get the powerline converter working in linux? (Ethernet cable to powerplug converter is from ACER)

Here you would need some expert for for networks :-) This is from one of the earlier posts:

...

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. ... eth0 dhcpcd is still waiting for data waiting eth0 interface could not be set up until now.

I would assume that NIC driver doesn't get all data timely during the boot and the driver is not loaded. To check run lsmod and see does 3com driver, or anything that seems to be 3com is listed. If you can't find the module under 3com<something> than save output of lsmod to the file, go on with YaST Network, than back to lsmod and compare outputs.

Once you have the correct name you may reboot, check network status, and try to load manually the driver with modprobe <driver name> and see if it helps. Hopefully there are not some module parameters that should be added to make it load correctly.

If there is module when network is down than just try to rmmode <driver name> and then modprobe <driver name> and see result.

In both cases after module is (re)loaded run rcnetwork restart and see if you have network.

Thanks - I shall give that a try later and investigate the applicable driver for powerline cases. Anybody out there who has done this sort of thing before for networking via powerline - there was a post 03852 on 26 Sept 2003 at 23:10, so maybe someone solved this sort of thing before? Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org