Slow browsing with cable modem

Discussion in 'Linux Networking' started by Stephen Zilliox, Apr 21, 2004.

  1. I have been unable to connect successfully to the internet while in the
    linux operating system through my toshiba

    PCX 2200
    cable modem and Netgear FA311
    ethernet card. Until 3 months ago I had 56k dialup and linux internet access
    was no problem. I have a dual boot

    machine
    that I can boot into Windows XP or Mandrake Linux 10 community (although I
    had the exact same problem with 9.2)
    My ISP is Charter Cable through charter.net. With Windows XP I have no
    trouble surfing the web, sending e-mail,

    etc.
    No help from charter--they do not support linux. I prefer to work with linux
    but these broadband problems are

    driving
    me back to windows. I have used DHCP under the Mandrake connect wizards
    which reports that I am connected. I can

    ping
    some sites successfully but others no. (examples below.) With the browzers
    sometimes the sites will partially

    load
    very slowly and sometimes the browser will just enter the "waiting for..."
    mode and never get anywhere. The

    following
    is the info from Windows XP which it uses to connect to Charter Cable:

    IP Address=66.189.180.71
    Subnet Mask=255.255.254.0
    Physical Address=00-09-5b-60-64-79
    Default Gateway=66.189.180.1
    DHCP Server=192.168.4.27
    DNS Servers=66.189.219.29 66.189.219.30 66.169.254,30 66.169.254.29

    Many of these addresses are the same as those assigned by DHCP under Linux.
    I have included the contents of

    several
    of the files I have noted while reading posts concerning internet problems.
    I should mention that I have tried

    disabling
    the Shorewall firewall, but that was of no help. (I have since reenabled
    it.) Can anyone help me? Suggestions?
    Thanks.

    ifcfg-eth0

    DEVICE=eth0
    BOOTPROTO=dhcp
    IPADDR=66.189.180.71
    NETMASK=255.255.254.0
    NETWORK=66.189.180.0
    BROADCAST=66.189.181.255
    ONBOOT=yes
    MII_NOT_SUPPORTED=no
    NEEDHOSTNAME=yes

    --------------------------------------------

    network

    NETWORKING=yes
    GATEWAY=66.189.180.1very similar

    ------------------------------------------------

    resolv.conf

    nameserver 66.189.219.29
    nameserver 66.189.219.30
    nameserver 66.169.254.30
    nameserver 66.169.254.29
    search 189.180.1

    ---------------------------------------------------

    hosts

    127.0.0.1 localhost
    66.189.180.71 66.189.180.1 66
    68.113.7.247 66.189.180.1 66

    -----------------------------------------------------

    [email protected] etc]# ifconfig
    eth0 Link encap:Ethernet HWaddr 00:09:5B:60:64:79
    inet addr:68.113.7.247 Bcavery similarst:255.255.255.255 Mask:255.255.254.0
    inet6 addr: fe80::209:5bff:fe60:6479/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:12156 errors:0 dropped:0 overruns:0 frame:0
    TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:735059 (717.8 Kb) TX bytes:13523 (13.2 Kb)
    Interrupt:11 Base address:0xc000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:490 errors:0 dropped:0 overruns:0 frame:0
    TX packets:490 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:31808 (31.0 Kb) TX bytes:31808 (31.0 K

    ----------------------------------------------------------------------------
    -

    Here is some more information concerning my problem. I've included in this
    message the ping attempts I made from

    linux below. Don't know if these are helpful. I did some further
    investigating while in linux and came up with

    some confusing behavior. In Mandrake Linux when you open any browser the
    default page includes shortcuts to many

    Mandrake sites. In Mozilla when I attempt to access any of these (such as
    mandrakelinux.com) I get the "waiting

    for mandrakelinux.com" message in the lower left hand of the browser window.
    With Mozilla this is what happens

    when I attempt to go to any site. With Konqueror or Epiphany browsers this
    is also sometimes the case but not

    always. For instance, when I click the shortcut to mandrakelinux.com in
    either of these two browsers I will go to

    the web site. In this case the alphanumerics will load up rather quickly but
    the graphics will take an

    inordinately long time. None of the three browsers will go to
    google.com----they will all sit spinning their

    wheels at "waiting for google.com". To me this behavior is bizarre---what is
    the difference between Mozilla and

    the other two browsers? The answer to this question would probably give
    important clues as to what is going on

    here. What do you think? The one thing I notice thats different between the
    network connection details of

    windows xp and linux is windows includes two items referring to "leasing":
    Lease Obtained and Lease Expires,

    after these two items are listed dates. I can not find these details listed
    anywhere in Mandrake Linux or its

    documentation. Is XP doing some kind of handshaking with my ISP that linux
    does not and could this account for

    my problems?

    [email protected] etc]# ping -c 1 127.0.0.1
    PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
    64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.091 ms

    --- 127.0.0.1 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.091/0.091/0.091/0.000 ms
    [[email protected] etc]# ping -c 1 localhost
    PING localhost (127.0.0.1) 56(84) bytes of data.
    64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.087 ms

    --- localhost ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.087/0.087/0.087/0.000 ms
    [[email protected] etc]# hostname -f
    66.189.180.1
    [[email protected] etc]# ping -c 1 216.239.57.99
    PING 216.239.57.99 (216.239.57.99) 56(84) bytes of data.
    64 bytes from 216.239.57.99: icmp_seq=1 ttl=241 time=43.8 ms

    --- 216.239.57.99 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 43.820/43.820/43.820/0.000 ms
    [[email protected] etc]# ping -c 1 google.com
    PING google.com (216.239.39.99) 56(84) bytes of data.
    64 bytes from 216.239.39.99: icmp_seq=1 ttl=239 time=80.3 ms

    --- google.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 80.322/80.322/80.322/0.000 ms
    [[email protected] etc]# ping -c 1 excite.com
    PING excite.com (208.45.133.23) 56(84) bytes of data.

    --- excite.com ping statistics ---
    1 packets transmitted, 0 received, 100% packet loss, time 0ms
     
    Stephen Zilliox, Apr 21, 2004
    #1
    1. Advertisements

  2. Please change this into:
    DEVICE=eth0
    BOOTPROTO=dhcp
    ONBOOT=yes
    Please change this into:

    127.0.0.1 localhost

    Make a /etc/init.d/network restart

    If your problems persist, with or without Shorewall running, the
    output of:
    ifconfig
    cat /etc/resolv.conf
    route -n
    is very relevant...

    BTW: Thanks for providing that much information in your first posting.

    --
    mvh/regards
    Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti
     
    Joachim =?iso-8859-1?b?TcOmbGFuZCI=?=, Apr 21, 2004
    #2
    1. Advertisements

  3. I did as you suggested. There was no effect. Things are just as described
    before. Here are the relevant outputs: further suggestions?


    [[email protected] sysconfig]# ifconfig

    eth0 Link encap:Ethernet HWaddr 00:09:5B:60:64:79

    inet addr:68.113.7.247 Bcast:255.255.255.255 Mask:255.255.254.0

    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    RX packets:15412 errors:285 dropped:0 overruns:0 frame:569

    TX packets:304 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:1000

    RX bytes:952108 (929.7 Kb) TX bytes:42183 (41.1 Kb)

    Interrupt:11 Base address:0xc000




    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:250 errors:0 dropped:0 overruns:0 frame:0

    TX packets:250 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:0

    RX bytes:16268 (15.8 Kb) TX bytes:16268 (15.8 Kb)




    [[email protected] sysconfig]# cat /etc/resolv.conf

    nameserver 66.189.219.29

    nameserver 66.189.219.30

    nameserver 66.169.254.30

    nameserver 66.169.254.29




    [[email protected] sysconfig]# route -n

    Kernel IP routing table

    Destination Gateway Genmask Flags Metric
    Ref Use Iface

    68.113.6.0 0.0.0.0 255.255.254.0 U 0
    0 0 eth0

    127.0.0.0 0.0.0.0 255.0.0.0 U 0
    0 0 lo

    0.0.0.0 68.113.6.1 0.0.0.0 UG 0
    0 0 eth0





     
    Stephen Zilliox, Apr 22, 2004
    #3
  4. This shows your Internet IP address to be 68.113.7.247.

    ....
    This shows the default route is through eth0 using the gateway IP address
    68.113.6.1 .

    All that looks as I would expect, and should be correct.

    OTOH, the hosts and resolv.conf files from the first post looked very
    strange to me. The resolv.conf file showed "search 189.180.1" instead
    of a domain name. The hosts file showed IP addresses used as hostnames
    and the first quad of an IP address used as aliases in hosts:

    hosts

    127.0.0.1 localhost
    66.189.180.71 66.189.180.1 66
    68.113.7.247 66.189.180.1 66

    Even if it's valid to do these things, I have only a vague idea as to
    what you are trying to accomplish. My thought is that the search option
    should be changed to domain name (or deleted) and the last two lines in
    host should be deleted, period.

    Finally, the output of Microsoft's "route PRINT" (?) command in that
    first post showed

    Default Gateway=66.189.180.1

    which is an IP address that is not related to the default gateway in
    the output of the *nix route command, but rather is an IP address for
    some interface on the Wintendo host.

    So if the peculiar hosts arrangement is an attempt to somehow link the
    Windows default route to the IP addresses obtained by DHCP (66.189.180.71
    was the *nix host address in the first post) then it's a futile effort.

    Oh, and regarding pinging excite.com. It doesn't return echo-replies
    for me either; it's very likely blocking ICMP messages, or at least
    blocking either incoming ping echo-requests or out-going echo-replies.

    This is probably all I can say with any conviction since I've never
    used DHCP.

    Addendum
    --------
    Your post today verifies that the default route above is indeed correct:

    option routers 68.113.6.1;

    Expect a follow-up to today's post with additional comments.
     
    Clifford Kite, Apr 23, 2004
    #4
  5. Again, it's your Internet IP address, not a gateway in the *nix sense.
    You should configure the DHCP "router address" as the gateway IP address,
    if any manual configuration is required. That's one of the things DHCP
    provides. I don't know what ''the "network" file'' means but suspect
    it is distribution related.
    Little wonder..
    Now this I can't explain definitively. It is assigned to "MDFRD-OR"
    according to the whois web server http://www.arin.net/whois/index.html.
    Nonsense. It was the default route shown with "route -n" in your
    second post.
    The first 2 DNS nameserver addresses are valid. The others are assigned
    to "MDFRD-OR" (Medford, Oregon ? isn't Oregon near Washington? :>) but do
    not have FQDNs.

    host 66.189.219.29
    29.219.189.66.IN-ADDR.ARPA domain name pointer ns1.wa.charter.com
    host 66.189.219.30
    30.219.189.66.IN-ADDR.ARPA domain name pointer ns2.ca.charter.com

    Doesn't "wa" mean Washington?
    Wintendo is bizarre.
    The "fixed address" certainly does. I don't know why using different
    browsers should make a difference.

    ....
     
    Clifford Kite, Apr 23, 2004
    #5
  6. Below is the output of : cat /var/lib/dhcp/dhclient-eth0.leases. Of
    interest to me is the "fixed address 68.113.7.247"---this address appears
    nowhere in my windows XP network parameters listing, but has shown up in
    linux in the "network" file as "GATEWAY=68.113.7.247". When this line
    existed my linux browsers would not access other sites at all, just going
    into the perpetual "waiting for" mode. When I changed the address to
    66.189.180.1---the default gateway listed under windows XP---then I could
    access some websites as described before with Konqueror and Epiphany
    although very slowly. Mozilla, however, remained in the "waiting for" mode.
    The routers address is one I haven't seen before. All the other addresses in
    the file below are present in windows XP also. Very bizarre. Does this file
    give any further clues as to what might be going on? I have a feeling that
    the "fixed address" value has something to do with my problem as well as the
    difference between Mozilla and the other two browsers. Thanks alot for
    your assistance. Do you have any further suggestions?



    [email protected] network-scripts]# cat /var/lib/dhcp/dhclient-eth0.leases

    lease {

    interface "eth0";

    fixed-address 68.113.7.247;

    option subnet-mask 255.255.254.0;

    option time-offset -21600;

    option dhcp-lease-time 172800;

    option routers 68.113.6.1;

    option dhcp-message-type 5;

    option dhcp-server-identifier 192.168.4.27;

    option domain-name-servers
    66.189.219.29,66.189.219.30,66.169.254.30,66.169.25 4.29;

    option broadcast-address 255.255.255.255;

    renew 5 2004/4/23 22:07:13;

    rebind 6 2004/4/24 21:47:17;

    expire 0 2004/4/25 03:47:17;

    }

    lease {

    interface "eth0";

    fixed-address 68.113.7.247;

    option subnet-mask 255.255.254.0;

    option time-offset -21600;

    option routers 68.113.6.1;

    option dhcp-lease-time 172342;

    option dhcp-message-type 5;

    option domain-name-servers
    66.189.219.29,66.189.219.30,66.169.254.30,66.169.25 4.29;

    option dhcp-server-identifier 192.168.4.27;

    option broadcast-address 255.255.255.255;

    renew 6 2004/4/24 05:23:46;

    rebind 0 2004/4/25 04:48:16;

    expire 0 2004/4/25 10:47:19;

    }


     
    Stephen Zilliox, Apr 23, 2004
    #6
  7. Let's go serious... :)

    Please get rid of all old leases, just in case:

    mv /var/lib/dhcp/dhclient-eth0.leases
    /var/lib/dhcp/dhclient-eth0.leases.old (No line break)

    Fix all settings:

    #ifcfg-eth0
    DEVICE=eth0
    BOOTPROTO=dhcp
    ONBOOT=yes

    #hosts
    127.0.0.1 localhost

    Get a fresh start:

    /etc/init.d/network restart

    Remove any blocking firewall rules:

    /etc/init.d/iptables stop

    Check the output of, (and please post if appropriate):

    cat /etc/resolv.conf
    ifconfig
    route -n

    What's the output from the following tests?

    dig all google.com
    <bonus test>
    dig @<each IP-address from resolv.conf> coogle.com
    </bonus test>
    ping -c 3 google.com
    traceroute -n google.com
    ping -c 3 216.239.57.99
    traceroute -n 216.239.57.99

    If you can ping google.com, please get yourself a real browser...:

    urpmi lynx (IMHO: _The_ browser for testing)

    then, as normal user, (not root):

    lynx -accept_all_cookies http://www.google.com/

    Did it work, how about Mozilla?

    As a last resort, find the thread starting with Message ID:
    "" at:
    http://www.google.com/advanced_group_search?hl=en and test the dhclient
    tweak, described in Message ID:
    ""

    --
    mvh/regards
    Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti
     
    Joachim =?iso-8859-1?b?TcOmbGFuZCI=?=, Apr 23, 2004
    #7
  8. Stephen Zilliox

    P Gentry Guest

    This _is_ your assigned IP address when in Linux -- normal. See
    below.
    Your IP address cannot be the GW router used to connect to other net
    segments -- this would indicate _serious_ config problems.
    Sheer luck(?) that the GW still had arp entries for your MAC from your
    Windows use. The slowness was re-adjusting to the new IP of your
    Linux box. When Win is used again, the poor GW is really going to be
    confused.
    According to earlier posts your Win IP is placed on an entirely
    different sub-net from your Linux IP -- IP Address=66.189.180.71 for
    Win and 68.113.7.247 for Linux. Compare your ifconfig output to your
    ifcfg-eth0 file listing in your first post. Big problem here! Or
    just a typo, which would be OK and understandable if you're not
    cut-n-pasting.
    Which is it -- 66.189.180.71 or 68.113.7.247 at ifconfig?
    This is the previous accepted lease -- used as a backup if lease
    request fails.
    See, 68.113.7.247 _is_ the IP for your Linux interface. This is quite
    common on dual boot machines because Win and Linux use different
    client-ids when requesting a lease. J.M. is newly familiar with Win
    vs. Linux client-ids re: Verizon ;-)
    This is your GW when using Linux. Should be able to ping this almost
    as fast as localhost. It _must_ be on the same subnet as you.
    These are your DNS servers where all name lookups will be sent. They
    should also appear in resolv.conf. Note they are _not_ on your
    subnet, so you must be routed to them via GW. These may or may not be
    the same used when in Win.
    This is the DHCP server where you acquired this lease. Renewals will
    be sent directly here rather that via broadcast requests.
    [snip]

    First, browsers are _useless_ (almost) for diagnosing network
    configuration problems. Observed behavior could stem from hundreds of
    _browser_ differences irrespective of network problems. And no two
    cache the same info.

    Second, ping is not much better unless you know how to interpret the
    results. As the Linuxforum guy said, Excite, eg., doesn't allow that
    kind of traffic. Ping 127.0.0.1, then localhost, then your GW, then
    your name servers to establish a _basic_ working network
    configuration. Problems here must be corrected before anything else
    will work properly or consistently.

    When ping has you wondering, pull out your traceroute guns to follow
    the actual path your packets are taking. Eg., traceroute to excite
    would reveal where your ping packets are being dropped -- nothing you
    can do about that and not your problem. The "failed" ping shows
    nothing.

    Third, _never_ change your network settings that were set via DHCP to
    solve a problem. It's very tricky and ill-advised to do this to
    investigate a problem -- you run the very real risk of "poisoning"
    network data concerning your configuration that can be a real pain to
    clear up. Remember, network traffic and data is two way -- routers
    and servers are learning about you as you use the network. Eg., don't
    change your GW by hand, nor your IP or masks or routing tables nor
    your DNS name servers -- unless you know what you're doing and can
    clean up afterwards.

    Now, to your very real problems...

    I'm not familiar with Charter and you may have to locate someone who
    is to get good, consistent service from both Win and Linux. Right
    now, the DHCP servers and routers and perhaps other servers see two
    IPs bound to one MAC -- Charter's network may not like that. Routers
    certainly don't -- it plays games with the arp cache.

    One possibility is to change the MAC address in one OS -- Win is a
    good candidate and in Linux it's almost too easy. That way, you'll
    get one MAC-IP pair for Win and another with Linux. This may not work
    because a) it will look like you're running two computers and you're
    certainly using two IPs (which your account may not allow) and b) the
    cable modem may not like handling two MACs.

    Re: the last point, I'm not familiar with Toshibas and my web source
    for such info is in the process of moving. Be sure you monitor the CM
    configuration during this process to see how it behaves from Win and
    Linux if you try this.

    You can also set up your Linux sessions to request DHCP config info in
    the same way that your Win sessions do if you use dhclient in Linux.
    The config file can be set up to send the same client-id as Windows.
    Thus you will always appear to the network to be using one computer
    _and_ you'll actually only require one IP address. Try this for some
    background:
    http://homepage.ntlworld.com/robin.d.h.walker/cmtips/dhcp.html
    I would have to look around to get the details -- J.M. may have them
    handy.

    After your networking configuration is "correct", then you can tackle
    issues regarding browsers and email performance. Don't try to "fix"
    it all at once -- you'll never know what changes are working and which
    are not or making things worse.

    My "gut" tells me that you'll probably need to make your Linux
    sessions/DHCP requests look the same as your Win sessions. Just a
    guess at this point, so don't take it to heart without investigating
    further.

    Hang in there -- you're doing good so far. Most would have given up
    long ago.

    hth,
    prg
    email above disabled
     
    P Gentry, Apr 23, 2004
    #8
  9. Stephen Zilliox

    ACT Guest

    I had a similar problem with my internet connection where *some* websites
    wouldn't load and those same sites wouldn't respond to pings.

    I fixed this problem after many attempts by changing the MTU (Maximum
    Transmission Unit). The default value in linux for a lan connection is
    1500. When you do 'ifconfig eth0' it shows your MTU (yours is 1500). I
    changed mine down to 1492 and instantly I was able to load all the websites
    that were previously not working.

    To change the MTU for device eth0 do the following command:

    ifconfig eth0 mtu 1492

    When you run this command the effect will be instant and you won't need a
    reboot. If 1492 doesn't work then try lowering it to say, 1450.

    It may a be a stab in the dark but it's worth a try...

    AC
     
    ACT, Apr 24, 2004
    #9
  10. It seems to me that his IP address, 68.113.7.247, is on the same CIDR
    subnet, 68.113.6.0/31, as the router's IP address, 68.113.6.1 .

    If I'm wrong then please don't hesitate correct me and explain why.
     
    Clifford Kite, Apr 24, 2004
    #10
  11. Stephen Zilliox

    P Gentry Guest

    You are almost correct, and I was too loose with my late day typing
    freenzy.

    My, erh, comments related to the IPs in the first post where there
    were inconsistent IP address/subnet numbers. The last post does
    indeed reveal what seems to be a consistent set of IPs. It was also
    meant to warn OP against changing the DHCP settings manually in an
    attempt to fix it by trial-n-stumble. I should have been clearer.

    I _think_ the first post inconsistencies were typos mostly, but can't
    be sure without confirmation from OP.

    BTW, OP's net uses a /23 prefix -- there is no such beast as a /31.
    /30 is the smallest posssible as one IP for net, one IP for broadcast,
    and two IP's for hosts (one at each end) is the smallest you can go.
    /31 provides only 2 IPs and 2 are always reserved -- one for net
    segment and one for broadcast, leaving no IPs for hosts.

    I'm always preaching the need for exactness and clarity when dealing
    with network configuration problems, so it's only fair to be rightly
    called to task. I hope I've cleared it up. Sharp eyes make for
    quicker fixes.

    regards,
    prg
    email above disabled
     
    P Gentry, Apr 24, 2004
    #11
  12. Stephen Zilliox

    P Gentry Guest

    This is generally a fix for xDSL setups rather than cable modems. The
    xDSL protocols require an extra 8 bytes minimum overhead -- sometimes
    you have to drop down all the way 1408 or there abouts.

    I overlooked the possibility that it _may_ apply here, so it's good
    you mentioned it just in case.

    regards,
    prg
    email above disabled
     
    P Gentry, Apr 24, 2004
    #12
  13. Stephen Zilliox

    Bit Twister Guest

    Those routes are droping your trace packets. Add -I and they might respond.
     
    Bit Twister, Apr 24, 2004
    #13
  14. This all looked OK..
    [..]
    You're obviosly resolving google, can ping based on both name and
    IP-address.
    Where's your default GW...?
    Where's your default GW...?
    So your awake... :) (I wasn't...)
    Strange... Have you checked your proxy settings?

    Can you ping default GW? (68.113.6.1)
    Traceroute ?

    Is this the case...?:
    We're just about to start... Or what, folks...?

    --
    mvh/regards
    Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti
     
    Joachim =?iso-8859-1?b?TcOmbGFuZCI=?=, Apr 24, 2004
    #14
  15. There were indeed many strange things, some of which I am unable to
    see as being typos.
    Okay, that would be true in regard to 68.113.6.0/31 if it applied only to
    the last quad, i.e., with a netmask of 255.255.255.0 . The netmask above
    is shown to be 255.255.254.0, so I'm not sure that's correct in this case.

    In exploring the effect of the netmask 255.255.254.0 here I came up with
    these results for my eth0 interface:

    ifconfig eth0 192.168.1.1/23 broadcast 255.255.255.255 up
    ifconfig eth0
    eth0 Link encap:Ethernet HWaddr 00:20:AF:1B:5C:48
    inet addr:192.168.1.1 Bcast:255.255.255.255 Mask:255.255.254.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    Interrupt:10 Base address:0x280

    route add 192.168.0.247 eth0
    route add default gw 192.168.1.1 eth0
    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.0.247 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
    192.168.0.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

    OTOH, I found this when trying to add a default route that wasn't covered
    by the netmask 255.255.254.0 this was the result:

    route del default gw 192.168.1.1 eth0
    route add default gw 192.168.2.1 eth0
    SIOCADDRT: Network is unreachable
    Thanks..
     
    Clifford Kite, Apr 24, 2004
    #15
  16. Gak! Sorry, you're right about the /31 network. Please disregard my
    remarks about it. No excuse will do. (I really dislike following up
    and correcting my own posts!)

    --
    Clifford Kite Email: "echo |rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* "PPPoE has many advantages for DSL service providers, and
    practically none for DSL consumers."
    - David F. Skoll */
     
    Clifford Kite, Apr 24, 2004
    #16
  17. All done
    OK

    [[email protected] etc]# cat /etc/resolv.conf
    nameserver 66.189.219.29
    nameserver 66.189.219.30
    nameserver 66.169.254.30
    nameserver 66.169.254.29

    [[email protected] etc]# ifconfig
    eth0 Link encap:Ethernet HWaddr 00:09:5B:60:64:79[[email protected]
    etc]# dig 66.189.219.30 google.com

    ; <<>> DiG 9.2.3 <<>> 66.189.219.30 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46773
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.189.219.30. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 50 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:49:47 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20678
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 135 IN A 216.239.57.99
    google.com. 135 IN A 216.239.37.99
    google.com. 135 IN A 216.239.39.99

    ;; AUTHORITY SECTION:
    google.com. 345443 IN NS ns2.google.com.
    google.com. 345443 IN NS ns3.google.com.
    google.com. 345443 IN NS ns4.google.com.
    google.com. 345443 IN NS ns1.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313665 IN A 216.239.32.10

    ;; Query time: 31 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:49:47 2004
    ;; MSG SIZE rcvd: 164

    inet addr:68.113.7.247 Bcast:255.255.255.255
    Mask:255.255.254.0dos2unix
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:32173 errors:562 dropped:0 overruns:0 frame:1124
    TX packets:713 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2188633 (2.0 Mb) TX bytes:104714 (102.2 Kb)
    Interrupt:11 Base address:0xc000

    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:452 errors:0 dropped:0 overruns:0 frame:0
    TX packets:452 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:29324 (28.6 Kb) TX bytes:29324 (28.6 Kb)

    [email protected] etc]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    68.113.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
    0.0.0.0 68.113.6.1 0.0.0.0 UG 0 0 0 eth0

    ; <<>> DiG 9.2.3 <<>> all google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7733
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;all. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 43 msecdos2unix
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:43:46 2004
    ;; MSG SIZE rcvd: 96

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16109
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 127 IN A 216.239.37.99
    google.com. 127 IN A 216.239.39.99
    google.com. 127 IN A 216.239.57.99

    ;; AUTHORITY SECTION:
    google.com. 345575 IN NS ns2.google.com.
    google.com. 345575 IN NS ns3.google.com.
    google.com. 345575 IN NS ns4.google.com.
    google.com. 345575 IN NS ns1.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 314026 IN A 216.239.32.10
    [[email protected] etc]# dig 66.169.254.29 google.com

    ; <<>> DiG 9.2.3 <<>> 66.169.254.29 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18215
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.29. IN A

    ;; AUTHORITY SECTION:
    .. 8468 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 19 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:52:54 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5795
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 293 IN A 216.239.37.99
    google.com. 293 IN A 216.239.39.99
    google.com. 293 IN A 216.239.57.99

    ;; AUTHORITY SECTION:
    google.com. 345593 IN NS ns1.google.com.
    google.com. 345593 IN NS ns2.google.com.
    google.com. 345593 IN NS ns3.google.com.
    google.com. 345593 IN NS ns4.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313478 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:52:54 2004
    ;; MSG SIZE rcvd: 164

    ;; Query time: 32 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:43:46 2004
    ;; MSG SIZE rcvd: 164

    [[email protected] etc]# dig 66.189.219.29 google.com

    ; <<>> DiG 9.2.3 <<>> 66.189.219.29 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48456
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.189.219.29. IN A

    ;; AUTHORITY SECTION:
    .. 3053 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 21 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:48:16 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8959
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 226 IN A 216.239.57.99
    google.com. 226 IN A 216.239.37.99
    google.com. 226 IN A 216.239.39.99

    ;; AUTHORITY SECTION:
    google.com. 345534 IN NS ns3.google.com.
    google.com. 345534 IN NS ns4.google.com.; <<>> DiG
    9.2.3 <<>> 66.169.254.30 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59980
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.30. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 55 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37810
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 54 IN A 216.239.39.99
    google.com. 54 IN A 216.239.57.99
    google.com. 54 IN A 216.239.37.99

    ;; AUTHORITY SECTION:
    google.com. 345541 IN NS ns4.google.com.
    google.com. 345541 IN NS ns1.google.com.
    google.com. 345541 IN NS ns2.google.com.
    google.com. 345541 IN NS ns3.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313584 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 164

    google.com. 345534 IN NS ns1.google.com.
    google.com. 345534 IN NS ns2.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313756 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:48:16 2004
    ;; MSG SIZE rcvd: 164

    [[email protected] etc]# dig 66.189.219.30 google.com

    ; <<>> DiG 9.2.3 <<>> 66.189.219.30 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46773
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.189.219.30. IN A; <<>> DiG 9.2.3 <<>> 66.169.254.30
    google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59980
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.30. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 55 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37810
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 54 IN A 216.239.39.99
    google.com. 54 IN A 216.239.57.99
    google.com. 54 IN A 216.239.37.99

    ;; AUTHORITY SECTION:
    google.com. 345541 IN NS ns4.google.com.
    google.com. 345541 IN NS ns1.google.com.
    google.com. 345541 IN NS ns2.google.com.
    google.com. 345541 IN NS ns3.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313584 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 164


    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 50 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:49:47 2004
    ;; MSG SIZE rcvd: 106; <<>> DiG 9.2.3 <<>> 66.169.254.30 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59980
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.30. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 55 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37810
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1dos2unix

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 54 IN A 216.239.39.99
    google.com. 54 IN A 216.239.57.99
    google.com. 54 IN A 216.239.37.99

    ;; AUTHORITY SECTION:
    google.com. 345541 IN NS ns4.google.com.
    google.com. 345541 IN NS ns1.google.com.
    google.com. 345541 IN NS ns2.google.com.
    google.com. 345541 IN NS ns3.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313584 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 164


    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20678
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 135 IN A 216.239.57.99
    google.com. 135 IN A 216.239.37.99
    google.com. 135 IN A 216.239.39.99

    ;; AUTHORITY SECTION:
    google.com. 345443 IN NS ns2.google.com.
    google.com. 345443 IN NS ns3.google.com.
    google.com. 345443 IN NS ns4.google.com.
    google.com. 345443 IN NS ns1.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313665 IN A 216.239.32.10

    ;; Query time: 31 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:49:47 2004
    ;; MSG SIZE rcvd: 164

    ; <<>> DiG 9.2.3 <<>> 66.169.254.30 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59980
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.30. IN A

    ;; AUTHORITY SECTION:
    .. 10800 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 55 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37810
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 54 IN A 216.239.39.99
    google.com. 54 IN A 216.239.57.99
    google.com. 54 IN A 216.239.37.99

    ;; AUTHORITY SECTION:
    google.com. 345541 IN NS ns4.google.com.
    google.com. 345541 IN NS ns1.google.com.
    google.com. 345541 IN NS ns2.google.com.
    google.com. 345541 IN NS ns3.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313584 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:51:08 2004
    ;; MSG SIZE rcvd: 164

    [[email protected] etc]# dig 66.169.254.29 google.com

    ; <<>> DiG 9.2.3 <<>> 66.169.254.29 google.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18215
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.169.254.29. IN A

    ;; AUTHORITY SECTION:
    .. 8468 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 19 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:52:54 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5795
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;google.com. IN A

    ;; ANSWER SECTION:
    google.com. 293 IN A 216.239.37.99
    google.com. 293 IN A 216.239.39.99
    google.com. 293 IN A 216.239.57.99

    ;; AUTHORITY SECTION:
    google.com. 345593 IN NS ns1.google.com.
    google.com. 345593 IN NS ns2.google.com.
    google.com. 345593 IN NS ns3.google.com.
    google.com. 345593 IN NS ns4.google.com.

    ;; ADDITIONAL SECTION:
    ns1.google.com. 313478 IN A 216.239.32.10

    ;; Query time: 30 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:52:54 2004
    ;; MSG SIZE rcvd: 164

    [[email protected] etc]# dig 66.189.219.29 coogle.com

    ; <<>> DiG 9.2.3 <<>> 66.189.219.29 coogle.com
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42922
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;66.189.219.29. IN A

    ;; AUTHORITY SECTION:
    .. 2634 IN SOA A.ROOT-SERVERS.NET.
    NSTLD.VERISIGN-GRS.COM. 2004042400 1800 900 604800 86400

    ;; Query time: 11 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:55:15 2004
    ;; MSG SIZE rcvd: 106

    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39280
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;coogle.com. IN A

    ;; ANSWER SECTION:
    coogle.com. 43200 IN A 66.175.28.51

    ;; AUTHORITY SECTION:
    coogle.com. 43200 IN NS ns.cedant.com.
    coogle.com. 43200 IN NS ns2.cedant.com.

    ;; Query time: 128 msec
    ;; SERVER: 66.189.219.29#53(66.189.219.29)
    ;; WHEN: Sat Apr 24 08:55:15 2004
    ;; MSG SIZE rcvd: 86

    [[email protected] etc]# ping -c 3 google.com
    PING google.com (216.239.39.99) 56(84) bytes of data.
    64 bytes from 216.239.39.99: icmp_seq=1 ttl=239 time=81.3 ms
    64 bytes from 216.239.39.99: icmp_seq=2 ttl=239 time=83.8 ms
    64 bytes from 216.239.39.99: icmp_seq=3 ttl=239 time=80.9 ms

    --- google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 80.907/82.024/83.804/1.293 ms
    dos2unix
    [[email protected] etc]# traceroute -n google.com
    traceroute: Warning: google.com has multiple addresses; using 216.239.57.99
    traceroute to google.com (216.239.57.99), 30 hops max, 38 byte packets
    1 10.210.32.1 34.228 ms 12.221 ms 8.632 ms
    2 172.29.32.161 8.492 ms 29.435 ms 8.636 ms
    3 172.29.32.2 29.265 ms 9.007 ms 9.860 ms
    4 12.127.79.149 22.138 ms 20.282 ms 23.729 ms
    5 12.123.44.61 24.699 ms 17.386 ms 17.875 ms
    6 12.122.12.161 25.581 ms 16.673 ms 15.377 ms
    7 12.123.44.177 17.178 ms 19.441 ms 14.116 ms
    8 192.205.32.22 16.987 ms 14.895 ms 13.999 ms
    9 209.247.9.45 15.892 ms 16.924 ms 17.567 ms
    10 64.159.1.130 34.655 ms 36.787 ms 40.362 ms
    11 64.159.2.100 33.838 ms 34.904 ms 33.358 ms
    12 209.247.202.218 35.107 ms 33.097 ms 32.502 ms
    13 216.239.47.194 53.416 ms 33.069 ms 34.060 ms
    14 216.239.49.2 35.852 ms 34.033 ms 35.668 ms
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    [[email protected] etc]# ping -c 3 216.239.57.99
    PING 216.239.57.99 (216.239.57.99) 56(84) bytes of data.
    64 bytes from 216.239.57.99: icmp_seq=1 ttl=241 time=31.3 ms
    64 bytes from 216.239.57.99: icmp_seq=2 ttl=241 time=32.6 ms
    64 bytes from 216.239.57.99: icmp_seq=3 ttl=241 time=32.4 ms

    --- 216.239.57.99 ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2000ms
    rtt min/avg/max/mdev = 31.372/32.170/32.656/0.568 ms

    [[email protected] etc]# traceroute -n 216.239.57.99
    traceroute to 216.239.57.99 (216.239.57.99), 30 hops max, 38 byte packets
    1 10.210.32.1 8.841 ms 28.184 ms 9.585 ms
    2 172.29.32.161 8.881 ms 26.570 ms 9.493 ms
    3 172.29.32.2 27.011 ms 16.571 ms 18.500 ms
    4 12.127.79.149 23.765 ms 17.265 ms 14.536 ms
    5 12.123.44.61 18.044 ms 14.033 ms 16.793 ms
    6 12.122.12.161 25.002 ms 15.116 ms 16.837 ms
    7 12.123.44.177 22.523 ms 19.084 ms 16.937 ms
    8 192.205.32.22 24.194 ms 38.801 ms 15.378 ms
    9 209.247.9.45 26.655 ms 21.459 ms 15.309 ms
    10 64.159.1.130 33.247 ms 32.619 ms 34.207 ms
    11 64.159.2.100 32.824 ms 31.545 ms 34.484 ms
    12 209.247.202.218 31.936 ms 32.297 ms 34.237 ms
    13 216.239.47.194 34.646 ms 33.709 ms 32.553 ms
    14 216.239.49.2 35.775 ms 35.140 ms 33.441 ms
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    This asterisks in lines 15 to 30 on both traceroutes took an inordinately
    long time to print. Any significance?
    Did not know if coogle.com was a typo but I included one dig to it.
    Evidently it is a website. :)
    Already installed
    Able to access google with lynx
    No change with Mozilla.

    I have been trying to resolve this for months. Did read your above
    suggestions previously and tried them but no go.

    Thanks alot for your help. Any further recourse?

    Steve Z.
     
    Stephen Zilliox, Apr 25, 2004
    #17
  18. Do you have any clues regarding the first 3 IP-addresses in this
    traceroute, (your LAN?)?

    In another posting, you mentioned the DHCP-server address: 192.168.4.27.
    Is this pingable? How about traceroute? Any clues regarding this
    IP-address?

    Can you please make the same traceroute, without the n-option...? The
    private IP-addresses puzzles me a lot... The same traceroute from Windoze
    would be appreciated...

    Can you please make a traceroute to each of the 4 first IP-addresses
    listed in your traceroute?

    Can you please make a traceroute to 1 or each of the nameserves listed
    in resolv.conf..?

    The output from MTR, http://www.bitwizard.nl/mtr/ can give additional
    information:

    mtr -rc 5 <google/gw/nameserver>
    mtr -rnc 5 <google/gw/nameserver>

    I hope our demand for information doesn't give you to much trouble... :)

    --
    mvh/regards
    Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti
     
    Joachim =?iso-8859-1?b?TcOmbGFuZCI=?=, Apr 25, 2004
    #18
  19. Stephen Zilliox

    James Knott Guest

    Some IPs use the private address ranges within their network. There's
    nothing wrong with that, as they work the same as any other address range.
    The only thing is that they must not be used off their network.

    --

    Fundamentalism is fundamentally wrong.

    To reply to this message, replace everything to the left of "@" with
    james.knott.
     
    James Knott, Apr 25, 2004
    #19
  20. Your'e right, but compared to the public IP-address of the default GW, the
    default GW not showing up in the trace and strange browsing troubles, this
    makes me wonder. This is not necessarily an indication of the problems,
    but something is definitely wrong with his setup, or his ISP's setup and
    I'm trying to figure out what...

    The whole case is undoubtedly very simple, once we have the answer. IMHO;
    all we now have are some answers, a lot of questions, and a few loose
    ends.

    --
    mvh/regards
    Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti
     
    Joachim =?iso-8859-1?b?TcOmbGFuZCI=?=, Apr 25, 2004
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.