- Products
- Network Security
- Threat Protection
- Secure Access Service Edge (SASE)
- Cloud Security
- Endpoint Security
- Email Security
- Secure Access
-
Wi-Fi 6 Access Points
SonicWall SonicWave 600 series access points provide always-on, always-secure connectivity for complex, multi-device environments.
Read More
- Solutions
- Industries
- Use Cases
- Solutions Widgets
- Solutions Content Widgets
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
- Solutions Image Widgets
-
- Partners
- SonicWall Partners
- Partner Resources
- Partner Widgets
- Custom HTML : Partners Content WIdgets
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
- Partners Image Widgets
-
- Support
- Support
- Resources
- Capture Labs
- Support Widget
- Custom HTML : Support Content WIdgets
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
- Support Image Widgets
-
- COMPANY
- PROMOTIONS
- MANAGED SERVICES
- Contact Sales
-
- Menu
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
How can I add static routes in Email Security appliances?
03/26/2020 
1,038 People found this article helpful
198,870 Views
Description
How To Add Static Routes in Email Security Appliances
Resolution
Question:
How to add static route in ES appliances?
Login to the ES via SSH with putty (snwcli@IP-from-ES) and enter help route to display the syntax :
EXAMPLE:
SNWLCLI> help route
route [{--add <target> --destination <destination>|--remove <index>}]
With no arguments displays route. With --add, adds a route where target is a host as IP, a net as IP/CIDR, or "default", and destination is an interface name or a gateway IP With --remove, removes a route specified by index number.
SNWLCLI>route --add 192.168.100.0/24 --destination 10.71.20.251
SNWLCLI> route
Index Target Destination
----- ------ -----------
1 default 10.71.20.254
2 192.168.100.0/24 10.71.20.251
SNWLCLI> route --remove 2
SNWLCLI> route
Index Target Destination
----- ------ -----------
1 default 10.71.20.254
SNWLCLI>
route [{--add <target> --destination <destination>|--remove <index>}]
With no arguments displays route. With --add, adds a route where target is a host as IP, a net as IP/CIDR, or "default", and destination is an interface name or a gateway IP With --remove, removes a route specified by index number.
SNWLCLI>route --add 192.168.100.0/24 --destination 10.71.20.251
SNWLCLI> route
Index Target Destination
----- ------ -----------
1 default 10.71.20.254
2 192.168.100.0/24 10.71.20.251
SNWLCLI> route --remove 2
SNWLCLI> route
Index Target Destination
----- ------ -----------
1 default 10.71.20.254
SNWLCLI>
NOTE: The following limitations when adding a route:
- No CIDR like 192.168.200.32/26
- Only supported netmasks are 8/16/24-bit
Related Articles
- Network Security Essentials eLearning Training Course
- How do I check if syslogs are getting forwarded by an Email Security Appliance?
- How to add inbound path in Hosted Email Security
YES
NO