On Thu, Oct 20, 2022 at 6:23 AM Jon Lewis wrote:
> [...]
> While writing this though, two things occurred to me.
>
> 1) Are there any networks with routing policy that looks at prepends and
> says "if we see a peering path with >X number of prepends (or maybe
> just path length >X),
>
> 1) Are there any networks with routing policy that looks at prepends and
> says "if we see a peering path with >X number of prepends (or maybe
> just path length >X), demote the localpref to transit or lower"? "i.e.
> They obviously don't want us using this path, turn it into a
WATANAPONGSE
Cc: nanog@nanog.org
Subject: Re: Newbies Question: Do I really need to sacrifice Prefix-aggregation
to do BGP Load-sharing?
WARNING!! This message originated from an External Source. Please use proper
judgment and caution when opening attachments, clicking links, or responding to
this email
On Thu, Oct 20, 2022 at 5:13 AM Pirawat WATANAPONGSE via NANOG
wrote:
> I have considered the prepending myself, but dare not implement it yet
> for the fear that BGP (Human) Community will burn me alive, witch-hunt style,
> because of the following reasons:
> 1. I can see from looking glass(es)
On Thu, 20 Oct 2022, Tom Beecher wrote:
1. Prepending by itself isn’t bad. Prepending past the point that it is
effective in accomplishing anything is what you generally want to avoid. Even
then, it’s not nearly
as big a deal as some make it out to be in most cases.
To me, it's somewhat
1. Prepending by itself isn’t bad. Prepending past the point that it is
effective in accomplishing anything is what you generally want to avoid.
Even then, it’s not nearly as big a deal as some make it out to be in most
cases.
2. De-aggregation has it’s uses and it’s place. Have a /20 , but
If your Upstream(Transit provider) prepends your routes without you asking
or authorizing it to do so, you should SERIOUSLY consider switching
providers!
In the other email I talked about traffic engineering BGP communities.
If those prepends were made from some community you were applying... OK,
Dear all,
Before all else:
thank you all for the lightning-fast responses (even taking the time zone
advantage into account).
I really, really, really appreciate all your recommendations.
Virtually all of you recommend prepending as the first choice.
I also get the feeling that you guys
I imagine it's an ISP you are talking about, where the traffic is mostly
inbound.
Hire transit companies that have good traffic engineering community
policies.
- Selective prepending or seletive no-export by:
-> Type of peer.
-> Geographic location of their routers.
-> ASN specific.
And then you
On 10/18/22 23:27, Pirawat WATANAPONGSE via NANOG wrote:
Dear Guru(s),
My apologies if these questions have already been asked;
in that case, please kindly point me to the answer(s).
I hope the following information sufficiently describes my current
"context":
- Single customer: ourselves
-
The inbound traffic will be determined by how the Tier 1’s decide to route, as
you are observing they will pick either you or your other upstream. Traffic
engineering as the Tier 3 carrier you have described has this kind of
unexpected traffic routing. As you have obviously already tried
On Tue, Oct 18, 2022 at 11:27 PM Pirawat WATANAPONGSE via NANOG
wrote:
> - Two upstreams (See the following lines), fully cross-connected to our
> gateways
> - One (pure) commercial ISP
> - One academic consortium ISP (who actually uses the above-mentioned
> commercial ISP as one of its
12 matches
Mail list logo
