Package: ppp Version: 2.4.4rel-2 Severity: normal I diagnosed this while trying to understand why my ddclient can't update my DynDNS at Internet connection startup.
Look at the connection syslog: Nov 11 23:08:16 harris pppd[32450]: Plugin rp-pppoe.so loaded. Nov 11 23:08:16 harris pppd[32451]: pppd 2.4.4 started by fabien, uid 1000 Nov 11 23:08:16 harris pppd[32451]: PPP session is 2140 Nov 11 23:08:16 harris pppd[32451]: Using interface ppp0 Nov 11 23:08:16 harris pppd[32451]: Connect: ppp0 <--> eth0 Nov 11 23:08:16 harris pppd[32451]: CHAP authentication succeeded: Welcome to use Quidway ROUTER, Huawei Tech.^M^J Nov 11 23:08:16 harris pppd[32451]: CHAP authentication succeeded Nov 11 23:08:16 harris pppd[32451]: peer from calling number 00:E0:FC:2B:48:B2 authorized Nov 11 23:08:16 harris dnsmasq[10387]: no servers found in /var/run/dnsmasq/resolv.conf, will retry Nov 11 23:08:16 harris pppd[32451]: local IP address 84.101.106.18 Nov 11 23:08:16 harris pppd[32451]: remote IP address 84.101.106.1 Nov 11 23:08:16 harris pppd[32451]: primary DNS address 84.103.237.143 Nov 11 23:08:16 harris pppd[32451]: secondary DNS address 86.64.145.143 Nov 11 23:08:16 harris ddclient[32533]: WARNING: cannot connect to members.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'members.dyndns.org' Nov 11 23:08:16 harris ddclient[32533]: FAILED: updating fcoutant.homelinux.net: Could not connect to members.dyndns.org. ... Nov 11 23:10:34 harris dnsmasq[10387]: reading /var/run/dnsmasq/resolv.conf Nov 11 23:10:34 harris dnsmasq[10387]: using nameserver 86.64.145.143#53 Nov 11 23:10:34 harris dnsmasq[10387]: using nameserver 84.103.237.143#53 Nov 11 23:10:34 harris dnsmasq[10387]: using local addresses only for domain localnet See the 1st dnsmasq line ? It's a try-to-update from dnsmasq, indirectly triggered by resolvconf (from /etc/ppp/ip-up.d/000resolvconf). But it fails because there's no DNS yet; Actually there's no IP address either at that step ! It looks like pppd is launching ip-up.d scripts as soon as the PPP network interface is "literally" up, i.e. from a technical status point of view. But this is wrong, it should wait for the interface to be "ready", not only "up". Which means waiting for an IP address to come, and DNS addresses too when using "usepeerdns" (my case). Other important packages to notice: ii ddclient 3.6.7-2 Update dynamic IP address at DynDNS.org ii dnsmasq 2.35-1 A small caching DNS proxy and DHCP server ii resolvconf 1.36 nameserver information handler -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages ppp depends on: ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libpam-modules 0.79-4 Pluggable Authentication Modules f ii libpam-runtime 0.79-4 Runtime support for the PAM librar ii libpam0g 0.79-4 Pluggable Authentication Modules l ii libpcap0.8 0.9.5-1 System interface for user-level pa ii netbase 4.27 Basic TCP/IP networking system ii procps 1:3.2.7-3 /proc file system utilities ii zlib1g 1:1.2.3-13 compression library - runtime ppp recommends no packages. -- no debconf information -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
