And, of course, routes you add outside of the CLI aren't known to XORP. If
you add the route using protocol static you can then redistribute via
OSPF.
Justin
On Jan 8, 2008 11:57 AM, Jonathon Exley [EMAIL PROTECTED] wrote:
I have also had problems exporting connected routes into OSPF.
Try adding static routes into the export policy:
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] show configuration policy
policy-statement ExportCon
term 10 {
from {
protocol: connected
}
then {
action: accept
}
}
term 20 {
from {
protocol: static
}
then {
action: accept
}
}
This seemed to allow the connected interfaces into the OSPF database,
although they were tagged with ASExt-2:
[EMAIL PROTECTED] show ospf4 database
OSPF link state database, Area 0.0.0.0
Type ID Adv Rtr Seq Age Opt Cksum
Len
ASExt-2 *192.168.2.0 192.168.101.10x8001 790 0x2 0x4354
36
Jonathon
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
