Bug 397966

Created attachment 220747 [details]
yast2logs

It works perfectly for me.
Also from your yast log, it's configured perfectly.
And as you wrote, network "somehow" works. But :
>Unknown (PPPoE-style) DSL Device Detected

says that device is probably unknown for kernel. What is "hwinfo --dsl" output?
What device name is that?
Is there some warning/error in "dmesg" or "/var/log/messages" during dsl network failed?

YaST has always said that my DSL modem is unknown (Unknown (PPPoE-style) DSL Device Detected), but it has always worked nonetheless. I am working from 10.3 right now (my modem is a D-Link 302T).

hwinfo --dsl doesn't give any output.

However I am attaching: a snapshot of hardware information, PPP over Ethernet, the  "dmesg" output and a copy of "/var/log/messages".

Created attachment 221309 [details]
Attachments as described above

Info provided in above attachment

Could you compare working and non-working configuration files? Under /etc/sysconfig/network/ifcfg-dsl0 and /etc/sysconfig/network/providers/* ?

Created attachment 222114 [details]
Info as requested.

Info as requested.

The folder "Working" relates to 10.3. The folder "Not-Working" relates to 11.0 before starting smpppd. The folder "Minimally-Working" refers to 11.0 after starting smpppd manually.

This is probably dsl driver problem - configuration files are without difference
On 10.3 what is "hwinfo --dsl" output?

Do you actually use your network interface for anything? It's configured for dhcp and gets an ip address assigned. The lease time for it is only 60 seconds though. So it gets renewed all the time. Maybe that disturbs the dsl connection. Also dhcpcd and pppd are fighting for the ownership of /etc/resolv.conf. Have you tried to configure your eth0 interface to a fixed static ip or to not configure any ip at all (the interface needs to be up though)?

Mr  Michal Zugec,

As I already told you, hwinfo --dsl doesn't give any output.

Mr Ludwig Nussel

Yes, of course I use my network interface (when it works) for surfing, mail, p2p...
Regarding everything else I have borrowed a router from a friend, which of course works.
However I can reinstall my modem if you want.

(In reply to comment #9 from Michal Zugec)
> This is probably dsl driver problem - configuration files are without
> difference
> On 10.3 what is "hwinfo --dsl" output?
> 

Sorry Mr Zugec, I misunderstood you. As I said to Mr Nussel, I am using a router now, but if you want I can reinstall my modem.

We can't debug the problem if you don't actually use the modem of course. Please restore the setup with the dsl modem on 10.3 and run "hwinfo --dsl" and post the result. If that works reboot into 11.0 and also run "hwinfo --dsl" and attach the result.
If 11.0 can't dial in properly please configure the network interface eth0 to a static ip address and try again and let us know the result.

Mr Ludwig Nussel

I did as required. The following is the outcome:

OpenSUSE 10.3

hwinfo --dsl

pppoe.2: discovery

No output
-----------------------------------------
OpenSUSE 11.0 (updated to 17 June 2008

hwinfo --dsl

(very fast attempt to get info, I can't read it)


No output

---------------------------------------------------

Reconfigured DSL, pppoe, no other change

I still need to start smpppd manually, but the internet connection works fine now.

Sorry, of course I need to start kinternet manually as well.

So the real bug is that smpppd was not started. Kinternet will start automatically only if smpppd is already running when you log into kde.

Mr Nussel

I wouldn't say that the "real bug is that smpppd was not started"
Rather, something has changed after a "zypper dist-upgrade", because as I explain in my original post, originally starting smpppd and kinternet was not enough.

I have installed 11.0 final, after formatting.
The only problem now seems that kinternet refuses to start until you start smpppd manually. However the connetion works! (working as root).

Working as user the situation is almost identical (the connection works).
But if you want to use kinternet you must start smpppd with root privileges, obviously).

use the yast2 runlevel editor (or "chkconfig smpppd on") to enable smpppd at boot. YaST should have done that though.

Test following code, please:
{
import "ISDN";
import "Wizard";
import "Popup";
include "network/runtime.ycp";

Wizard::CreateDialog();
ISDN::Read();

Popup::Message(sformat("Dialup interfaces :%1", HaveDialupLikeInterfaces()));

}

write it into /tmp/test.ycp and run as root "yast2 /tmp/test.ycp"

Mr  Ludwig Nussel,

I did what you suggested, thanks. However I haven't rebooted yet, but I suppose it will work.


Mr  Michal Zugec

I tested your code. YaST starts "Initializing ISDN Card Configuration" (AFAIK, I don't have one): dialup interfaces:true

Mr Nussel

I can confirm: I rebooted and kinternet started on its own, wow!

Ok, one more test:
- disable smpppd by: "insserv -r smpppd"
- check with "chkconfig smpppd" (expected is "off")
- backup yast logfile "mv /var/log/YaST2/y2log /var/log/YaST2/y2log.old"
- start YaST, edit your DSL settings
- check service status again: "chkconfig smpppd" (expected is "on")
- in case that service status is "off", attach here /var/log/YaST2/y2log file

Thank you

Created attachment 223531 [details]
YaST2.tar.gz

Mr  Michal Zugec  

I did as you suggested. The last "chkconfig smpppd" check returned "off"
I am therefore attaching the entire /var/log/YaST2/ compressed folder.

Oh, yes!
After long time problem detected
fixed in yast2-network-2.17.4
Thank you for participation, Lanfranco

Great!
You are very welcome. I am always glad to help my favourite distribution :)