|
Bugzilla – Full Text Bug Listing |
| Summary: | interface not automatically started in kinternet even after configuring DoD | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Raghu GS <raghugs> |
| Component: | Network | Assignee: | Arvin Schnell <aschnell> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Raghu GS
2005-11-11 07:53:25 UTC
Dial-on-Demand: Any access to a remote adress should trigger a dialin. i think you had'nt understand my description correctly. first of all for triggering a dailin the interface must be started before, else any request to remote address would fail. Expected Behaviour is Kinternet must automatically start the interface in every boot. Set STARTMODE='auto' in /etc/sysconfig/network/ifcfg-dsl0 or by using YaST. (In reply to comment #3) > Set STARTMODE='auto' in /etc/sysconfig/network/ifcfg-dsl0 or by > using YaST. > Actually, even setting this does not automatically start kinternet IF automatic login is selected for a given user. Steps to reproduce: 1. Configure kinternet to start automatically. 2. Configure automatic login for a user (with privs to run kinternet). 3. Restart system. Condition: KDE desktop initializes, but kinternet does not start. It can be manually started from the kicker. Should be: kinternet should start automatically. If the user is subsequently configured NOT to automatically login, that is, if the system boots to the login screen, logs in (that same user or another one), kinternet will automatically start. Reproduceable: Always Lewis We do not invest further resources in kinternet. It will be replaces by NetworkManager. |