1 |
On Sat, Feb 18, 2012 at 21:36, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Sat, 18 Feb 2012 06:00:00 -0600 |
3 |
> Dale <rdalek1967@×××××.com> wrote: |
4 |
> |
5 |
>> > And no, the intartubes will NOT be switched off. |
6 |
>> > |
7 |
>> |
8 |
>> I don't really think they can unless they just cut power to all the |
9 |
>> computers. After all, the internet is supposed to be redundant right? |
10 |
>> If there is a few computers still running that have a connection, it |
11 |
>> is still working. Sort of anyway. |
12 |
>> |
13 |
>> Does make one wonder tho. They have been talking about having a |
14 |
>> internet "off switch" but I'm not sure it would be that easy. |
15 |
> |
16 |
> To switch off the internet, you don't switch off the computers on the |
17 |
> internet. You switch off the routers that drive the internet. |
18 |
> |
19 |
|
20 |
You don't need to turn off the routers. |
21 |
|
22 |
Just inject BGP poison. |
23 |
|
24 |
I just re-found the news: |
25 |
|
26 |
http://www.computerworld.com/s/article/9197019/Update_Report_sounds_alarm_on_China_s_rerouting_of_U.S._Internet_traffic |
27 |
|
28 |
The article I linked above contains 2 incidents: |
29 |
|
30 |
The first incident rerouted traffic for a huge swath of Internet, |
31 |
including traffic destined to Microsoft, the Office of the USA SecDef, |
32 |
and others. |
33 |
|
34 |
The second incident blocked traffic for some sites, notably Twitter, |
35 |
Yahoo, and Facebook. |
36 |
|
37 |
BOTH incidents happened because of BGP poisoning. BOTH incidents |
38 |
affected traffic FROM the USA to destinations IN the USA even though |
39 |
the poisoning happened from OUTSIDE of the USA. |
40 |
|
41 |
The country where both incidents happened (in these cases, China) is |
42 |
not essential. ANY country with a BGP router connected to the backbone |
43 |
can easily poison other international backbone routers. Especially if |
44 |
said country has a HUGE International bandwidth. |
45 |
|
46 |
Rgds, |
47 |
-- |
48 |
FdS Pandu E Poluan |
49 |
~ IT Optimizer ~ |
50 |
|
51 |
• LOPSA Member #15248 |
52 |
• Blog : http://pepoluan.tumblr.com |
53 |
• Linked-In : http://id.linkedin.com/in/pepoluan |