[arm-allstar] Hotspot Blues -- echolink, IRLP, AllStar ports needed

[David McGough]

Hi John,

As Tim mentioned, you need to setup your NAT-firewall device as the WAN
host on the DMZ, rather than the RasPi node. Then, selectively forward the
ports needed from the NAT-firewall to the BBB and RasPi on its LAN side.

For the RasPi:
echolink requires two ports:
	Forward UDP ports 5198 and 5199 to the RasPi LAN IP.

IRLP is more complex. All these ports go to the RasPi LAN IP:
	Forward UDP ports 2074 through 2093
	Forward: TCP ports 15425, 15426, 15427

For the BBB, assuming you're using the default port:
AllStar: Forward UDP port 4569 to the BBB LAN IP.

That should do it, I think!

73, David KB4FXC


On Sun, 13 Jul 2014, John wrote:

> I'm stumped as to how to accomplish a task that I'm sure others have
> already solved...
> 
> As a full-time RVer, I rely on my Verizon-based hotspot to provide Internet
> service because WiFi at campgrounds is notoriously lousy when it work at
> all. The hotspot is working well with my Blackberry Pi-based Echolink/IRLP
> node. I have a static IP that seems to help. In order to make everything
> work and play well together, I had to DMZ my node IP on the Hotspot because
> it does not allow custom forwarding of specific ports. That was fine when
> it was the only system.
> 
> Now that I'm bringing up a BBB node, I don't know how to handle port
> forwarding. Yes, I am using a router (WiFiRange G02) for the rest of my
> computers, laptops, and iPhones, but that introduces another network
> (Hotspot is 192.168.1xx and router serves up 10.159.xx.xx). The
> all-or-nothing DMZ throws a monkey wrench in the soup! Yes, I know I will
> have EchoLink capabilities on the BBB, but of course, NOT IRLP.
> 
> Would setting up the already available VPN help or am I just making things
> harder than they should be?  Suggestions appreciated.
> 
> John / WB5NFC
>