[SATLUG] 50/50 ppp connection

Todd W. Bucy todd at bucy-medrano.me
Tue Sep 4 12:24:56 CDT 2012


have you tried using mtr? it can help you determine if there is something
wrong upstream or in between.
On Sep 4, 2012 11:50 AM, "Craig" <sargonemail at gmail.com> wrote:

> Hey,
>
> Any thoughts on what might be causing the following weired
> internet issues. The connection is through ppp.  It doesn't
> doesn't matter what distro used (ubuntu, puppy, slax, suse,
> etc..); boot/run type live cd/dvd, usb, hard drive;
> hardware (modem card / usb modem / serial port modem)
> and ppp versions don't seem to matter either.
> This is independent of time of day, connection time length,
> machine uptime.
> The end result is every other packet sent is silently dropped.
> PPP-ing to someone elses house/box shows that they never receive
> 47% to 52% of the packets sent (and vise versa).
> No tcp/ip request to retransmit is issued for any of the dropped/lossed
> packets.
>
> In the ping example note icmp_req # being skipped.
> Ping time is resonable for ppp connection, icmp_req sequence
> skipping is not.
> The time between icmp_request= (odd_number) && icmp_requests
> = (odd_number + 1) is between 8 && 24 seconds.
> Icmp_requests may start even or start odd.
> Packet loss is always in a range between 47% && 52%
>
> Throw in slow dial-up times && other than an interesting
> research issue(s), dial-up is worthless with the above issue.
> Any hints/suggestions (other than switch to something other than
> dial-up)?
>
> Craig
>
> Ping example.
> machine:>$ ping www.google.com
> PING www.l.google.com (209.85.225.99) 56(84) bytes of data.
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=1 ttl=48
> time=232 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=3 ttl=48
> time=298 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=5 ttl=48
> time=252 ms
> 64 bytes from 209.85.225.99: icmp_req=7 ttl=48 time=212 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=9 ttl=48
> time=279 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=11 ttl=48
> time=243 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=13 ttl=48
> time=190 ms
> 64 bytes from 209.85.225.99: icmp_req=15 ttl=48 time=207 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=17 ttl=48
> time=232 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=19 ttl=48
> time=239 ms
> 64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=21 ttl=48
> time=246 ms
> ^C64 bytes from iy-in-f99.1e100.net (209.85.225.99): icmp_req=23
> ttl=48 time=292 ms
>
> --- www.l.google.com ping statistics ---
> 23 packets transmitted, 12 received, 47% packet loss, time 98043ms
> rtt min/avg/max/mdev = 190.731/244.018/298.424/31.700 ms
> --
> _______________________________________________
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
> Powered by Rackspace (www.rackspace.com)
>


More information about the SATLUG mailing list