<div dir="ltr">Thanks, Ian. No joy in the bridge mode. </div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 15, 2014 at 3:41 PM, <span dir="ltr"><<a href="mailto:gm4upx@gb7jd.co.uk" target="_blank">gm4upx@gb7jd.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">John,<br>
<br>
A stab in the dark as I do not know your Hotspot.<br>
<br>
Is there an option to choose between [ bridge ] and [ raw ] somewhere as in a VBox situation ??<br>
<br>
If so [ bridge ] would give a 192.168.x.x. address which might help you..<br>
<br>
Regards,<br>
<br>
Ian..<br>
<br>
<br>
<br>
On 15-07-2014 18:00, <a href="mailto:arm-allstar-request@hamvoip.org" target="_blank">arm-allstar-request@hamvoip.<u></u>org</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send arm-allstar mailing list submissions to<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-<u></u>bin/mailman/listinfo/arm-<u></u>allstar</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arm-allstar-request@hamvoip.org" target="_blank">arm-allstar-request@hamvoip.<u></u>org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arm-allstar-owner@hamvoip.org" target="_blank">arm-allstar-owner@hamvoip.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of arm-allstar digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Hotspot Blues -- echolink, IRLP, AllStar ports needed (John)<br>
2. Re: Hotspot Blues -- echolink, IRLP, AllStar ports needed<br>
(David McGough)<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>----------<br>
<br>
Message: 1<br>
Date: Mon, 14 Jul 2014 15:13:42 -0500<br>
From: John <<a href="mailto:wb5nfc@gmail.com" target="_blank">wb5nfc@gmail.com</a>><br>
To: BeagleBone Black ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] Hotspot Blues -- echolink, IRLP, AllStar<br>
ports needed<br>
Message-ID:<br>
<CALfzjYR==<a href="mailto:y3c1CpnDgqhsXaWP_pvAOAgid00Mg8JQSanCxARvQ@mail.gmail.com" target="_blank">y3c1CpnDgqhsXaWP_<u></u>pvAOAgid00Mg8JQSanCxARvQ@mail.<u></u>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Tim & David, thanks for the information, but I'm still missing something.<br>
Hopefully, it's just a passing Homer Simpson moment on my part.<br>
<br>
I understand the ports that must be forwarded and how to set them up in the<br>
router as well as the need to move the hotspot behind the router. I think<br>
it's the first link in the chain that's throwing me.<br>
<br>
As I mentioned, the Hotspot is tethered to the router via a USB cable. On<br>
the router Status page under Connection information, the Current IP Address<br>
is listed as 192.168.1.4 and the Current Default Gateway as 192.168.1.5. If<br>
I DMZ the gateway (192.168.1.5) on the hotspot, the router will not connect<br>
to the Internet - the hotspot ceased to operate. Remove the DMZ and<br>
Internet service is restored. Elsewhare on the router Status page (under<br>
Device Information) Cellular is listed at 192.168.4.<br>
<br>
Isn't 192.168.1.5 the IP I should be DMZing on the Hotsopt?<br>
<br>
John<br>
<br>
<br>
On Sun, Jul 13, 2014 at 2:21 PM, David McGough <<a href="mailto:kb4fxc@inttek.net" target="_blank">kb4fxc@inttek.net</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi John,<br>
<br>
As Tim mentioned, you need to setup your NAT-firewall device as the WAN<br>
host on the DMZ, rather than the RasPi node. Then, selectively forward the<br>
ports needed from the NAT-firewall to the BBB and RasPi on its LAN side.<br>
<br>
For the RasPi:<br>
echolink requires two ports:<br>
Forward UDP ports 5198 and 5199 to the RasPi LAN IP.<br>
<br>
IRLP is more complex. All these ports go to the RasPi LAN IP:<br>
Forward UDP ports 2074 through 2093<br>
Forward: TCP ports 15425, 15426, 15427<br>
<br>
For the BBB, assuming you're using the default port:<br>
AllStar: Forward UDP port 4569 to the BBB LAN IP.<br>
<br>
That should do it, I think!<br>
<br>
73, David KB4FXC<br>
<br>
<br>
On Sun, 13 Jul 2014, John wrote:<br>
<br>
> I'm stumped as to how to accomplish a task that I'm sure others have<br>
> already solved...<br>
><br>
> As a full-time RVer, I rely on my Verizon-based hotspot to provide<br>
Internet<br>
> service because WiFi at campgrounds is notoriously lousy when it work at<br>
> all. The hotspot is working well with my Blackberry Pi-based<br>
Echolink/IRLP<br>
> node. I have a static IP that seems to help. In order to make everything<br>
> work and play well together, I had to DMZ my node IP on the Hotspot<br>
because<br>
> it does not allow custom forwarding of specific ports. That was fine when<br>
> it was the only system.<br>
><br>
> Now that I'm bringing up a BBB node, I don't know how to handle port<br>
> forwarding. Yes, I am using a router (WiFiRange G02) for the rest of my<br>
> computers, laptops, and iPhones, but that introduces another network<br>
> (Hotspot is 192.168.1xx and router serves up 10.159.xx.xx). The<br>
> all-or-nothing DMZ throws a monkey wrench in the soup! Yes, I know I will<br>
> have EchoLink capabilities on the BBB, but of course, NOT IRLP.<br>
><br>
> Would setting up the already available VPN help or am I just making<br>
things<br>
> harder than they should be? Suggestions appreciated.<br>
><br>
> John / WB5NFC<br>
><br>
<br>
______________________________<u></u>_________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-<u></u>bin/mailman/listinfo/arm-<u></u>allstar</a><br>
<br>
Visit the BBB web page -<br>
<a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/<u></u>hamradio/<u></u>BeagleBoneBlackAllstar/</a><br>
<br>
</blockquote>
<br>
<br>
<br>
--<br>
John Kenney<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140714/28185e11/attachment-0001.html" target="_blank">http://lists.hamvoip.org/<u></u>pipermail/arm-allstar/<u></u>attachments/20140714/28185e11/<u></u>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 15 Jul 2014 09:20:18 -0400 (EDT)<br>
From: David McGough <<a href="mailto:kb4fxc@inttek.net" target="_blank">kb4fxc@inttek.net</a>><br>
To: BeagleBone Black ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] Hotspot Blues -- echolink, IRLP, AllStar<br>
ports needed<br>
Message-ID:<br>
<<a href="mailto:Pine.LNX.4.44.1407150857330.4378-100000@goliath.inttek.net" target="_blank">Pine.LNX.4.44.1407150857330.<u></u>4378-100000@goliath.inttek.net</a><u></u>><br>
Content-Type: TEXT/PLAIN; charset=US-ASCII<br>
<br>
<br>
Hi John,<br>
<br>
I'm not 100% clear on the config that you've got. However, below is the<br>
basic config you need, the IP addresses may not be right. Please excuse<br>
the ASCII art!<br>
<br>
Verizon adapter (IP: 192.168.1.5)<br>
^<br>
| (usb cable)<br>
v<br>
Network Router / DMZ host (WAN IP: 192.168.1.4, LAN IP: 10.159.x.1)<br>
^^^<br>
|||<br>
||| (LAN side ethernet)<br>
||+---------------------------<u></u>----------+<br>
|+--------------+ |<br>
v v v<br>
BBB (IP:10.159.x.100) RasPi (IP:10.159.x.101) PC (IP:10.159.x.z)<br>
<br>
<br>
Note that this case, the "Network Router" should be the DMZ host, so the<br>
Verizon adapter should show a DMZ host address of: 192.168.1.4--the WAN<br>
address of the router. The LAN gateway (gateway on BBB, RasPi, etc.)<br>
should be 10.159.x.1, the LAN address of the "Network Router".<br>
<br>
The last step would be to config the "Network Router" to perform<br>
selective port forwarding to the BBB and RasPi, as mentioned in the<br>
earlier post.<br>
<br>
....I hope this helps and the diagram survives the list server.<br>
<br>
73, David KB4FXC<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Mon, 14 Jul 2014, John wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tim & David, thanks for the information, but I'm still missing something.<br>
Hopefully, it's just a passing Homer Simpson moment on my part.<br>
<br>
I understand the ports that must be forwarded and how to set them up in the<br>
router as well as the need to move the hotspot behind the router. I think<br>
it's the first link in the chain that's throwing me.<br>
<br>
As I mentioned, the Hotspot is tethered to the router via a USB cable. On<br>
the router Status page under Connection information, the Current IP Address<br>
is listed as 192.168.1.4 and the Current Default Gateway as 192.168.1.5. If<br>
I DMZ the gateway (192.168.1.5) on the hotspot, the router will not connect<br>
to the Internet - the hotspot ceased to operate. Remove the DMZ and<br>
Internet service is restored. Elsewhare on the router Status page (under<br>
Device Information) Cellular is listed at 192.168.4.<br>
<br>
Isn't 192.168.1.5 the IP I should be DMZing on the Hotsopt?<br>
<br>
John<br>
<br>
<br>
On Sun, Jul 13, 2014 at 2:21 PM, David McGough <<a href="mailto:kb4fxc@inttek.net" target="_blank">kb4fxc@inttek.net</a>> wrote:<br>
<br>
><br>
> Hi John,<br>
><br>
> As Tim mentioned, you need to setup your NAT-firewall device as the WAN<br>
> host on the DMZ, rather than the RasPi node. Then, selectively forward the<br>
> ports needed from the NAT-firewall to the BBB and RasPi on its LAN side.<br>
><br>
> For the RasPi:<br>
> echolink requires two ports:<br>
> Forward UDP ports 5198 and 5199 to the RasPi LAN IP.<br>
><br>
> IRLP is more complex. All these ports go to the RasPi LAN IP:<br>
> Forward UDP ports 2074 through 2093<br>
> Forward: TCP ports 15425, 15426, 15427<br>
><br>
> For the BBB, assuming you're using the default port:<br>
> AllStar: Forward UDP port 4569 to the BBB LAN IP.<br>
><br>
> That should do it, I think!<br>
><br>
> 73, David KB4FXC<br>
><br>
><br>
> On Sun, 13 Jul 2014, John wrote:<br>
><br>
> > I'm stumped as to how to accomplish a task that I'm sure others have<br>
> > already solved...<br>
> ><br>
> > As a full-time RVer, I rely on my Verizon-based hotspot to provide<br>
> Internet<br>
> > service because WiFi at campgrounds is notoriously lousy when it work at<br>
> > all. The hotspot is working well with my Blackberry Pi-based<br>
> Echolink/IRLP<br>
> > node. I have a static IP that seems to help. In order to make everything<br>
> > work and play well together, I had to DMZ my node IP on the Hotspot<br>
> because<br>
> > it does not allow custom forwarding of specific ports. That was fine when<br>
> > it was the only system.<br>
> ><br>
> > Now that I'm bringing up a BBB node, I don't know how to handle port<br>
> > forwarding. Yes, I am using a router (WiFiRange G02) for the rest of my<br>
> > computers, laptops, and iPhones, but that introduces another network<br>
> > (Hotspot is 192.168.1xx and router serves up 10.159.xx.xx). The<br>
> > all-or-nothing DMZ throws a monkey wrench in the soup! Yes, I know I will<br>
> > have EchoLink capabilities on the BBB, but of course, NOT IRLP.<br>
> ><br>
> > Would setting up the already available VPN help or am I just making<br>
> things<br>
> > harder than they should be? Suggestions appreciated.<br>
> ><br>
> > John / WB5NFC<br>
> ><br>
><br>
> ______________________________<u></u>_________________<br>
><br>
> arm-allstar mailing list<br>
> <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-<u></u>bin/mailman/listinfo/arm-<u></u>allstar</a><br>
><br>
> Visit the BBB web page -<br>
> <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/<u></u>hamradio/<u></u>BeagleBoneBlackAllstar/</a><br>
><br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
------------------------------<br>
<br>
______________________________<u></u>_________________<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-<u></u>bin/mailman/listinfo/arm-<u></u>allstar</a><br>
<br>
<br>
End of arm-allstar Digest, Vol 2, Issue 9<br>
******************************<u></u>***********<br>
</blockquote>
______________________________<u></u>_________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-<u></u>bin/mailman/listinfo/arm-<u></u>allstar</a><br>
<br>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/<u></u>hamradio/<u></u>BeagleBoneBlackAllstar/</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>John Kenney
</div>