Hi again,
Suse 10.0 will not connect thru a wired (linksys) home network...This is still a struggle but I may finally have a clue..
I ran as su the command "ifstatus eth0" and discovered that in 9.2 and 9.3 there is only (1) one configured route..Both the above
suse versions connect to the internet/DHCP with no problem.. Same exact systen with another hard drive, suse 10 (OSS) shows three configured routes with one active..This also shows that (No-Carrier broadcast,multicast.notrailers.up line..I am guessing there is some kind of script error that is stopping my connection to the internet..
It is evident that this seems to be a problem for some and not for others...My question is yast putting three routes even though only one is entered..
How can one check the routing..Is there some file to inspect?
Thank You for any help or suggestions,
jolphil

look at the "route" command

Thanks, I will...Wow that was simple enough..
Thanks again, and I will get back with any results..
jolphil

Hi again,
Sorry about the delay..I tried just about all I know (very little) and what I read but still no joy..I may have to give up on the later versions of Suse on my system..
Not only network problems on 10.0 but also parallel port printer problems on 9.3 version..The last one to work on my system is 9.2 and that works perfectly..Iam on it at this very moment..sigh!!
jolphil

Hi,
Just an update to this problem..Unable to resolve the network problems in 10.0 but at least was finally able to connect to the internet for about a minute or so several times..I can only go to the novell website in konqueror once or maybe two pages at the most...Then it shuts down and refuses to go anywhere else..I tried for a month or so including altering the boot options (acpi=off,acpi=noirq) discussed in other threads..It seems to me that somehow the interrupts are causing my problems..My network card irq is combined with the usb interrupts and others..I guess my combination of motherboard and devices are more than 10.0 can handle..Even if I can connect to the internet I cannot resolve my parallel printer problem..I have tried altering my BIOS settings for the port but that also does not help..
I went back to the 9.3 version and it connects to the internet just fine but will not configure my parallel port HP810/812 printer..Yast complains no communications with the lp0..Like the above I exhausted my tries at getting it to work..

Thus my favorite Linux distro cannot be upgraded from my working 9.2 version..I'll have to stick with that for now..
I took the hard drive with suse 10.0 and wiped it clean and installed Mandriva 2006..First time everything worked..Sad but true..Thank you for all the help and for reading this post..
Actually while not a Mandrake/Mandriva fan it looks good and better yet works fine..Even tried Ubuntu and it installed and works on the same system..Go figure..
jolphil

Hello,
One thing in your post caught my eye, ie. "was finally able to connect to the internet for about a minute or so several times".

This same thing happened to me; I was using *KInternet in version 9.3 and attempted to do the same when I upgraded to 10.0. I fiddled with it for over a week and could only connect for a minute or so everytime.

In desperation, I tried KPPP. It worked the first try and has been working ever since. I have no idea what caused this, whether something I did, hardware or what, but it only takes a few minutes to set up KPPP and it worked for me.

Note that KPPP and KInternet (both on K-Menu>Internet>dialup both show the same icon on the *menu, but when running *KInternet the icon *in the system tray will show as a connector or plugged in connector depending on whether you are connected or not.

KPPP on the other hand, shows the shows the same icon in the system tray (globe over modem icon). I would have thought that these programs were equivalent, but KPPP works for me under 10.0 and I could not make KInternet work.

Hope this helps,
J.May

Incidentally, this could be responsible for your other network problems under Suse 10.0
That is, assuming you are using ppp and allowing it to modify resolv.conf which is usually the case. **If this is what is happening, you are correct that it is a scripting problem.
If you are not using ppp then I apologize for wasting your time and you should disregard this post.

Once the pppd has established a connection exists between you and your isp, it calls the add_nameservers() function in the ip-up script. This function in turn calls the /sbin/modify_resolvconf script.

The addresses of your isp's name servers (passed in to pppd right after the initial modem handshake) are now passed to modify_resolvconf which makes a copy of your existing /etc/resolvconf file and adds the isp's nameservers to this copy. It then renames the original resolv.conf, then renames the copy to resolv.conf and then causes the dns service to reload it's config files (thus adding the isp's nameservers to the routing table).

There are very few isp's which don't use dhcp and pass in the nameservers this way. This makes it very difficult to manually maintain the resolv.conf file; it also is the only logical way to do it.

When the connection goes down, ip-down is called and the process is exactly reversed; that is the ppp copy of resolv.conf is deleted and the original is renamed back to its proper name of resolv.conf. Again the dns service is called upon to reload it's config files. This causes the isp's nameservers to be removed from the routing table and puts everything back the way it was before you dialed in.

**If your connection is going down after a minute or two (or seconds) after it is established the routing table is going to be unreliable for your clients. In this scenario *_ANY_* network service (and any client using these services) which rely on the machine from which the dialup is being done will have problems.

Good luck,
J.May

Interesting reply..But as I mentioned the drive was wiped clean and another system was installed on it,but it may help others..I am a bit confused as I thought those two packages were for dial up and i am on cablemodem..Any way glad to hear you box is working..kudos to you..
Thank you for your reply that is in the true spirit of this forum..
jolphil

Hi again,
Finally after a month, now online..For all users that may have the same problem,heres what I found..
On the Suse forum one user suggested that it is a bug in the "tulip" module..He gave the Bugzilla url, "https://bugzilla.novell.com/show_bug.cgi?id=12894"
Since I had wiped Suse off the HD I had to do a new installation,
and choose to install without acpi..Im Not sure that did much good but did it anyway..During the install it again failed to connect to the internet,as B4.. after installation completed,went to yast and network devices,edit,advanced hardware details, and changed the module to "dmfe" no quotes and "forced" options no quotes..I then rebooted and volia internet..
I have just installed the updates and rebooted again so far so good..What a battle.......
jolphil

If you have a cable modem don't use dial up connections like kinternet. Set your network interface to eth0, your Ethernet port. I'd install knemo as it gives you a visual of the network connection and has a pop up with with all the IP and other connection information.