[arm-allstar] Incoming connect

[Doug Crompton]

This is a common mistake. Always make sure you are not dealing with two (or more) serially connected routers. Port forwarding on one downstream of another that is not port forwarded will never work!

If you have a modem router combo and you don't want to use the router most have the option to act just as a modem to an external router. Then you are not going through two routers.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


Date: Tue, 7 Jul 2015 21:38:04 +0000
From: bjbuelow at yahoo.com
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Incoming connect


Success!
After much fooling around, buying a new router (which didn't initially help at all), the problem has been identified and fixed. I"d been looking at MANY forum posts of Port Forward problems and found a nugget.  One of the posts pointed out that the DSL modem is also a router. I connected to the modem and DID find a set of router commands. All of the port rejections were coming from the modems internal router.  

At the time I was talking to k5tra and n7glv on the 900 hub. Joel said to setup the modem for DMZ which lets all the traffic go to the new Netgear router. The Netgear was already set to Port Forward. Using a web port checker, I was able to set that port 80 and 222 were open. This provided confidence that 4569 was open and it all started working.
My thanks to Tom and Joel for assisting. It was getting to be frustrating.  If someone wants a more detailed description for the drupal pages, let me know and I'll write something up.
Barry

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2 web page - http://hamvoip.org 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150707/302b2936/attachment.html>