DNS problem? - Networking

This is a discussion on DNS problem? - Networking ; Hi all, I posted this question in some other groups but can't get any answer. I'm trying to connect to the Internet via an UMTS Internet Box from Option (you can view it at http://www.option.com/products/globesurfer_icon.shtml ). I followed this guide ...

+ Reply to Thread
Results 1 to 11 of 11

Thread: DNS problem?

  1. DNS problem?

    Hi all,
    I posted this question in some other groups but can't get any answer.
    I'm trying to connect to the Internet via an UMTS Internet Box from Option
    (you can view it at http://www.option.com/products/globesurfer_icon.shtml).
    I followed this guide http://wwwu.uni-klu.ac.at/agebhard/GlobeSurfer/ and
    apparently I can estabilish a connection, but I can neither visualize web
    apges nor ping any address.
    The final part of the connection log sais:

    Cannot determine ethernet address for proxy ARP
    local IP address 151.82.6.8
    remote IP address 10.64.64.64 <--- ???
    primary DNS address 10.11.12.13 <--- ???
    secondary DNS address 10.11.12.14 <--- ???

    Normally (using a cell phone for the connection and the same SIM card) I
    get something like 192.200.1.21 for the remote IP address and
    193.70.152.25 and 193.70.192.25 for the primary and secondary DNS
    addresses respectively. I hope I am in the right place to find some help,
    but, if I'm not can someone suggest me some kind of resource?
    Thanks in advance.

  2. Re: DNS problem?

    On 2007-04-27, Luciano PELLE wrote:
    > Cannot determine ethernet address for proxy ARP
    > local IP address 151.82.6.8
    > remote IP address 10.64.64.64 <--- ???


    Strange, usually the local and remote ip are in the same subnet,
    what does route -n returns?

    Davide

    --
    "You are trapped in a maze of screens and ssh sessions all alike."
    "It is dark, and you are likely to log off the wrong account."
    -- from alt.sysadmin.recovery

  3. Re: DNS problem?

    Il Fri, 27 Apr 2007 17:29:39 +0200, Davide Bianchi ha scritto:

    > On 2007-04-27, Luciano PELLE wrote:
    >> Cannot determine ethernet address for proxy ARP
    >> local IP address 151.82.6.8
    >> remote IP address 10.64.64.64 <--- ???

    >
    > Strange, usually the local and remote ip are in the same subnet,
    > what does route -n returns?
    >
    > Davide
    >


    Connecting via cell phone I get:

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.200.1.21 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
    0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0

    Whilst this is the response when I use the SIM on the GlobeSurfer

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    10.64.64.64 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
    0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 ppp0

    Can you help me?
    Thanks.

  4. Re: DNS problem?

    >> Try pinging an address like
    >> 69.147.114.210 (www.yahoo.com) and look at the last lines of
    >> /var/log/syslog.

    Unfortunately I can't ping this address and syslog does not show anything
    more that the results for the connection.

    > It might simply be that there is no auto-magic setup for DNS by the
    > distribution.


    What does it mean "auto-magic setup"? I noticed that /etc/resolv.conf and
    /etc/ppp/resolv.conf are automatically updated with the correct
    nameserver(s) lines

    nameserver 193.70.152.25
    nameserver 193.70.192.25

    when I connect via my cell. Are those things related? I have just
    installed a Debian Etch, maybe it's a bug in the pppd daemon (2.4.4) in
    this distro?
    Thanks for your patience.

  5. Re: DNS problem?

    Luciano PELLE wrote:
    >>> Try pinging an address like
    >>> 69.147.114.210 (www.yahoo.com) and look at the last lines of
    >>> /var/log/syslog.

    > Unfortunately I can't ping this address and syslog does not show anything
    > more that the results for the connection.


    If you can't ping an IP address then there is a problem unrelated to
    DNS nameservers. What message is generated by ping when it fails
    for 69.147.114.210? Does ping fail for 10.64.64.64?

    >> It might simply be that there is no auto-magic setup for DNS by the
    >> distribution.


    > What does it mean "auto-magic setup"? I noticed that /etc/resolv.conf and
    > /etc/ppp/resolv.conf are automatically updated with the correct
    > nameserver(s) lines


    > nameserver 193.70.152.25
    > nameserver 193.70.192.25


    > when I connect via my cell. Are those things related? I have just


    They are related. But /etc/ppp/resolv.conf is updated by pppd and
    /etc/resolv.conf is updated by the "auto-magic" of the distribution
    (by using /etc/ppp/resolv.conf, or by using the environmental variables
    DNS1, DNS2 that pppd makes available in the /etc/ppp/ip-up script).
    The resolver only uses /etc/resolv.conf.

    > installed a Debian Etch, maybe it's a bug in the pppd daemon (2.4.4) in
    > this distro?


    I don't think so, unless Debian modifies the standard pppd 2.4.4.

    There is a lot involved in what you are doing that is not related to
    PPP and with which I am not familiar. If you really believe the problem
    is a PPP problem then you can add this line to /etc/syslog.conf

    daemon.*;local2.* /var/log/ppp.log

    and then do "kill -HUP `pidof syslogd` to get syslogd to reread
    syslog.conf. The log file produced during connection may be useful.

    > Thanks for your patience.


    --
    Clifford Kite
    /* Those who can't write, write manuals. */

  6. Re: DNS problem?

    Ok, I don't know why (maybe the line you suggested to add to the
    syslog.conf? I think not) but I can ping yahoo at 69.147.114.210 as you can see

    zion:/home/ciano# ping -c4 69.147.114.210
    PING 69.147.114.210 (69.147.114.210) 56(84) bytes of data.
    64 bytes from 69.147.114.210: icmp_seq=1 ttl=53 time=473 ms
    64 bytes from 69.147.114.210: icmp_seq=2 ttl=53 time=486 ms
    64 bytes from 69.147.114.210: icmp_seq=3 ttl=53 time=695 ms
    64 bytes from 69.147.114.210: icmp_seq=4 ttl=53 time=546 ms

    Why I can't ping 10.64.64.64?

    zion:/home/ciano# ping -c4 10.64.64.64 PING 10.64.64.64 (10.64.64.64) 56(84) bytes of data.
    --- 10.64.64.64 ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 3009ms

    zion:/home/ciano# tail -f /var/log/ppp.log
    Apr 28 21:55:08 localhost pppd[4836]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
    Apr 28 21:55:08 localhost pppd[4836]: PAP authentication succeeded
    Apr 28 21:55:13 localhost ntpd[3154]: sendto(87.98.219.90) (fd=16):Network is unreachable <--- ???
    Apr 28 21:55:14 localhost ntpd[3154]: sendto(195.139.204.141) (fd=16):Network is unreachable <--- ???
    Apr 28 21:55:15 localhost pppd[4836]: Could not determine remote IP address: defaulting to 10.64.64.64
    Apr 28 21:55:15 localhost pppd[4836]: Cannot determine ethernet address for proxy ARP
    Apr 28 21:55:15 localhost pppd[4836]: local IP address 151.82.7.24
    Apr 28 21:55:15 localhost pppd[4836]: remote IP address 10.64.64.64
    Apr 28 21:55:15 localhost pppd[4836]: primary DNS address 10.11.12.13
    Apr 28 21:55:15 localhost pppd[4836]: secondary DNS address 10.11.12.14

    Typing http://69.147.114.210 in the address bar of the Iceweasel browser shows me (very slowly for the truth) the yahoo
    home page without images, whilst typing an internet address (like www.debian.org) produces the web page is not displayed.

    So, I think it can be a DNS/resolver problem but don't know how to (re)solve :-) it.
    Is there anything else I can try?

    Thanks a lot for your help.

  7. Re: DNS problem?

    These are the results for the pinging of the two addresses:

    ciano@zion:~$ ping -c4 10.11.12.13
    PING 10.11.12.13 (10.11.12.13) 56(84) bytes of data.

    --- 10.11.12.13 ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 3010ms


    ciano@zion:~$ ping -c4 10.11.12.14
    PING 10.11.12.14 (10.11.12.14) 56(84) bytes of data.

    --- 10.11.12.14 ping statistics ---
    4 packets transmitted, 0 received, 100% packet loss, time 3010ms

    Is there a way to disable that kind of auto-magic setup and to set the
    DNSs according to those of the mobile ISP?
    Is it a good idea or you suggest something else?
    Thanks again.

  8. Re: DNS problem?

    Luciano PELLE wrote:
    > Ok, I don't know why (maybe the line you suggested to add to the
    > syslog.conf? I think not) but I can ping yahoo at 69.147.114.210


    You think correctly. Since you can ping that IP address it again appears
    that something is amiss with DNS nameserver lookup. It could be useful
    to know what message ping generates when you try to ping yahoo and fail.

    > as you can see


    > zion:/home/ciano# ping -c4 69.147.114.210
    > PING 69.147.114.210 (69.147.114.210) 56(84) bytes of data.
    > 64 bytes from 69.147.114.210: icmp_seq=1 ttl=53 time=473 ms
    > 64 bytes from 69.147.114.210: icmp_seq=2 ttl=53 time=486 ms
    > 64 bytes from 69.147.114.210: icmp_seq=3 ttl=53 time=695 ms
    > 64 bytes from 69.147.114.210: icmp_seq=4 ttl=53 time=546 ms


    > Why I can't ping 10.64.64.64?


    Because it's a local address supplied by pppd, not the actual IP address
    of the peer, whatever the "peer" means in this case.

    > zion:/home/ciano# ping -c4 10.64.64.64 PING 10.64.64.64 (10.64.64.64) 56(84) bytes of data.
    > --- 10.64.64.64 ping statistics ---
    > 4 packets transmitted, 0 received, 100% packet loss, time 3009ms


    > zion:/home/ciano# tail -f /var/log/ppp.log
    > Apr 28 21:55:08 localhost pppd[4836]: Warning - secret file /etc/ppp/pap-secrets has world and/or group access
    > Apr 28 21:55:08 localhost pppd[4836]: PAP authentication succeeded
    > Apr 28 21:55:13 localhost ntpd[3154]: sendto(87.98.219.90) (fd=16):Network is unreachable <--- ???
    > Apr 28 21:55:14 localhost ntpd[3154]: sendto(195.139.204.141) (fd=16):Network is unreachable <--- ???


    The NTP daemon is sending requests before the PPP interface comes up.

    > Apr 28 21:55:15 localhost pppd[4836]: Could not determine remote IP address: defaulting to 10.64.64.64


    Sigh, my bad. I forgot to tell you to add the pppd "debug" option and
    so the IPCP negotiations, as well as some others, weren't recorded.
    IPCP is used to negotiate IP addresses. The "debug" can go in the
    /etc/ppp/peers/umts file, or on the pppd command line, e.g., "pppd call
    umts debug".

    > Apr 28 21:55:15 localhost pppd[4836]: Cannot determine ethernet address for proxy ARP
    > Apr 28 21:55:15 localhost pppd[4836]: local IP address 151.82.7.24
    > Apr 28 21:55:15 localhost pppd[4836]: remote IP address 10.64.64.64
    > Apr 28 21:55:15 localhost pppd[4836]: primary DNS address 10.11.12.13
    > Apr 28 21:55:15 localhost pppd[4836]: secondary DNS address 10.11.12.14


    > Typing http://69.147.114.210 in the address bar of the Iceweasel
    > browser shows me (very slowly for the truth) the yahoo home
    > page without images, whilst typing an internet address (like
    > www.debian.org) produces the web page is not displayed.


    I don't know why images wouldn't be present - unless they came from
    off-site, and even then I can't be sure due to a lack of knowledge
    about the intricacies of web browsing.

    > So, I think it can be a DNS/resolver problem but don't know how to
    > (re)solve :-) it.


    Agreed. And I still think the DNS nameserver IP addresses shown above
    are suspect. If they are bogus and are in /etc/resolv.conf then "ping
    www.yahoo.com" should hang for a short time after which ping will exit
    with the message
    ping: unknown host www.yahoo.com
    Make sure to wait until the PPP interface is up before pinging.

    (If no nameserver is given in resolv.conf then ping will exit immediately
    with the same message.)

    > Is there anything else I can try?


    Try adding the debug option and post the part of the log for another
    connection - that should show us where those nameserver IP addresses
    actually come from. If they are bogus and come from the "peer" then
    I'm out of suggestions.

    P.S. In answer to the next to last question of your latest post, to
    disable the "auto-magic" just remove usepeerdns from /etc/ppp/peers/umts.
    You can manually insert other nameserver IP's in /etc/resolv.conf.

    > Thanks a lot for your help.


    --
    Clifford Kite

  9. Re: DNS problem?

    Clifford Kite wrote:

    > P.S. In answer to the next to last question of your latest post, to
    > disable the "auto-magic" just remove usepeerdns from /etc/ppp/peers/umts.
    > You can manually insert other nameserver IP's in /etc/resolv.conf.


    Ah hum.. You may also need to disable part or all of a distro script that
    makes changes to /etc/resolv.conf using nameserver addresses obtained
    from usepeerdns, probably run from /etc/ppp/ip-up. The changes could
    also be made directly from ip-up by echoing DNS1 and DNS1 with redirection
    to overwrite /etc/resolv.conf.

    --
    Clifford Kite
    /* 97.3% of all statistics are made up. */

  10. Re: DNS problem?

    IT WORKS!!!
    I've added the "debug" line and disabled (commented out) the lines
    "usepeerdns" and "replacedefaultroute" and the lines after the comment
    "t-mobile specific".
    Also I've added the correct DNS address from my mobile ISP in
    /etc/resolv.conf and in /etc/ppp/resolv.conf.
    Plus I've inserted the standard user and password strings provided by the
    mobile ISP (even if I think they're not necessary, isn't it?). The
    connection is working ... not too fast, but working. What can I try to
    make my connection faster? Is there something I can add or uncomment?
    Thanks for your help. Thanks a lot.

  11. Re: DNS problem?

    Luciano PELLE wrote:
    > IT WORKS!!!


    Great!

    > I've added the "debug" line and disabled (commented out) the lines
    > "usepeerdns" and "replacedefaultroute" and the lines after the comment
    > "t-mobile specific".


    I wondered about the replacedefaultroute since it is not a feature
    of the standard pppd, but I saw no harm in it being there - assuming
    it's function was implied by the name. You'll likely want to disable
    "debug" when you decide you've tweaked as much as you can.

    > Also I've added the correct DNS address from my mobile ISP in
    > /etc/resolv.conf and in /etc/ppp/resolv.conf.
    > Plus I've inserted the standard user and password strings provided by the
    > mobile ISP (even if I think they're not necessary, isn't it?). The


    Something may need to be given as user and password but, as I (poorly)
    understand it, for GPRS/PPP the actual authentication occurs outside
    the scope of PPP.

    > connection is working ... not too fast, but working. What can I try to
    > make my connection faster? Is there something I can add or uncomment?


    I can *guess* something but lack experience with USB-to-serial adapters
    and so cannot guarantee it will work. You can try changing the
    OK "AT+IPR=115200 lines in umts-prep and umts-prep-nopin to
    OK "AT+IPR=460800" , and if that fails, try OK "AT+IPR=230400" .

    The rational is that umts sets a speed of 460800 which pppd uses to
    set the speed of the ttyUSB0 device file, and while setting an adapter
    speed of 115200 works, a speed setting nearer to that of the device file
    might also work. The throughput cannot be larger than the smaller of
    the two speeds, but there may be factors unknown to me that would cause
    communication failure if the two speeds are too close to one another.

    > Thanks for your help. Thanks a lot.


    Thanks for the post, I learned some things too.

    --
    Clifford Kite
    /* The wealth of a nation is created by the productive labor of its
    * citizens. */

+ Reply to Thread