Change the port HM is 'listening on'

[Mike Wallace]

Yes, time for a new router. Or first, what kind of internet do you have? Cable? DSL? I'm on DSL and my modem is a modem router, I have it doing all the routing. My wireless router is being used as a wireless access point only. What make/model modem do you have?

 

[John Bostwick]

John, Don't you have an original Heater Meter built on a Linksys WRT router? Not sure if you can roll it back to router mode, but if you can do that and load Tomato firmware on it you will have the port forwarding options you need.

Now that would be interesting, lol. Its been sitting outside, for the last 2 or years in a plastic container that I keep bbq stuff in. I have been wanting to see if it still works, I guess this would be a good time to try.

The Cable(Comcast) modems router is just as basic and that one would not work as the Wifi on it is poor, The wifi Wireless-N router I just bought also lacks the option in the port forwarding.

 

[Mike Wallace]

The Cable(Comcast) modems router is just as basic and that one would not work as the Wifi on it is poor, The wifi Wireless-N router I just bought also lacks the option in the port forwarding.

So do you have the cable modem router only acting as a modem, and you have the WRN3500 plugged into it to give your routing and wifi? If so, you might be able to do the routing with the modem router as I suggested, but keep its wifi turned off and use the WRN3500 as a wireless access point (turn off the routing, plug the Ethernet cable from the cable modem into one of the LAN ports on the WRN3500 instead of into the WAN port)

What is the make/model of the cable modem? It might have port forward option you need (external port)

 

[T. Stinnett]

DD-WRT on your existing router may be an option depending on the specific version. http://www.dd-wrt.com/site/support/router-database

If supported, that'll get you what you need and another project for a few hours.

 

[Dave R]

I am in the same boat as John. My router will only let me do a straight through forwarding of ports...incoming port = port on internal IP address. It won't let me take an incoming request on port 1000 and send it to an internal IP with port 80, it has to be the same port 1000. That is why I needed to find out how to change the listenting port on the HM. I have something else set on my firewall for port 80.

Dave

 

[John Bostwick]

It doesn't matter what router I use or modem I have. If you can't change the listening port via the router, nothing will work unless you can change the listen port of the hm from 80 to something else.

 

[Steve_M]

It doesn't matter what router I use or modem I have. If you can't change the listening port via the router, nothing will work unless you can change the listen port of the hm from 80 to something else.

It has everything to do with the modem or router you have, more specifically, the software running on the modem or router that gives you better control over your port forwarding configuration. Even the stock Linksys firmware lets you select both the external and internal port. Not sure why Netgear didn't include that functionality into theirs.

 

[John Bostwick]

It has everything to do with the modem or router you have, more specifically, the software running on the modem or router that gives you better control over your port forwarding configuration. Even the stock Linksys firmware lets you select both the external and internal port. Not sure why Netgear didn't include that functionality into theirs.

That's kinda what I met to say, but it's not just netgear.

Anyways, the wnr3500 is not compatible with any of the aftermarket firmwares. But, this weekend will try to get the old linksys running.

 

[Mike Wallace]

John, what is the cable modem model? You mentioned it has wireless (but not good). Again, it might be able to handle the routing.

 

[John Bostwick]

John, what cable modem model? You mentioned it has wireless (but not good). Again, it might be able to handle the routing.

it has the same port forwarding as the others we have. In fact it even has less function the a router. The only way to turn off the router part of the modem is to call Comcast. It also has voip phone that we don't even use lol

I knew what needed to be done, just couldn't figure out how to do it with the stuff I had.

 

[RalphTrimble]

If you are able change the port to something unique on each HM, for instance 8080, 8081, 8082 etc, then it seems you should be able to forward incoming on port 8080 to the IP address for HM1 at port 8080, and incoming on port 8081 to the IP of HM2 on port 8081 etc etc. That way the External and Internal ports are the same, I think your router will do that, right?

 

[John Bostwick]

