Sigh. And this is why I rarely post. I'll take my toys and go home now.
For what it's worth, you're right if Hostwinds peers with both then I'm
wrong. It certainly won't be the first mistake I've made day. :-)
John
> On Jan 23, 2017, at 23:00, Roman Mamedov wrote:
>
On Tue, 24 Jan 2017 03:40:05 +
John Ricketts wrote:
> It is entirely possible this is a result of the HE vs Cogent feud, big break
> in the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure
> where they are in that negotiation...
Any basis for that
Is there any good reason why you (and all the others) are not waving torches
and pitchforks?
niftybunny
ab...@to-surf-and-protect.net
> On 24 Jan 2017, at 05:28, John Ricketts wrote:
>
> I am forced to peer with both Cogent and HE because of this.
>
> On Jan 23, 2017, at
I am forced to peer with both Cogent and HE because of this.
On Jan 23, 2017, at 22:28, niftybunny
> wrote:
BGP should choose another path? BGP Routing is highly "political" but IPs just
black holed is really really bad ...
If
BGP should choose another path? BGP Routing is highly “political” but IPs just
black holed is really really bad …
If this is true: WTF?!
niftybunny
ab...@to-surf-and-protect.net
> On 24 Jan 2017, at 05:24, teor wrote:
>
>
>> On 24 Jan 2017, at 15:18, niftybunny
This may help.
https://lists.gt.net/nanog/users/187011
On Jan 23, 2017, at 22:24, teor >
wrote:
On 24 Jan 2017, at 15:18, niftybunny
> wrote:
Could I get an ELI5 for this
> On 24 Jan 2017, at 15:18, niftybunny wrote:
>
> Could I get an ELI5 for this please?
If you want an ELI5, explain your request like I'm five years old.
>> On 24 Jan 2017, at 04:40, John Ricketts wrote:
>>
>> It is entirely possible this is
Could I get an ELI5 for this please?
niftybunny
ab...@to-surf-and-protect.net
> On 24 Jan 2017, at 04:40, John Ricketts wrote:
>
> It is entirely possible this is a result of the HE vs Cogent feud, big break
> in the IPv6 routing tables as a cogent is refusing to peer with
It is entirely possible this is a result of the HE vs Cogent feud, big break in
the IPv6 routing tables as a cogent is refusing to peer with HE. Not sure
where they are in that negotiation...
> On Jan 23, 2017, at 21:38, teor wrote:
>
>
>> On 24 Jan 2017, at 14:31,
> On 24 Jan 2017, at 14:31, niftybunny wrote:
>
> inet6 addr: 2607:5500:2000:5d3::de95/64 Scope:Global
> UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
> RX packets:3169513589 errors:0 dropped:0 overruns:0 frame:0
>
inet6 addr: 2607:5500:2000:5d3::de95/64 Scope:Global
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:3169513589 errors:0 dropped:0 overruns:0 frame:0
TX packets:3438384506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
> On 24 Jan 2017, at 14:18, niftybunny wrote:
> ...
> Connecting to dist.torproject.org
> (dist.torproject.org)|2a01:4f8:211:6e8:0:823:2:1|:443... failed: Network is
> unreachable.
> Connecting to dist.torproject.org (dist.torproject.org)|38.229.72.16|:443...
>
xxx@:~# wget https://www.torproject.org/dist/tor-0.2.9.9.tar.gz
converted 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (ANSI_X3.4-1968)
-> 'https://www.torproject.org/dist/tor-0.2.9.9.tar.gz' (UTF-8)
--2017-01-23 22:12:32-- https://www.torproject.org/dist/tor-0.2.9.9.tar.gz
13 matches
Mail list logo