John Andersen wrote:
On Sunday 04 February 2007, Peter Breger wrote:
John Andersen wrote:
I thought I had seen where you configured your computer to use a nic rather than USB and then configured the router via a web browser, and the problem was solved.
Did I confuse two threads?
Yes - I think you must have. But the problem is still as vexing as ever. Regards, Peter
Well that was the solution on that other thread, and it was mentioned that it was the only way you will likely get it working and the usb interface seems only available to windows, whereas the use of a standard NIC in the machine works flawlessly and is actually easier to manage.
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org