Bugzilla – Bug 462686
netconfig fails to adjust DNS config on pppd dial in
Last modified: 2009-01-27 11:12:20 UTC
After upgrading from 11.0 to 11.1 on my MSI Wind U100 netbook, I cannot connect to internet via kinternet, my nokia phone and bluetooth (worked perfectly fine with 11.0 :-(). While the hard part (pppd on /dev/rfcomm setup, etc..) all worked fine, setting up a proper /etc/resolv.conf failed, and looks like the new netconfig stuff is responsible for that mess. syslog: Dec 28 19:01:20 pitu bluetoothd[6439]: Adapter /org/bluez/6439/hci0 has been enabled Dec 28 19:01:20 pitu bluetoothd[6439]: Starting security manager 0 Dec 28 19:01:25 pitu pppd[6448]: Plugin passwordfd.so loaded. Dec 28 19:01:25 pitu kernel: PPP generic driver version 2.4.2 Dec 28 19:01:25 pitu pppd[6448]: pppd 2.4.5 started by root, uid 0 Dec 28 19:01:29 pitu bluetoothd[6439]: link_key_request (sba=x:x:x, dba=y:y:y) Dec 28 19:01:44 pitu pppd[6448]: Script /usr/bin/wvdial --chat --no-syslog --config /var/run/smpppd/chat-modem0.conf smpppd finished (pid 6469), status = 0x0 Dec 28 19:01:44 pitu pppd[6448]: Serial connection established. Dec 28 19:01:44 pitu kernel: ppp0 renamed to modem0 by pppd [6448] Dec 28 19:01:44 pitu pppd[6448]: Renamed interface ppp0 to modem0 Dec 28 19:01:44 pitu pppd[6448]: Using interface modem0 Dec 28 19:01:44 pitu pppd[6448]: Connect: modem0 <--> /dev/rfcomm0 Dec 28 19:01:47 pitu pppd[6448]: PAP authentication succeeded Dec 28 19:01:47 pitu kernel: PPP BSD Compression module registered Dec 28 19:01:47 pitu kernel: PPP Deflate Compression module registered Dec 28 19:01:48 pitu pppd[6448]: local IP address 10.223.81.142 Dec 28 19:01:48 pitu pppd[6448]: remote IP address 10.6.6.6 Dec 28 19:01:48 pitu pppd[6448]: primary DNS address 193.254.160.130 Dec 28 19:01:48 pitu pppd[6448]: secondary DNS address 193.254.160.1 all is fine, but /etc/resolv.conf only contains comments about netconfig: ### /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! I tried to manually set the above noted DNS servers with yast2 modem, but connection failed in the same way. The NetworkManager seems to set up the DNS config just fine, thus it smells like a pure pppd<->netconfig problem.
*** This bug has been marked as a duplicate of bug 443788 ***
Reopened, since the problem persists.
I am have a the same problem but instead am I am using wvdial. It connects to the internet fine but it does not create the default route and neither populate the resolv.conf
syslog: Jan 14 11:13:42 linux-7ib2 pppd[21389]: Plugin passwordfd.so loaded. Jan 14 11:13:42 linux-7ib2 pppd[21389]: pppd 2.4.5 started by root, uid 0 Jan 14 11:13:42 linux-7ib2 pppd[21389]: Using interface ppp0 Jan 14 11:13:42 linux-7ib2 pppd[21389]: Connect: ppp0 <--> /dev/ttyUSB0 Jan 14 11:13:42 linux-7ib2 pppd[21389]: CHAP authentication succeeded Jan 14 11:13:42 linux-7ib2 pppd[21389]: CHAP authentication succeeded Jan 14 11:13:45 linux-7ib2 pppd[21389]: Could not determine remote IP address: defaulting to 10.64.64.64 Jan 14 11:13:45 linux-7ib2 pppd[21389]: local IP address 166.217.160.255 Jan 14 11:13:45 linux-7ib2 pppd[21389]: remote IP address 10.64.64.64 Jan 14 11:13:45 linux-7ib2 pppd[21389]: primary DNS address 209.183.33.23 Jan 14 11:13:45 linux-7ib2 pppd[21389]: secondary DNS address 209.183.35.23 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: using default zone 'ext' for interface pan0 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: using default zone 'ext' for interface ppp0 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: using default zone 'ext' for interface vmnet1 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: using default zone 'ext' for interface vmnet8 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: using default zone 'ext' for interface wmaster0 Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: batch committing... Jan 14 11:13:46 linux-7ib2 SuSEfirewall2: Firewall rules successfully set Jan 14 11:13:46 linux-7ib2 pppd[21389]: Script /etc/ppp/ip-up finished (pid 21394), status = 0x0
I have same problem with HUAWEI modem on SONY Vaio VGN-FE41S. I'm able to connect but I get no DNS answer. It worked fine until I switched to 11.1 from 11.0 (fresh install). pppd version 2.4.5 WvDial 1.60 Linux linux-b68r 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux -------- wvdial.conf --------------------------------------- [Dialer Defaults] Debug mode = 1 Phone = *99***1# Username = internet Password = internet Stupid Mode = 1 Dial Command = ATDT Modem = /dev/ttyUSB0 Baud = 460800 Init1 = ATZ Init2 = ATE0V1&D2&C1S0=0+IFC=2,2 ISDN = 0 Modem Type = Analog Modem Init5 = AT+CGDCONT=1,"IP","ointernet" ------------wvdial---------------------------------- # wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ OK --> Sending: ATE0V1&D2&C1S0=0+IFC=2,2 ATE0V1&D2&C1S0=0+IFC=2,2 OK --> Sending: AT+CGDCONT=1,"IP","ointernet" OK --> Modem initialized. --> Sending: ATDT*99***1# --> Waiting for carrier. CONNECT --> Carrier detected. Starting PPP immediately. --> Starting pppd at Mon Jan 19 23:29:31 2009 --> Pid of pppd: 9299 --> Using interface ppp0 --> pppd: 6[7f] --> pppd: 6[7f] --> pppd: 6[7f] --> pppd: 6[7f] --> pppd: 6[7f] --> local IP address 10.20.44.120 --> pppd: 6[7f] --> remote IP address 10.64.64.64 --> pppd: 6[7f] --> primary DNS address 217.77.161.130 --> pppd: 6[7f] --> secondary DNS address 217.77.161.131 --> pppd: 6[7f] --> Script /etc/ppp/ip-up run successful --> Default route Ok. --> warning, no nameserver found `/etc/resolv.conf` --> Nameserver (DNS) failure, the connection may not work. --> Connected... Press Ctrl-C to disconnect --> pppd: 6[7f] ------------ ifconfig ---------------------------------------------- ppp0 Link encap:Point-to-Point Protocol inet addr:10.20.44.120 P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:6 errors:3 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:90 (90.0 b) TX bytes:129 (129.0 b) --------------route----------------------------------------------- Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.64.64.64 * 255.255.255.255 UH 0 0 0 ppp0 loopback * 255.0.0.0 U 0 0 0 lo default * 0.0.0.0 U 0 0 0 ppp0 ------------------------------------------------------------------
Please provide the outputs of: grep -E "^NETWORKMANAGER|^NETCONFIG" /etc/sysconfig/network/config and netconfig update -v See also bug 429772 comment 22. You've to set up custom netconfig policy _when_ you've enabled NetworkManager and use any traditional way as well. The /etc/ppp/ip-up script makes the "netconfig modify" call but the settings are discarded because of NETWORKMANAGER=yes and "auto" DNS netconfig policy.
Resolving as duplicate of bug 429772 [bug 443788 was wrong duplicate; it was about invalid parameter in the dhclient.conf]. Dan, please provide the output requested in comment #6, when you're using NETWORKMANAGER=no. *** This bug has been marked as a duplicate of bug 429772 ***