3 ms·

Ah interesting. I don't see mention of NAT or address translation at all in the datasheet for the switch I am using. Since the original plan was just to mate CM

Ah interesting. I don't see mention of NAT or address translation at all in the datasheet for the switch I am using. Since the original plan was just to mate CM4s with a switch I hadn't considered any additional network hardware. This seems like a Rev2 thing. I could get the basic system up and running without additional complexity. But I really like the idea of forks of my work so once I've proven the basic layout I'd be happy to collaborate with the community on improvements. Do you have any more information on that type of hardware or suggestions on how to learn more? Maybe I should get on the OpenWRT mailing list and introduce myself.

dnautics 5y ago
I'm going to be making a video about how I turned an Asus PN50 into an AP using Linux NAT but tbh the performance is pretty bad (but good enough for my home office)... It's also possible I'm configuring it wrongly. The general principles should be the same as RPi and even the net configuration is likely to be identical. Rpis are notorious for just dying though. You may want to consider something more robust. Don't know if it's SSD corruption or what.
- TaylorAlexander 5y ago
  My understanding is that the issues with pi's dying is related to SD cards. But the Raspberry Pi Compute Module 4 (CM4) uses industrial eMMC memory which should have a much better lifetime.
  - dnautics 5y ago
    Thanks for the confirmation! Apologies, I meant SD, not SSD. I didn't know cm4 was better! Good to know
Abishek_Muthian 5y ago
> Maybe I should get on the OpenWRT mailing list and introduce myself. I agree. OpenWrt's HW NAT support seems to be limited to mt7621 (i.e. At least upstream version). Unless the SoC is purpose built for network computation I don't think they feature HW NAT, But open-source drivers for the SoC's which has HW acceleration is a bigger problem. I think aiming for a good SW offloading is a more reasonable goal to start with, Which OpenWrt seems to be doing with MIPS based CPUs.
- TaylorAlexander 5y ago
  Interesting. The mt7621 is significantly more advanced than the basic switch chip I am using so far. I will continue with my current design and still try to reach out to the OpenWrt community for comment.

dnautics 5y ago

I'm going to be making a video about how I turned an Asus PN50 into an AP using Linux NAT but tbh the performance is pretty bad (but good enough for my home office)... It's also possible I'm configuring it wrongly. The general principles should be the same as RPi and even the net configuration is likely to be identical. Rpis are notorious for just dying though. You may want to consider something more robust. Don't know if it's SSD corruption or what.

TaylorAlexander 5y ago
My understanding is that the issues with pi's dying is related to SD cards. But the Raspberry Pi Compute Module 4 (CM4) uses industrial eMMC memory which should have a much better lifetime.
- dnautics 5y ago
  Thanks for the confirmation! Apologies, I meant SD, not SSD. I didn't know cm4 was better! Good to know

Abishek_Muthian 5y ago

> Maybe I should get on the OpenWRT mailing list and introduce myself. I agree. OpenWrt's HW NAT support seems to be limited to mt7621 (i.e. At least upstream version). Unless the SoC is purpose built for network computation I don't think they feature HW NAT, But open-source drivers for the SoC's which has HW acceleration is a bigger problem. I think aiming for a good SW offloading is a more reasonable goal to start with, Which OpenWrt seems to be doing with MIPS based CPUs.

TaylorAlexander 5y ago
Interesting. The mt7621 is significantly more advanced than the basic switch chip I am using so far. I will continue with my current design and still try to reach out to the OpenWrt community for comment.