Hi all,
How can I inject a default route from BGP protocol ?
My FusionHub Virtual appliance needs to inject a default route to AWS Transit Gateway (using Transit Gateway Connect).
The BGP peering is IP but I need to inject a default route.
May I know the use case for the default ? We cannot simply inject 0.0.0.0/0 route due to the security concerns. Beside that, AWS TGW may not accept such route if the feature is applicable.
Would you please share your network design for such route ?
@sitloongs , I think you are wrong, It’s possible to inject default route into AWS Transit gateway.
By the way, I currently writing a doc about the integration between Azure Route server and Peplink like
If you check the following document, it would be nice to inject a default route (from the FH to the ARS) for OUTBOUND traffic to the Intternet. If the the primary FH fails, the traffic will be forwarded to the remaining FH appliance…
If it’s not resolved yet, i’d be happy to help. For your default route, it’s only possible to do from the AWS side. You need to create the 0.0.0.0/0 route on the TGW’s Route table and then have it point towards your FusionHub’s VPC. It’s something I too struggled with and have since made a guide for as well as will be speaking on at the Peplink Tech Summit this November. Feel free to reach out if you have any questions!