We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Redirect Traffic between Multiple Virtual Router Instances

  • Last updated on

Virtual routers handle traffic on network paths that are isolated from paths handled by other routers. In certain situations, however, you might need to redirect traffic from one virtual router to another. You can redirect traffic by modifying the access rule that is directly associated with the corresponding virtual router instance.

The following example demonstrates how to redirect requests originating from the private network 192.168.0.0/24 (eth2) handled by the virtual router VR01 to the interface that is connected to the Internet (e.g., eth1) and handled by the default router. To do so, the existing access rule that forwards traffic from eth2 to eth3 must be modified.

vr_redirect.png

Before You Begin

You must have already configured an additional virtual router instance. For more information, see How to Configure and Activate a Virtual Router Instance with Hardware, Virtual, VLAN, or Bundled Interfaces.

Step 1. Modify the Access Rule to Redirect Traffic

  1. Go to CONFIGURATION > Configuration Tree > Virtual Servers > your virtual server > Assigned Services > NGFW (Firewall) > Forwarding Rules.
  2. Click Lock.
  3. Locate the access rule that handles the traffic flow from eth2 to eth3, e.g., VRF-Classroom1-to-INTERNET.
  4. Double-click the access rule to open it for modification.
  5. From the list Destination VR instance, select default.
    vrf_modify_access_rule_to_redirect_traffic.png
  6. Click OK.
  7. Click Send Changes.
  8. Click Activate.

Step 2. Verify that Traffic from the Private Network is Redirected to the Default Router

Verify that the Internet is connected to the public interface that is handled by the default router, e.g., eth1. Also verify that your client PC is connected to the private network 192.168.0.0/24 and the default route points to 192.168.0.254 (eth2 on the firewall).

  1. Go to FIREWALL > Live.
  2. The Live view will display a mixture of traffic flowing both through the default router and the virtual router you configured earlier, e.g., VR01.
  3. Click +.
  4. From the list, select Src. VR Instance.
  5. For the filter Src. VR Instance, enter VR01.
  6. From the list, select Dst. VR Instance.
  7. For the filter Dst. VR Instance, enter default.
    vrf_create_filter_for_redirected_traffic.png
  8. Create traffic on your client by requesting a website, e.g., www.nytimes.com
  9. Check traffic flowing between your private network (eth2, 192.168.0.1) and the Internet (eth1).
    vrf_traffic_check_for_redirection.png

You firewall is now redirecting traffic from virtual router VR01 to the default router.

Last updated on