Thanks again for your feedback.
I finally got things more or less working now with the static
When I turned the IP Passthrough off, clients I had configured
with static IP's in the assigned block were able to access the web.
The NVG510 I received, came with the Firewall/IP Passthough
options set for DHCPS-static and Manual.
The 5 Public IP's and Public Gateway IP were all in the
The IP that the NVG510 gets is in the 172.12.xx.xx segment,
with its Gateway as 172.12.xx.1
It also seemed as if things were not quite right when I was doing
some testing with a client machine using the Private IP pool, so
it would get an IP of 192.168.1.64.
I was able to connect to the server via external address, but
the login to the FTP server was unusually slow, and would
tend to crash on the LIST command after login if there was
a large number of files in the host directory.
Moved that client behind a Linksys router, and that problem
vanished. (I am sure there is nothing amiss with the server.)
The NVG510 doesn't seem to deal with DHCP very well.
I have that turned off on both the NVG510 and the Linksys.
Looking at the description of the options for that IP Passthrough
feature, I can see where it would be a good way for somebody
with a 1 IP package to make their PC visible, but it doesn't
seem to make sense if you are using the 5 public IP's.
At the moment I have a Linksys router configured with one
of the Public IP's, and a test linux server, which I have
only running FTP and a UnrealTournament server.
Currently still trying to get my production server working
from behind the Linksys.
For the test server I just configured the local LAN adapter
with one of the public IP's, but doing that for my
production server, is something I would really like to avoid
for a number of reasons. (Dozens of java beans compiled
with local IP hardcoded in them for one....)
I miss my Cayman.........
Got the Linksys configured so my production server is working
fine behind it, with its old internal 198.168.1.xxx IP.
Client PC on the Linksys hits either FTP server fine now.
HTTP & the antique UT99 servers are back up also.
I brought back a site I wrote long ago, and set it as the default
for numeric access at »188.8.131.52/
I think it is up and running, but I can't actually test it from outside
the lan, as the NVG510 treats any IP I use as local. I am 1 hop
from any device on my network now, regardless of IP used it seems.
The various bot & random traffic is trickling into the logs, so I am
pretty sure it is working, but I miss the ability to confirm by
testing the server via either WAN or LAN.
If I wanted to put my "test" server back into production with one
of the other Public IP's I was given, and use an internal IP for its
lan adapter, it seems I will have to get another gateway/router
device to do the NAT.
I can configure multiple clients behind this linksys, and make them
work in harmony with 1 server, but I think that is all it can do.
I really miss my old Cayman.....