kristoff

I run OpenRTX on a Retevis RT3s, which can be done without any hardware modification. (I do not know if original firmware is available somewhere -I have not checked-. If that is the case, it should be possible to reflash the stock firmware on the device).

Anycase, I must say that M17 does not run correctly on that radio. There seems to be an issue that the first 300 ms or so of the transmission is not correctly modulated (something related to the FM modulator) and also the end of the transmission is broken of halfway the end-of-transmission frame.

I am currenly at the stage of trying to understand how OpenRTX really works, and my first idea is to implement POCSAG-paging into it. (As I have the source-code for that here anyway) and I also have some ideas for APRS to want to delve in.

(OK, that is, if I have some time left next to all the other stuff I am working on :-) ).

73 kristoff - ON1ARF

Onno,

The reason I added the cfp was to show that it is not a pure technical conference like FOSDEM or GRCON. We added a non-technical part and did that on purpose. In a way, our goal is to try to start a discussion on "how do we see the amateurradio hobby in the post-dinosaur era?"

Looking at a distance, we see a number of different evolutions:

• amateurradio is slowly starting to invert the "buy-and-use" attitude we have seen the last 20 to 30 years. Your remark on the opensourcing the firmware of radios fit into that, as does OpenRTX and similar projects.
• We also see more and more an overlap of amateurradio with other communities, like the makers, developers (think FOSDEM), SDR-experts (think GNU Radio), IoT nerds, infosecurity people, science, etc. I get the impression that these communities start to understand the value of amateurradio as a technical / scientific hobby, which is probably related to the fact that radio/wireless communication technology has become part of almost any field of technology.
• A 3th element is that the organisational structure of amateurradio is changing. The vast amount of subfields of amateurradio has shown the limits of the hierarchical 'IARU - IARU Region - National radio-society - local radioclub' structure. Using the internet (mailing-lists, webforums. telegram-groups, discord channels, matrix rooms, ...) radioamateurs with similar interests have set up virtual communities that live next to the local radioclubs.

So, in essence, we kind-of see a return of amateurradio to a 'I-want-to-know-how-it-works / experimenter / challenges' hobby, probably by the evolution of radio-technology and the 'competion' with other scienfic and technical hobbies. In my personal opinion, that is surely a good thing.

But, to get there, there are -as I see it- two big issues:

• Knowledge. Most (technically minded) radio-amateurs have a background in standard electronics, or in 'building systems'.

To return to your call for opensource firmware for radios, having access to the source-code is one thing, but actually understanding it and having the knowledge to modify or enhance it does require quite different knowledge that 'standard' analog electronics. You need knowledge of SDR and signal-processing techniques -which are much more based on math that standard electronics- plus possibly some HDL to program the FPGA and C/C++/rust for the RTOS that runs on the microcontroller inside the FPGA. Modern radio-communication equipement requires a much larger scale of knowledge then the radio-technology of 20 to 30 years ago that is the basis of the amateurradio exams (and hence courses).

Now, I see two ways to fix this:

1. Work on the knowledge-level of the amateurradio community by new and better courses that include modern radio-technology.
2. Pull in people from communities (see point 2 above) into amateurradio.

• Option 2 above looks for me the most easy option, but it does hit another big issue: how make the current amateurradio community (especially the local clubs) ready to receive these new people.

When I am at an infostand on amateurradio at -say- FOSDEM or a Makerfaire, or you meet somebody at a infosecurity conference, the most difficult question you usually have is this: "wauw. That amateurradio hobby does look interesting. How do I begin? Where do I need to go?"

I've had people at FOSDEM who said "I once went to the local radioclub in my city as I wanted some help on setting up a mesh network in my cities, so I thought that the radioamateur guys might be able to help me. There where just some old men and the only reply I got was that that is no real radio". I've come to a point where I sometimes advice people to go to their local hackerspace and see if there are no hams overthere, instead of sending them to a radioclub.

As said, there are now these communities inside the amateurradio hobby who kind-of operate next to the local clubs, but in the end, you do still need a club for certain things -like courses, or doing an exam- and being in a local club does also include things like a local fieldday or taking part in a contest or so.

