I was curious to know how everyone is using 44net ip assignments within the mesh.
I notice the node web UI's Network menu has a LAN option to use 44net subnet assignments. But testing that out yielded that only local devices on the same 44net subnet can access each other, leaving neighboring nodes, or non-local nodes not being able to access services/devices that have a 44net address, even with the "LAN to 44Net" option enabled. This was tested with the ac lite, ac2 and ac3, running 3.25.8.0 and 20250821-2240974b FW's. Even more strange is that the nodes were indeed advertising the 44net subnet. Both the Hna4 section and OLSRD plugin both showed the 44net information.
Devices using the default 10net/29 assignment are accessible from both neighbors and local devices. For now, I switched it back to the default 10net. Hopefully, it was something that I missed or did wrong, as I would expect to have seen another ticket about this. When I am back in town, I will play with it some more and maybe create some static IP routes to see if that fixes (unless a reboot unfixes, LOL).
We have a 44net BGP block, as well as few /28 blocks that I wanted to put to use as we deploy AREDN nodes. But I have not been able to find much in the documentation with the use of 44net. It's not mandatory that we use 44net subnets, just thought it would be nice/cool. But I really wanted to know how everyone else was using them.
Thanks for your help!
Tony
I notice the node web UI's Network menu has a LAN option to use 44net subnet assignments. But testing that out yielded that only local devices on the same 44net subnet can access each other, leaving neighboring nodes, or non-local nodes not being able to access services/devices that have a 44net address, even with the "LAN to 44Net" option enabled. This was tested with the ac lite, ac2 and ac3, running 3.25.8.0 and 20250821-2240974b FW's. Even more strange is that the nodes were indeed advertising the 44net subnet. Both the Hna4 section and OLSRD plugin both showed the 44net information.
Devices using the default 10net/29 assignment are accessible from both neighbors and local devices. For now, I switched it back to the default 10net. Hopefully, it was something that I missed or did wrong, as I would expect to have seen another ticket about this. When I am back in town, I will play with it some more and maybe create some static IP routes to see if that fixes (unless a reboot unfixes, LOL).
We have a 44net BGP block, as well as few /28 blocks that I wanted to put to use as we deploy AREDN nodes. But I have not been able to find much in the documentation with the use of 44net. It's not mandatory that we use 44net subnets, just thought it would be nice/cool. But I really wanted to know how everyone else was using them.
Thanks for your help!
Tony
The question I have is, are you trying to use your 44net allocation IN PLACE OF the default 10/ or actually trying to put your MESH network
on the AMPRNET which requires IPIP encapsulization. The later is what I am trying to do.
And to the developers. What was the reasoning behind adding the 44net option. Was it to, as asked above, use the allocation IN PLACE OF the default 10/ ip block or actually give us the ability to join a MESH network to the AMPRNET.
I run an amprnet gateway which I have an IPIP encap tunnel but would like other MESH nodes and their LANS to be able to access my amprnet gateway giving them access to the amprnet itself and services that are avaiable.
Thanks
Kilo (Harold)
K7ILO
I am more interested in knowing how it's supposed to be used. I was experimenting and based on what I saw, it seems the devs intend the 44net to replace the default IP block. The node will hand out 44net IP's to the devices, they are not reachable from neighbors, despite them being advertised. But there is so little information/documentation on this, so I wish to learn how others, if any, use this. It's a cool idea if they can get it to work. Unless I missed something, it does not seem to work as currently implemented.
Regards,
Tony