Bug 128619 - kppp fails since pppd now writes resolv.conf in /var/run/ppp
Summary: kppp fails since pppd now writes resolv.conf in /var/run/ppp
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdenetwork
Version: 2
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-27 09:40 UTC by Malcolm Lee
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-07-28 10:16:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Malcolm Lee 2004-07-27 09:40:53 UTC
Description of problem:
kppp fails since pppd  now writes resolv.conf in /var/run/ppp whereas
kppp is still looking for it in /etc/ppp

Version-Release number of selected component (if applicable):
ppp-2.4.2-2   kdenetwork-3.2.2-1

How reproducible: Consistently (every time)


Steps to Reproduce:
1. Remove any old versions of /etc/ppp/resolv.conf
2. Use kppp to connect to an ISP using DNS setting of automatic
3.
  
Actual results:
/etc/resolv.conf is unchanged after connection since kppp is looking
for the ISP DNS addresses in /etc/ppp/resolv.conf whereas pppd has
written them into /var/run/ppp/resolv.conf. As a result no internet
addresses can be resolved and hence no connections of any sort can be
made.

Expected results:
/etc/resolv.conf is normally updated by kppp (for the duration of
connection) with the ISP DNS addresses eg

search xxxxx.yyy
nameserver 127.0.0.1
nameserver a.b.c.d        #kppp temp entry
nameserver w.x.y.z   #kppp temp entry



Additional info:
A simple workround is obviously to symbolic link /etc/ppp/resolv.conf
to /var/run/ppp/resolv.conf but it would obviously be better if pppd
and kppp both agreed on the location of the "temporary" resolv.conf file.

Comment 1 Than Ngo 2004-07-28 10:16:39 UTC
it's a know bug, which is already fixed in kde-3.2.3 or newer in rawhide.


Note You need to log in before you can comment on or make changes to this bug.