+ Post New Thread
Results 1 to 4 of 4
*nix Thread, Ping timeouts in Technical; I'm having an issue when setting up a squid proxy but I don't think it's a Squid issue. I have ...
  1. #1
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54

    Ping timeouts

    I'm having an issue when setting up a squid proxy but I don't think it's a Squid issue. I have one 1Gb ethernet connection set with two IP addresses eth1 and eth1:1

    eth0 does exist but it's a 100Mbs and I couldn't get Debian to configure them both together by simply editing /etc/network/interfaces so I stuck with just the one.

    The problem occurs when trying to ping a router for internet access. I can ping it fine from my windows machine but the output I get from debian is


    login as: mjf
    mjf@10.97.29.1's password:
    Linux SCUTTER 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.

    Code:
    root@SCUTTER:/home/mjf# ping 192.168.1.254
    PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
    64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=1.35 ms
    64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=0.642 ms
    64 bytes from 192.168.1.254: icmp_req=58 ttl=64 time=0.627 ms
    64 bytes from 192.168.1.254: icmp_req=59 ttl=64 time=0.597 ms
    64 bytes from 192.168.1.254: icmp_req=60 ttl=64 time=0.609 ms
    64 bytes from 192.168.1.254: icmp_req=61 ttl=64 time=0.940 ms
    64 bytes from 192.168.1.254: icmp_req=62 ttl=64 time=0.612 ms
    64 bytes from 192.168.1.254: icmp_req=118 ttl=64 time=0.611 ms
    64 bytes from 192.168.1.254: icmp_req=119 ttl=64 time=0.621 ms
    64 bytes from 192.168.1.254: icmp_req=120 ttl=64 time=0.597 ms
    64 bytes from 192.168.1.254: icmp_req=121 ttl=64 time=0.618 ms
    64 bytes from 192.168.1.254: icmp_req=122 ttl=64 time=0.636 ms
    64 bytes from 192.168.1.254: icmp_req=123 ttl=64 time=0.609 ms
    ^C
    --- 192.168.1.254 ping statistics ---
    126 packets transmitted, 13 received, 89% packet loss, time 125002ms
    rtt min/avg/max/mdev = 0.597/0.698/1.357/0.209 ms
    root@SCUTTER:/home/mjf#
    As you can see I get a ridiculous number of packet dropout. I get the same when the network is configured with only 1 IP. What can possibly cause this when I can get no dropped packets at all from my pc to either the router or the debian server.

  2. #2

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,624
    Thank Post
    1,240
    Thanked 778 Times in 675 Posts
    Rep Power
    235
    Quote Originally Posted by cromertech View Post
    I'm having an issue when setting up a squid proxy but I don't think it's a Squid issue. I have one 1Gb ethernet connection set with two IP addresses eth1 and eth1:1 ... eth0 does exist but it's a 100Mbs and I couldn't get Debian to configure them both together by simply editing /etc/network/interfaces so I stuck with just the one.
    It would seem to make sense to have one IP address per network interface - you couldn't just clone the section in /etc/network/interfaces for eth1 and edit it for eth0?

    As you can see I get a ridiculous number of packet dropout.
    I seem to remember seeing the exact same effect somewhere - I think the problem turned out to simply be a duplicate IP address elsewhere on the network.

  3. Thanks to dhicks from:

    cromertech (8th April 2011)

  4. #3

    powdarrmonkey's Avatar
    Join Date
    Feb 2008
    Location
    Alcester, Warwickshire
    Posts
    4,859
    Thank Post
    412
    Thanked 777 Times in 650 Posts
    Rep Power
    182
    Quote Originally Posted by cromertech View Post
    I'm having an issue when setting up a squid proxy but I don't think it's a Squid issue. I have one 1Gb ethernet connection set with two IP addresses eth1 and eth1:1

    eth0 does exist but it's a 100Mbs and I couldn't get Debian to configure them both together by simply editing /etc/network/interfaces so I stuck with just the one.
    That seems horribly... broken. What did you put into /etc/network/interfaces?

    Quote Originally Posted by dhicks View Post
    I seem to remember seeing the exact same effect somewhere - I think the problem turned out to simply be a duplicate IP address elsewhere on the network.
    I've seen that too - put it onto an address that definitely doesn't already ping from another machine, for testing purposes.

  5. Thanks to powdarrmonkey from:

    cromertech (8th April 2011)

  6. #4
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54
    That seems to be it. No idea where the other IP address is but setting it to one that was definately not in use worked. Redid the etc/networking/interfaces too so now have both NICs working fine. Thanks

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 5
    Last Post: 8th December 2009, 03:30 PM
  2. [CLOSED] Bug/Error: Remove timeouts
    By matt40k in forum EduGeek.net Site Problems
    Replies: 13
    Last Post: 3rd July 2009, 09:53 AM
  3. [Ubuntu] Squid timeouts
    By localzuk in forum *nix
    Replies: 5
    Last Post: 21st May 2009, 10:50 AM
  4. PHP Timeouts
    By dan400007 in forum Windows Server 2008
    Replies: 0
    Last Post: 6th November 2008, 08:41 AM
  5. Screensaver password timeouts.
    By snakepottery in forum Windows
    Replies: 19
    Last Post: 12th May 2006, 10:44 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •