Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nrf]

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...

[fordem]

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.

[JordiBoy]

Wes,

Take a look at 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.

[ECF]

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.

[nrf]

huh? 

[ECF]

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. 

[nrf]

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.

[fordem]

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

[nrf]

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)

[WesStewart]

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.

[JordiBoy]

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.

[pkarna01]

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.