Europe has the advantage -compaired to Australie- of having a larger population concentrated in a smaller area. For us, a conference is a good option to try to advance the hobby that way. I guess that, in the end, everybody has to find out what he/she can do.

73 kristoff - ON1ARF

(Posted this as a seperate message so not to mix multiple subjects)

As you mention "microcontrollers in the signal-chain of a transceiver", I am currently looking into OpenRTX.

It is really a very nice example of exactly what you mention and something that has become possible to last 1 to 2 years. With these radios that support opensource firmware, It really has allowed amateurs a look of what is inside of the firmware of a "commercial-grade" handheld radio.

Two weeks ago, I helped out in an infobooth on Amateurradio at a makerfaire here in Belgium. Things like OpenRTX allow to explain to IT-people (who normally only work on computers) how "embedded software" works, how software that runs in devices we use everyday operates. In that sense, FOSS is as much an educational tool as it is "just a piece of code that does something".

Kristoff (ON1ARF)

I completely agree with your remarks.

For people who are interested in opensource and amateurradio, I propose you have a look at the conferences on that topic.

Overhere in Europe, there are two of them

• FOSDEM ("Free and Open Source Developers European Meeting") is a yearly event held in Brussels every 1st weekend of February. In the 2024 edition, there was a devroom ("developers room") on SDR and Amateur-radio. https://fosdem.org/2024/schedule/track/radio/

The videos of the talks are online. I propose to have a look at the talks on M17 and on OpenRTX.(*) Also open source hardware is becoming more interesting.

• Next september, we will be hosting "spectrum24", a new conference on "novel ways to use the spectrum we -as citizens- are able to use. It puts a lot of emphesis on Open-source as yes, most -if not all- of the new projects coming out in amateur-radio are open source.

For this conference, we are at the "cfp" (Call for Presentations) stage. See here: https://spectrum-conference.org/24/cfp

I know that Europe is the opposite side of the globe for you in Autralia. Perhaps there are similar events on your side of the world.

Kristoff (ON1ARF)

That is valid .. in peace-time when everybody accepts that.

The problem is that the reality is a lot complex. Open source only exists, because of the open source licenses. The open source licenses are only valid, because of the copyright legislation. That legislation is only valid, .. because the nation-state has determined it is valid.

Consider a scenario where a nation-state (whatever state that may be, just making a general starement here) decides that for sectors it conciders critical for the state, it -or companies that act on its behalve- are allowrd to use / copy / enclose whatever open source technology they want without being subject to the requirements that come with the opensource license. So they can use whatever open source technology they want but they do not have to return anything to it. They can even use it in closed products.

How do you propose to handle such a scenario?

Kr.

Yes, that's a very useful idea. Thanks!

If you get your domain from OVH, you get one single mailbox (be it with a lot of aliases, like a different email-address for every service/website you use) for free.

What is your 'deleted files' policy? How long do you keep them? I had a similar issue but then found out that the nextcloud cron-process wasn't running so files in the 'deleted files' folder where never really deleted.

Well, based on advice of Samsy, take a backup of home-server network to a NAS on your home-network. (I do home that your server-segment and your home-segment are two seperated networks, no?) Or better, set up your NAS at a friend's house (and require MFA or a hardware security-key to access it remotely)

What was that saying again?

"the biggest thread to the safety and cybersecurity of the citizens of a country ... are managers who think that cybersecurity is just a number on an exellsheet"

(I don't know where I read this, but I think it really hits the nail on the head)

I have been thinking the same thing.

I have been looking into a way to copy files from our servers to our S3 backup-storage, without having the access-keys stored on the server. (as I think we can assume that will be one of the first thing the ransomware toolkits will be looking for).

Perhaps a script on a remote machine that initiate a ssh to the server and does a "s3cmd cp" with the keys entered from stdin ? Sofar, I have not found how to do this.

Does anybody know if this is possible?

Yes. Fair point.

On the other hand, most of the disaster senarios you mention are solved by geographic redundancy: set up your backup // DRS storage in a datacenter far away from the primary service. A scenario where all services,in all datacenters managed by a could-provider are impacted is probably new.

It is something that, considering the current geopolical situation we are now it, -and that I assume will only become worse- that we should better keep in the back of our mind.