Re: Help: Mandriva drops DHCP IP address nor can't ping to local host

From: Michael Badt (mb_at_yahoo.com)
Date: 07/18/05

  • Next message: vicky: "Re: prob: NFS: /etc/exports" 
    Date: Mon, 18 Jul 2005 05:49:17 +0300

    Thanks all,
    I'll try to turn off IPV6.
    DNS works for me.
    I'll test other options and let you know.

    Michael Badt

    Jack Masters wrote:

    > Michael Badt wrote:
    >> Hi,
    >> My dual boot (Mandriva LE 2005 LE - fully updated/Win2000) at work worked
    >> fine (both OS) till this weekend.
    >> The laptop is connected to a physical LAN with a DHCP server.
    >> This week, I couldn't browse in Linux, although I was able to download
    >> emails from the local exchange server (but not my other, "external"
    >> account). Trying to analyze the problem (details below) I noticed that,
    >> among others:
    >> a. The laptop couldn't ping to 127.0.0.1
    >
    > From your logs it looks like lo is set up for DHCP (and using a V6
    > address) ???? If you are using IPV4, it should be hard configured to
    > 127.0.0.1 (don't personally use MDK, but that is supposed to be
    > somewhere in the network startup scripts)
    >
    >> b. The system log showed that eth0 has been allocated an IP address, yet,
    >> less than a minute afterwards dhclient notified that there weren't free
    >> leases (see below). Manually initiating dhclient resulted the same.
    >
    > Probably dhclient whinging about lo, eth0 seems OK.
    >
    > First step: can you ping the default gateway (10.4.253.253) ?
    >
    > Next step: does DNS resolution and ping to outside addresses work? What
    > does 'ping www.example.com' tell you?
    >
    >>
    >> Trying to compare, I switched to Win 2000 only to find that I COULD
    >> browse using MS Explorer (Yak) but could NOT browse using (Win) Firefox.
    >> Weird!
    >
    > Most likely scenario: network admin has blocked outbound traffic on port
    > 80, and installed a login script on the windoze domain server that sets
    > up IE to use a proxy. Check the proxy server configuration in IE, and if
    > it has a proxy configured copy that setting into Firefox.
    >
    >> I've checked the Win networking parameters and found these were identical
    >> to those as Linux. The Win parameters were:
    >> IP 10.4.4.3
    >> Net Mask 255.255.0.0
    >> GW 10.4.253.253
    >> DNS Suffix rf.local
    >>
    >> Needless to mention that my Sys Administrator isn't concerned neither
    >> about Linux nor Firefox...
    >>
    >> Please advise.
    >>
    >> TIA
    >> Michael Badt
    >>
    >>
    >> -----------following are the relevant Linux commands and
    >> responses--------- Commands ran as root in updated Mandriva 2005 LE
    >> -----------------
    >> [root@Atlantis miki]# ifconfig
    >> eth0 Link encap:Ethernet HWaddr 00:02:A5:BA:EF:CC
    >> inet addr:10.4.4.13 Bcast:10.4.255.255 Mask:255.255.0.0
    >> inet6 addr: fe80::202:a5ff:feba:efcc/64 Scope:Link
    >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    >> RX packets:289 errors:0 dropped:0 overruns:0 frame:0
    >> TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
    >> collisions:0 txqueuelen:1000
    >> RX bytes:28768 (28.0 Kb) TX bytes:7662 (7.4 Kb)
    >>
    >> lo Link encap:Local Loopback
    >> inet6 addr: ::1/128 Scope:Host
    >> UP LOOPBACK RUNNING MTU:16436 Metric:1
    >> RX packets:25 errors:0 dropped:0 overruns:0 frame:0
    >> TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
    >> collisions:0 txqueuelen:0
    >> RX bytes:4171 (4.0 Kb) TX bytes:4171 (4.0 Kb)
    >>
    >> sit0 Link encap:IPv6-in-IPv4
    >> inet6 addr: ::127.0.0.1/96 Scope:Unknown
    >> UP RUNNING NOARP MTU:1480 Metric:1
    >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    >> TX packets:0 errors:10 dropped:0 overruns:0 carrier:0
    >> collisions:0 txqueuelen:0
    >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    >> --------------------------
    >> [root@Atlantis miki]# ping 127.0.0.1
    >> PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
    >>
    >> --- 127.0.0.1 ping statistics ---
    >> 87 packets transmitted, 0 received, 100% packet loss, time 85986ms
    >>
    >> [root@Atlantis miki]# ping 10.4.4.13
    >> PING 10.4.4.13 (10.4.4.13) 56(84) bytes of data.
    >> 64 bytes from 10.4.4.13: icmp_seq=1 ttl=64 time=0.122 ms
    >> 64 bytes from 10.4.4.13: icmp_seq=2 ttl=64 time=0.086 ms
    >> 64 bytes from 10.4.4.13: icmp_seq=3 ttl=64 time=0.074 ms
    >>
    >> --- 10.4.4.13 ping statistics ---
    >> 3 packets transmitted, 3 received, 0% packet loss, time 1999ms
    >> rtt min/avg/max/mdev = 0.074/0.094/0.122/0.020 ms
    >>
    >> ------------------
    >>
    >> route
    >> Kernel IP routing table
    >> Destination Gateway Genmask Flags Metric Ref Use
    >> Iface
    >> 10.4.0.0 * 255.255.0.0 U 0 0 0
    >> eth0
    >> default 10.4.253.253 0.0.0.0 UG 0 0 0
    >> eth0 ------------------
    >> cat /etc/resolv.conf
    >> search rf.local
    >> nameserver 10.2.34.1
    >> nameserver 10.2.34.2
    >> ---------------
    >> cat /etc/hosts
    >> 127.0.0.1 Atlantis localhost
    >> -----------------
    >> relevant part of /var/log/syslog
    >> Jul 17 13:54:01 Atlantis dhclient: DHCPACK from 194.90.39.108
    >> Jul 17 13:54:01 Atlantis dhclient: bound to 10.4.4.13 -- renewal in
    >> 297597 seconds.
    >> Jul 17 13:54:05 Atlantis dhclient: DHCPDISCOVER on lo to 255.255.255.255
    >> port 67 interval 15
    >> Jul 17 13:54:07 Atlantis dhclient: DHCPDISCOVER on sit0 to
    >> 255.255.255.255 port 67 interval 11
    >> Jul 17 13:54:18 Atlantis dhclient: DHCPDISCOVER on sit0 to
    >> 255.255.255.255 port 67 interval 7
    >> Jul 17 13:54:20 Atlantis dhclient: DHCPDISCOVER on lo to 255.255.255.255
    >> port 67 interval 9
    >> Jul 17 13:54:25 Atlantis dhclient: DHCPDISCOVER on sit0 to
    >> 255.255.255.255 port 67 interval 7
    >> Jul 17 13:54:29 Atlantis dhclient: DHCPDISCOVER on lo to 255.255.255.255
    >> port 67 interval 21
    >> Jul 17 13:54:32 Atlantis dhclient: DHCPDISCOVER on sit0 to
    >> 255.255.255.255 port 67 interval 12
    >> Jul 17 13:54:43 Atlantis ntpd[7123]: synchronized to LOCAL(0), stratum=10
    >> Jul 17 13:54:43 Atlantis ntpd[7123]: kernel time sync disabled 0041
    >> Jul 17 13:54:44 Atlantis dhclient: DHCPDISCOVER on sit0 to
    >> 255.255.255.255 port 67 interval 10
    >> Jul 17 13:54:50 Atlantis dhclient: DHCPDISCOVER on lo to 255.255.255.255
    >> port 67 interval 5
    >> Jul 17 13:54:54 Atlantis dhclient: No DHCPOFFERS received.
    >> Jul 17 13:54:54 Atlantis dhclient: No working leases in persistent
    >> database - sleeping.
    >>
    >>

  • Next message: vicky: "Re: prob: NFS: /etc/exports"

    Relevant Pages

    • Re: Internet Access problems in Fedora Core 4
      ... using the raw ip was to factor out DNS from the troubleshooting. ... set right or your card's interface isn't setup right. ... nameserver <proxy if proxy does dns to you or isp's dns> ... PING 64.233.179.99 56bytes of data. ...
      (comp.os.linux.misc)
    • ISP DNS, proxies and security
      ... >dns lookups are not done by the isp, ... As far as DNS goes, that's a good question, but I do not know of DNS ... Can you be certain that the proxy itself isn't monitoring ... They do this with transparent proxies, ...
      (comp.security.misc)
    • Re: Internet Access problems in Fedora Core 4
      ... I m using an ethernet LAN card to access the internet. ... your ISP via DNS. ... by trying a URL in your browser that's already in numeric format. ... your proxy is working and most likely DNS is misconfigured. ...
      (comp.os.linux.misc)
    • Re: Accessing windows 2000 dns through linux
      ... We can able to access the internet.. ... But if we want to access the intranet access sites(for example ... use the proxy server for local address - In exceptions tab we have to ... We can access intranet access perfectly by giving dns ip without proxy ...
      (comp.os.linux.setup)
    • Re: DNS Forwarding
      ... Morning, Tried the recursion setting and it worked, for 5 minutes then went ... >> to a DNS cache of theirs which forwards onto others. ... >> addresses (which we need for proxy access to internet), ... >> When you point directly to the DNS cache resolution is fine, ...
      (microsoft.public.windows.server.dns)