Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2403 > unrolled thread
| Started by | billy <billy@is.invalid> |
|---|---|
| First post | 2013-10-08 03:32 +0000 |
| Last post | 2013-10-13 02:04 +0200 |
| Articles | 7 on this page of 127 — 22 participants |
Back to article view | Back to comp.os.linux.networking
Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-08 03:32 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "Gary R. Schmidt" <grschmidt@acm.org> - 2013-10-08 15:37 +1100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 14:26 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Thomas Keusch <fwd+usenet-spam2013q4-1381444031@spam2013q4.bsd-solutions-duesseldorf.de> - 2013-10-10 22:32 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out David Hough <noone$$@llondel.org> - 2013-10-08 07:30 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-08 19:32 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2013-10-08 23:16 +0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 17:39 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-09 11:28 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 18:52 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2013-10-09 22:47 +0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 20:50 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 21:30 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 01:05 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 01:09 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 19:51 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 20:42 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out ~BD~ <~BD~@nomail.afraid.org> - 2013-10-09 22:09 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 01:07 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out ~BD~ <~BD~@nomail.afraid.org> - 2013-10-10 07:41 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 21:36 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-09 15:51 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 00:15 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:19 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:33 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 10:54 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 11:09 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "ps56k" <pschuman_no5pam_m3@interserv.com> - 2013-10-10 16:34 -0500
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 22:40 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "ps56k" <pschuman_no5pam_m3@interserv.com> - 2013-10-10 18:27 -0500
Re: Frustrated that I don't UNDERSTAND why my network times out Thad Floryan <thad@thadlabs.com> - 2013-10-10 16:49 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 00:40 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Thomas Keusch <fwd+usenet-spam2013q4-1381456101@spam2013q4.bsd-solutions-duesseldorf.de> - 2013-10-11 01:50 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 03:24 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out dyrmak <dyrmak@orange.fr.invalid> - 2013-10-11 08:50 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:26 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-11 16:03 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 20:19 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-11 20:38 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2013-10-11 21:34 +0300
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-11 00:00 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 11:18 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2013-10-09 15:16 +0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 17:41 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-09 19:22 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 21:18 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Rick Jones <rick.jones2@hp.com> - 2013-10-09 20:44 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 21:46 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:39 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Rick Jones <rick.jones2@hp.com> - 2013-10-10 01:30 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 01:32 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2013-10-09 22:25 -0400
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 03:48 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 05:10 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out ein <ein@no.spam> - 2013-10-10 13:24 +0200
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-10 10:31 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 17:37 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-11 00:01 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 20:21 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 21:04 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 01:18 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-11 00:03 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 00:57 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 01:07 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Richard Kettlewell <rjk@greenend.org.uk> - 2013-10-11 08:56 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:47 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:58 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Rick Jones <rick.jones2@hp.com> - 2013-10-10 01:24 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Bit Twister <BitTwister@mouse-potato.com> - 2013-10-09 12:23 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Chris Davies <chris-usenet@roaima.co.uk> - 2013-10-09 19:27 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 21:21 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 21:47 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 10:43 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 10:51 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out nemesis <nemesis@home.it> - 2013-10-09 08:14 -0300
Re: Frustrated that I don't UNDERSTAND why my network times out "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> - 2013-10-09 12:24 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out nemesis <nemesis@home.it> - 2013-10-09 08:42 -0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 13:57 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> - 2013-10-09 15:09 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 11:27 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out nemesis <nemesis@home.it> - 2013-10-09 08:58 -0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 18:44 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 19:58 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 21:23 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 21:38 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-09 16:14 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:30 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-09 18:02 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out Rick Jones <rick.jones2@hp.com> - 2013-10-10 01:37 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-10 03:17 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 20:03 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 20:06 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-09 21:27 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 22:15 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-10 00:35 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> - 2013-10-10 09:15 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 01:40 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out nemesis <nemesis@home.it> - 2013-10-10 23:03 -0300
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:43 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out ~BD~ <~BD~@nomail.afraid.org> - 2013-10-11 16:11 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-11 04:11 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 04:19 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 04:25 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-11 04:45 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out ein <ein@no.spam> - 2013-10-11 08:06 +0200
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:32 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:41 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:48 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Richard Kettlewell <rjk@greenend.org.uk> - 2013-10-11 09:00 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:30 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out Rick Jones <rick.jones2@hp.com> - 2013-10-14 19:20 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> - 2013-10-11 10:17 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out billy <billy@is.invalid> - 2013-10-11 14:23 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> - 2013-10-11 22:46 +0100
Re: Frustrated that I don't UNDERSTAND why my network times out Scott Hemphill <hemphill@hemphills.net> - 2013-10-14 16:47 -0400
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-09 16:17 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "ps56k" <pschuman_no5pam_m3@interserv.com> - 2013-10-10 16:41 -0500
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-10 15:16 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-10 15:18 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out "ps56k" <pschuman_no5pam_m3@interserv.com> - 2013-10-13 14:34 -0500
Re: Frustrated that I don't UNDERSTAND why my network times out Mike Easter <MikeE@ster.invalid> - 2013-10-13 14:27 -0700
Re: Frustrated that I don't UNDERSTAND why my network times out "ps56k" <pschuman_no5pam_m3@interserv.com> - 2013-10-17 14:58 -0500
Re: Frustrated that I don't UNDERSTAND why my network times out "petrus bitbyter" <petrus.bitbyter@hotmail.com> - 2013-10-11 22:17 +0200
Re: Frustrated that I don't UNDERSTAND why my network times out "petrus bitbyter" <petrus.bitbyter@hotmail.com> - 2013-10-11 22:42 +0200
Re: Frustrated that I don't UNDERSTAND why my network times out unruh <unruh@invalid.ca> - 2013-10-11 21:16 +0000
Re: Frustrated that I don't UNDERSTAND why my network times out "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2013-10-11 18:15 -0400
Re: Frustrated that I don't UNDERSTAND why my network times out "petrus bitbyter" <petrus.bitbyter@hotmail.com> - 2013-10-13 02:04 +0200
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2013-10-13 14:27 -0700 |
| Message-ID | <bc0hheFn2mtU1@mid.individual.net> |
| In reply to | #2528 |
ps56k wrote: > weird - yup - > it times out from my network - and other "online testing sites" - > so... ???? > > Ping - centos.org - 85.12.30.227 --> Amsterdam location That is the correct IP. > Ping - www.centos.org - 72.232.194.162 ---> ???? That is not the correct IP resolution according to google's DNS. That is, www.centos.org resolves to 85.12.30.227 but 85.12.30.227 does not rDNS to www.centos.org However, 72.232.194.162 rDNS to www.centos.org which does not resolve to 72.232.194.162 > their TCP/IP world seems messed up somewhere within their DNS records - The DNSreport on centos.org says the MX, SOA, WWW, are all OK but the Parent nameservice fails on one dns report but not another. Parent Failed Parent nameservers centos.org Your NS records at the parent server are: Failed Nameservers for domain in DNS centos.org Your NS records at your nameservers are: However, my dig worked OK showing ns1, ns3, & ns4.centos.org and their IPs and all 3 nameservers produced the MXes etc. The report at mxtoolbox said the ns at the parent was OK, but then the information said it was not. I don't understand this inconsistency in the parent DNS status for centos.org. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | "ps56k" <pschuman_no5pam_m3@interserv.com> |
|---|---|
| Date | 2013-10-17 14:58 -0500 |
| Message-ID | <l3pfhg$9m3$1@dont-email.me> |
| In reply to | #2529 |
"Mike Easter" <MikeE@ster.invalid> wrote in message news:bc0hheFn2mtU1@mid.individual.net... > ps56k wrote: >> weird - yup - >> it times out from my network - and other "online testing sites" - >> so... ???? >> >> Ping - centos.org - 85.12.30.227 --> Amsterdam location > > That is the correct IP. > >> Ping - www.centos.org - 72.232.194.162 ---> ???? > > That is not the correct IP resolution according to google's DNS. > > That is, www.centos.org resolves to 85.12.30.227 but 85.12.30.227 does not > rDNS to www.centos.org > > However, 72.232.194.162 rDNS to www.centos.org which does not resolve to > 72.232.194.162 > >> their TCP/IP world seems messed up somewhere within their DNS records - > > The DNSreport on centos.org says the MX, SOA, WWW, are all OK but the > Parent nameservice fails on one dns report but not another. > > Parent Failed Parent nameservers centos.org Your NS records at the parent > server are: > > Failed Nameservers for domain in DNS centos.org Your NS records at your > nameservers are: > > However, my dig worked OK showing ns1, ns3, & ns4.centos.org and their IPs > and all 3 nameservers produced the MXes etc. > > The report at mxtoolbox said the ns at the parent was OK, but then the > information said it was not. I don't understand this inconsistency in the > parent DNS status for centos.org. > YEAH - this is one weird DNS situation - I'd like to find out what eventually turns out to be the problem with the DNS, but this discussion is all over the map with various tangents regarding the orig problem.
[toc] | [prev] | [next] | [standalone]
| From | "petrus bitbyter" <petrus.bitbyter@hotmail.com> |
|---|---|
| Date | 2013-10-11 22:17 +0200 |
| Message-ID | <52585c88$0$1672$e4fe514c@dreader35.news.xs4all.nl> |
| In reply to | #2403 |
"billy" <billy@is.invalid> schreef in bericht news:l2vumu$4bj$1@speranza.aioe.org... > Why can't I connect (via port 80 or any port) to a certain web site? > > For more than a year I've had the same problem, and, it's NOT > the way I'm running traceroute! (e.g., it's not ICMP vs TCP, etc.). > It's also not that the server I'm pinging is down, or slow. > > There's something wrong with "my" home networking setup. > But what? > > I just want to UNDERSTAND the problem. That's it. > It makes NO sense what I've been seeing over the past year. > > Basically, for months at a time, I can't connect to centos.org > and, for months at a time, I can connect to the web site. > > When I can't connect, traceroute (ICMP or TCP) fails to connect; > when I can connect, traceroute also connects. > > So, it isn't HOW I'm running traceroute, as traceroute is telling > me exactly what Firefox is telling me. > > This happens for months at a time, and has happened about five > times in the past two years. > > I change NOTHING (not my router firewall, not my computer firewall, > not my networking setup, etc.) in the interim. > > When this happens, I switch to TOR, and I can EASILY connect to > centos.org via the proxy Firefox - so there's nothing wrong with > my firewall or with my home broadband router (as far as I can tell). > > When I can't connect, I ask my NEIGHBORS who "can" get to centos.org > to show me their traceroute, and it looks the same as mine except > for the fact that their times are slightly faster and they get > past that last hop - whereas mine dies at the penultimate hop. > > So, THAT would implicate something on "my" side (but what?). > > I switch to Knoppix 7, and I get the same result. > I go to a Windows PC, and I get the same result. > So, it's NOT the PC! > > If I knew how to get around my router, I would, but it has > all the setup for the ISP (it's a WISP, not cable or DSL). > > My question? > > How can I debug WHY (for months at a time), I can't get to a web site? > > Here's a traceroute run just now: > knoppix@Microknoppix:~$ traceroute www.centos.org > traceroute to www.centos.org (72.232.194.162), 30 hops max, 60 byte > packets > 1 192.168.1.1 (192.168.1.1) 2.835 ms 2.809 ms 20.293 ms > 2 REDACTED_WISP.net (xxx.xxx.xxx.xxx) 20.280 ms 20.265 ms 20.248 > ms > 3 10.50.0.1 (10.50.0.1) 29.973 ms 29.959 ms 29.943 ms > 4 10.25.0.1 (10.25.0.1) 39.067 ms 42.759 ms 42.745 ms > 5 10.20.0.1 (10.20.0.1) 82.295 ms 82.280 ms 82.265 ms > 6 10.0.0.1 (10.0.0.1) 122.956 ms 159.675 ms 159.654 ms > 7 69.36.226.193 (69.36.226.193) 198.537 ms 201.445 ms 201.433 ms > 8 vl2.core1.scl.layer42.net (69.36.225.129) 201.423 ms 201.412 ms > 201.388 ms > 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 201.377 ms 201.361 > ms 201.346 ms > 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 239.215 ms 239.185 ms > 239.171 ms > 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 239.137 ms 239.122 > ms 239.061 ms > 12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 239.030 ms 123.544 ms > 178.276 ms > 13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 178.261 ms 178.264 ms > 178.231 ms > 14 border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.234 ms > border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 178.187 ms > border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.199 ms > 15 layered-11.border1.dal004.pnap.net (63.251.44.74) 178.171 ms > 178.139 ms 178.123 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > I know, from two years of experiencing this, that the hop after the > last hop showing resuls "is" Centos.org! So, when it works, it gets to > the last hop; but when it dies, it always dies at just before the last > hop. But why? > > Can you help me UNDERSTAND why/how this situation can be happening? > Note: All other web sites work just fine. > > NOTE: I already know that YOU will be able to access this same site > with much lower ping times (you're not on a WISP either) - but that > doesn't help ME figure out what the problem is. > > Is there freeware extant to help me UNDERSTAND why this happens to me?
[toc] | [prev] | [next] | [standalone]
| From | "petrus bitbyter" <petrus.bitbyter@hotmail.com> |
|---|---|
| Date | 2013-10-11 22:42 +0200 |
| Message-ID | <52586264$0$3212$e4fe514c@dreader36.news.xs4all.nl> |
| In reply to | #2403 |
"billy" <billy@is.invalid> schreef in bericht news:l2vumu$4bj$1@speranza.aioe.org... > Why can't I connect (via port 80 or any port) to a certain web site? > > For more than a year I've had the same problem, and, it's NOT > the way I'm running traceroute! (e.g., it's not ICMP vs TCP, etc.). > It's also not that the server I'm pinging is down, or slow. > > There's something wrong with "my" home networking setup. > But what? > > I just want to UNDERSTAND the problem. That's it. > It makes NO sense what I've been seeing over the past year. > > Basically, for months at a time, I can't connect to centos.org > and, for months at a time, I can connect to the web site. > > When I can't connect, traceroute (ICMP or TCP) fails to connect; > when I can connect, traceroute also connects. > > So, it isn't HOW I'm running traceroute, as traceroute is telling > me exactly what Firefox is telling me. > > This happens for months at a time, and has happened about five > times in the past two years. > > I change NOTHING (not my router firewall, not my computer firewall, > not my networking setup, etc.) in the interim. > > When this happens, I switch to TOR, and I can EASILY connect to > centos.org via the proxy Firefox - so there's nothing wrong with > my firewall or with my home broadband router (as far as I can tell). > > When I can't connect, I ask my NEIGHBORS who "can" get to centos.org > to show me their traceroute, and it looks the same as mine except > for the fact that their times are slightly faster and they get > past that last hop - whereas mine dies at the penultimate hop. > > So, THAT would implicate something on "my" side (but what?). > > I switch to Knoppix 7, and I get the same result. > I go to a Windows PC, and I get the same result. > So, it's NOT the PC! > > If I knew how to get around my router, I would, but it has > all the setup for the ISP (it's a WISP, not cable or DSL). > > My question? > > How can I debug WHY (for months at a time), I can't get to a web site? > > Here's a traceroute run just now: > knoppix@Microknoppix:~$ traceroute www.centos.org > traceroute to www.centos.org (72.232.194.162), 30 hops max, 60 byte > packets > 1 192.168.1.1 (192.168.1.1) 2.835 ms 2.809 ms 20.293 ms > 2 REDACTED_WISP.net (xxx.xxx.xxx.xxx) 20.280 ms 20.265 ms 20.248 > ms > 3 10.50.0.1 (10.50.0.1) 29.973 ms 29.959 ms 29.943 ms > 4 10.25.0.1 (10.25.0.1) 39.067 ms 42.759 ms 42.745 ms > 5 10.20.0.1 (10.20.0.1) 82.295 ms 82.280 ms 82.265 ms > 6 10.0.0.1 (10.0.0.1) 122.956 ms 159.675 ms 159.654 ms > 7 69.36.226.193 (69.36.226.193) 198.537 ms 201.445 ms 201.433 ms > 8 vl2.core1.scl.layer42.net (69.36.225.129) 201.423 ms 201.412 ms > 201.388 ms > 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 201.377 ms 201.361 > ms 201.346 ms > 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 239.215 ms 239.185 ms > 239.171 ms > 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 239.137 ms 239.122 > ms 239.061 ms > 12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 239.030 ms 123.544 ms > 178.276 ms > 13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 178.261 ms 178.264 ms > 178.231 ms > 14 border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.234 ms > border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 178.187 ms > border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.199 ms > 15 layered-11.border1.dal004.pnap.net (63.251.44.74) 178.171 ms > 178.139 ms 178.123 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > I know, from two years of experiencing this, that the hop after the > last hop showing resuls "is" Centos.org! So, when it works, it gets to > the last hop; but when it dies, it always dies at just before the last > hop. But why? > > Can you help me UNDERSTAND why/how this situation can be happening? > Note: All other web sites work just fine. > > NOTE: I already know that YOU will be able to access this same site > with much lower ping times (you're not on a WISP either) - but that > doesn't help ME figure out what the problem is. > > Is there freeware extant to help me UNDERSTAND why this happens to me? Reading all I can of this thread (maybe not all because off my newsserver is not 100% reliable) I followed the diving into the routing and the protocol. AFAIS one cause has been overlooked so far: An intermittend hardware error. To me all results so far point in that direction. Suspect is all hardware between your computer and WISP. Shortest way to find out is exchanging all parts of it one at a time, including cables and power supplies. The logic behind it looks like obvious to me. All that equipment is similar to that of your neighbours but the latter has no problem. Your computer has no problem when using it too. So your equipment itself or the place or way it has been installed may cause that peculiar problem. petrus bitbyter
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-11 21:16 +0000 |
| Message-ID | <fVZ5u.50812$K71.48483@fx21.iad> |
| In reply to | #2522 |
On 2013-10-11, petrus bitbyter <petrus.bitbyter@hotmail.com> wrote: > > "billy" <billy@is.invalid> schreef in bericht > news:l2vumu$4bj$1@speranza.aioe.org... >> Why can't I connect (via port 80 or any port) to a certain web site? >> >> For more than a year I've had the same problem, and, it's NOT >> the way I'm running traceroute! (e.g., it's not ICMP vs TCP, etc.). >> It's also not that the server I'm pinging is down, or slow. >> >> There's something wrong with "my" home networking setup. >> But what? >> >> I just want to UNDERSTAND the problem. That's it. >> It makes NO sense what I've been seeing over the past year. >> >> Basically, for months at a time, I can't connect to centos.org >> and, for months at a time, I can connect to the web site. >> >> When I can't connect, traceroute (ICMP or TCP) fails to connect; >> when I can connect, traceroute also connects. >> >> So, it isn't HOW I'm running traceroute, as traceroute is telling >> me exactly what Firefox is telling me. >> >> This happens for months at a time, and has happened about five >> times in the past two years. >> >> I change NOTHING (not my router firewall, not my computer firewall, >> not my networking setup, etc.) in the interim. >> >> When this happens, I switch to TOR, and I can EASILY connect to >> centos.org via the proxy Firefox - so there's nothing wrong with >> my firewall or with my home broadband router (as far as I can tell). >> >> When I can't connect, I ask my NEIGHBORS who "can" get to centos.org >> to show me their traceroute, and it looks the same as mine except >> for the fact that their times are slightly faster and they get >> past that last hop - whereas mine dies at the penultimate hop. >> >> So, THAT would implicate something on "my" side (but what?). >> >> I switch to Knoppix 7, and I get the same result. >> I go to a Windows PC, and I get the same result. >> So, it's NOT the PC! >> >> If I knew how to get around my router, I would, but it has >> all the setup for the ISP (it's a WISP, not cable or DSL). >> >> My question? >> >> How can I debug WHY (for months at a time), I can't get to a web site? >> >> Here's a traceroute run just now: >> knoppix@Microknoppix:~$ traceroute www.centos.org >> traceroute to www.centos.org (72.232.194.162), 30 hops max, 60 byte >> packets >> 1 192.168.1.1 (192.168.1.1) 2.835 ms 2.809 ms 20.293 ms >> 2 REDACTED_WISP.net (xxx.xxx.xxx.xxx) 20.280 ms 20.265 ms 20.248 >> ms >> 3 10.50.0.1 (10.50.0.1) 29.973 ms 29.959 ms 29.943 ms >> 4 10.25.0.1 (10.25.0.1) 39.067 ms 42.759 ms 42.745 ms >> 5 10.20.0.1 (10.20.0.1) 82.295 ms 82.280 ms 82.265 ms >> 6 10.0.0.1 (10.0.0.1) 122.956 ms 159.675 ms 159.654 ms >> 7 69.36.226.193 (69.36.226.193) 198.537 ms 201.445 ms 201.433 ms >> 8 vl2.core1.scl.layer42.net (69.36.225.129) 201.423 ms 201.412 ms >> 201.388 ms >> 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 201.377 ms 201.361 >> ms 201.346 ms >> 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 239.215 ms 239.185 ms >> 239.171 ms >> 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 239.137 ms 239.122 >> ms 239.061 ms >> 12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 239.030 ms 123.544 ms >> 178.276 ms >> 13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 178.261 ms 178.264 ms >> 178.231 ms >> 14 border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.234 ms >> border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 178.187 ms >> border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.199 ms >> 15 layered-11.border1.dal004.pnap.net (63.251.44.74) 178.171 ms >> 178.139 ms 178.123 ms >> 16 * * * >> 17 * * * >> 18 * * * >> 19 * * * >> 20 * * * >> 21 * * * >> 22 * * * >> 23 * * * >> 24 * * * >> 25 * * * >> 26 * * * >> 27 * * * >> 28 * * * >> 29 * * * >> 30 * * * >> >> I know, from two years of experiencing this, that the hop after the >> last hop showing resuls "is" Centos.org! So, when it works, it gets to >> the last hop; but when it dies, it always dies at just before the last >> hop. But why? >> >> Can you help me UNDERSTAND why/how this situation can be happening? >> Note: All other web sites work just fine. >> >> NOTE: I already know that YOU will be able to access this same site >> with much lower ping times (you're not on a WISP either) - but that >> doesn't help ME figure out what the problem is. >> >> Is there freeware extant to help me UNDERSTAND why this happens to me? > > Reading all I can of this thread (maybe not all because off my newsserver is > not 100% reliable) I followed the diving into the routing and the protocol. > AFAIS one cause has been overlooked so far: An intermittend hardware error. > To me all results so far point in that direction. Suspect is all hardware > between your computer and WISP. Shortest way to find out is exchanging all > parts of it one at a time, including cables and power supplies. The logic > behind it looks like obvious to me. All that equipment is similar to that of > your neighbours but the latter has no problem. Your computer has no problem > when using it too. So your equipment itself or the place or way it has been > installed may cause that peculiar problem. > It is hard for me to see how a hardware error could cause troubles with ONLY centos.org. Remember that he says that he can browse almost all other web sites, even during the months that he cannot browse centos.org. It is really really hard to imagine some hardware error that would be that selective in its application, and furthermore one that allowed the packets to reach the penultimate link on a long chain and then fail on that final link. He has certainly been aware of your possibility, but has no idea how that could explain the symptoms. Perhaps you could explain how, even in the wildest of scenarios, this could explain his symptoms. And if it does, how he could figure our WHAT is wrong.
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2013-10-11 18:15 -0400 |
| Message-ID | <op.w4s9grbya3w0dxdave@hodgins.homeip.net> |
| In reply to | #2523 |
On Fri, 11 Oct 2013 17:16:59 -0400, unruh <unruh@invalid.ca> wrote: > It is hard for me to see how a hardware error could cause troubles with > ONLY centos.org. Remember that he says that he can browse almost all > other web sites, even during the months that he cannot browse > centos.org. It is really really hard to imagine some hardware error that > would be that selective in its application, and furthermore one that > allowed the packets to reach the penultimate link on a long chain and > then fail on that final link. This reminds me of a problem I encountered with a system using a RTL8111/8168B PCI Express Gigabit Ethernet controller. Every once in a while, it would stop connecting to some sites, while still working for other sites, and I could still use ssh to access the system. My nephew suggested rebooting the system. I explained, this was a linux system, and wouldn't make any difference. After arguing a bit, I rebooted it to show him, it wouldn't matter. To my surprise, it did clear the problem. That system is using a 50ft cable to connect to the router. My current guess, is that some packet is getting mangled, some of the time, and when it does, the only way to clear the problem, is to reset the pci device, by rebooting the system. Restarting the network is not enough. The system has to actually be rebooted. I suggested changing the wiring, and moving the router so a shorter cable could be used, but the owner has chosen to just reboot the system, whenever this happens, typically about every other week. This has been going on for a couple of years now, with multiple kernel updates during that time, and no change in behaviour. So there are cases where a hardware problem will affect some sites, but not others. Without disassembling the firmware, I have no idea what the nic is doing, so I can only confirm the observed results. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.)
[toc] | [prev] | [next] | [standalone]
| From | "petrus bitbyter" <petrus.bitbyter@hotmail.com> |
|---|---|
| Date | 2013-10-13 02:04 +0200 |
| Message-ID | <5259e376$0$3170$e4fe514c@dreader36.news.xs4all.nl> |
| In reply to | #2523 |
"unruh" <unruh@invalid.ca> schreef in bericht news:fVZ5u.50812$K71.48483@fx21.iad... > On 2013-10-11, petrus bitbyter <petrus.bitbyter@hotmail.com> wrote: >> >> "billy" <billy@is.invalid> schreef in bericht >> news:l2vumu$4bj$1@speranza.aioe.org... >>> Why can't I connect (via port 80 or any port) to a certain web site? >>> >>> For more than a year I've had the same problem, and, it's NOT >>> the way I'm running traceroute! (e.g., it's not ICMP vs TCP, etc.). >>> It's also not that the server I'm pinging is down, or slow. >>> >>> There's something wrong with "my" home networking setup. >>> But what? >>> >>> I just want to UNDERSTAND the problem. That's it. >>> It makes NO sense what I've been seeing over the past year. >>> >>> Basically, for months at a time, I can't connect to centos.org >>> and, for months at a time, I can connect to the web site. >>> >>> When I can't connect, traceroute (ICMP or TCP) fails to connect; >>> when I can connect, traceroute also connects. >>> >>> So, it isn't HOW I'm running traceroute, as traceroute is telling >>> me exactly what Firefox is telling me. >>> >>> This happens for months at a time, and has happened about five >>> times in the past two years. >>> >>> I change NOTHING (not my router firewall, not my computer firewall, >>> not my networking setup, etc.) in the interim. >>> >>> When this happens, I switch to TOR, and I can EASILY connect to >>> centos.org via the proxy Firefox - so there's nothing wrong with >>> my firewall or with my home broadband router (as far as I can tell). >>> >>> When I can't connect, I ask my NEIGHBORS who "can" get to centos.org >>> to show me their traceroute, and it looks the same as mine except >>> for the fact that their times are slightly faster and they get >>> past that last hop - whereas mine dies at the penultimate hop. >>> >>> So, THAT would implicate something on "my" side (but what?). >>> >>> I switch to Knoppix 7, and I get the same result. >>> I go to a Windows PC, and I get the same result. >>> So, it's NOT the PC! >>> >>> If I knew how to get around my router, I would, but it has >>> all the setup for the ISP (it's a WISP, not cable or DSL). >>> >>> My question? >>> >>> How can I debug WHY (for months at a time), I can't get to a web site? >>> >>> Here's a traceroute run just now: >>> knoppix@Microknoppix:~$ traceroute www.centos.org >>> traceroute to www.centos.org (72.232.194.162), 30 hops max, 60 byte >>> packets >>> 1 192.168.1.1 (192.168.1.1) 2.835 ms 2.809 ms 20.293 ms >>> 2 REDACTED_WISP.net (xxx.xxx.xxx.xxx) 20.280 ms 20.265 ms 20.248 >>> ms >>> 3 10.50.0.1 (10.50.0.1) 29.973 ms 29.959 ms 29.943 ms >>> 4 10.25.0.1 (10.25.0.1) 39.067 ms 42.759 ms 42.745 ms >>> 5 10.20.0.1 (10.20.0.1) 82.295 ms 82.280 ms 82.265 ms >>> 6 10.0.0.1 (10.0.0.1) 122.956 ms 159.675 ms 159.654 ms >>> 7 69.36.226.193 (69.36.226.193) 198.537 ms 201.445 ms 201.433 ms >>> 8 vl2.core1.scl.layer42.net (69.36.225.129) 201.423 ms 201.412 ms >>> 201.388 ms >>> 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 201.377 ms 201.361 >>> ms 201.346 ms >>> 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 239.215 ms 239.185 ms >>> 239.171 ms >>> 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 239.137 ms 239.122 >>> ms 239.061 ms >>> 12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 239.030 ms 123.544 ms >>> 178.276 ms >>> 13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 178.261 ms 178.264 ms >>> 178.231 ms >>> 14 border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.234 ms >>> border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 178.187 ms >>> border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 178.199 ms >>> 15 layered-11.border1.dal004.pnap.net (63.251.44.74) 178.171 ms >>> 178.139 ms 178.123 ms >>> 16 * * * >>> 17 * * * >>> 18 * * * >>> 19 * * * >>> 20 * * * >>> 21 * * * >>> 22 * * * >>> 23 * * * >>> 24 * * * >>> 25 * * * >>> 26 * * * >>> 27 * * * >>> 28 * * * >>> 29 * * * >>> 30 * * * >>> >>> I know, from two years of experiencing this, that the hop after the >>> last hop showing resuls "is" Centos.org! So, when it works, it gets to >>> the last hop; but when it dies, it always dies at just before the last >>> hop. But why? >>> >>> Can you help me UNDERSTAND why/how this situation can be happening? >>> Note: All other web sites work just fine. >>> >>> NOTE: I already know that YOU will be able to access this same site >>> with much lower ping times (you're not on a WISP either) - but that >>> doesn't help ME figure out what the problem is. >>> >>> Is there freeware extant to help me UNDERSTAND why this happens to me? >> >> Reading all I can of this thread (maybe not all because off my newsserver >> is >> not 100% reliable) I followed the diving into the routing and the >> protocol. >> AFAIS one cause has been overlooked so far: An intermittend hardware >> error. >> To me all results so far point in that direction. Suspect is all hardware >> between your computer and WISP. Shortest way to find out is exchanging >> all >> parts of it one at a time, including cables and power supplies. The logic >> behind it looks like obvious to me. All that equipment is similar to that >> of >> your neighbours but the latter has no problem. Your computer has no >> problem >> when using it too. So your equipment itself or the place or way it has >> been >> installed may cause that peculiar problem. >> > > It is hard for me to see how a hardware error could cause troubles with > ONLY centos.org. Remember that he says that he can browse almost all > other web sites, even during the months that he cannot browse > centos.org. It is really really hard to imagine some hardware error that > would be that selective in its application, and furthermore one that > allowed the packets to reach the penultimate link on a long chain and > then fail on that final link. > > He has certainly been aware of your possibility, but has no idea how > that could explain the symptoms. Perhaps you could explain how, even in > the wildest of scenarios, this could explain his symptoms. > And if it does, how he could figure our WHAT is wrong. > > Well, I agree. It's very hard see how it may happen. Nevertheless, the impossible never happens and hard to see is not impossible. In a situation like this I'd want to rule out the possibillity that the error is caused by my own equipment somehow. It's not only the pure hardware I think about. I consider the firmware a part of the hardware in this equipment. I have some experience maintaining computer equipment and I several times saw unexplainable errors disapear by exchanging parts or equipment that seem to have nothing to do with it. *If* the cause of the problem has been located in this part of the path, there's a question left that may be next to impossible to answer: How does it happen? As the OP mentioned that's the most frustrating part of the problem. petrus bitbyter
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | comp.os.linux.networking
csiph-web