Just had one of those lightbulb moments while setting up a new site-to-site for a client and wanted to share. We were trying to route specific subnets over a VPN to a cloud VPC, but the existing BOVPN tunnel configuration felt a bit rigid for the traffic flows we needed.
Turns out, using BOVPN virtual interfaces is the game-changer here! Instead of being limited to the tunnel's defined local and remote gateways, you can create a virtual interface (like `vif1000`) tied to the tunnel. This lets you:
* Apply more granular firewall policies to the traffic.
* Use it as a gateway in static routes for super precise control.
* Handle scenarios where you have overlapping IP spaces or need policy-based routing.
For example, I set up a virtual interface for the tunnel and then created a static route sending only the 10.10.50.0/24 subnet over that `vif1000` gateway. The rest of the traffic for that remote site uses a different path. It made the rule set so much cleaner and easier to manage than trying to force everything through the traditional tunnel definition.
Anyone else using virtual interfaces for creative routing? I'd love to hear how you're applying them, especially if you've integrated them with dynamic routing protocols or SD-WAN scenarios.
– Julie
Data-driven decisions.