Abundant evidence indicates that AS18466, allocated by LACNIC, has been
hijacked.
All of the routes currently announced by this AS, i.e.:
170.25.0.0/19
170.25.32.0/19
170.25.160.0/19
170.25.192.0/19
are currently routing IP blocks, also allocated by LACNIC, which have also
On May 12, 2011, at 8:31 PM, Roy wrote:
On 5/12/2011 4:03 PM, George Herbert wrote:
Large end-user companies generally multihomed by that time, and you
generally did that by BGP4 at the time (post-1994), and before that
BGP3, and before that EGP, and before that... well, there was
To do this, you only need 2 numbers: the nth digit of pi and the number of
digits.
Simply convert your message into a single extremely long integer. Somewhere,
in the digits of pi, you will find a matching series of digits the same as
your integer!
Decompressing the number is relatively easy
On Fri, May 20, 2011 at 06:46:45PM +, Eu-Ming Lee wrote:
To do this, you only need 2 numbers: the nth digit of pi and the number of
digits.
Simply convert your message into a single extremely long integer. Somewhere,
in the digits of pi, you will find a matching series of digits the
On 05/20/2011 08:53 AM, Brett Frankenberger wrote:
On Fri, May 20, 2011 at 06:46:45PM +, Eu-Ming Lee wrote:
To do this, you only need 2 numbers: the nth digit of pi and the number of
digits.
Simply convert your message into a single extremely long integer. Somewhere,
in the digits of pi,
On Fri, May 20, 2011 at 09:34:59AM -1000, Paul Graydon said:
Not quite sure I follow that. Start at position xyz, carry on for 1
bits shouldn't be as long as telling it all 1 bits?
what position # do you think your exact 1 bits will appear at?
(infact, mathies, whats the
On Fri, May 20, 2011 at 09:34:59AM -1000, Paul Graydon wrote:
On 05/20/2011 08:53 AM, Brett Frankenberger wrote:
On Fri, May 20, 2011 at 06:46:45PM +, Eu-Ming Lee wrote:
To do this, you only need 2 numbers: the nth digit of pi and the number of
digits.
Simply convert your message into a
On Fri, 20 May 2011 09:34:59 -1000, Paul Graydon said:
Not quite sure I follow that. Start at position xyz, carry on for 1
bits shouldn't be as long as telling it all 1 bits?
The problem is that the length of 'xyz' will probably be on the same order of
magnitude as the length of your
On 05/20/2011 03:34 PM, Paul Graydon wrote:
On 05/20/2011 08:53 AM, Brett Frankenberger wrote:
Even if those problems were solved, you'd need (on average) just as
many bits to represent which digit of pi to start with as you'd need to
represent the original message.
-- Brett
Not quite
I could not help but admire nanog in its full form ;) and I cannot resist
anymore. Allow me to suggest the EPR paradox machine.
The cost of regenerating unpredictable information is inefficient by orders
of magnitude, but wait... isn't it what we are trying to solve?
On May 20, 2011, at
BGP Update Report
Interval: 12-May-11 -to- 19-May-11 (7 days)
Observation Point: BGP Peering with AS131072
TOP 20 Unstable Origin AS
Rank ASNUpds % Upds/PfxAS-Name
1 - AS982943670 3.4% 63.8 -- BSNL-NIB National Internet
Backbone
2 - AS17974
This report has been generated at Fri May 20 21:12:21 2011 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org for a current version of this report.
Recent Table History
Date
On 5/20/2011 12:44 PM, Ken Chase wrote:
On Fri, May 20, 2011 at 09:34:59AM -1000, Paul Graydon said:
Not quite sure I follow that. Start at position xyz, carry on for 1
bits shouldn't be as long as telling it all 1 bits?
what position # do you think your exact 1 bits will appear
Thanks for all who assisted me on this issue. Was invaluable to get router
output from all over the country.
Bottom line Level3 had some issues with poking a whole in there
summarization filters. Appeared that the problem was only with peers
connected to the HSA1 and HSA2 routers in San Diego.
14 matches
Mail list logo
