Network Manager Strikes Again!!!!

[jim lawrence]

On Mon, 17 Jan 2005 15:59:30 +0000, Paul Howarth <paul at city-fan.org> wrote:
> jim lawrence wrote:
> > why can't i connect to the internet when i have NetworkManager running?
> > see below
> > ####################################################################
> > [root at JimsNotebook ~]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:40:D0:5E:70:4F
> >           inet addr:192.168.1.53  Bcast:192.168.1.255  Mask:255.255.255.0
> >           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:1240 (1.2 KiB)  TX bytes:703 (703.0 b)
> >           Interrupt:3
> >
> > eth1      Link encap:Ethernet  HWaddr 00:0E:35:1F:CE:CF
> >           UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
> >           RX packets:9 errors:0 dropped:1 overruns:0 frame:0
> >           TX packets:1 errors:0 dropped:0 overruns:0 carrier:1
> >           collisions:0 txqueuelen:1000
> >           RX bytes:6743093 (6.4 MiB)  TX bytes:1925226 (1.8 MiB)
> >           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:1399 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1399 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:1388648 (1.3 MiB)  TX bytes:1388648 (1.3 MiB)
> > I ping my router  just fine.....
> > [root at JimsNotebook ~]# ping -c4 192.168.1.49
> > PING 192.168.1.49 (192.168.1.49) 56(84) bytes of data.
> > 64 bytes from 192.168.1.49: icmp_seq=0 ttl=150 time=1.81 ms
> > 64 bytes from 192.168.1.49: icmp_seq=1 ttl=150 time=0.489 ms
> > 64 bytes from 192.168.1.49: icmp_seq=2 ttl=150 time=0.489 ms
> > 64 bytes from 192.168.1.49: icmp_seq=3 ttl=150 time=0.479 ms
> >
> > --- 192.168.1.49 ping statistics ---
> > 4 packets transmitted, 4 received, 0% packet loss, time 3000ms
> > rtt min/avg/max/mdev = 0.479/0.817/1.814/0.576 ms, pipe 2
> > can't ping google
> > [root at JimsNotebook ~]# ping -c4 www.google.com
> > ping: unknown host www.google.com
> > [root at JimsNotebook ~]# service network restart
> > Shutting down interface Lan:                               [  OK  ]
> > Shutting down loopback interface:                          [  OK  ]
> > Setting network parameters:                                [  OK  ]
> > Bringing up loopback interface:                            [  OK  ]
> > [root at JimsNotebook ~]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:40:D0:5E:70:4F
> >           inet addr:192.168.1.53  Bcast:192.168.1.255  Mask:255.255.255.0
> >           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:11 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:2932 (2.8 KiB)  TX bytes:1840 (1.7 KiB)
> >           Interrupt:3
> >
> > eth1      Link encap:Ethernet  HWaddr 00:0E:35:1F:CE:CF
> >           UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
> >           RX packets:9 errors:0 dropped:1 overruns:0 frame:0
> >           TX packets:1 errors:0 dropped:0 overruns:0 carrier:1
> >           collisions:0 txqueuelen:1000
> >           RX bytes:6743093 (6.4 MiB)  TX bytes:1925226 (1.8 MiB)
> >           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:1407 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1407 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:1389308 (1.3 MiB)  TX bytes:1389308 (1.3 MiB)
> > still can't ping google
> >
> > [root at JimsNotebook ~]# ping -c4 www.google.com
> > ping: unknown host www.google.com
> 
> This may be a raw connectivity problem or a name resolution problem.
> 
> What happens why you try the ping using just the IP address?
> 
> $ ping -c4 64.233.161.104
> 
> If this works, check out the difference in /etc/resolv.conf when
> NetworkManager is running.
> 
> Paul.
 
******************************************

When NM is running 


; generated by NetworkManager, do not edit!
; Use a local caching nameserver controlled by NetworkManager

nameserver 127.0.0.1
-- 

When Not Running  

; generated by /sbin/dhclient-script
search rochester.rr.com
nameserver 24.93.1.120
nameserver 24.93.1.247
nameserver 24.93.1.118

********************************************************
When I'm feeling down, I like to whistle. 
It makes the neighbor's dog run to the end of his chain and gag himself.
************************************
Registered Linux User: #376813

jim lawrence



> 
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>