Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 384883

Summary: net-dialup/ppp: with net-dns/openresolv /etc/ppp/ip-up.d/50-initd.sh stomps /etc/ppp/ip-up.d/40-dns.sh nameserver config
Product: Gentoo Linux Reporter: Bill Prendergast <dek.devel>
Component: Current packagesAssignee: Alon Bar-Lev (RETIRED) <alonbl>
Status: RESOLVED DUPLICATE    
Severity: normal CC: alonbl
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Bill Prendergast 2011-09-29 07:54:56 UTC
when using net-dialup/ppp with net-dns/openresolv the /etc/ppp/ip-up.d/40-dns.sh script correctly sets nameservers in /etc/resolv.conf via openresolv -a [ifname] but then /etc/ppp/ip-up.d/50-initd.sh calls /etc/init.d/net.[ifname] and there are no nameservers servers available to the net.[ifname] script and it runs openresolv -a [ifname] without any nameservers. This results in /etc/resolv.conf being written without nameservers obtained through pppd



Reproducible: Always

Steps to Reproduce:
1. configure a ppp interface ppp[x]
2. cd /etc/init.d/ && ln -s net.lo net.ppp[x]
3. start the ppp interface (/etc/init.d/net.ppp[x] start
Actual Results:  
when pppd runs the ip-up scripts nameservers obtained from the remote ppp server are first added and then later removed from the system /etc/resolv.conf

Expected Results:  
that /etc/resolv.conf would have the pppd configured name servers.

running the 40-dns.sh after the 50-initd.sh does correctly add the nameservers to /etc/resolv.conf (i.e. by renaming 40-dns.sh to 51-dns.sh) 

header from /var/run/resolvconf/interfaces/ppp0 when run by 40-dns.sh
# Generated by ppp for ppp0

header from /var/run/resolvconf/interfaces/ppp0 when run by 50-initd.sh
# Generated by net-scripts for interface ppp0
Comment 1 Alon Bar-Lev (RETIRED) gentoo-dev 2013-05-11 07:56:51 UTC
dup of bug#400845?
Comment 2 Alon Bar-Lev (RETIRED) gentoo-dev 2013-06-01 20:52:38 UTC

*** This bug has been marked as a duplicate of bug 353045 ***