Networks Thread, D-Link DIR-655 router - Port Forwarding or Virtual Server? in Technical; Hey everyone. I'm just wondering about my home network here. I run 6 servers at home and more than half ...
-
12th January 2008, 08:45 AM #1 [ANSWERED] D-Link DIR-655 router - Port Forwarding or Virtual Server?
Hey everyone. I'm just wondering about my home network here. I run 6 servers at home and more than half of them run services outside the network. I use the D-Link DIR-655 router as mentioned in the subject.
I'm curious, I've always used Port Forwarding for things like FTP, Web services etc. But I'm wondering about Virtual Server. Are the two the exact same? They appear to be pretty close. Here are the descriptions for each as shown at the top of the configuration pages.
Virtual Server:
The Virtual Server option allows you to define a single public port on your router for redirection to an internal LAN IP Address and Private LAN port if required. This feature is useful for hosting online services such as FTP or Web Servers.
Port Forwarding:
This option is used to open multiple ports or a range of ports in your router and redirect data through those ports to a single PC on your network. This feature allows you to enter ports in various formats including, Port Ranges (100-150), Individual Ports (80, 68, 888), or Mixed (1020-5000, 689).
I'm currently using port forwarding, but I'm not sure which is prefered or which is better.
Anyways, if anyone has any information on this, that would be great! Thanks!
Last edited by link470; 15th January 2008 at 02:41 AM.
-
-
IDG Tech News
-
12th January 2008, 09:11 PM #2 I believe "virtual server" is equivalent to forwarding *all* ports to a single machine. Not only will this throw a spanner in the works, but its a security nightmare waiting to happen. If pf is working as is, i would suggest "if it aint broke dont try and fix it".
-
-
12th January 2008, 11:02 PM #3 
Originally Posted by
tom_newton
I believe "virtual server" is equivalent to forwarding *all* ports to a single machine. Not only will this throw a spanner in the works, but its a security nightmare waiting to happen. If pf is working as is, i would suggest "if it aint broke dont try and fix it".
@tom_newton I think that what you are thinking about it DMZ (demiliterised zone) which will forward all external requests that are not handled by port forwards or virtual servers to that internal address.
In answer to the OP I think that they are pretty much the same thing, most of the routers that I deal with have either port forwarding or virtual server options. I think that your router may just be able to group things that would take multiple port forwarders to accomplish into a single port forward configuration.
-
-
20th December 2008, 02:27 AM #4
- Rep Power
- 0

Originally Posted by
link470
Hey everyone. I'm just wondering about my home network here. I run 6 servers at home and more than half of them run services outside the network. I use the D-Link DIR-655 router as mentioned in the subject.
I'm curious, I've always used Port Forwarding for things like FTP, Web services etc. But I'm wondering about Virtual Server. Are the two the exact same? They appear to be pretty close. Here are the descriptions for each as shown at the top of the configuration pages.
Virtual Server:
The Virtual Server option allows you to define a single public port on your router for redirection to an internal LAN IP Address and Private LAN port if required. This feature is useful for hosting online services such as FTP or Web Servers.
Port Forwarding:
This option is used to open multiple ports or a range of ports in your router and redirect data through those ports to a single PC on your network. This feature allows you to enter ports in various formats including, Port Ranges (100-150), Individual Ports (80, 68, 888), or Mixed (1020-5000, 689).
I'm currently using port forwarding, but I'm not sure which is prefered or which is better.
Anyways, if anyone has any information on this, that would be great! Thanks!
Hello Link470,
I was wondering if you could give me a hand since you are running six servers I figure you know the nuances.
I am running the same DIR655. I just built a Fedora 10 box. When it comes up with a DHCP private network (192.168... )address ( assigned by the DIR655) I can get the DIR655 to forward port 80. When I change the server to a static private network IP it will not forward! I have been banging my head on this for two weeks. I can see the web server on my LAN but I cannot see iton the ourside (Internet) I have tried it with Ubuntu too with the same result.
I changed the forwarding address from the DHCP address to the static address on the router. I also reserved that static IP address as a static address in the router's DHCP table.
Any ideas?
-
-
21st December 2008, 02:51 PM #5
- Rep Power
- 9

Originally Posted by
pushback
Hello Link470,
I changed the forwarding address from the DHCP address to the static address on the router. I also reserved that static IP address as a static address in the router's DHCP table.
Any ideas?
If you are reserving the address via MAC allocation on the router, then you should leave the machine set to DHCP.
-
Thanks to Jay from:
pushback (21st December 2008)
-
21st December 2008, 09:59 PM #6
- Rep Power
- 0

Originally Posted by
Jay
If you are reserving the address via MAC allocation on the router, then you should leave the machine set to DHCP.
Yes, that's what it was. Thanks!
-
-
22nd December 2008, 09:09 AM #7 Ya I've done the exact same thing. I either use one, setting the machine as static, and not setting a reservation, or setting the reservation for the MAC address of the computer you wish to set a specific IP address to within the router and leaving the computer on DHCP, since it will always collect the same IP from the server. But I never set both. Some systems seem ok with it, but some just see an IP conflict and end up with either a valid address but no connectivity, or an APIPA 169.254.x.x address. Glad you figured it out and it was something simple! I hate those...lol. The kind of things that make you go "no way, I just spent HOW long on that?". Kind of like FTP. I'm still trying to master that protocol. I'm a network engineer and I still can't make FTP work properly all the time for everyone. I'm at the point where it works "well enough", but it's still a pain. Freakin passive mode and passive ports :P *sigh*
-
-
22nd December 2008, 10:34 AM #8 In answer to the OP: look at your descriptions. Virtual server is a single port, port forwarding is multiple or ranges of ports.
-
-
29th March 2011, 06:05 PM #9
- Rep Power
- 0
Port Forward vs Virtual Server
I think the difference is that Virtual server can map public ports to different private ports.
Port forward on the other hand allows using a range of ports, but the public ports are the same as the private ports.
-
-
29th March 2011, 10:53 PM #10 2008 just called, they want their thread back...
-
-
4th January 2012, 06:18 PM #11
- Rep Power
- 0

Originally Posted by
powdarrmonkey
2008 just called, they want their thread back...
The thread still shows up in google meaning it needs a correct answer, it's to bad the people in 2008 couldn't give a correct answer.
Thanks fakevrn
-
SHARE:
Similar Threads
-
By Kyle in forum Thin Client and Virtual Machines
Replies: 10
Last Post: 7th March 2007, 12:01 AM
-
By kiran in forum Thin Client and Virtual Machines
Replies: 5
Last Post: 26th February 2007, 07:51 PM
-
By GrumbleDook in forum *nix
Replies: 36
Last Post: 21st December 2006, 05:56 PM
-
By ajbritton in forum Thin Client and Virtual Machines
Replies: 0
Last Post: 31st August 2006, 06:19 AM
-
By Norphy in forum Windows
Replies: 20
Last Post: 4th April 2006, 01:54 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules