Hi All
As I've previously posted, I've got my HAP Lite connected to my home router via a LAN port with no issues - all seems to be working fine. I can connect to the Wifi side of the Lite and access my local Mesh network (I'm tunneling in).
What of the other 3 (currently) unused LAN Ports? Are they in the LIte's subnet or my home router's?
As I've previously posted, I've got my HAP Lite connected to my home router via a LAN port with no issues - all seems to be working fine. I can connect to the Wifi side of the Lite and access my local Mesh network (I'm tunneling in).
What of the other 3 (currently) unused LAN Ports? Are they in the LIte's subnet or my home router's?
Ports 2 - 4 are on the same LAN as the hAP's WiFi. Whatever you put there will be connected to the AREDN mesh. Assuming you have the hAP set for the default LAN addressing mode, the hAP will function as a DHCP server, and therefore assign 10.x.x.x addresses to devices connected to port 2 - 4 or connected via WiFi (if the hAP is configured to operate a WiFi access point on either 2.4 or 5 GHz). Some things that you may want to put there are: IP phone, a PC or Raspberry Pi, IP camera, etc. Any of those will be directly accessible from the AREDN mesh.
I ask because I'm setting up an Allstar node on my existing Raspberry Pi IRLP one and want to keep IRLP on the internet (which it currently does via WiFi to my home's router) but Allstar (via the hardwired LAN port) is to be on the Mesh only.
"is to be on the Mesh only."
So, you are considering moving your Raspberry Pi from being LAN connected to you home router
to being LAN connected to your hAP.
You already have a port forward in your home router so that other IRLPs can link with your IRLP.
(or is IRLP a client/server service?)
If you have a port forward in your home router for IRLP, you will need to also forward that port in the hAP.
You want to add another service on the Raspberry PI; Allstar.
Is Allstar a client-server or peer-to-peer?
If peer-to-peer;
Without a port forward in both the hAP and the home router, the internet cannot reach your Allstar.
Else if client/server, the Allstar is not 'Mesh only'.
Maybe separate Raspberry Pis would be a solution.
I hope this helps,
Chuck
I think I understand your completely run together sentence for paragraph 2. As I read it, you will have one RasPi that will have both IRLP and Allstar on it. You want the IRLP to be on the Internet by way of your home WiFi. The Allstar node should be only on the mesh by way of a wired LAN connection from the RasPi to a LAN port (ports 2 - 4) the hAP. If that is correct, as long as the routing tables in the Pi, and the two applications understand that separation, you should be good to go..
Roger that (I have a habit of turning a novella into War & Peace
)
Thanks for the confirmation - you have my plans exactly correct. (now to figure out the hAP routing!)
That's what I figured, thanks.
Guess I'm still missing a piece to the puzzle however. As both eth0 and wlan0 are active, I'm trying to wrap my head around how either can be told to use one and not the other...
Well hiya Keith
Here's the thing. IRLP has a daemon (mynetd) that is used to detect incoming calls and requires Port 15425 be forwarded through one's router (in my case, the router that connects to my internet modem, not the hAP). I have the Wifi interface (wlan0) in the Pi set to use that router (192.168.x.x. subnet).
In a nutshell, Port 15425 is forwarded within the 192.168.x.x subnet but for some reason, that IRLP daemon is grabbing the IP assigned to the LAN port (10.150.x.x subnet and connected to the hAP) IF that LAN connection (eth0) is active. If not connected, the daemon grabs the wlan0, which is correct.
It seems to be an issue in that daemon so I may not be able to use the same Pi for both IRLP and Allstar