Eric have a VERY valid point.
Just one thing we need to confirm, the board ADRC will choose to promote will need to be a long term product and make sure that if there is a "new" improved version of it that the work they did to make the booting image is also compatible or easily portable.
If it would be compatible with openWRT would be a very good thing. And I think ARDC could even have a large scale rabate. This and a wa to mary a Ubiquity or Mikrotic dish or omni antenna And the capacity to either be a part of a "backbone" and/or a mesh and we have a winning solution.
I know that the entry level price of the raspberry pi is very appealing. Yes it would be nice to have a capacity to have the ethernet port to be able to connect to 44net and recive a /32. This could be a fun project to do. But it is not a viable one if anyone want to scale up a bit. the limitation will come back to bite us very fast.
If ARDC want to use raspeberry pi with let say pi-star/net44 interconnect, make it claer that it is ONLY for local terminaison of the network (client only) not for client and routing capacity.
In fact the real thing a Raspberry pi should do is to connect to a POP and recive a /32 and maybe relay it by wifi to other machine around the house just for fun. (Acces point mode) There are also a few distro that are specific to ham radio for the raspberry pi. Like HamPi https://github.com/dslotter/HamPi
Maybe contact those guys that are already supporting 80+ apps for ham on a rpi and ask if they would be ok to add a way to connect those RPI to net44 trough one of the POP with a simple wizard that would ask a few question like ID/password/location and if they are already connected to one of the networks or mesh on the 44 net to make sure no one will make bridges with out understanding what they are doing. And the wizard could do the hard pulling of configuring the network/vpn or wireguard etc. for the ham to actually connect to net 44 for his ham stuff.
This could be a very short time action ARDC could do to spark the use of net44
Pierre VE2PF
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Af6ep via 44Net 44net@mailman.ampr.org Envoyé : 9 août 2021 22:04 À : 44Net general discussion Cc : eric.fort.listmail@fortconsulting.org Objet : Re: [44net] On Allocations, PoPs, and Proposals
yes, one CAN add a hundred billion USB to Ethernet adapters to the pi. Yes, Linux WILL even run vlans..... but that doesn't make the PI a GOOD choice for a routing appliance with only a single ethernet port which if I remember right is itself connected via usb. A much better thing to base such an appliance on would be a board that had at least 3 (local and dual uplinks) separate hardware gigabit ethernet interfaces with each being attached to a vlan capable switch chip. Then design and build (or simply buy, aka wifi bridge) an ethernet to bits radio tranceiver. Could we not say together with TAPR, come up with and build the next TNC2021 (escentially a 3 port GigE router) and a DR2021 (long haul, point to point microwave data radio) and keep it at a price point around say $300 US. (about the cost of a decent mobile radio). This is where some of that Grant money and funds from ARDC ought be going...... To design and build needs based hardware for amaterur radio networks. Let's build a starter appliance for those who want to learn networking via 44net use. We have a grand opportunity yo elmer and teach the next generation of rf microwave data network, engineers. Given the way it's going it's going to bits and pieces (packets) (bad pun). lets take the lead and innovate while teaching the next generation. It gives us just one more important reason for which to hang on to our precious frequency allocations. May we lead in these areas and come up with a recommended appliance and config. That would move us far ahead.
On 2021-08-09 10:17, K7VE - John via 44Net wrote:
Pete,
RPI works just fine with USB to Ethernet adapters. You can add multiple Ethernet connections in this way.
On Mon, Aug 9, 2021 at 9:06 AM pete M via 44Net 44net@mailman.ampr.org wrote:
I have a question about using a RPI for net44.
Since this device only have one physical Ethernet port (and a Wi-Fi NIC).
By which way are you hoping to use those to route some traffic?
Entering by Wi-Fi then out from the Ethernet port? That can work, but I would not like that.
De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Toussaint OTTAVI via 44Net 44net@mailman.ampr.org Envoyé : 9 août 2021 05:07 À : 44net@mailman.ampr.org Cc : Toussaint OTTAVI Objet : Re: [44net] On Allocations, PoPs, and Proposals
Le 03/08/2021 à 18:54, Rob PE1CHL via 44Net a écrit : While I agree that it is attractive to use a Raspberry Pi because of its availability and the capability to also host some applications on the same device aside from doing the routing, in my experience it is much easier to use a dedicated router like the MikroTik hEX (RB750Gr3) available for about the same price, but having 5 ethernet ports and all software required for VPN and routing pre-installed and much easier to configure and maintain than a Raspberry Pi.
Of course there always are multiple options. And Raspberry Pi should be one of them.
The network setup must be as standard as possible, so that it can be implemented on a large amount of equipment :
- People building networks, remote sites, repeaters, or advanced users
with some network knowledge, may prefer a dedicated router platform, such as Mikrotik, UBNT, OpenWRT, etc...
- Beginners or standalone users may prefer plug-and-play setup on a
Raspberry Pi. The most obvious example that comes to my mind is Pi-Star (a very good Pi appliance for digital modes hotspot or repeater, which embeds many existing software for D-Star, DMR, YSF etc... into a coherent and easy to use WEB UI).
73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net