There are many use cases for SD-WAN these days and Riverbed is attempting to answer them with their Steel Connect product line. When we implemented it in a tiny bureau in Temecula, California, we wanted to make use of a Steel Connect SDI-130 gateway facilities as my usually corner router. To accomplish this, a gateway not usually indispensable to act as a hovel endpoint for other sites, though it also needs to concede and control inbound entrance from a internet to a mail and web server that’s onsite. This means a gateway indispensable to support NAT. Fortunately it does. In this essay we will cover how to configure NAT and capacitate inbound entrance on a Riverbed SD-WAN resolution famous as Steel Connect.
Configuring Inbound NAT Rules
The pattern of Static NAT in a Riverbed Steel Connect Manager uses some vernacular that was a small opposite than what we competence be used to if we come from a Cisco world. Normally we would configure Static NAT along with an inbound ACL as dual apart configurations on a Cisco ASA. In a Riverbed resolution we configure an inbound order though there’s a bit some-more to a setup that configuring a NAT rule. The high-level routine is as follows:
- Register your server device.
- Create a device form focus for email. (Only device form applications can be used in NAT rules.)
- Create a inbound NAT rule.
Register your Server
In my demo topology, we have an Apple Mac Mini regulating a server app. The server app has several services that could be enabled, however, in this box we’ve enabled a email server application. Once that is in place, that we am presumption we have already done, we need to register a a server inside a Steel Connect Manager so that it can be comparison in a NAT rule.
Create a Device Type Application
The subsequent step would be to emanate a device form application. This is a tradition focus that you’ll use to conclude a authorised incoming ports. In Riverbed’s resolution we don’t indeed write ACL statements to control inbound access. Everything is blocked until we supplement a order to permit.
Start by navigating to a list of tradition applications:
And afterwards supplement a new tradition application.
Note that we need to mention a focus form as “device” and a choice to extent pier numbers. This allows we to enter a list of ports distant by commas. You can entrance this choice underneath a dump down that is defaulted to “All protocols and ports.” Also, we need to name a server device that we registered.
Define a NAT Rule
Now that we have all in place we can emanate a NAT rule. Creating a NAT order also creates an inbound ACL entrance to assent a inbound traffic.
Start by navigating to RulesInbound Rules(NAT).
Next, name a New Inbound Rule button.
Upon formulating a new inbound order you’ll name a Application that we created, a uplink, a mode (DNAT), and we can determine a ports that should automobile populate.
At this indicate we should have a operative inbound NAT order that would concede email to your server. There are a few things that will need to be cared for outward of this configuration, namely a DNS pattern for a email domain, MX annals and so on. Assuming this is all in place, you’re prepared to go with inbound entrance to your Riverbed Steel Connect gateway regulating NAT.
So to determine a bit of this configuration, we can initial demeanour during your Apple Server to make certain that it’s rightly configured to permitting inbound mail connectivity.
Finally, send a exam summary and we’ve got inbound connectivity by a Riverbed SD-WAN solution.
Closing Thoughts
This setup was a bit fiddly though mostly given we was regulating a Apple server for testing. If sell were used, this would have been most easier given a ports are good documented. Apple does put out a list of ports that are used, though it’s not damaged down well. At any rate, a purpose is clearly to illustrate that we can in fact use a Riverbed SD-WAN resolution as your primary network gateway and concede inbound entrance to services.
Also see:
Getting started with Uncomplicated Firewall
How to register an ASA SFR procedure with a FirePOWER Management Center
How to supplement an AirPort Express to an AirPort Extreme to extend wireless networks
How to supplement a L2TP VPN choice to NetworkManager in Linux
Article source: http://www.techrepublic.com/article/how-to-configure-nat-and-enable-inbound-access-on-the-riverbed-sd-wan/#ftag=RSS56d97e7