[Xorp-users] Problem with filtering BGP

Peter Maersk-Moller peter@maersk-moller.net
Tue, 04 Apr 2006 03:33:40 +0200


Hi

I'm trying to export a few networks to all my external BGP peers
and import all their advertised routes. However all received
routes on ebgp are not included into the internal (final) routing table.
So obviously I'm doing something wrong, but what ?

Here is my policy.

The list "tobeincluded are the networks to be announced to ebgp peers.
I do receive a lot of announcements from peers, but none of them ends
up in the final table and subsequenly can't be seen by the unix
command # route -n

What am I doing wrong ?

The term drop is used to make sure I don't advertise to ebgp peers
any routes learned from other ebgp peers, but obviously my policy fails.

What should I do instead ?

Kind regards

--PMM

policy {
     network4-list tobeincluded {
         elements: "83.137.32.0/24,83.137.33.0/24"
     }
     policy-statement bgpconnected {
         term acceptown {
             from {
                 protocol: "connected"
                 network4-list: "tobeincluded"
             }
             then {
                 accept
             }
         }
         term drop {
             from {
                 protocol: "bgp"
             }
             then {
                 reject
             }
         }
     }
}
protocols {
     bgp {
         bgp-id: 192.38.7.16
         local-as: 31397

         /* export: "static" */
         export: "bgpconnected"
.....


-- 
+----------------------------------------------------------+
| Kabel-TV over Internettet   --   http://www.streamtv.dk/ |
+----------------------------------------------------------+