Nathan, I'm carbon copying the Ubnt Users list for the benefit of everyone.
Short Answer: You need a valid routing table entry for the network you're advertising. Just specifying the networks to advertise via BGP is not enough. Say you have a /22 that you want to advertise: If you don't have that entire /22 on a single interface, you won't have the /22 prefix in your routing table. Instead you'd have whatever smaller networks (longer prefixes of /23 or /24, etc) in your routing table. At that point you'd need to add a static route so you aggregate the smaller networks into the full /22. Until you add what EdgeOS calls a blackhole route (type=blackhole on MikroTik RouterOS and null route on Cisco IOS), your router doesn't meet BGP criteria (you'd see the route should not be valid * and best > on your router when showing bgp routes) for advertising the /22 to its peers. Interesting that pointing the route to the router's own IP address worked. With the new routing stack changes in 1.8.0 for EdgeOS, Ubnt removed Quagga and created a "proprietary routing stack" that EdgeOS uses now. That may explain the changes in behavior between versions... Regards, Mike On Wed, 2016-08-03 at 11:10 -0600, Nathan Babcock wrote: > Mike, > > We performed the upgrade this evening and discovered what changed > during the upgrade, We have the networks explicitly identified as far > as I understand it but no traffic would pass. Pulled up the config of > the now upgraded router, and discovered that our static routes that we > configured were no longer present. Attempted to re-add them and got > the following error: > > > Nexthop address cannot be same as own interface address(later learned > we are supposed to be using blackhole routes for this) > > > > We did have the route pointing to the routers own public interface > which is where we need it to go, but apparently not able to do this > any longer with the new version. As for what we are advertising, we > are only advertising our static routes and nothing more. With that, > we have three items being sent to our upstream provider even though we > have 70 entries on that routers route table. > > > > I did find this site, which solved everything for me as I am now > working correctly, and have a much better understanding of how to > setup bgp for a single upstream provider then when this all started: > http://www.networknoob.net/category/bgp/ > > Your information was a good first step and after my research it looks > like i have it all working correctly now, and am advertising the right > networks and nothing more. What i didnt truly understand and not sure > i entirely do, is why do i have to create the static route and specify > the network in the bgp policy for the ASN? Shouldnt specifying the > network in the BGP ASN be sufficient? Until i put in the static > routes, our router would not advertise any routes. > > > > On 8/1/2016 8:58 AM, Michael Bear wrote: > > > > > Nathan, > > > > You already have "network X.X.X.X" statements for two networks. > > If you can't redistribute then one option is to add explicit bgp network > > statements. > > > > Your BGP RID is the same as your peer's IP address, hopefully this is a > > typo when obfuscating your IP addresses. > > > > I'm surprised you aren't filtering your announcements with a route-map > > and/or prefix-list. Might look and see what you're advertising to your > > upstream (potentially a bunch of cruft without prefix-list/route-map > > when using redistribution). > > > > show ip bgp neighbors Z.Z.Z.Z advertised-routes > > > > If you need route maps, they're nested under "policy". > > set policy route-map <NAME> > > set policy prefix-list <NAME> > > > > set protocols bgp 53000 neighbor Z.Z.Z.Z route-map <NAME> > > run clear ip bgp neighbors Z.Z.Z.Z soft out > > run show ip bgp summary > > run show ip bgp neighbors Z.Z.Z.Z advertised-routes > > > > Syntax appears to be similar, but now that Brocade and VyOS are separate > > Vyatta code-bases I wouldn't bet on it. > > http://www.brocade.com/content/dam/common/documents/content-types/configuration-guide/vyatta-routingpolicies-3.5r3-v01.pdf > > > > Hope that helps. > > Regards, > > Mike > > > > On Sun, 2016-07-31 at 22:26 -0600, [email protected] wrote: > > > > > I am rather green to BGP setups, and need to upgrade our edge router. > > > PResently we are using redistribute static routes to advertise our > > > networks. As I am sure you know, with 1.8 that is now deprecated. I > > > need assistance in how to configure our BGP session post 1.8 so that > > > we can continue to work. > > > > > > set protocols bgp 53000 neighbor 71.10.13.42 description Plateau > > > set protocols bgp 53000 neighbor 71.10.13.42 remote-as 21782 > > > set protocols bgp 53000 neighbor 71.10.13.42 soft-reconfiguration > > > inbound > > > set protocols bgp 53000 network 70.11.128.0/21 > > > set protocols bgp 53000 network 19.8.146.0/22 > > > set protocols bgp 53000 parameters log-neighbor-changes > > > set protocols bgp 53000 parameters router-id 71.10.13.42 > > > set protocols bgp 53000 redistribute static > > > > > > Will anyone tell me how i need to go about changing that over to a > > > route map so we can upgrade our firmware? All id's and ip's have been > > > changed to keep the children safe. > > > _______________________________________________ > > > Ubnt_users mailing list > > > [email protected] > > > http://lists.wispa.org/mailman/listinfo/ubnt_users > >
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
