Nick,
I appreciate the explanation and example, and agree with that as a very strong
recommendation.
Reading Noction's IRP Lite documentation
(https://www.noction.com/wp-content/uploads/2016/09/irp-lite-documentation.pdf)
- page 214, with bgpd.as_pathset to "5 4 2 3" by default (table below),
Ryan-
Unfortunately it doesn't appear that you have a solid understanding of core
BGP fundamentals.
I suggest starting with a read of RFC4271.
Have a great weekend and holiday season.
On Fri, Dec 6, 2024 at 1:19 PM Ryan Hamel wrote:
> Tom,
>
> The automotive industry has normalized "syntheti
On Fri, Dec 6, 2024 at 11:03 AM Nick Hilliard wrote:
> Including - as an example of only of the harmful effects of this
> practice
Hi Nick,
There is consequence to resisting standards work in an area of need
just because you're broadly opposed to the technology being used that
way in any capacit
Ryan Hamel wrote on 06/12/2024 17:32:
That said, I can argue that upstreams not filtering their customers
properly removes a safety guard, upstreams not implementing RPKI removes
a safety guard, not properly prepending communities on synthetic routes
to drop them on export again removes a safet
Tom,
The automotive industry has normalized "synthetic". It's motor oil that is
artificially created, vs pulled out of the ground and refined. It's a perfect
analogy for routes that were created by third-party software, vs organically
created/redistributed from the proper AS.
Ryan Hamel
>
> not properly prepending communities on synthetic routes
Let's not normalize 'synthetic route' as a term. It's not a thing that
exists.
On Fri, Dec 6, 2024 at 12:32 PM Ryan Hamel wrote:
> Nick,
>
> I understand there are rules and unspoken guidelines/rules for the DFZ,
> but when it comes
* r...@rkhtech.org (Ryan Hamel) [Fri 06 Dec 2024, 18:46 CET]:
William,
Exactly! An example below is where operators/orgs do not have the
funds for a full table router deployment and gather top talkers from
sFlow, which says what routes are to be installed in TCAM, instead
of hitting a default
This is an automated weekly mailing describing the state of the Global
IPv4 Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to bg
William,
Exactly! An example below is where operators/orgs do not have the funds for a
full table router deployment and gather top talkers from sFlow, which says what
routes are to be installed in TCAM, instead of hitting a default route.
https://blog.sflow.com/2015/07/sdn-router-using-merchant
Nick,
I understand there are rules and unspoken guidelines/rules for the DFZ, but
when it comes to each individual AS, that org/operator can run their AS
internally however they please, and maybe they have considered the risks you
have mentioned.
That said, I can argue that upstreams not filte
On Fri, Dec 6, 2024 at 8:34 AM Nick Hilliard wrote:
> BGP ensures loop-free interdomain path computation by inspecting the AS
> path of each NLRI. If a routing optimiser rewrites all the AS paths for
> all the NLRIs it receives, then it's just pooped all over the primary
> component of BGP that's
Ryan Hamel wrote on 05/12/2024 23:45:
What does "these devices don't follow standard BGP behaviors" have to do
with adding a NO_EXPORT or specific community on the import policy when
a route is accepted, and being belt & suspenders with matching those
communities to drop those routes on export
*** VIDEO 🔥 Relive the Action – NANOG’s Last Meeting's Recap is Here!*
*Watch the NANOG 92 Recap Now*
*Did you attend NANOG 92 in Toronto (21-23 Oct.) or did you miss out?*
Either way, you need to see what happened at NANOG’s last meetin
The reason high voltage and low voltage aren’t permitted to share a
conduit is safety. Chafing/rub outs that would energize low voltage
cable and devices with high voltage aren’t protected against in the same
way that a high voltage to high voltage short would be. It’s a low
likelihood/high c
On 12/6/24 10:31, Saku Ytti wrote:
In the EU at least you cannot do that, you can't use the same conduits
for data and power. But it's been in the code for a long time now to
have ethernet upon delivery, both CAT6a (rooms) and fiber (just a
single place is enough, I think).
I am using after-
On Fri, 6 Dec 2024 at 05:30, Mark Tinka wrote:
> I ran Ethernet to every room, some of it using STP through conduits crossing
> the roof to get across one end of the house to the other. It helped me avoid
> wireless extenders and meshing technologies.
In the EU at least you cannot do that, you
16 matches
Mail list logo
