|
Bugzilla – Full Text Bug Listing |
| Summary: | Can't connect to ADSL | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Matej Repinc <mrepinc> |
| Component: | Network | Assignee: | Christian Zoz <zoz> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | jlp, max, mvidner, suse-beta |
| Version: | Beta 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Folders /var/log/YaST2/ and /etc/sysconfig/network. | ||
|
Description
Matej Repinc
2006-03-09 22:11:17 UTC
Please attach the directory /var/log/YaST/ as well as /etc/sysconfig/network. Created attachment 72832 [details]
Folders /var/log/YaST2/ and /etc/sysconfig/network.
I could only find the YaST2 directory and not YaST.
Asking Martin for help. I installed SuSE Linux 10.1 beta 9 today, and i still can't connect to ADSL. Do you need the folders /var/log/YaST/ and /etc/sysconfig/network ? Have you checked the bug? Will the bug be still present in 10.1 final release? Too much other work, sorry :-( The config files look ok (except the colons are replaced by underscores in the ifcfg filenames, but I suppose that's just a side effect of using zip instead of tar. see also http://en.opensuse.org/Bug_Reporting_FAQ#YaST ) So I think it is a sysconfig problem I tried to connect to adsl via console, but the commands pppoe-start, adsl-start and pppoe-conf were not found. May this be the problem? Disable NetworkManager and switch to 'traditional network setup'. Does dsl work then? I switched from Network Manager to "Traditional network setup with ifup" and it dosen't work either. Reinhard, afaik you inherited our dsl equipment and the dsl line from Arvin. Did you test dsl functionality on code10 products? I just re-checked it, and it works fine. Kinternet allows me to create and destroy the PPPoE connection, and if the password wasn't saved in the network configuration, it asks me for it. So this bug report looks much like a user error tom me. Matej, SUSE Linux doesn't contain commands that are named pppoe-start, adsl-start and pppoe-conf. PPP(oE) connections are opened either via dial-on-demand (which I think requires you to save the password in the network configuration), or via one of the client programs that connect to smpppd (i.e. kinternet or cinternet), which ask you for the password if needed when you tell them to establish the connection. The only peculiarity I noticed in my test was that the YaST DSL module didn't auto-detect the DSL modem (a regular ethernet-based one from Deutsche Telekom connected to eth1), although tcpdump showed that during the detection phase of the YaST module the right PPPoE discovery packages got sent and answered. Whoops, I have to correct myself. There is a command called pppoe-start in the rp-pppoe package that is contained in SUSE Linux, but that package is not needed for normal PPPoE internet access. Matej, does your DSL line work with other versions of (SUSE) Linux, or with other operating systems? My DSL line worked okay with Mandriva Linux 2005 and 2006, Knoppix and M$ win xp. Modem is ISKRATEL Calisto821(got it from my ISP SiOL). I'll try connecting with Kinternet and Cinternet. Yup, it works with Kinternet, thanks for all your help! Fine. NM cannot handle DSL connections currently. That's not a bug but a missing feature. NetControl (traditional method) works. --> INVALID |