NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 up in the FVS-318N.
I need to try and get this all run through the firewall now. I want to be able to have one connection from the cable modem to the FVS-318N, and then route various public IP's to the correct server on the LAN.
Is this possible with this device? If it's possible, can anyone explain how this is done?
I need to try and get this all run through the firewall now. I want to be able to have one connection from the cable modem to the FVS-318N, and then route various public IP's to the correct server on the LAN.
Is this possible with this device? If it's possible, can anyone explain how this is done?
24 Replies
- Huh? You've really lost me now. Can you be more specific? Default gateway where? On what?
- Whatever is on 192.168.0.249.
starion wrote: Huh? You've really lost me now. Can you be more specific? Default gateway where? On what?
it means the gateway address correctly setup on server itself on the device network properties- 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 - If using inbound/outbound rules with specifying public IP is not going to work then you will need to use classical routing feature in the router
- Yes, but then DHCP'd computers on your network can't reach the internet.
- You need another nat routers.
This has to be the worst support forum I've ever seen. Classical routing is not an option - the user is trying to use the router like it was designed to work and it isn't working (NAT with inbound rule for a static IP from his assigned block of multiple static IPs). The static IP assign to the WAN itself routes inbound properly. It is only when assign one of the other static IPs from the block where it doesn't route inbound. I have a 318Gv2 so it seems like a bug in the firmware.
What you need to do, is one outbound rule for that device, an ANY rule, and it uses a secondary address from that section of the manual.
That means any traffic it sends out, goes out that address. Incoming traffic, if you setup the inbound rule, will always respond on the same IP address as to be expected.
You shouldn't need to do classical routing; the feature has been in the devices for years now, and you will just need the oubound ANY rule, with the xxx.xxx.xxx.82 attached to it, and you will be good to go.
I'm still trying to setup a 2nd inbound static IP on an FVS318Gv2. I'm pretty sure it is the firmware bug, since I set this up on the exact same network with an FVS336G. The whole outbound policy is a wild goose chase. It never was needed before?
Here's a description of setting up a 1 to 1 NAT with a 2nd public IP - no mention of outbound policy is made - and this looks exactly like my fvs336g and fvs318Gv2 setup - except the 336 worked and the 318 doesn't for the 2nd public IP:
http://documentation.netgear.com/fvs338/enu/202-10046-03/FVS338-06-10.html
I'm still trying to setup a 2nd inbound static IP on an FVS318Gv2 with the latest firmware as of today (since previous firmwares all had their own various bugs). I'm pretty sure it is the firmware bug possibly related to impromper subnet handling, since I set this up on the exact same network with an FVS336G. The whole outbound policy is a wild goose chase. It never was needed before?
Here's a description of setting up a 1 to 1 NAT with a 2nd public IP - no mention of outbound policy is made - and this looks exactly like my fvs336g and fvs318Gv2 setup - except the 336 worked and the 318 doesn't for the 2nd public IP:
http://documentation.netgear.com/fvs338/enu/202-10046-03/FVS338-06-10.html
This also is the same as page 165 of the actual manual for the fvs318gv2:
http://www.downloads.netgear.com/files/GDC/FVS318GV2/FVS318Gv2_RM_21Oct2014.pdf
The outbound rule is needed only when the server is sending traffic out without being solicited first. Think of the inbound rule. The firewall remembers that when it came to your static IP, to respond with that same IP. However if a server sends out traffic and is not responding, without the outbound rule it would use the devices WAN IP. That is the purpose of having the outbound rule, and based on what you said earlier that all traffic from the device needs to use that one IP, it seems to be needed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
