NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
starion
Mar 03, 2013Aspirant
Multiple static IP's on FVS-318N
I have multiple static IP's from my internet provider. At the moment, I have various publicly available servers simply plugged into a five port hub off the cable modem and one of the static IP's set...
starion
Apr 08, 2013Aspirant
Okay, I think this whole thing has gotten muddled and way off track. Let me try to explain it a different way and with more detail.
I have a group of static IP's from our ISP. The first IP is assigned to the ISP/Wan settings of the FVS-318N, lets just call it xxx.xxx.xxx.82
I have a server on the LAN with an address of 192.168.0.235
I need this particular server to use a specific IP out of our public group, NOT the one that is assigned to the WAN interface.
In other words, when that server at .235 has communication, it needs to be using a specific public IP both in and out (although in is not so critical). The receiving server needs to see the traffic from a specific IP.
I think this might be WAN multi-homing maybe? Put yet another way:
LAN>WAN LAN DHCP Range>xxx.xxx.xxx.82
LAN>WAN 192.168.0.233>xxx.xxx.xxx.86
WAN>LAN xxx.xxx.xxx.82>LAN DHCP Range
WAN>LAN xxx.xxx.xxx.86>192.168.0.233
I believe I have tried every combination of inbound/outbound rules and none of them work. It always winds up sending out of the WAN port's ISP/Broadband set IP address. i.e. xxx.xxx.xxx.82
I have a group of static IP's from our ISP. The first IP is assigned to the ISP/Wan settings of the FVS-318N, lets just call it xxx.xxx.xxx.82
I have a server on the LAN with an address of 192.168.0.235
I need this particular server to use a specific IP out of our public group, NOT the one that is assigned to the WAN interface.
In other words, when that server at .235 has communication, it needs to be using a specific public IP both in and out (although in is not so critical). The receiving server needs to see the traffic from a specific IP.
I think this might be WAN multi-homing maybe? Put yet another way:
LAN>WAN LAN DHCP Range>xxx.xxx.xxx.82
LAN>WAN 192.168.0.233>xxx.xxx.xxx.86
WAN>LAN xxx.xxx.xxx.82>LAN DHCP Range
WAN>LAN xxx.xxx.xxx.86>192.168.0.233
I believe I have tried every combination of inbound/outbound rules and none of them work. It always winds up sending out of the WAN port's ISP/Broadband set IP address. i.e. xxx.xxx.xxx.82
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!