ER811 WAN Configuration with Multiple Static IP Addresses and Virtual Server Port Forwarding
ER811 WAN Configuration with Multiple Static IP Addresses and Virtual Server Port Forwarding
I recently bought my ER811 and am working on configuring it for the first time. My small business network has 5 static IPv4 addresses from Verizon; Verizon tells me that IPv6 addresses are still unavailable. My network has a number of small devices using DHCP, and two physical servers that require use of a static IPv4 address for accessibility to and from the public Internet.
I've configured the WAN-SFP+ port to use the first static IPv4 address from my block. I added the remaining 4 addresses to this same WAN port as WAN aliases. The remaining ports are configured as LAN ports.
I've configured multiple virtual servers for the ports I need to have forwarded to the two servers. For example, I configured one virtual server to forward tcp/80 from the first WAN alias address to the static private address for the first server. I configured a second virtual server to forward tcp/80 from the second WAN alias address to the static private address for the second server. I repeated this process for the other ports I need to forward, including SMTP, SSH, HTTPS, etc.
The "number of small devices using DHCP" are all connected to a NETGEAR GS116 switch. I'll have that switch connected to one of the ER811's LAN ports. I'll have the two servers each connected to an ER811 LAN port. For now, I've done all of the ER811 configuration in standalone mode because I want to minimize downtime when I replace my old router with this setup.
Will this setup work? Can I expect my devices that use DHCP to access the Internet using the first static IPv4 address from my assigned block, the first server using the second address, and the second server using the third address?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I didnt recommend One:One NAT for his use since to enable bidirectional traffic both in and out, using that function would totally expose the internal IP to the internet in its entirety, since for the response to come from that IP you would have to enable DMZ for each mapping.
I still recommend the multiple WAN with policy routing for the internal IPs, and simple port forwarding for inbound access through the firewall, and letting the firewall use its stateful rules for return traffic through the policy routed WAN
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 281
Replies: 11
Voters 0
No one has voted for it yet.
