Bug 133411 - interface not automatically started in kinternet even after configuring DoD
Summary: interface not automatically started in kinternet even after configuring DoD
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: 32bit SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Arvin Schnell
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-11 07:53 UTC by Raghu GS
Modified: 2005-11-23 14:14 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Raghu GS 2005-11-11 07:53:25 UTC 
after coniguring Dial-on-Demand,
in every boot the interface not automatically started by Kinternet,
ir must be manualy started,
without starting interface automatically then what is the purpose of Dial-on-Demand,
Comment 1 Dr. Werner Fink 2005-11-11 10:25:00 UTC 
Dial-on-Demand: Any access to a remote adress should trigger a dialin.
Comment 2 Raghu GS 2005-11-11 11:43:30 UTC 
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.
Comment 3 Arvin Schnell 2005-11-14 09:40:05 UTC 
Set STARTMODE='auto' in /etc/sysconfig/network/ifcfg-dsl0 or by
using YaST.
Comment 4 Lewis Rosenthal 2005-11-23 13:41:53 UTC 
(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
Comment 5 Arvin Schnell 2005-11-23 14:14:51 UTC 
We do not invest further resources in kinternet.  It will be replaces
by NetworkManager.