This report has been generated at Fri Jan 6 21:52:35 2006 AEST.
The report analyses the BGP Routing Table of an AS4637 (Reach) router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org/as4637 for a current version of this report.
Recent Table Hist
Hello,
In june 2005 LACNIC received two new IP block from IANA (189/8 and
190/8). And before starting to make allocation in it, we conducted
some reachability tests with valuable help from this community.
Those test showed that great majority of transit providers were not
block those network ran
And here i was expecting .ZIP file from the FBI and CIA telling me that
I need to full out a "survey" :)
-Wil
Martin Hannigan wrote:
Here is some more interesting information. I'm not positive this is
Sober.Z related but it's walking like and talking like a duck.
First I see the below DNS
Enough talk about viruses and unpatched hosts! Maybe if we try hard
enough, we can create a Y2K syndrome for the removal of 3ffe:: from global
routing?
- Forwarded message from Mike Bran <[EMAIL PROTECTED]> -
Date: Fri, 6 Jan 2006 10:27:11 -0500
From: Mike Bran <[EMAIL PROTECTED]>
To: [
On Fri, 6 Jan 2006, eric wrote:
>
> Enough talk about viruses and unpatched hosts! Maybe if we try hard
> enough, we can create a Y2K syndrome for the removal of 3ffe:: from global
> routing?
>
guess terado services will get a facelift then too? (since they
require/use the 3ffe range for comms)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hmm..I thought (correct me if I wrong) wsus followed a mirror
(distributed) model say if a group of servers were pegged the update
process would provide remote clients access to the closet and min
latency host(s) in order to distribute the load preven
On 6-Jan-2006, at 11:23, Christopher L. Morrow wrote:
guess terado services will get a facelift then too? (since they
require/use the 3ffe range for comms)
The most recent draft for teredo only requires use of 3FFE::/16
obliquely:
2.6 Global Teredo IPv6 service prefix
An IPv6 address
> guess terado services will get a facelift then too? (since
> they require/use the 3ffe range for comms)
Out of curiosity, how prevalent is Teredo these days?
Thanks
Bora
Ho Joe, all,
The last I heard was that the draft was pending of the final step with the
IESG review or something similar, but I'm not completely sure. Then IANA
will assign a production prefix.
I'm aware of at least 8 Teredo Relays (some of them only available within
specific ASs). We run one of
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
Daily listings are sent to [EMAIL PROTECTED]
If you have any comments please contact Philip Smith <[EMAIL PROTECTED]>.
Routing Table Report 04:00 +10GMT Sat 07 Jan, 2006
Joe Abley wrote:
>
>
> On 6-Jan-2006, at 11:23, Christopher L. Morrow wrote:
>
>> guess terado services will get a facelift then too? (since they
>> require/use the 3ffe range for comms)
>
> The most recent draft for teredo only requires use of 3FFE::/16 obliquely:
>
> 2.6 Global Teredo IPv6 s
On Fri, 06 Jan 2006 10:12:37 CST, eric said:
> We will begin filtering 3ffe::/16 traffic by the earlier of:
> (i) June 6 2006; (ii) when transiting traffic sourced from or
> destined to 3ffe address space drops below 5% of our aggregate
> network traffic.
Is that 5% of your IPv6 traffic, or 5% of
Apparently they have lost two authoritive servers. ETA is unknown.
-Wil
On Fri, 6 Jan 2006, Wil Schultz wrote:
Apparently they have lost two authoritive servers. ETA is unknown.
You forgot to mention that they only have two authoritive servers for
most of their domains...
--
William Leibzon
Elan Networks
[EMAIL PROTECTED]
Feeling the thrash all the way down here in Austin in
SBC-land... :-(
- ferg
-- Wil Schultz <[EMAIL PROTECTED]> wrote:
Apparently they have lost two authoritive servers. ETA is unknown.
-Wil
Well, that would explain it, make me feel better that they took
themselves out as well:
-bash-2.05b$ dig qwest.com
; <<>> DiG 9.3.1 <<>> qwest.com
;; global options: printcmd
;; connection timed out; no servers could be reached
-Wil
william(at)elan.net wrote:
On Fri, 6 Jan 2006, Wil Schul
Partially back up, I can resolve everthing here... They tell me that
it's not quite over yet.
-Wil
Wil Schultz wrote:
Well, that would explain it, make me feel better that they took
themselves out as well:
-bash-2.05b$ dig qwest.com
; <<>> DiG 9.3.1 <<>> qwest.com
;; global options: prin
[EMAIL PROTECTED] wrote:
> On Fri, 06 Jan 2006 10:12:37 CST, eric said:
>
>> We will begin filtering 3ffe::/16 traffic by the earlier of:
>> (i) June 6 2006; (ii) when transiting traffic sourced from or
>> destined to 3ffe address space drops below 5% of our aggregate
>> network traffic.
>
> Is t
On Fri, 6 Jan 2006, Wil Schultz wrote:
>
> Well, that would explain it, make me feel better that they took
> themselves out as well:
>
> -bash-2.05b$ dig qwest.com
> ; <<>> DiG 9.3.1 <<>> qwest.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
not anyca
On Fri, 6 Jan 2006, william(at)elan.net wrote:
On Fri, 6 Jan 2006, Wil Schultz wrote:
Apparently they have lost two authoritative servers. ETA is unknown.
You forgot to mention that they only have two authoritative servers for
most of their domains...
I didn't look at this while it was ha
Vicky Røde wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hmm..I thought (correct me if I wrong) wsus followed a mirror
(distributed) model say if a group of servers were pegged the update
process would provide remote clients access to the closet and min
latency host(s) in order to distri
21 matches
Mail list logo
