Has anyone attempted to run their Allstar nodes behind the AREDN network and make it work? Not have any luck with it registering even with ports forwarding set up in IPtables.
Eric
Eric
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
I setup several AllStar installs (HAMVOIP) which are all setup with both one public and one private node number on a Raspberry PI3B using an ethernet cable (eth0) to the LAN/router/WAN and a USB-to-Ethjernet adapater on a newly defined *eth1* which is connected into my Mesh network. I then "bridge" connect the public node to the private node on the same box and then connect that to another private node (eg, at our mtn top repeater). There are several ways to connect thru. Supermon web interface makes it real easy.
It works great for me but the eth1 setup is a bit confusing at first. Did a HT-to-local-pi-node thru to private (then over tunneled mesh connect to 750+ miles aways) and out the other end in reverse. Allows me to get to my mtn top repeater on different [mesh] paths when/if my primary part15 5.8 link is down.
Reminder: it's simply digital traffic - AllStar is simply VOIP over IP-based network connection, hard part is figuring out how to define/let HamVoip do the network connection path. (detailed instructions left off)
Have hope - it is possible and can work well depending on underlying metwork latency etc.
HTH,
- Don - AA7AU
It use to get put in the tmp directory but is no longer there. Maybe you can shed some light on that? Guess I could use one of my nodes as a hub link between the 192.x.x.x network and 10.x.x.x. network.
Eric
Should be plug and play just like in any other network, don't need to open ports for the Allstar node to register. If you need inbound connections(from the internet) to your Allstar node then you need to Port forward UDP 4569 in two places, on your home network router and on the AREDN node connected to your home network. Reserve local IP for Allstar node under DHCP tab.
If you are attempting to connect your Allstar nodes to each other on the same AREDN LAN, then you need to modify the rtp.conf files and map each node to the reserved IP address. Refer to this document:
https://www.hamvoip.org/multi-server%20howto.pdf
This will also work for Allstar nodes on different AREDN subnets, as long as you hardcode the node number and IPs in rtp.conf
Yes I have port forwarding done at the router and ARDEN node connected to my router. The Allstar node registers to my home IP (8.36.242.24) . On a inbound connection I get an error in the CLI that says the ip link dose not match 10.108.32.254 which is the Wifi GateWay of the AREDN node connected to my router that points to (8.36.242.24) my ISP. So, there is a routing problem as the ASL says my registered address of my Allstar node is (8.36.242.24) but the link is referencing the AREDN's WIFI GateWay Address. As long as I provide the node number and address of the connecting node in rpt.conf file, I have no problems. Im working with Allstar guys to address this issue .
Eric
The point which I was trying to make is 1) that (using HamVoip) you can have two node#s setup on one Pi; 2) you can have two different NICs on your PI (one for your LAN and one for your Mesh); 3) that you can continue to run your "public" node out thru your LAN and run your private node over the Mesh to other private nodes on the mesh; and 4) that you can bridge the public-to-private nodes within that PI to carry AllStar traffic between the public side and the mesh side without any further networking hassles or LAN exposure to the Mesh (which I avoid).
This does require setting up "private" nodes - which currently needs to be pre-defined to IP#s (or FQDN) in rpt.conf - HamVoip is working on creating a special registry feature for Private nodes# but it's not out yet.
Hope that makes sense,
- Don - AA7AU
One network connection from your AllStar-PI needs to be connected to your router (hopefully using MAC-defined IP-reservation) and your router setup for port forwarding 4569 (or whatever) to that IP.
The *other* network connection from your AllStar-PI gets connected to a LAN port on your mesh and gets its 10.x.x.x. there from your node.
The AllStar (public) node on your PI can be internally connected thru that PI to your Private node# which is available on the Mesh.
This effectively carries AllStar traffic from one network to the other by passing *thru* your AllStar node. That is the "bridge".
- Don - AA7AU
Eric
It's not required depending on how your have your mesh setup. Any LAN port will on the mesh node will serve up the DHCP from that mesh node - you get a 10.x.x.x IP (assuming that DHCP is turned on at the node). This doesn't require a VLAN switch unless you're using something like a Bullet/Rocket and trying to also break out the WLAN and/or dTd ports. If you have something like an AirRouter, just use one of the LAN ports already available.
AllStar is just digital traffic over an IP-based network. Public nodes are looked up using HamVoip/DNS or by the ASL/table; private nodes need to be pre-defined in rpt.conf at both end right now (until HamVoip takes its next step on this registry issue). If properly setup for that eth1 NIC, your PI will know how to find public nodes thru your LAN/router and how to find private nodes thru your 10.x.x.x mesh network. Note that I am NOT trying to directly connect thru the mesh to the WAN public nodes, only using private nodes to transit the Mesh.
The secret is properly defining the second NIC in ArchLinux(Pi) and in "permanently" connecting (bridging) the public and priavte node inside that single PI (easiest with Supermon).
Hope that make sense,
- Don - AA7AU
Sorry,. Eric. Guess my actual reply should have been "not me". You were asking about an AllStar node located *behind* your LAN/router on a MeshNetwork. All of my answers have involved connecting one of two PI ports to your router normally and then using the second port on the PI to connect to/thru the Mesh and then bridge AllStar traffic by connecting the public node to the private node.inside your PI.
AllStar is based on Asterisk which it uses to route/connect VOIP traffic to/from different unique node#s; Asterisk functions basically as a telephony system, implemented in software. . "Public" nodes are registered and looked up either be the ASL system and/or the HamVoip DNS-system and then routed over the network. You may be able to control that traffic from the LAN to/from your mesh, but I didn't struggle with that as my design works easily for me but involves using Private node#s and its different approach to "lookup".
Sorry to belabor the point.
Good luck,
- Don - AA7AU