Bug 465679 - pppd does not set resolv.conf
Summary: pppd does not set resolv.conf
Status: RESOLVED DUPLICATE of bug 429772
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Marius Tomaschewski
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-13 12:00 UTC by Michal Svec
Modified: 2009-01-13 14:20 UTC (History)
2 users (show)

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


Attachments
/var/run/netconfig contents (377 bytes, application/x-compressed-tar)
2009-01-13 12:52 UTC, Michal Svec
Details
/var/run/netconfig contents (ppp0 up) (386 bytes, application/x-compressed-tar)
2009-01-13 13:30 UTC, Michal Svec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Svec 2009-01-13 12:00:00 UTC
Despite it has usepeerdns and dns servers are received:

[...]
local  IP address 10.169.12.70
remote IP address 10.6.6.6
primary   DNS address 62.141.0.2
secondary DNS address 213.162.65.1
Script /etc/ppp/ip-up started (pid 4754)
Script /etc/ppp/ip-up finished (pid 4754), status = 0x0

Also, /var/run/ppp_resolv.conf.ppp0 is created:
nameserver 62.141.0.2
nameserver 213.162.65.1

But /etc/resolv.conf does not contain anything useful:
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
Comment 1 Marius Tomaschewski 2009-01-13 12:07:11 UTC
You're using NetworkManager, right? Please provide the outputs of

grep -E "^NETCONFIG|^NETWORKMANAGER" /etc/sysconfig/network/config
netconfig update -v

the /var/log/NetworkManager file and the netconfig state data using
e.g.:
tar cvzf /tmp/bnc465679-netconfig.tgz /var/run/netconfig
Comment 2 Michal Svec 2009-01-13 12:52:38 UTC
Created attachment 264755 [details]
/var/run/netconfig contents

Yes, I'm using NetworkManager.

bash# grep -E "^NETCONFIG|^NETWORKMANAGER" /etc/sysconfig/network/config
NETWORKMANAGER="yes"                                                       
NETCONFIG_MODULES_ORDER="dns-resolver dns-bind dns-dnsmasq nis ntp-runtime"
NETCONFIG_DNS_POLICY="auto"                                                
NETCONFIG_DNS_FORWARDER="resolver"                                         
NETCONFIG_DNS_STATIC_SEARCHLIST=""                                         
NETCONFIG_DNS_STATIC_SERVERS=""                                            
NETCONFIG_NTP_POLICY=""                                                    
NETCONFIG_NTP_STATIC_SERVERS=""                                            
NETCONFIG_NIS_POLICY="auto"                                                
NETCONFIG_NIS_SETDOMAINNAME="yes"
NETCONFIG_NIS_STATIC_DOMAIN=""
NETCONFIG_NIS_STATIC_SERVERS=""

bash# netconfig update -v
debug: lockfile created (/var/run/netconfig.pid) for PID 8700
debug: lockfile created
debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
debug: dns-resolver module called
debug: Static Fallback
debug: Use NetworkManager policy merged settings
debug: exec get_dns_settings: /var/run/netconfig//NetworkManager.netconfig
debug: exit get_dns_settings
debug: write_resolv_conf: ' suse.cz suse.cz suse.de' ' 10.20.0.2 10.20.0.8'
debug: No changes for /etc/resolv.conf
debug: dns-bind Module called
debug: dns-dnsmasq Module called
debug: nis Module called
debug: Overwrite Static
debug: Use NetworkManager policy merged settings
debug: exec get_nis_settings: /var/run/netconfig//NetworkManager.netconfig
debug: exit get_nis_settings
debug: set_nisdomainname:  eth0 58
debug: set_nisdomainname: => yes
debug: set_nisdomainname: old[]=, new[58]=
debug: format_yp_conf called with :
debug: Using static fallback
debug: format_static[0] called
debug: No changes for /etc/yp.conf
debug: nis domainname 'suse.cz' is up to date
debug: ntp-runtime Module called
Comment 3 Marius Tomaschewski 2009-01-13 13:27:37 UTC
OK, it looks like the data is from a moment where ppp0 was down.
And after the "netconfig update -v" you've (still)

  search suse.cz suse.de
  nameserver 10.20.0.2
  nameserver 10.20.0.8

