[Bug 53877] Re: kppp does not assign proper default gateway

Wed Nov 7 13:52:35 UTC 2018

Launchpad has imported 4 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=145027.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2007-05-04T15:56:41+00:00 Olivier Vitrat wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/53877/comments/10

------------------------------------------------------------------------
On 2009-03-07T20:30:42+00:00 Lamarque wrote:

This still happens in KDE 4.2.1.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/53877/comments/14

------------------------------------------------------------------------
On 2009-07-06T16:37:51+00:00 Lamarque wrote:

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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/53877/comments/15

------------------------------------------------------------------------
On 2018-11-02T23:03:47+00:00 Andrew-crouthamel wrote:

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!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/53877/comments/18

** Changed in: kdenetwork
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdenetwork in Ubuntu.
https://bugs.launchpad.net/bugs/53877

Title:
  kppp does not assign proper default gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdenetwork/+bug/53877/+subscriptions