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

From: jim lawrence (fedorajim_at_gmail.com)
Date: 01/20/05

  • Next message: James Mckenzie: "Re: Disk Druid - Fedora flame #1[Where o' where does a User get their Environment?]"
    Date: Thu, 20 Jan 2005 10:58:59 -0500
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    [root@JimsNotebook ~]# ifconfig -a
    eth0 Link encap:Ethernet HWaddr 00:40:D0:5E:70:4F
              UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
              RX packets:1754 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1806 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:771355 (753.2 KiB) TX bytes:226135 (220.8 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:2014 errors:0 dropped:0 overruns:0 frame:0
              TX packets:842 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:1621941 (1.5 MiB) TX bytes:401423 (392.0 KiB)
              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:3284 errors:0 dropped:0 overruns:0 frame:0
              TX packets:3284 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:1682103 (1.6 MiB) TX bytes:1682103 (1.6 MiB)

    [root@JimsNotebook ~]# ping -c4 24.93.1.118
    PING 24.93.1.118 (24.93.1.118) 56(84) bytes of data.
    64 bytes from 24.93.1.118: icmp_seq=0 ttl=252 time=8.72 ms
    64 bytes from 24.93.1.118: icmp_seq=1 ttl=252 time=10.1 ms
    64 bytes from 24.93.1.118: icmp_seq=2 ttl=252 time=9.43 ms
    64 bytes from 24.93.1.118: icmp_seq=3 ttl=252 time=59.2 ms

    --- 24.93.1.118 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3002ms
    rtt min/avg/max/mdev = 8.726/21.891/59.261/21.581 ms, pipe 2

    [root@JimsNotebook ~]# ping -c4 www.google.com
    ping: unknown host www.google.com
    [root@JimsNotebook ~]#

    -- 
    ********************************************************
    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@redhat.com
     To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: James Mckenzie: "Re: Disk Druid - Fedora flame #1[Where o' where does a User get their Environment?]"

    Relevant Pages

    • RE: Reg : RHEL 5.0 Installatio
      ... To subscribe or unsubscribe via the World Wide Web, ... Subject: Reg: RHEL 5.0 Installatio ... Ping from yourself to yourself; ping localhost, ...
      (RedHat)
    • RE: TCP not working over ppp connection (WAS: 5th day using Linux...)
      ... * You say you can ping outside addresses? ... > installed modules: lsmod ... > after the initial install, ... > with a subject of "unsubscribe". ...
      (Debian-User)
    • RE: Reg : RHEL 5.0 Installatio
      ... Ping from yourself to yourself; ping localhost, ... Subject: Reg: RHEL 5.0 Installatio ... 10:46:40 AM LINUX RESTART ...
      (RedHat)
    • Re: Re: Frequent loss of contact with ISP
      ... >> any unusual error messages. ... > is somewhere in the network config, ... I tried to ping the IP address after the word ... To unsubscribe, ...
      (freebsd-questions)
    • Re: cannot ping anything
      ... This means that my assumption of disabling IPF by removing all of the comments tertainin to it and IPNat from /etc/rc.conf were wrong because it it compiled statically. ... If you can ping those and still not the router at 192.168.1.1 check for other defaultrouter statements. ... To unsubscribe, ...
      (freebsd-questions)