RE: [nznog] [OT]Ispmap / isp locations / core routers
On Tue, 19 Jul 2005, Barry Murphy wrote: [...]
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations.
Any information gathered through probing networks will most certainly be inaccurate and could lead (as pointed out earlier) to increased frustration in helpdesks when some clueless customer rings up to report an ERX crash because they saw it on your intarwebnet page.
There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."
Ok,
So it would seem this is pointless, monitoring on a layer 2 would be much
better, so if any providers want the code, let me know ;)
No more discussion required on this topic.
Thanks for your input.
Barry
----- Original Message -----
From: "Donald Neal"
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations.
Any information gathered through probing networks will most certainly be inaccurate and could lead (as pointed out earlier) to increased frustration in helpdesks when some clueless customer rings up to report an ERX crash because they saw it on your intarwebnet page.
There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
No more discussion required on this topic
I think you've hurt his feelings guys... :P
Erin Salmon
Managing Director
Unleash Computers Ltd
www.unleash.co.nz
Phone: +64 3 365 1273
Mobile: +64 21 877 913
-----Original Message-----
From: Barry Murphy [mailto:barry(a)unix.co.nz]
Sent: Tuesday, 19 July 2005 11:08 a.m.
To: Donald Neal; nznog(a)list.waikato.ac.nz
Subject: Re: [nznog] [OT]Ispmap / isp locations / core routers - end
Ok,
So it would seem this is pointless, monitoring on a layer 2 would be much
better, so if any providers want the code, let me know ;)
No more discussion required on this topic.
Thanks for your input.
Barry
----- Original Message -----
From: "Donald Neal"
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations.
Any information gathered through probing networks will most certainly be inaccurate and could lead (as pointed out earlier) to increased frustration in helpdesks when some clueless customer rings up to report an ERX crash because they saw it on your intarwebnet page.
There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.1/51 - Release Date: 18/07/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.1/51 - Release Date: 18/07/2005
If you can adapt it to the operational address of local spammers then I think you'll have a hit. Useful information would be geographic location, wind speed, big windows into the building and nearby cover. You'd want a "no longer a threat" button on each spammer node however. You can see how the list would become out of date very quickly.
Ok,
So it would seem this is pointless, monitoring on a layer 2 would be much better, so if any providers want the code, let me know ;)
No more discussion required on this topic.
Thanks for your input. Barry
----- Original Message ----- From: "Donald Neal"
To: Sent: Tuesday, July 19, 2005 11:02 AM Subject: RE: [nznog] [OT]Ispmap / isp locations / core routers On Tue, 19 Jul 2005, Barry Murphy wrote:
[...]
I'm guessing customers connect directly to the erx's, thus if the erxcrash's and goes down, customer falling off that node will be effected.
The idea is a pretty map with colors indicating packet loss. Let's just see what happens when the next big network fault happens.
It is highly unlikely anyone will give you this information (and in some cases this is 100% unlikely) as this would tend to be considered "commercially sensitive" data to many large organisations.
Any information gathered through probing networks will most certainly be inaccurate and could lead (as pointed out earlier) to increased frustration in helpdesks when some clueless customer rings up to report an ERX crash because they saw it on your intarwebnet page.
There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual.
This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer.
The key question is what exactly it is anyone's trying to measure.
- Donald Neal
"This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
participants (4)
-
Barry Murphy
-
Donald Neal
-
Erin Salmon - Unleash Computers Ltd
-
justin@skull.co.nz