Hello Insan, I guess I'm not sure I understand that statement, or I'm miss-interpreting the rdomain configuration section and how it interacts with rtables. If I understand the documentation correctly additional rib tables defined in bgpd must exist inside the default routing domain. The error messages read as if I missed a step and need to create the additional routing table some how, which I'm having trouble finding how to do that. Are you suggesting I add a rdomain section in bgpd.conf in to create the rtable?
On Tue, Jul 19, 2011 at 4:40 PM, Insan Praja SW <insan.pr...@gmail.com> wrote: > Hi, > > You missed rdomain. > On Wed, 20 Jul 2011 01:26:37 +0700, Josh Hoppes <josh.hop...@gmail.com> > wrote: > >> I'm trying to configure bgpd to run in an alternate routing table so I >> can use it to manage black holed prefixes. When trying to specify an >> alternate routing table I get the error message "rtable id 1 does not >> exist" when starting bgpd. I've gone through route(8) and route(4) but >> can't find any information on creating a routing table. My attempts at >> creating by just adding a prefix appear to be of no use. I'm sure I >> missed something in the documentation and I would appreciate any hints >> people can provide. >> >> This is on OpenBSD 4.9 GENERIC.MP#819 amd64 >> >> Basic bgpd.conf I'm using >> >> # global configuration >> AS 65100 >> fib-update no >> route-collector yes >> holdtime 10 >> >> # Alternate Routing Table >> rtable 1 >> >> Error output from bgpd: >> >> # bgpd -vnf bgpd.conf >> bgpd.conf:8: rtable id 1 does not exist >> >> error output from route: >> >> # route -T 1 add -inet 192.168.0.0/24 127.0.0.1 >> route: routing table 1: No such file or directory >> >> Thanks in advance, and sorry for the noise. >> > > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/