I added a simple "custom_options" field to /usr/local/pkg/openbgpd.xml and the
corresponding code to /usr/local/pkb/openbgpd.inc - although the modifications
are trivial, is there a correct way to submit a patch? (BTW: the $config
mechanism, coupled with the XML description files, looks quite simple - I'm
very happy it was that easy to customize the configuration page!)
Anyway, after adding "deny from all prefix { 192.139.69.160/28 }" to bgpd.conf,
I no longer see the particularly bizarre behaviour previously described.
Instead I now see new bizarre behaviour :-).
Although I have "fib-update yes", the system routing table never fully fills at
startup.
# netstat -rn | wc -l
8781
# bgpctl show fib | wc -l
11147
If I do a "bgpctl fib decouple", wait a minute for bgpd to finish complaining
about all the routes that "vanished before delete", and then run "bgpctp fib
couple" things seem to sync up correctly.
Killing and restarting bgpd reproduces the same behaviour - it's not just at
boot.
After the decouple/couple commands, things look better:
# netstat -rn | wc -l ; bgpctl show fib | wc -l
10332
10340
I don't know enough about BSD networking internals to know where to start on
this one!
Thanks,
-Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Commercial support available - https://portal.pfsense.org
