[arm-allstar] Forward woes
John
wb5nfc at gmail.com
Wed Jul 23 19:43:08 EST 2014
Thanks, Ian. No joy in the bridge mode.
On Tue, Jul 15, 2014 at 3:41 PM, <gm4upx at gb7jd.co.uk> wrote:
> John,
>
> A stab in the dark as I do not know your Hotspot.
>
> Is there an option to choose between [ bridge ] and [ raw ] somewhere as
> in a VBox situation ??
>
> If so [ bridge ] would give a 192.168.x.x. address which might help you..
>
> Regards,
>
> Ian..
>
>
>
> On 15-07-2014 18:00, arm-allstar-request at hamvoip.org wrote:
>
>> Send arm-allstar mailing list submissions to
>> arm-allstar at hamvoip.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> or, via email, send a message with subject or body 'help' to
>> arm-allstar-request at hamvoip.org
>>
>> You can reach the person managing the list at
>> arm-allstar-owner at hamvoip.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of arm-allstar digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: Hotspot Blues -- echolink, IRLP, AllStar ports needed
>> (John)
>> 2. Re: Hotspot Blues -- echolink, IRLP, AllStar ports needed
>> (David McGough)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 14 Jul 2014 15:13:42 -0500
>> From: John <wb5nfc at gmail.com>
>> To: BeagleBone Black ARM Allstar <arm-allstar at hamvoip.org>
>> Subject: Re: [arm-allstar] Hotspot Blues -- echolink, IRLP, AllStar
>> ports needed
>> Message-ID:
>> <CALfzjYR==y3c1CpnDgqhsXaWP_pvAOAgid00Mg8JQSanCxARvQ at mail.
>> gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Tim & David, thanks for the information, but I'm still missing something.
>> Hopefully, it's just a passing Homer Simpson moment on my part.
>>
>> I understand the ports that must be forwarded and how to set them up in
>> the
>> router as well as the need to move the hotspot behind the router. I think
>> it's the first link in the chain that's throwing me.
>>
>> As I mentioned, the Hotspot is tethered to the router via a USB cable. On
>> the router Status page under Connection information, the Current IP
>> Address
>> is listed as 192.168.1.4 and the Current Default Gateway as 192.168.1.5.
>> If
>> I DMZ the gateway (192.168.1.5) on the hotspot, the router will not
>> connect
>> to the Internet - the hotspot ceased to operate. Remove the DMZ and
>> Internet service is restored. Elsewhare on the router Status page (under
>> Device Information) Cellular is listed at 192.168.4.
>>
>> Isn't 192.168.1.5 the IP I should be DMZing on the Hotsopt?
>>
>> John
>>
>>
>> On Sun, Jul 13, 2014 at 2:21 PM, David McGough <kb4fxc at inttek.net> wrote:
>>
>>
>>> 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
>>> >
>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB web page -
>>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>>>
>>>
>>
>>
>> --
>> John Kenney
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <http://lists.hamvoip.org/pipermail/arm-allstar/
>> attachments/20140714/28185e11/attachment-0001.html>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Tue, 15 Jul 2014 09:20:18 -0400 (EDT)
>> From: David McGough <kb4fxc at inttek.net>
>> To: BeagleBone Black ARM Allstar <arm-allstar at hamvoip.org>
>> Subject: Re: [arm-allstar] Hotspot Blues -- echolink, IRLP, AllStar
>> ports needed
>> Message-ID:
>> <Pine.LNX.4.44.1407150857330.4378-100000 at goliath.inttek.net>
>> Content-Type: TEXT/PLAIN; charset=US-ASCII
>>
>>
>> Hi John,
>>
>> I'm not 100% clear on the config that you've got. However, below is the
>> basic config you need, the IP addresses may not be right. Please excuse
>> the ASCII art!
>>
>> Verizon adapter (IP: 192.168.1.5)
>> ^
>> | (usb cable)
>> v
>> Network Router / DMZ host (WAN IP: 192.168.1.4, LAN IP: 10.159.x.1)
>> ^^^
>> |||
>> ||| (LAN side ethernet)
>> ||+-------------------------------------+
>> |+--------------+ |
>> v v v
>> BBB (IP:10.159.x.100) RasPi (IP:10.159.x.101) PC (IP:10.159.x.z)
>>
>>
>> Note that this case, the "Network Router" should be the DMZ host, so the
>> Verizon adapter should show a DMZ host address of: 192.168.1.4--the WAN
>> address of the router. The LAN gateway (gateway on BBB, RasPi, etc.)
>> should be 10.159.x.1, the LAN address of the "Network Router".
>>
>> The last step would be to config the "Network Router" to perform
>> selective port forwarding to the BBB and RasPi, as mentioned in the
>> earlier post.
>>
>> ....I hope this helps and the diagram survives the list server.
>>
>> 73, David KB4FXC
>>
>>
>>
>>
>>
>>
>> On Mon, 14 Jul 2014, John wrote:
>>
>> Tim & David, thanks for the information, but I'm still missing something.
>>> Hopefully, it's just a passing Homer Simpson moment on my part.
>>>
>>> I understand the ports that must be forwarded and how to set them up in
>>> the
>>> router as well as the need to move the hotspot behind the router. I think
>>> it's the first link in the chain that's throwing me.
>>>
>>> As I mentioned, the Hotspot is tethered to the router via a USB cable. On
>>> the router Status page under Connection information, the Current IP
>>> Address
>>> is listed as 192.168.1.4 and the Current Default Gateway as 192.168.1.5.
>>> If
>>> I DMZ the gateway (192.168.1.5) on the hotspot, the router will not
>>> connect
>>> to the Internet - the hotspot ceased to operate. Remove the DMZ and
>>> Internet service is restored. Elsewhare on the router Status page (under
>>> Device Information) Cellular is listed at 192.168.4.
>>>
>>> Isn't 192.168.1.5 the IP I should be DMZing on the Hotsopt?
>>>
>>> John
>>>
>>>
>>> On Sun, Jul 13, 2014 at 2:21 PM, David McGough <kb4fxc at inttek.net>
>>> wrote:
>>>
>>> >
>>> > 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
>>> > >
>>> >
>>> > _______________________________________________
>>> >
>>> > arm-allstar mailing list
>>> > arm-allstar at hamvoip.org
>>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>> >
>>> > Visit the BBB web page -
>>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>>> >
>>>
>>>
>>>
>>>
>>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>>
>> End of arm-allstar Digest, Vol 2, Issue 9
>> *****************************************
>>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page - http://www.crompton.com/hamradio/
> BeagleBoneBlackAllstar/
>
--
John Kenney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140723/ab90503c/attachment-0001.html>
More information about the arm-allstar
mailing list