in /etc/resolv.conf... netconfig worked IMO propelly.

Please provide the outpus and /var/log/NetworkManager (!) again while
ppp0 is _up_. Or did you not configured ppp0 with NetworkManager?

The NetworkManager makes use of a plugin that provides the DNS settings
to the NetworkManager.

Using a mix of NetworkManager and any other method else is not supported.
Comment 4 Michal Svec 2009-01-13 13:30:42 UTC
Created attachment 264762 [details]
/var/run/netconfig contents (ppp0 up)
Comment 5 Michal Svec 2009-01-13 13:33:27 UTC
Again, with ppp0 up:

bash# netconfig update -v
debug: lockfile created (/var/run/netconfig.pid) for PID 11521
debug: lockfile created
debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
debug: dns-resolver module called
debug: Static Fallback
debug: Use NetworkManager policy merged settings
debug: exec get_dns_settings: /var/run/netconfig//NetworkManager.netconfig
debug: exit get_dns_settings
debug: write_resolv_conf: '' ''
debug: No changes for /etc/resolv.conf
debug: dns-bind Module called
debug: dns-dnsmasq Module called
debug: nis Module called
debug: Overwrite Static
debug: Use NetworkManager policy merged settings
debug: exec get_nis_settings: /var/run/netconfig//NetworkManager.netconfig
debug: exit get_nis_settings
debug: set_nisdomainname:  eth0 58
debug: set_nisdomainname: => yes
debug: set_nisdomainname: old[]=, new[58]=
debug: format_yp_conf called with :
debug: Using static fallback
debug: format_static[0] called
debug: No changes for /etc/yp.conf
debug: nis domainname 'suse.cz' is up to date
debug: ntp-runtime Module called

I'm using pppd directly, no NM at all (I run rcnetwork stop before).
So I guess this is not related to NetworkManager.
Comment 6 Marius Tomaschewski 2009-01-13 13:45:51 UTC
$ cat var/run/netconfig/NetworkManager.netconfig 
CREATETIME='58'
SERVICE='NetworkManager'
INTERFACE='eth0'
$ cat var/run/netconfig/ppp0/netconfig0
CREATETIME='5816'
SERVICE='pppd'
INTERFACE='ppp0'
IPADDR='10.168.1.192'
PTPADDR='10.6.6.6'
DNSSERVERS='62.141.0.2 213.162.65.1'
NETBIOSNAMESERVER=''

OK, the ip-up script provides the settings correctly to netconfig but
they're not used because NetworkManager mode is active.

NetworkManager (ppp plugin) seems to still not provide any DNS settings
to netconfig. I've already reassigned to Tambet before...

Or is pppd not started/configured via NetworkManager? In this case it
is a WONTFIX -- you've to set custom DNS policy, e.g.:

  NETCONFIG_DNS_POLICY="STATIC_FALLBACK ppp0 NetworkManager"
Comment 7 Marius Tomaschewski 2009-01-13 13:51:45 UTC
(In reply to comment #5)
> Again, with ppp0 up:
> 
> bash# netconfig update -v
[...]
> debug: write_resolv_conf: '' ''
[...]

OK, correct. NetworkManager is exclusive.

> I'm using pppd directly, no NM at all (I run rcnetwork stop before).
> So I guess this is not related to NetworkManager.

OK, see above - unsupported / in custom policy like this only:

NETCONFIG_DNS_POLICY="STATIC_FALLBACK ppp* NetworkManager"
Comment 8 Michal Svec 2009-01-13 13:56:35 UTC
What I do is:
  bash# rcnetwork stop
  bash# pppd

I'd expect if NM is not running that netconfig sets resolv.conf despite
the policy. But anyways, I'll then try setting NETCONFIG_DNS_POLICY and
let's see.
Comment 9 Marius Tomaschewski 2009-01-13 14:20:04 UTC
No, the policy is always applied.

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