Comments

  • Yup, that is the problem. Apparently whatever mix of attempts I was trying was not working. For whatever reason, not saying it's wrong, but the default route in WGs is apparently an AD of 5. Getting Quagga (which I am not super familiar with) to change the BGP AD to less than 5 was sure making me feel dumb. Anyway, I think…
  • Hi Robert, Thats the opposite of what I want to do. I was trying to find the right verbiage to explain I want to have those imported default routes get ahead of the built in default routes in the WG. Maybe that should have been my first question. Is what is the process that takes an external interface and turns it into a…
  • Thanks. That gives me enough to work with and bring back to the people that know the WGs much better than I do. I appreciate the help.
  • Alright, so trying to think this through a bit. I assume the issue is asymmetric routing. Say someone on the Internet wants to get to 50.50.50.50 which is assigned to a server at my branch office. The route comes in via BGP to my data center, I have routes for 50.50.50.50 in my core routers pointed at my WG. I put some…
  • Assign a /24 to internal devices at the branch office The /24, and it doesn't have to be a /24 (more than likely just a few /29s,) but a subset of the /22 would be used for public IPs at the branch office... assigned to servers and other network devices at the branch office.