If you are able change the port to something unique on each HM, for instance 8080, 8081, 8082 etc, then it seems you should be able to forward incoming on port 8080 to the IP address for HM1 at port 8080, and incoming on port 8081 to the IP of HM2 on port 8081 etc etc. That way the External and Internal ports are the same, I think your router will do that, right?

Yep. and I have not tried it yet may give it a try this weekend. I can set up a NOip address to UDS.ddns.net:8080 and that should get it to the HM using 8080 instead of port 80

 

[Steve_M]

Yep. and I have not tried it yet may give it a try this weekend. I can set up a NOip address to UDS.ddns.net:8080 and that should get it to the HM using 8080 instead of port 80

John,

You don't need multiple DNS entries to use multiple ports. Once you setup your port forward for port 8080, just put http://UDS.servebeer.com:8080 into a web browser and you'll be good to go.

You only have 1 IP address for your home internet connection. Mapping multiple DNS names to that IP won't give you any additional functionality.

 

[RalphTrimble]

I thought he was attempting to have several HM's accessible over the internet at one ddns address/internet IP. So first HM 8080, second HM 8081 etc

 

[John Bostwick]

John,

You don't need multiple DNS entries to use multiple ports. Once you setup your port forward for port 8080, just put http://UDS.servebeer.com:8080 into a web browser and you'll be good to go.

You only have 1 IP address for your home internet connection. Mapping multiple DNS names to that IP won't give you any additional functionality.

I already have one mapped to port 80. I need another Heatermeter mapped to port 8080

 

[Dave R]

John,
You just need to have the HM2 changed to listen on port 8080. Have your router forward requests from the Internet on port 8080 to the internal IP of HM2 on port 8080. For you to see your second HM from the Internet, just type your IP:8080. By default, if you just type your IP, port 80 it thought to the port you are wanting to connect to. If you want to connect to a different port, just add ortnumber to the end of your IP address. You shouldn't need to get another NOip address to UDS.ddns.net:8080.

Hopefully that made as much sense as it did when I was typing it.

Dave

 

[Steve_M]

Posting this here since it's somewhat relevant and might help others.

I've got a bunch of internal devices that I wanted to reach via ssl and found a way to do it via nginx.

I've got this running on my utility raspberry pi that stays on 24x7. On my router, I port forward 443 to port 443 on my raspberry pi, and now nginx intercepts the SSL calls sends them off to the correct device.

Now I can go to https://hm40.converged.ca or https://hm41.converged.ca (offline right now)

I created some free certs at https://www.startssl.com/. Looks to be working well.

This is the entire config.

cat /etc/nginx/sites-enabled/sslproxy

upstream hm40 {
      server 192.168.1.88; 
}

upstream hm41 {
      server 192.168.1.89; 
}


# Dummy server. If someone enters http://my.ip.add.ress/ in the their web browser
# we'll redirect them to google.
server {
	listen       443 ssl;
	server_name  test.com;
        ssl_certificate		/etc/nginx/ssl/test.crt;
        ssl_certificate_key	/etc/nginx/ssl/test.key;
	rewrite ^/(.*) http://www.google.com permanent;
}

server {
	listen 			443 ssl;
	server_name 		hm40.converged.ca;
        ssl_certificate		/etc/nginx/ssl/hm40.crt;
        ssl_certificate_key	/etc/nginx/ssl/hm40.key;

	location / {
        proxy_pass  http://hm40;
	proxy_http_version 1.1;
	proxy_read_timeout 600s;
	proxy_buffering off;
	}
}

server {
	listen 			443 ssl;
	server_name 		hm41.converged.ca;
        ssl_certificate		/etc/nginx/ssl/hm41.crt;
        ssl_certificate_key	/etc/nginx/ssl/hm41.key;

	location / {
        proxy_pass  http://hm41;
	proxy_http_version 1.1;
	proxy_read_timeout 600s;
	proxy_buffering off;
	}
}