On Sun, Sep 09, 2018 at 01:17:40PM +0000, Tim Jones wrote:
> Hi,
>
> I'm working with something in a lab environment at the moment, testing out
> OpenBGPD to see if it can replace "something else" on an internal network.
>
> I have three OpenBSD instances (A <->B<->C), and whilst B is learning routes
> from C, it is not pushing them out to A, no matter how relaxed I make my
> filters.
>
> On the other hand, going in the other direction, C is learning the default
> route sent by A without problems.
>
> This is on OpenBSD 6.3.
>
> $bgpctl sho nei A-1
> Update statistics:
> Sent Received
> Updates 0 1
> Withdraws 0 0
> End-of-Rib 1 1
>
> $bgpctl sho nei C-1
> Update statistics:
>
> Sent Received
>
> Updates 1 1
>
> Withdraws 0 0
>
> End-of-Rib 1 1
>
>
> $ bgpctl sho ri nei C-1
> *> 198.51.100.164/32 198.51.100.164 100 0 64555 i
>
> AS 64515
> router-id 192.0.2.97
> socket "/var/www/run/bgpd.rsock" restricted
> rde med compare always
>
> # network inet connected # I have tried both with and without this line
>
> group "A_NETS" {
> neighbor 192.0.2.122 {
> descr "A-1"
> remote-as 64500
> local-address 192.0.2.121
"announce all" is probably missing here, since the default in 6.3 was
"announce self" and so transit routes would be filtered.
> }
> }
> group "C_NETS" {
> neighbor 198.51.100.164 {
> descr "C-1"
> remote-as 64555
> local-address 198.51.100.252
> announce default-route
> }
> }
> match from any set { origin igp }
> allow from any
> deny to any
> allow to any prefix 198.51.100.164/32
> allow to any prefix 203.0.113.0/24 prefixlen >= 24
> allow to group "C_NETS"
>
--
:wq Claudio
