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 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
- aditMentorUse Rules to assign Services to specific LAN Devices with each public IP.
- starionAspirantCan you please provide specific examples? I have tried every combination and cannot get it to work.
- aditMentorRead page 135 of the manual, last section.
- jmizoguchiVirtuosohttp://interface.netgear-forum.com/FVS336G/add_inbound.htm
same interface....
WAN is where you specify your public IP that is useable - starionAspirantI don't have the layout you show on my router (FVS-318N). Here's a screenshot of what I have set up...it doesn't work by the way...
- jmizoguchiVirtuosoYou in the right place and WAN is place to use look ok
- starionAspirantExcept nothing is being routed to 192.168.0.249 from 74.87.108.87. The WAN IP is basically non-responsive to anything.
- starionAspirantI have tried numerous variations in the configuration and I CANNOT get 74.87.108.86 (one of my static IP's) to talk to the internal LAN IP 192.168.0.249.
Without any evidence to the contrary, I must assume that the configurations suggested by both users here and technical support do not work, thus broken.
If anyone can verify that this type situation can work, I would be very interested in how you were able to make it work. - starionAspirantI have also set up inbound and outbound rules to allow all between those IP's and it still doesn't work.
- RyanJNETGEAR Employee Retired
It works, and I have seen it work countless times. However, I have also seen the feature have issues on devices, can't recall if ever on the FVS318N. Generally it falls in to a few categories:
1. ISP isn't actually sending traffic to that IP and have not configured a route on their end, if a capture shows nothing and you're sending traffic to that IP to test, then you'll know this is the case immediately.
2. The ISP wants a Proxy ARP which our devices historically did not support, although may currently(I'd have to check); rebooting the modem, removing the battery if it has one and waiting a moment before putting it back in, generally fixes that outright.
3. It is working, but the traffic doesn't appear to be; running a capture will show what is happening and is always recommended for verification. Software issues look like this generally, where the network and all is fine but something isn't configured right elsewhere.
4. ISP isn't actually sending traffic to that IP and told you the incorrect range of IPs, and you have to call them to verify what it is. (rarely, but occurs enough that I've seen it a few times)
5. Old firmware bugs. Stable currently doesn't mean it always was, and I didn't see which one it is, mentioned above. The latest I always recommend if having issue. If you're fine and stable, never change. If it aint broke, don't fix it is always sound advice.
6. Something else/fluke/bug. For that we would collect as much information, config file, remote access if possible, and work with our Engineering team to debug the issue and figure out what is going on. (rarest, as port forwarding part of the unit is the most stable and least changing feature)
Either way, I'd check the first 5 before heading to number 6. Also, captures will give you a lot of information. Forward ping instead of your service for testing, or send that IP to an HTTP server you have and test with your phone. All this should at least give you an idea of where the issue truly is, and if it is us, then having all of that information on hand is the fastest way to go forward. More info helps everyone involved. Right now we're just throwing out ideas and things we've commonly seen. :smileywink:
As far as how you have it configured, other than the service, it looks fine, although now the devices have the secondary addresses on newer firmware. I'd have to check when they added it but I thought it was the 4.x firmware codebase, which would imply you're on the old 3.x firmware, but again that's my memory and I could be wrong.
Edit: Also, in seeing a later reply, you do need the outbound rule bound to that IP as well.
- aditMentorIs the default gateway set on .249? Is it the LAN IP of the 318?
Related Content
NETGEAR Academy

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