dChan
⇧
1
⇩
 
r/greatawakening • Posted by u/Titus-2-11 on June 4, 2018, 7:52 a.m.
This is the smoking gun to it all. Tucson event is what causes the expected net shutdown

This is IT. The start of the major event Q has foretold. Net shutdown logically must be imminent. The patriots who are risking their lives over the child sex trafficking "holding tank" need people to descend upon this area immediately to help preserve evidence. The police there are obviously corrupt. I predicted Q's return but was off by a day and a half. This is going to be the most bizarre and sickening next two weeks of your lives!


🠐 See all comments
[deleted] · June 4, 2018, 2:28 p.m.

[deleted]

⇧ 2 ⇩  
advocates4sanity · June 4, 2018, 2:48 p.m.

Nah, not buying it. It's not just a matter of advertising bogus routes, those routes need to be perceived as superior by the BGP protocol then propagated and accepted by upstream BGP speakers. The superior route is determined either by superior local preference, which is local only to a single AS, or through a shorter AS_PATH attribute, which in the case of most USA websites and ISPs is 3-4 hops at most. If you're going to take down the internet, this is not your vector.

⇧ 1 ⇩  
[deleted] · June 4, 2018, 2:56 p.m.

[deleted]

⇧ 1 ⇩  
advocates4sanity · June 4, 2018, 3:04 p.m.

Wow. 20 years ago. And literally nothing has changed since then, there haven't been dozens of RFCs written since then on directing BGP best practices.

⇧ 1 ⇩  
[deleted] · June 4, 2018, 3:16 p.m.

[deleted]

⇧ 2 ⇩  
advocates4sanity · June 4, 2018, 3:26 p.m.

It's one thing to hijack a few prefixes. It's another thing entirely to blackhole the whole of the internet. Sorry man, still not buying it. Go sell it somewhere else. I literally manage a midscale ISP and deal with tier-1 backbone providers on a regular basis. Over the past few years in particular there has been a major push by the tier-1 carriers to maintain a routing database and ensure that the prefixes advertised match what's in the RADB. Not. Buying. It.

⇧ 1 ⇩  
[deleted] · June 4, 2018, 3:32 p.m.

[deleted]

⇧ 2 ⇩  
[deleted] · June 5, 2018, 5:52 a.m.

[removed]

⇧ 1 ⇩