I'm trying to help a friend with a bgpd problem and I'm cutting down the
bgpd.conf more
than I normally would because I'm prepping for a serious eye operation and I
don't have
the time to edit the entire file to make it impervious to unwanted viewers.
Here are what I think illustrates the problem and the pertinent parts of the
conf.
<BOF>
network A.B.C/21
nexthop qualify via bgp
neighbor $LowPri {
remote-as *****
descr "LowPriv4"
passive
set prepend-self 8
set prepend-neighbor 8
announce self
announce IPv6 none
neighbor $Best {
remote-as ******
descr "Bestv4"
passive
set weight 0
set prepend-self 2
set prepend-neighbor 2
announce self
announce IPv6 none
<EOF>
$Best is a high reliability, reasonable priced neighbour.
The $LowPri neighbour has an upstream peer neighbour which refuses to honour
prepends or any other means of making it a path of lower priority.
There has been a suggestion that $Best should be seeing the /21 as two /22s
which would
make it a more preferable path.
Any suggestions?
I don't like unaggreated net blocks and I don't know how to modify the bgpd
config to do
that either.
My mother would have said: "When needs must, the devil drives!"
Questions may have a slow response whilst I'm being treated. I <may> see them
but be
unable to reply promptly.
TIA,
/Rod/
*** NOTE *** Please DO NOT CC me. I <am> subscribed to the list.
Mail to the sender address that does not originate at the list server is
tarpitted. The reply-to: address is provided for those who feel compelled to
reply off list. Thankyou.
Rod/
---
This life is not the real thing.
It is not even in Beta.
If it was, then OpenBSD would already have a man page for it.
