1st question why do you have a static route pointing to your local
ip_address as the next hop? Vyatta should learn this as a connected
route, no other static entry would be needed.
2nd you do realize if this config is right, that your /30 BGP speaker
addresses are "within" the /27 network that's being annouced? Can your
provider not give you a separate /30 address for peering ?
Here's what I would do with the export policy filter
> policy-statement myloc {
> term 1 {
> from {
> protocol: "connected"
> network4: 1.1.1.0/27
> }
> then {
> action: "accept"
> }
> }
> }
3rd, does you upstream have any bgp prefix-list or route-maps enable ?
( have them do a "show ip bgp neigh 1.1.1.8 " and send the output ) It
will tell you right off any type of BGP filters are applied and then
go from their.
Lastly, all of your ?????????????????? are making it hard to review the
output ;)
_______________________________________________
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
