providers would add RPKI ROAs as a data
source for BGP filter generation.Supporting RPKI ROAs would mean that you
don't have to create both IRR route objects and RPKI ROAs for each IP block.
--
Clinton Work
.
--
Clinton Work
RADB MAINT-AS15290 was restored this morning along with all the original route
objects. The proxy route objects I added Tuesday were replaced by the
original MAINT-AS15290 objects.
--
Clinton Work
On Tue, Mar 3, 2020, at 11:39 AM, Job Snijders wrote:
> On Tue, Mar 03, 2020 at 11:22:3
The ARIN IRR doesn't support an API interface like the RADB IRR. I hear that
ARIN is working on an API, but I don't know the timeline. I don't want to go
back to email templates.
https://www.arin.net/resources/manage/irr/userguide/
--
Clinton Work
On Wed, Mar 4, 20
ht it was Akamai, but
they swear up and down that the servers don't belong to them.
Here are some of the HTTP/HTTPS servers in 8.240.0.0/12:
8.253.151.248
8.251.135.126
8.240.167.126
8.240.228.126
8.240.168.126
8.240.126.254
8.240.191.254
--
Clinton Work
Airdrie, AB
50.92.128.0/17 AS10990
--
Clinton Work
Airdrie, AB
r two incidents and a root
cause was never found.
--
Clinton Work
Airdrie, AB
On Wed, Aug 19, 2020, at 6:46 AM, Nicholas Warren wrote:
> We've got a 100g qsfp in an mx204 that has 1207 bit errors and 29666
> errored blocks after 24 hours of just being linked up...
> I would assume
257 68799843 331607000 00:00:50
Active
--
Clinton Work
esent:TCP Checksum Offloading (IPV6) -> Disabled
UDP Checksum Offloading (IPV6) -> Disabled
- Try Windows update again
--
Clinton Work
Airdrie, AB
On Sun, Nov 11, 2018, at 2:29 AM, Mark Tinka wrote:
> Hi all.
>
> Anyone ever figured out why Windows updates fail when the computer
&
I'm looking for a Snapchat CDN/network contact to discuss some non-optimal
traffic delivery into our network. I couldn't find a peerindb entry for their
AS395291.
--
Clinton Work
My understanding is that the Bell Aliant outage was a double fault
situation. Bell Aliant had a fiber cut on one of their fiber routes
early in the morning and then they had a fault on the diverse fiber
route before the first trouble could be repaired.
On Tue, Aug 15, 2017, at 11:22 AM, Rod Be
I can't speak for the Bell Aliant network, but I'm only aware of two
diverse fiber routes out of Halifax, Nova Scotia. Halifax -> New
Brunswick -> Quebec City is the Canadian route and Halifax -> Boston is
the diverse route.
On Tue, Aug 15, 2017, at 01:52 PM, Jared Mauch wrote:
> Perhaps some
TELUS AS852 has three address blocks hijacked by AS133955 as well. We
have not been able to get in contact with AS24155. It looks like they
are buying transit from PCCW AS3491 and Taiwan Internet Gateway AS9505.
68.182.255.0/24
74.49.255.0/24
96.1.255.0/24
On Tue, Oct 3, 2017, at 10:30 AM, M
My understanding is that nobody has a 2nd diverse fiber route north of
the great lakes from Winnipeg to Toronto. Every provider makes use of
a fiber route south of the great lakes thru the US in order to provide
diversity.
The following map shows that the CN rail and CP Rail lines across ove
d BGP communities to your ISP for other BGP route
manipulation, you can add another community for ISP AS prepending rather
than modifying your local policies to add AS prepending.
You are 1.
ISP is 2.
1 1 2 - You prepend
1 2 2 - ISP prepends
--
Clinton Work
Airdrie, AB
On Thu, Oct 26, 201
Can a Verizon AS701 contact me to discuss why you are advertising BGP
routes for the following TELUS AS852 address space. I tried to open a
ticket with your IP NOC, but you won't open a ticket for a non-customer.
207.34.206.0/24
207.34.222.0/24
207.34.250.0/24
207.34.251.0/24
The AS701 BGP routes have been removed. Thanks.
On Thu, Nov 16, 2017, at 02:34 PM, Clinton Work wrote:
> Can a Verizon AS701 contact me to discuss why you are advertising BGP
> routes for the following TELUS AS852 address space. I tried to open a
> ticket with your IP NOC, but you won
BGP communities I use the most:
- Influence the transit provider BGP local-preference: customer preferred,
customer backup, peer, and transit LP values
- Only advertise routes to the transit provider customers and not their peers
- Don't advertise routes to transit providers' peer ASx.
- AS-p
x27;t share event traffic predictions. I reached
out to Akamai before the 2014 Winter Olympics and they wouldn't share
anything.
--
Clinton Work
Airdrie, AB
On Sun, Jun 8, 2014, at 03:48 PM, Alvaro Pereira wrote:
> In Canada, the last Winter Olympic Games were streamed from
> olympics.
BRAS functionality would normally be large scale DHCP or PPPoE customer
termination handled by RADIUS for authentication and policy management.
On Fri, Aug 14, 2015, at 11:00 AM, Baldur Norddahl wrote:
> I have a related question. What functionality defines BRAS?
>
> I do not think I have any
The ALU 7750 MS-ISA card can handle 10Gbps of NAT64 traffic and supports
464XLAT as well.
On Thu, Aug 20, 2015, at 07:44 AM, Jawaid Shell2 wrote:
> Who out there is using production-scale NAT64? What solution are you
> using?
If you use separate VLANs for each customer then the CPE router doesn't
even require an external IPV6 address for DHCPv6-PD. IPV6 link-local
addresses can be used between your BRAS and customer CPE router. Some
CPEs can even allocate a WAN/mgmt IPV6 address out of the delegated
subnet via DHCPv6-
Granted that having the CPE request both a IA_NA and IA_PD is a more
common configuration. Some of the CPEs using only DHCPv6 PD can
allocate a /64 out of the delegated /48 for WAN address & management.
The IPV6 traceroute is not broken with the DHCPv6 PD only configuration.
On Wed, Sep 9, 20
n NANOG
knows a technical contact at Enterprise.
--
Clinton Work
Many transit providers support BGP communities to modify how your
announced routes are treated within their network. A quick search shows
that AT&T supports BGP community 7018:70 to lower the default local-pref
100 down to 70 (below peer routes). If you tag your AT&T announced
routes with BGP comm
The NLNOG RING servers would be good targets and they expected to get
pinged.
https://ring.nlnog.net/participants/
On Thu, Jan 7, 2016, at 08:34 AM, Brian R. Swan wrote:
> I’m setting up smokeping to try and gather some latency statistics on my
> ISP to different parts of the world. Does there
IPV6 connectivity to fireball.acr.fi is failing inside Cogent AS174. I
have already contacted the Cogent NOC, but I haven't heard anything back
yet. I'm wondering if somebody else with Cogent IPV6 connectivity can
run some tests. IPV4 connectivity is working fine.
--
Clinton Work
I can reach fireball.acr.fi on TCP port 80 so it looks like Cogent is
just filtering or dropping IPV6 traceroute packets.
Thanks for checking connectivity from other locations.
--
Clinton Work
Calgary, AB
On Sun, Nov 3, 2013, at 01:38 PM, Andrew Fried wrote:
> From AS54054 in Ashburn, V
I should have stated that I tried icmpv6, UDP, and TCP traceroute with
the same results. Looks like Cogent is not returning TTL expired IPV6
packets within their core. I can only guess that this is a result of
using 6PE and propagating the IPV6 TTL into MPLS.
Clinton
On Sun, Nov 3, 2013, at
29 matches
Mail list logo
