Beware of bind-9.2.4-8_FC3:20 (was BIND (Network Manager Strikes Again!!!!))

[Paul Howarth]

jim lawrence wrote:
>>What's the output of:
>># ifconfig -a
>># netstat -rn
>># rpm -q NetworkManager wireless-tools
> 
> 
> [root at JimsNotebook ~]# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:40:D0:5E:70:4F
>           inet addr:192.168.1.51  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:150 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:64929 (63.4 KiB)  TX bytes:23079 (22.5 KiB)
>           Interrupt:3
> 
> eth1      Link encap:Ethernet  HWaddr 00:0E:35:1F:CE:CF
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:1155 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:249 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0x6000 Memory:e0001000-e0001fff
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:1394 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1394 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1473712 (1.4 MiB)  TX bytes:1473712 (1.4 MiB)
> 
> [root at JimsNotebook ~]# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 lo
> 0.0.0.0         192.168.1.49    0.0.0.0         UG        0 0          0 eth0
> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0 eth0

Looks like things should have been working with this configuration - was 
it not? Not sure where that last entry in the routing table came from 
though.

> [root at JimsNotebook ~]# rpm -q NetworkManager wireless-tools
> NetworkManager-0.3.3-1.cvs20050112.1.fc3
> wireless-tools-27-0.pre25.3

No version conflicts there.

> [root at JimsNotebook ~]#
> 
> What is reallt FUBAR  is that i just rebooted,  plugged in my cable,
> and was connected.
> 10 minutes ago  wasn't the case.   after copying the above from the
> terminal, i unplugged the  cable, NM scanned and connected to my
> router   as seen below
> 
> [root at JimsNotebook ~]# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:40:D0:5E:70:4F
>           UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
>           RX packets:156 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:173 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:65478 (63.9 KiB)  TX bytes:23283 (22.7 KiB)
>           Interrupt:3
> 
> eth1      Link encap:Ethernet  HWaddr 00:0E:35:1F:CE:CF
>           inet addr:192.168.1.52  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:26 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1925 (1.8 KiB)  TX bytes:691 (691.0 b)
>           Interrupt:11 Base address:0x6000 Memory:e0001000-e0001fff
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:1394 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1394 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1473712 (1.4 MiB)  TX bytes:1473712 (1.4 MiB)
> 
> [root at JimsNotebook ~]# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
> 169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 lo
> 0.0.0.0         192.168.1.49    0.0.0.0         UG        0 0          0 eth1
> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0 eth1
> [root at JimsNotebook ~]# ping -c4 www.google.com
> PING www.google.akadns.net (64.233.161.104) 56(84) bytes of data.
> 64 bytes from 64.233.161.104: icmp_seq=0 ttl=242 time=32.6 ms
> 64 bytes from 64.233.161.104: icmp_seq=1 ttl=242 time=32.8 ms
> 64 bytes from 64.233.161.104: icmp_seq=2 ttl=242 time=31.5 ms
> 64 bytes from 64.233.161.104: icmp_seq=3 ttl=242 time=30.1 ms
> 
> --- www.google.akadns.net ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3002ms
> rtt min/avg/max/mdev = 30.198/31.812/32.880/1.087 ms, pipe 2
> [root at JimsNotebook ~]#
> 
> Go figure on why this is hit and mis with NM or named 

I suspect that the problem's with NM rather than named. If it happens 
again, try pinging by IP address rather than by name. If IPs don't work, 
it's nothing to with named.

Paul.