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 | 20 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 5 of 7 — ← Prev page 1 2 3 4 [5] 6 7 Next page →
| From | nemesis <nemesis@home.it> |
|---|---|
| Date | 2013-10-09 08:58 -0300 |
| Message-ID | <1ndekkpbhgdeu$.137rkh4i05687.dlg@40tude.net> |
| In reply to | #2416 |
On Wed, 09 Oct 2013 11:27:09 +0000, billy wrote: > nemesis wrote: > >> Just boot from a freeware live CD and do it from there. >> If it traceroutes, it's your OS config. >> If not, something in your hardware/network. > > I'm all for a DIAGNOSTIC approach, since what I'm trying > to figure out is WHY the Internet fails me on just one > web site. > > I just tried it from Knoppix and it is the same result > (see below for the details). > > I also have tried it from other PC's on the network, > running Windows XP and Windows 7, and the same thing > occurs. > > I also run it via TOR on both Windows & Linux, and it > works fine. > > So, its clearly not the PC itself. > It's in the network - but WHERE? Check your wireless router settings also DSL settings. If it does not void your ISP contract, reset them (backup settings first) to default and reinstall the backdoors, I mean, reflash the firmware <paranoid times>. You have root on them, right ?
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-09 18:44 +0000 |
| Message-ID | <l34879$rst$1@speranza.aioe.org> |
| In reply to | #2418 |
On Wed, 09 Oct 2013 08:58:25 -0300, nemesis wrote: > Check your wireless router settings also DSL settings. If it does not void > your ISP contract, reset them (backup settings first) to default and > reinstall the backdoors, I mean, reflash the firmware <paranoid times>. > You have root on them, right ? I have the basic Netgear home broadband router, just like most of you do, and, yes, I have admin as I set it up years ago. Bear in mind that nothing changes on the router that I know of, when this problem comes and goes (for months). But, if there was a particular setting on that router that causes this, I'd love to know what it would be, as mine is set up mostly at default settings (wpa2-psk encryption). The one thing I have that most of you do not have is I have another radio and antenna on my roof since there are no wires or cables going into my house that contain Internet service (too far from the switch for DSL). For you, that 'thing' on my roof would be the "modem' and for all intents and purposes, it's the same setup you have, only I get to log into my receiver/transmitter and see what its settings are. Again, I set it up myself, so, I'm admin there also, and, again, nothing has changed in the two years time that it was set up. Meanwhile, the ability to connect by the web to centos.org has come and gone over time. So, while there *could* be a setting in either radio, I wouldn't know where to look since both are set up in the normal configuration for a standard WISP setup. PS: Where is Jeff Liebermann when you need him! :)
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-09 19:58 +0000 |
| Message-ID | <Zzi5u.45987$Bi.25820@fx17.iad> |
| In reply to | #2427 |
On 2013-10-09, billy <billy@is.invalid> wrote: > On Wed, 09 Oct 2013 08:58:25 -0300, nemesis wrote: > >> Check your wireless router settings also DSL settings. If it does not void >> your ISP contract, reset them (backup settings first) to default and >> reinstall the backdoors, I mean, reflash the firmware <paranoid times>. >> You have root on them, right ? > > I have the basic Netgear home broadband router, just like most of you do, > and, yes, I have admin as I set it up years ago. Bear in mind that nothing > changes on the router that I know of, when this problem comes and goes > (for months). But, if there was a particular setting on that router that > causes this, I'd love to know what it would be, as mine is set up mostly > at default settings (wpa2-psk encryption). You have connection to the web. That is not the problem since you say you can connect to other places. There is something about centos.org that is behaving weirdly. Now it could be something on your end, and it is almost certainly something on their end. They may have decided that you are a pain in the ass and blackballed you (I have no idea why), or it might be some sort of technical incompatibility between you and them. The only way to clear it up is to talk to them about it. If you cannot then I cannot see how you are going to figure it out. Note you could take your computer with you to some other place which connects to the web in some other way than your microwave link and see if that works there. > > The one thing I have that most of you do not have is I have another > radio and antenna on my roof since there are no wires or cables going > into my house that contain Internet service (too far from the switch > for DSL). > > For you, that 'thing' on my roof would be the "modem' and for all intents > and purposes, it's the same setup you have, only I get to log into my > receiver/transmitter and see what its settings are. > > Again, I set it up myself, so, I'm admin there also, and, again, nothing > has changed in the two years time that it was set up. > > Meanwhile, the ability to connect by the web to centos.org has come > and gone over time. > > So, while there *could* be a setting in either radio, I wouldn't know > where to look since both are set up in the normal configuration for > a standard WISP setup. > > PS: Where is Jeff Liebermann when you need him! :)
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-09 21:23 +0000 |
| Message-ID | <l34hfs$n2t$3@speranza.aioe.org> |
| In reply to | #2434 |
On Wed, 09 Oct 2013 19:58:49 +0000, unruh wrote: > There is something about centos.org > that is behaving weirdly. Now it could be something on your end, and it > is almost certainly something on their end. They may have decided that > you are a pain in the ass and blackballed you (I have no idea why), or > it might be some sort of technical incompatibility between you and them. I have long ago written to the Centos.org sysadmins, and they confirm there is nothing wrong with my IP address or login account. (The login works fine and no, there's no reason for them to have blackballed me.) If it were *that* simple, I wouldn't be asking for networking advice here ... :) This is not a simple one.
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-09 21:38 +0000 |
| Message-ID | <x1k5u.55839$D22.23985@fx27.iad> |
| In reply to | #2441 |
["Followup-To:" header set to comp.os.linux.networking.] On 2013-10-09, billy <billy@is.invalid> wrote: > On Wed, 09 Oct 2013 19:58:49 +0000, unruh wrote: > >> There is something about centos.org >> that is behaving weirdly. Now it could be something on your end, and it >> is almost certainly something on their end. They may have decided that >> you are a pain in the ass and blackballed you (I have no idea why), or >> it might be some sort of technical incompatibility between you and them. > > I have long ago written to the Centos.org sysadmins, and they confirm > there is nothing wrong with my IP address or login account. > > (The login works fine and no, there's no reason for them to have > blackballed me.) What do you mean "the login works fine"? You told us you could not connect in any way to that machine? Was that wrong? > > If it were *that* simple, I wouldn't be asking for networking > advice here ... :) It is really hard to give help if information supplied is missing or wrong. > > This is not a simple one. >
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2013-10-09 16:14 -0700 |
| Message-ID | <bbm6adFtf1vU1@mid.individual.net> |
| In reply to | #2441 |
billy wrote: > (The login works fine and no, there's no reason for them to have > blackballed me.) Login? Are you talking about login here? https://www.centos.org/user.php The difference between http and https protocols is the layering of http over the SSL/TLS protocol and the other difference is the use of port 443 instead of 80. Or perhaps you are talking about logging in to some other server - the centos forums are at https centos as well. The bugs.centos server login is at a different IP 83.149.86.133 -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-10 00:30 +0000 |
| Message-ID | <l34sph$g9b$1@speranza.aioe.org> |
| In reply to | #2450 |
Mike Easter wrote: > Login? Are you talking about login here? > https://www.centos.org/user.php All I do, on TOR, is type 'http://www.centos.org' or "centos.org", and it gives me a screen where I can enter in my login and password and it logs me in. On Firefox, I do the same, when everything is working. Then, for months at a time, I can't even connect to www.centos.org or to 'centos.org' - getting the standard "connection timed out" message. When I run a traceroute (any type of traceroute), the result is that the last hop before centos.org is the last hop that returns anything. The centos.org hop is asterisked out. There's absolutely nothing wrong with my login (I easily log in with TOR, and I have an old thread asking THEM what's going on, and they don't know either). So, I 'think' it's the ISP that they use. I remember having a similar problem with telephones not being able to call certain numbers, and, we found out it was a routing thing at the Ooma headquarters. Nobody on the planet could call these specific numbers, one of whom was a relative of mine so I knew that the number existed. Yet, nobody could call the number from VOIP. Same kind of idea seems to be here. Some router somewhere is very badly set up. The funny thing, is that I'm the only one with the problem. Worse yet, there are no debugging tools for when a router is dropping packets. That's the saddest part. I've been trying to solve this for two years running. Or, at least understand how it could possibly happen. > The bugs.centos server login is at a different IP 83.149.86.133 When I point my browser to http://83.149.86.133 I get the message: Forbidden You don't have permission to access / on this server. Apache/2.2.3 (CentOS) Server at 83.149.86.133 Port 80 # telnet 83.149.86.133 80 Trying 83.149.86.133... Connected to 83.149.86.133. Escape character is '^]'. HEAD HTTP/1.0 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> <hr> <address>Apache/2.2.3 (CentOS) Server at mirror.centos.org Port 80</address> </body></html> Connection closed by foreign host. # traceroute -M icmp 83.149.86.133 # traceroute -M icmp 83.149.86.133 traceroute to 83.149.86.133 (83.149.86.133), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 3.423 ms 3.405 ms 6.261 ms 2 MY_WISP_ADDRESS (xx.xx.xx.xx) 9.844 ms 9.842 ms 9.839 ms 3 10.50.0.1 (10.50.0.1) 15.284 ms 139.930 ms 139.937 ms 4 10.25.0.1 (10.25.0.1) 148.735 ms 148.734 ms 148.729 ms 5 10.20.0.1 (10.20.0.1) 164.306 ms 169.567 ms 169.564 ms 6 10.0.0.1 (10.0.0.1) 344.049 ms 70.997 ms 189.575 ms 7 69.36.226.193 (69.36.226.193) 189.531 ms 34.070 ms 136.902 ms 8 vl2.core2.scl.layer42.net (69.36.225.130) 139.000 ms 47.370 ms 133.156 ms 9 xe3-4.core1.mpt.layer42.net (69.36.239.110) 133.125 ms 35.300 ms 61.929 ms 10 any2ix.coresite.com (206.223.143.213) 73.838 ms 32.061 ms 94.368 ms 11 te5-2.msc2.wdc.leaseweb.net (217.20.125.40) 155.304 ms 99.444 ms 109.215 ms 12 * * * 13 31.31.32.5 (31.31.32.5) 260.392 ms 220.540 ms 229.781 ms 14 ten5-4.sbp-sr2.leaseweb.net (85.17.100.202) 229.737 ms 166.166 ms 243.165 ms 15 centos.yourname.nl (83.149.86.133) 239.189 ms 176.139 ms 194.943 ms So, I have absolutely no problem getting to this site. But, why would I have a problem getting to centos.org? Could it be that anything after 15 hops fails no matter what? To test, do you know of a site that would be more than 15 hops away from San Francisco, CA?
[toc] | [prev] | [next] | [standalone]
| From | Mike Easter <MikeE@ster.invalid> |
|---|---|
| Date | 2013-10-09 18:02 -0700 |
| Message-ID | <bbmcl7F3i6U1@mid.individual.net> |
| In reply to | #2453 |
billy wrote: > Mike Easter wrote: >> The bugs.centos server login is at a different IP 83.149.86.133 > > When I point my browser to http://83.149.86.133 I get the message: > Forbidden > You don't have permission to access / on this server. > Apache/2.2.3 (CentOS) Server at 83.149.86.133 Port 80 When you are trying to access a webserver, you should aim at its name, not its IP address for general purposes. One webserver might serve many names. The bugs front page is at: http://bugs.centos.org/main_page.php login is at http://bugs.centos.org/login_page.php?return=%2Fmain_page.php%3F > # telnet 83.149.86.133 80 My browser pointed at that IP gives me a forbidden page instead of the bugs.centos front door.. http://83.149.86.133 Forbidden You don't have permission to access / on this server. Apache/2.2.3 (CentOS) Server at 83.149.86.133 Port 80 Some webservers which serve only one front page will give you that page, but some will not serve you the page when addressed the IP way. That 'rule' does not apply to such as mailservers and news servers who don't care about the name vs the IP, except that the name is 'better' in the sense that the name might have more than one IP. > <h1>Bad Request</h1> > <p>Your browser sent a request that this server could not > understand.<br /> > # traceroute -M icmp 83.149.86.133 > 15 centos.yourname.nl (83.149.86.133) 239.189 ms > So, I have absolutely no problem getting to this site. > But, why would I have a problem getting to centos.org? bugs.centos.org is at a different place than centos.org but they have the same nameservice. > Could it be that anything after 15 hops fails no matter what? > To test, do you know of a site that would be more than 15 hops > away from San Francisco, CA? I don't think that is a useful theory. -- Mike Easter
[toc] | [prev] | [next] | [standalone]
| From | Rick Jones <rick.jones2@hp.com> |
|---|---|
| Date | 2013-10-10 01:37 +0000 |
| Message-ID | <l350cd$tki$4@usenet01.boi.hp.com> |
| In reply to | #2458 |
Mike Easter <MikeE@ster.invalid> wrote: > billy wrote: > > Could it be that anything after 15 hops fails no matter what? > > To test, do you know of a site that would be more than 15 hops > > away from San Francisco, CA? > I don't think that is a useful theory. It does seem unlikely, but if there is something capping the TTL at 15 or 0xF I suppose that could explain it. Though in that case I would expect it to be all the time not months-on/months-off. Unless there was something else causing his traffic to go through different kit somewhere along the way. Perhaps some servers in Europe or Asia would be > 15 hops. rick jones -- firebug n, the idiot who tosses a lit cigarette out his car window these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-10 03:17 +0000 |
| Message-ID | <U_o5u.69773$yx6.28197@fx26.iad> |
| In reply to | #2465 |
On 2013-10-10, Rick Jones <rick.jones2@hp.com> wrote: > Mike Easter <MikeE@ster.invalid> wrote: >> billy wrote: > >> > Could it be that anything after 15 hops fails no matter what? >> > To test, do you know of a site that would be more than 15 hops >> > away from San Francisco, CA? > >> I don't think that is a useful theory. > > It does seem unlikely, but if there is something capping the TTL at 15 > or 0xF I suppose that could explain it. Though in that case I would > expect it to be all the time not months-on/months-off. Unless there > was something else causing his traffic to go through different kit > somewhere along the way. > > Perhaps some servers in Europe or Asia would be > 15 hops. No It depends maily on the endpoints, not the distance. > > rick jones
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-10 20:03 +0000 |
| Message-ID | <l371ir$kut$1@speranza.aioe.org> |
| In reply to | #2465 |
Rick Jones wrote: > Perhaps some servers in Europe or Asia would be > 15 hops. As additional datapoints, my neighbors on the same WISP to run the same traceroutes as I did. They get through. Here are the details from one neighbor, with her IP address redacted for privacy. NEIGHBOR #1: C:\Windows\system32>tracert centos.org Tracing route to centos.org [72.232.194.162] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms REDACTED_IP.ridgewireless.net [xx.xx.xx.xx] 2 3 ms 1 ms 1 ms 10.50.0.1 3 9 ms 5 ms 31 ms 10.25.0.1 4 5 ms 11 ms 13 ms 10.20.0.1 5 33 ms 28 ms 25 ms 10.0.0.1 6 68 ms 70 ms 62 ms 69.36.226.193 7 40 ms 13 ms 66 ms vl2.core1.scl.layer42.net [69.36.225.129] 8 14 ms 6 ms 12 ms 216.156.84.141.ptr.us.xo.net [216.156.84.141] 9 86 ms 85 ms 87 ms 207.88.14.233.ptr.us.xo.net [207.88.14.233] 10 81 ms 63 ms 62 ms vb15.rar3.dallas-tx.us.xo.net [207.88.12.45] 11 58 ms 59 ms 60 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34] 12 61 ms 55 ms 99 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74] 13 117 ms 112 ms 65 ms border1.pc2-bbnet2.dal004.pnap.net [216.52.191.81] 14 98 ms 53 ms 54 ms layered-11.border1.dal004.pnap.net [63.251.44.74] 15 * * * Request timed out. 16 63 ms 54 ms 58 ms www.centos.org [72.232.194.162] Trace complete. C:\Windows\system32> C:\Windows\system32>tracert linuxreference.com Tracing route to linuxreference.com [72.232.194.162] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms REDACTED_IP.ridgewireless.net [xx.xx.xx.xx] 2 7 ms 5 ms 1 ms 10.50.0.1 3 2 ms 3 ms 2 ms 10.25.0.1 4 5 ms 5 ms 11 ms 10.20.0.1 5 38 ms 15 ms 32 ms 10.0.0.1 6 61 ms 83 ms 86 ms 69.36.226.193 7 37 ms 80 ms 47 ms vl2.core1.scl.layer42.net [69.36.225.129] 8 15 ms 15 ms 10 ms 216.156.84.141.ptr.us.xo.net [216.156.84.141] 9 84 ms 150 ms 70 ms 207.88.14.233.ptr.us.xo.net [207.88.14.233] 10 132 ms 70 ms 64 ms vb15.rar3.dallas-tx.us.xo.net [207.88.12.45] 11 83 ms 163 ms 124 ms 207.88.14.34.ptr.us.xo.net [207.88.14.34] 12 59 ms 79 ms 91 ms 207.88.185.74.ptr.us.xo.net [207.88.185.74] 13 177 ms * 81 ms border1.pc1-bbnet1.dal004.pnap.net [216.52.191.19] 14 102 ms 84 ms 63 ms layered-11.border1.dal004.pnap.net [63.251.44.74] 15 * * * Request timed out. 16 52 ms 59 ms 64 ms www.centos.org [72.232.194.162] Trace complete. C:\Windows\system32>
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-10 20:06 +0000 |
| Message-ID | <l371n0$kut$2@speranza.aioe.org> |
| In reply to | #2477 |
billy wrote:
> Here are the details from one neighbor, with her IP address
> redacted for privacy.
Here are details from a second neighbor, on the same WISP.
% traceroute www.centos.org
traceroute to www.centos.org (72.232.194.162), 64 hops max, 52 byte
packets
1 192.168.1.1 (192.168.1.1) 1.461 ms 0.955 ms 0.848 ms
2 IP_REDACTED.ridgewireless.net (xx.xx.xx.xx) 1.584 ms 1.642 ms
1.191 ms
3 10.50.0.1 (10.50.0.1) 19.264 ms 15.133 ms 22.613 ms
4 10.25.0.1 (10.25.0.1) 24.238 ms 11.541 ms 23.235 ms
5 10.20.0.1 (10.20.0.1) 274.715 ms 175.756 ms 164.049 ms
6 utm9s (10.0.0.1) 179.232 ms 170.025 ms 112.407 ms
7 69.36.226.193 (69.36.226.193) 237.651 ms 279.127 ms 131.729 ms
8 vl2.core1.scl.layer42.net (69.36.225.129) 229.883 ms 212.336 ms
262.883 ms
9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 320.652 ms 181.714
ms 319.745 ms
10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 410.173 ms 410.476 ms
314.872 ms
11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 453.813 ms 297.798
ms 380.139 ms
12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 384.894 ms 428.511 ms
451.605 ms
13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 384.011 ms 356.507 ms
290.830 ms
14 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 445.664 ms
border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 234.716 ms
258.429 ms
15 layered-11.border1.dal004.pnap.net (63.251.44.74) 354.172 ms
445.370 ms 146.977 ms
16 * * *
17 www.centos.org (72.232.194.162) 285.244 ms !Z 180.605 ms !Z
149.697 ms !Z
%
Both neighbors make it to Centos.org in about the same number
of hops that mine fails at.
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-09 21:27 +0000 |
| Message-ID | <l34hn6$n2t$4@speranza.aioe.org> |
| In reply to | #2434 |
On Wed, 09 Oct 2013 19:58:49 +0000, unruh wrote: > Note you could take your computer with you to some other place which > connects to the web in some other way than your microwave link and see > if that works there. It's not the computer because that same computer works fine at the library and at Starbucks and at a neighbor's house. The ONLY thing I can think of that's different is a) My IP address (it's static) b) My home broadband router (standard setup) c) My WISP radio (standard setup) But, all of this is local. The problem actually seems to occur way down at hop #15, which is beyond my control (far beyond my control). Is there any way to go around that hop #15?
[toc] | [prev] | [next] | [standalone]
| From | unruh <unruh@invalid.ca> |
|---|---|
| Date | 2013-10-09 22:15 +0000 |
| Message-ID | <4Ak5u.24071$uS4.15313@fx19.iad> |
| In reply to | #2442 |
On 2013-10-09, billy <billy@is.invalid> wrote: > On Wed, 09 Oct 2013 19:58:49 +0000, unruh wrote: > >> Note you could take your computer with you to some other place which >> connects to the web in some other way than your microwave link and see >> if that works there. > > It's not the computer because that same computer works fine at > the library and at Starbucks and at a neighbor's house. > > The ONLY thing I can think of that's different is > a) My IP address (it's static) > b) My home broadband router (standard setup) > c) My WISP radio (standard setup) > > But, all of this is local. > > The problem actually seems to occur way down at hop #15, > which is beyond my control (far beyond my control). > > Is there any way to go around that hop #15? For you? No. Get in touch with them. >
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-10 00:35 +0000 |
| Message-ID | <l34t2v$g9b$3@speranza.aioe.org> |
| In reply to | #2448 |
unruh wrote: >> Is there any way to go around that hop #15? > For you? No. Get in touch with them. I will contact them at the email addresses already posted and ask them if they're periodically doing something nasty to my IP address for months at a time (like putting me on a blacklist or something). I'll report back if/when they respond.
[toc] | [prev] | [next] | [standalone]
| From | "p-0''0-h the cat (ES)" <super.pooh@furryfreeware.invalid> |
|---|---|
| Date | 2013-10-10 09:15 +0100 |
| Message-ID | <ccoc5951ae061jjdsjnedpcak3i3it314m@4ax.com> |
| In reply to | #2455 |
On Thu, 10 Oct 2013 00:35:11 +0000, billy <billy@is.invalid> wrote: >unruh wrote: > >>> Is there any way to go around that hop #15? >> For you? No. Get in touch with them. > >I will contact them at the email addresses already posted >and ask them if they're periodically doing something nasty >to my IP address for months at a time (like putting me on a >blacklist or something). Yeah, that'll get their back up. Just be polite and present the results of your tests. Wide area networking is an altogether different game. I wouldn't tell them their job, because you'll be wrong. >I'll report back if/when they respond. -- p-0.0-h the cat Internet Terrorist, Mass sock puppeteer, Agent provocateur, Gutter rat, Devil incarnate, Linux user#666, BaStarD hacker, Resident evil, Monkey Boy, Certifiable criminal, Spineless cowardly scum, textbook Psychopath, the SCOURGE, l33t p00h d3 tr0ll, p00h == lam3r, p00h == tr0ll, troll infâme, the OVERCAT [The BEARPAIR are dead, and we are its murderers], lowlife troll, shyster [pending approval by STATE_TERROR], cripple, sociopath, kook, smug prick, smartarse, arsehole, moron, idiot, imbecile, snittish scumbag, liar, and shill. Honorary SHYSTER and FRAUD awarded for services to Haberdashery. By Appointment to God Frank-Lin.
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-11 01:40 +0000 |
| Message-ID | <l37l8k$v7v$1@speranza.aioe.org> |
| In reply to | #2416 |
Below (sorry for the top post) is the old traceroute from yesterday on Microknoppix. Here is the new traceroute from a few seconds ago. The route is entirely different! Since *UNDERSTANDING* is what we're after, can you give me insight into *how* all of a sudden, the route is so very different (and why it works now)? Who decides what route my packets will take? knoppix@Microknoppix:~$ traceroute www.centos.org traceroute to www.centos.org (85.12.30.227), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 2.940 ms 2.915 ms 5.895 ms 2 67-218-118-85.ridgewireless.net (67.218.118.85) 23.983 ms 23.970 ms 23.953 ms 3 10.50.0.1 (10.50.0.1) 23.935 ms 23.920 ms 23.905 ms 4 10.25.0.1 (10.25.0.1) 33.716 ms 33.701 ms 33.687 ms 5 10.20.0.1 (10.20.0.1) 113.640 ms 127.266 ms 127.251 ms 6 10.0.0.1 (10.0.0.1) 155.135 ms 198.034 ms 198.014 ms 7 69.36.226.193 (69.36.226.193) 77.534 ms 88.951 ms 88.940 ms 8 vl2.core2.scl.layer42.net (69.36.225.130) 101.711 ms 101.700 ms 107.203 ms 9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 111.422 ms 111.419 ms 111.404 ms 10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 111.376 ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49) 111.352 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 111.341 ms 11 be2047.ccr22.sjc01.atlas.cogentco.com (154.54.5.113) 111.324 ms 111.311 ms be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 111.251 ms 12 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 111.238 ms be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 58.660 ms be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 66.012 ms 13 be2132.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 168.366 ms be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 168.350 ms be2133.ccr22.mci01.atlas.cogentco.com (154.54.30.66) 165.709 ms 14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 168.316 ms 168.300 ms be2158.mpd21.ord01.atlas.cogentco.com (154.54.7.130) 168.285 ms 15 be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 139.555 ms 133.671 ms be2138.ccr22.bos01.atlas.cogentco.com (154.54.43.202) 155.781 ms 16 be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 139.505 ms te0-3-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.230) 208.018 ms te0-4-0-3.ccr22.lpl01.atlas.cogentco.com (154.54.44.190) 208.007 ms 17 te0-5-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.87.65) 211.696 ms be2182.ccr21.ams03.atlas.cogentco.com (154.54.77.245) 226.780 ms te0-4-0-6.ccr22.lpl01.atlas.cogentco.com (154.54.44.214) 211.705 ms 18 be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 229.203 ms te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190) 310.294 ms be2185.mpd22.ams03.atlas.cogentco.com (154.54.37.105) 310.272 ms 19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.393 ms te0-0-0-12.mag21.ams03.atlas.cogentco.com (154.54.76.134) 310.218 ms 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.367 ms 20 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 305.344 ms 305.321 ms 310.147 ms 21 85.12.30.227 (85.12.30.227) 305.263 ms !X 305.254 ms !X 205.255 ms !X knoppix@Microknoppix:~$ > root@Microknoppix:/# traceroute -M icmp centos.org > traceroute to centos.org (72.232.194.162), 30 hops max, 60 byte packets > 1 192.168.1.1 (192.168.1.1) 2.932 ms 2.929 ms 2.928 ms > 2 WISP_IP_REDACTED (xxx.xxx.xxx.xxx) 5.683 ms 5.683 ms 5.680 ms > 3 10.50.0.1 (10.50.0.1) 20.479 ms 20.477 ms 20.474 ms > 4 10.25.0.1 (10.25.0.1) 20.469 ms 30.272 ms 33.014 ms > 5 10.20.0.1 (10.20.0.1) 33.009 ms 36.190 ms 36.187 ms > 6 10.0.0.1 (10.0.0.1) 36.182 ms 16.332 ms 39.405 ms > 7 69.36.226.193 (69.36.226.193) 39.377 ms 20.721 ms 23.093 ms > 8 vl2.core1.scl.layer42.net (69.36.225.129) 23.066 ms 16.977 ms 16.947 > ms 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 16.917 ms 12.782 ms > 18.611 ms 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 69.341 ms > 119.252 ms 119.222 ms 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) > 116.010 ms 84.054 ms 84.022 ms 12 207.88.14.34.ptr.us.xo.net > (207.88.14.34) 83.978 ms 53.016 ms 52.987 ms 13 > 207.88.185.74.ptr.us.xo.net (207.88.185.74) 56.341 ms 53.502 ms 59.458 > ms 14 border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 59.430 ms > 58.240 ms border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 61.422 ms 15 > layered-11.border1.dal004.pnap.net (63.251.44.74) 61.383 ms 54.510 ms > 54.494 ms 16 * * * <== centos.org is here 17 * * * 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > root@Microknoppix:/#
[toc] | [prev] | [next] | [standalone]
| From | nemesis <nemesis@home.it> |
|---|---|
| Date | 2013-10-10 23:03 -0300 |
| Message-ID | <hewe19aeaul2.zyxwrgk6i5rt$.dlg@40tude.net> |
| In reply to | #2496 |
On Fri, 11 Oct 2013 01:40:04 +0000, billy wrote: > Below (sorry for the top post) is the old traceroute from yesterday on > Microknoppix. > > Here is the new traceroute from a few seconds ago. > The route is entirely different! > Since *UNDERSTANDING* is what we're after, can you give me > insight into *how* all of a sudden, the route is so very different > (and why it works now)? > > Who decides what route my packets will take? The guy at 67.218.118.85. He probably lives nearby. Kick his a¨%&¨¨. -- I am a troll
[toc] | [prev] | [next] | [standalone]
| From | billy <billy@is.invalid> |
|---|---|
| Date | 2013-10-11 14:43 +0000 |
| Message-ID | <l39364$8ns$2@speranza.aioe.org> |
| In reply to | #2498 |
nemesis wrote: > The guy at 67.218.118.85. > He probably lives nearby. Kick his a¨%&¨¨. That's me! :) Anyway, the problem is back, and shown below. If I had a better DIAGNOSTIC TOOL, I'd feel better with the data. It's not the MTU, the TTL, the DNS server, the operating system, etc. I just wish I had a better diagnostic tool than traceroute... knoppix@Microknoppix:~$ traceroute !$ traceroute centos.org traceroute to centos.org (85.12.30.227), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 6.125 ms 6.094 ms 6.077 ms 2 67-218-118-85.ridgewireless.net (67.218.118.85) 33.527 ms 33.515 ms 33.499 ms 3 10.50.0.1 (10.50.0.1) 33.485 ms 39.686 ms 47.348 ms 4 10.25.0.1 (10.25.0.1) 82.142 ms 82.128 ms 82.113 ms 5 10.20.0.1 (10.20.0.1) 101.802 ms 101.787 ms 101.771 ms 6 10.0.0.1 (10.0.0.1) 111.627 ms 52.710 ms 52.672 ms 7 69.36.226.193 (69.36.226.193) 52.637 ms 25.633 ms 25.613 ms 8 vl2.core2.scl.layer42.net (69.36.225.130) 25.599 ms 25.584 ms 32.306 ms 9 xe-0-0-0-22.r07.snjsca04.us.bb.gin.ntt.net (140.174.21.101) 36.545 ms 36.530 ms 36.515 ms 10 te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.477 ms te0-4-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.10.49) 36.463 ms te0-7-0-32.ccr21.sjc03.atlas.cogentco.com (154.54.11.85) 36.433 ms 11 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 36.442 ms 36.427 ms 17.909 ms 12 be2164.ccr21.sfo01.atlas.cogentco.com (154.54.28.33) 26.295 ms be2166.mpd21.sfo01.atlas.cogentco.com (154.54.28.69) 26.279 ms be2167.mpd22.sfo01.atlas.cogentco.com (154.54.28.77) 31.666 ms 13 be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.979 ms be2134.mpd21.mci01.atlas.cogentco.com (154.54.6.38) 81.949 ms be2135.mpd22.mci01.atlas.cogentco.com (154.54.6.34) 81.943 ms 14 be2159.mpd22.ord01.atlas.cogentco.com (154.54.24.82) 91.739 ms 110.049 ms be2156.ccr21.ord01.atlas.cogentco.com (154.54.6.86) 110.039 ms 15 be2140.ccr22.bos01.atlas.cogentco.com (154.54.43.186) 118.042 ms be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 112.212 ms be2137.ccr21.bos01.atlas.cogentco.com (154.54.43.194) 118.011 ms 16 te0-2-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.190) 185.107 ms te0-0-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.170) 185.082 ms 185.048 ms 17 te0-3-0-6.ccr21.lpl01.atlas.cogentco.com (154.54.6.142) 191.782 ms be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69) 204.548 ms te0-5-0-4.ccr22.lpl01.atlas.cogentco.com (154.54.87.53) 191.749 ms 18 te0-7-0-0.mag21.ams03.atlas.cogentco.com (154.54.76.170) 191.771 ms 199.379 ms be2184.mpd21.ams03.atlas.cogentco.com (154.54.37.69) 199.369 ms 19 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 199.355 ms 199.325 ms te0-0-0-4.mag21.ams03.atlas.cogentco.com (154.54.76.190) 207.195 ms 20 * * 10ge-2-3.cr1.ams3.baseip.com (149.6.128.198) 188.627 ms 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * knoppix@Microknoppix:~$ knoppix@Microknoppix:~$ traceroute linuxreference.com traceroute to linuxreference.com (72.232.194.162), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 2.834 ms 2.810 ms 9.836 ms 2 67-218-118-85.ridgewireless.net (67.218.118.85) 19.635 ms 19.625 ms 19.610 ms 3 10.50.0.1 (10.50.0.1) 46.754 ms 46.748 ms 46.730 ms 4 10.25.0.1 (10.25.0.1) 51.077 ms 51.065 ms 51.051 ms 5 10.20.0.1 (10.20.0.1) 53.594 ms 53.583 ms 53.574 ms 6 10.0.0.1 (10.0.0.1) 53.548 ms 37.843 ms 37.816 ms 7 69.36.226.193 (69.36.226.193) 35.370 ms 35.323 ms 37.883 ms 8 vl2.core1.scl.layer42.net (69.36.225.129) 37.878 ms 37.863 ms 37.847 ms 9 216.156.84.141.ptr.us.xo.net (216.156.84.141) 37.832 ms 59.609 ms 59.597 ms 10 207.88.14.233.ptr.us.xo.net (207.88.14.233) 112.224 ms 112.214 ms 104.915 ms 11 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 104.885 ms 104.859 ms 104.813 ms 12 207.88.14.34.ptr.us.xo.net (207.88.14.34) 101.385 ms 133.165 ms 133.144 ms 13 207.88.185.74.ptr.us.xo.net (207.88.185.74) 111.137 ms 111.135 ms 111.097 ms 14 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 111.084 ms border1.pc2-bbnet2.dal004.pnap.net (216.52.191.81) 111.070 ms border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 114.155 ms 15 layered-11.border1.dal004.pnap.net (63.251.44.74) 114.144 ms 114.133 ms 114.110 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * knoppix@Microknoppix:~$
[toc] | [prev] | [next] | [standalone]
| From | ~BD~ <~BD~@nomail.afraid.org> |
|---|---|
| Date | 2013-10-11 16:11 +0100 |
| Message-ID | <tZadnd8NudSniMXPnZ2dnUVZ7rydnZ2d@bt.com> |
| In reply to | #2514 |
billy wrote: > nemesis wrote: > >> The guy at 67.218.118.85. >> He probably lives nearby. Kick his a¨%&¨¨. > > That's me! :) > > Anyway, the problem is back, and shown below. > > If I had a better DIAGNOSTIC TOOL, I'd feel better with the data. > It's not the MTU, the TTL, the DNS server, the operating system, > etc. > > I just wish I had a better diagnostic tool than traceroute... Oh dear! I thought you'd cracked it Billy! Have you ever 'played' with .... http://nmap.org/ ? I've no idea if it will help you .... but you might find it fun! ;-) Please advise.
[toc] | [prev] | [next] | [standalone]
Page 5 of 7 — ← Prev page 1 2 3 4 [5] 6 7 Next page →
Back to top | Article view | comp.os.linux.networking
csiph-web