D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-321 => Topic started by: WesStewart on April 02, 2009, 07:06:04 AM
-
I have several devices that have web based configurations. Is there a way I can change the default port 80 for the DNS-321 to be some other value so I can access the configuration screen remotely along with the other devices.
Right now I have to log into my router and change the routing for port 80 to go to the DNS and then change it again to go to another device. Would be simpler if I could change to DSN-321 port and not have to modify the router configuration all the time.
Thanks,
Wes
-
Does your router support "port translation" - where you can forward port 880 to port 80 or similar?
-
You bet. That is where I have to change my port 80 to the DNS321 or some other device I have. I was hoping to get all of my devices on a different port so I can set the port translation only once.
Thanks,
Wes
-
You create a port forwarding rule for each device and forward the port you choose to access the device at to port 80 and the IP address of that device you want to access at that port. Then when you access the device remotely you enter in you browser http://(your WAN IP address):(the port you choose for that device) example: http://67.135.144.128:8080
-
ECF, I understand how to do the port forwarding in my router, what I need to know is how to change the port 80 on the DNS-321 to something else. All of my devices default to port 80 and I need to change each device to something other than 80 so I come to this fourm to find out how to change the DNS-321.
Thanks,
Wes
-
Sorry it cant be changed.
-
I think what he is saying is to something like forwarding port 8080 to your 321-s port 80, so if you said router_ip:8080 it would go to the dns . can your router do that?
-
Here is what I would like to end up with:
Assumes internet browser is used.
1. routerip:8080 would open router configuration login screen
2. routerip:8081 would open DNS-321 configuration login screen
3. routerip:8082 would open networked printer configuration screen
4. routerip:8083 would open networked mp3 player configuration screen
5. .....
Since all of the devices I use as an example above default to port 80 for the web interface I have to log into my router and port forward 80 to the ip address of the device I wish to configure.
I do not think a router (not a consumer version anyway) can accept inbound data on one port, switch to another port/internal IP, get outbound data from device on internal port 80 and send back out to remote browser on 8081. Port triggering is close, but not the solution as suggested earlier.
Wes
-
why not be more specific? which router? I don't think you are asking for something unreasonable...
nrf
-
on my dgl-4300, there is a concept of 'public port' and 'private port'.
you could map the dns with public port 8081 and the private port of 80.
mission accomplished!
what does your router have?
-
I have a LinkSys WRT54G2 with ver 1.0.01 firmware
www default port is 80 so I was hoping to find a simple solution to change it on the DNS-321. If the router could do the work then even better because I don't think my other devices can be changed.
My router has port forwarding and port triggering
Wes
-
I have a LinkSys WRT54G2 with ver 1.0.01 firmware
www default port is 80 so I was hoping to find a simple solution to change it on the DNS-321. If the router could do the work then even better because I don't think my other devices can be changed.
My router has port forwarding and port triggering
Wes
I reviewed the manual for your router and I don't think it supports standard port mapping. http://www.linksysbycisco.com/US/en/support/WRT54G2/download (http://www.linksysbycisco.com/US/en/support/WRT54G2/download) page 17 explains port forwarding, but many routers support port mapping with "port from"/"port to". This model only seems to support forwarding ports to a specific address, not to an address and port. Port mapping would allow you to do what you are looking for with routerip:8080, routerip:8081, routerip:8082, etc...
Your router does support dd-wrt and this would allow you to forward specific ports to an ip address and port, but you have to load dd-wrt using tftp for the wrt54g2 http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54G2 (http://www.dd-wrt.com/wiki/index.php/Linksys_WRT54G2)
Upgrading to dd-wrt should allow you to do exactly what you want.
Hope this helps.
-
Thanks for all the advise on this. JordiBoy, thanks for the link and I will try that tonight. If I crash it worse case is buy a new router and they don't cost too much.
If you do not hear from me again, my wife killed me for loosing internet access on a Friday night.
Wes
-
I do not think a router (not a consumer version anyway) can accept inbound data on one port, switch to another port/internal IP, get outbound data from device on internal port 80 and send back out to remote browser on 8081. Port triggering is close, but not the solution as suggested earlier.
Wes
I've seen several that do it, including a $25 D-Link DI-604
-
Ok, I loaded the dd-wrt firmware, which has a ton of cool features and options, but still have the same problem.
I see the port forward stuff, but I think the problem is I need it to be bi-directional.
My web request comes in on port 8081 and must be forwarded to port 80 on the IP address of he DNS-321, when the DNS-321 sends data back based on the request it sends it on port 80 and I don't think anything is converting it back to the original port 8081.
Since I request a webpage on port 8081 I must have the results returned on the same port.
I think the port-forwarding features are uni-directional for inbound data only.
Wes
-
somehow I doubt that it would only allow data to flow in one direction. I can't think of a single service that would work that way. Unfortunately I am not an expert on ddwrt...
-
Ok, I loaded the dd-wrt firmware, which has a ton of cool features and options, but still have the same problem.
I see the port forward stuff, but I think the problem is I need it to be bi-directional.
My web request comes in on port 8081 and must be forwarded to port 80 on the IP address of he DNS-321, when the DNS-321 sends data back based on the request it sends it on port 80 and I don't think anything is converting it back to the original port 8081.
Since I request a webpage on port 8081 I must have the results returned on the same port.
I think the port-forwarding features are uni-directional for inbound data only.
Wes
Speaking as one who has redirected ports for web servers before - you forward the incoming port. period.
-
Wes,
Take a look at https://secure.dd-wrt.com/wiki/images/7/7f/DD-WRT_Port_Forward_Web_GUI_v23_SP1.png (https://secure.dd-wrt.com/wiki/images/7/7f/DD-WRT_Port_Forward_Web_GUI_v23_SP1.png) and I will try to walk you through this.
Let’s assume the following:
Internal Router IP: 192.168.1.1
DNS-321 IP: 192.168.1.20
Printer IP: 192.168.1.30
MP3 Player: 192.168.1.40
External Router IP: 97.96.120.200
You would set your port forwarding similar to this:
Application Port From Protocol IP Address Port To
Router 8080 TCP 192.168.1.1 80
DNS-321 8081 TCP 192.168.1.20 80
Printer 8082 TCP 192.168.1.30 80
MP3 8083 TCP 192.168.1.40 80
The Application field is just a comment field. Do not forget to set “Enable”
From outside your network, you would access your router using: 97.63.120.200:8080. The router would look at port 8080 and know to forward that to port 80 at your internal IP address of 192.168.1.1.
From outside your network, you would access your DNS-321 using: 97.63.120.200:8081. The router would look at port 8080 and know to forward that to port 80 at your internal IP address of 192.168.1.20.
I would also recommend using dyndns (or any service you prefer) to map your external address to something like wes.dyndns.org, then you could access your DNS-321 with wes.dyndns.org:8081.
-
Ok, I loaded the dd-wrt firmware, which has a ton of cool features and options, but still have the same problem.
I see the port forward stuff, but I think the problem is I need it to be bi-directional.
My web request comes in on port 8081 and must be forwarded to port 80 on the IP address of he DNS-321, when the DNS-321 sends data back based on the request it sends it on port 80 and I don't think anything is converting it back to the original port 8081.
Since I request a webpage on port 8081 I must have the results returned on the same port.
I think the port-forwarding features are uni-directional for inbound data only.
Wes
Yeah port forwarding on most routers are uni-directional for inbound data only.
-
huh? ???
-
The inbound data comes in on the desired port configured in the port forwarding rule and goes to port 80 at the IP address specified then the outbound data is sent out on port 80 for http traffic.
-
if this is true it would be totally worthless. the outbound port 80 from the inside ip to the outside ip should be associated with a memory structure noting the connection and mapped back to the original port on the public side. I can't imagine any possible use for a 'forwarding' feature that works in the way you just described. even a one-way flow like streaming video would need some way to 'slow down' the stream in the case of congestion.
-
The incoming port on which the initial connection is made bears no relationship to the outgoing port - can you imagine an ecommerce server which only allowed a single user for the duration of each transaction.
As I said in an earlier post - I have forwarded port 80 to a different internal port on many occasions (I'm running ip cameras) and all you need to do is to forward the port on which the initial connection is made, and you can ignore the rest - it will work
-
having done some research on this, if someone should come across such a router the way to 'fix' it is with port trigger settings. (afaik)
-
I have done some port routing for websites before, but I was forwarding the inbound webpage request to a webserver that was hosting a website on that port.
In other words I put in a browser say: http://www.somewebsite.com:8081
That would be forewarded to a system hosting a webserver using that same port 8081 and that system would send the website contents back on the same port 8081 to my browser.
The port triggering I think is for special applications like games that would transmit on one port and receive on another.
To do what I need I would need a port forward for inbound port 8081 to port 80 then outbound port 80 to port 8081. Seems like it could get pretty difficult.
I wish there was an easy way like there is in Microsoft Internet Server to set a website to a certain port so it will receive requests and transmit results on the same port no problem.
I may just have to put up a small Microsoft Web Server that will forward everything. I may have to actually use Remote Desktop to be able to do what I need.
-
Wes, What I posted in #17 works. I use this everyday so I am not sure why you think you need another method to forward the ports. It allows you to go to http://www.somewebsite.com:8081 and everything will be returned to your browser.
-
Since you have ddwrt now, you can ssh into your router and setup a tunnel to get to your DNS web admin page. You don't need any port forwarding. That's what I do. It is also more secure, since you will have to ssh to the router first. if you want I can give you instructions on how to do so, although I'm not too familiar with ddwrt, I use tomato instead.