Bug 145027 - doesn't set default gateway if already present
Summary: doesn't set default gateway if already present
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-04 15:56 UTC by Olivier Vitrat
Modified: 2023-01-12 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Vitrat 2007-05-04 15:56:41 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284744

Hi,

I am on an ethernet network that gives me a default gateway. When I
use kppp to connect to the Internet, I would expect kppp to overwrite
the already present default gateway with the PPP partner. This does
not happen.

What am I doing wrong?

Greetings
Marc

.kde/share/config/kppprc:
[Account0]
AccountingEnabled=0
AccountingFile=
Authentication=4
AutoDNS=1
AutoName=0
BeforeConnect=
BeforeDisconnect=
CallbackPhone=
CallbackType=0
Command=
DNS=
DefaultRoute=1
DisconnectCommand=
Domain=
ExDNSDisabled=0
Gateway=0.0.0.0
IPAddr=0.0.0.0
Name=GPRS
Password=t-d1
Phonenumber=*99#
ScriptArguments=
ScriptCommands=
StorePassword=1
SubnetMask=0.0.0.0
TotalBytes=29754
Username=t-d1
VolumeAccountingEnabled=3
pppdArguments=

[Account1]
pppdArguments=

[General]
DefaultAccount=GPRS
DefaultModem=rfcomm0
DockIntoPanel=1
NumberOfAccounts=1
NumberOfModems=1
PPPDebug=0
ShowLogWindow=0

[Graph]
Background=255,255,255
Enabled=true
InBytes=0,0,255
OutBytes=255,0,0
Text=0,0,0

[Modem]
AnswerResponse=CONNECT
AnswerString=ATA
BusyResponse=BUSY
ConnectResponse=CONNECT
DLPResponse=DIGITAL LINE DETECTED
Device=/dev/rfcomm0
DialString=ATDT
EscapeGuardTime=50
EscapeResponse=OK
EscapeString=+++
HangUpResponse=OK
HangupString=+++ATH
InitDelay=50
InitResponse=OK
InitString=ATZ
InitString1=
NoCarrierResponse=NO CARRIER
NoDialToneDetection=ATX3
NoDialToneResp=NO DIALTONE
PreInitDelay=50
RingResponse=RING
ToneDuration=70
VolumeHigh=M1L3
VolumeMedium=M1L1
VolumeOff=M0L0
WaitForDialTone=0

[Modem0]
AnswerResponse=CONNECT
AnswerString=ATA
BusyResponse=BUSY
BusyWait=0
ConnectResponse=CONNECT
DLPResponse=DIGITAL LINE DETECTED
Device=/dev/rfcomm0
DialString=ATDT
Enter=CR
EscapeGuardTime=50
EscapeResponse=OK
EscapeString=+++
FlowControl=Hardware [CRTSCTS]
HangUpResponse=OK
HangupString=+++ATH
InitDelay=50
InitResponse=OK
InitString=ATZ
InitString1=
Name=rfcomm0
NoCarrierResponse=NO CARRIER
NoDialToneDetection=ATX3
NoDialToneResp=NO DIALTONE
PreInitDelay=50
RingResponse=RING
Speed=57600
Timeout=60
ToneDuration=70
UseLockFile=1
Volume=1
VolumeHigh=M1L3
VolumeMedium=M1L1
VolumeOff=M0L0
WaitForDialTone=0

[WindowPosition]
WindowPositionStatWinX=355
WindowPositionStatWinY=153
Comment 1 Lamarque V. Souza 2009-03-07 20:30:42 UTC
This still happens in KDE 4.2.1.
Comment 2 Lamarque V. Souza 2009-07-06 16:37:51 UTC
Well, I have found a workaround for this: add noauth in /etc/ppp/options, that will make pppd NOT assign the default route, but it will assign the IP address. Then you have to add the 'route add default gw <gateway IP>' command in /etc/ppp/ip-up script. In Gentoo the ip-up script just walks through /etc/ppp/ip-up.d/* files and run then one by one, in one of then I add this command:

route add default gw $5

$5 is the gateway IP address pppd obtained from the ppp server. That works for me.
Comment 3 Andrew Crouthamel 2018-11-02 23:03:47 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 05:38:36 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-13 02:53:23 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-28 05:23:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-12 05:16:16 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!