gerdesj

I (my little company) employ a bloke to support https://www.uzerp.com/ - we use it ourselves and ditched Sage (yay!)

If you fancy it then give us a shout - it is open source - you get it for free but our time is costed if you need assistance.

That is the Open Source Covenant

I do use it quite a lot. The pfSense package for ACME can run scripts, which might use scp. Modern Windows boxes can run OpenSSH daemons and obviously, all Unix boxes can too. They all have systems like Task Scheduler or cron to pick up the certs and deploy them.

I do IT security for a living. It is quite complicated but not unrealistic for you to DIY.

Do a risk assessment first off - how important is your data to you and a hostile someone else? Outputs from the risk assessment might be fixing up backups first. Think about which data might be attractive to someone else and what you do not want to lose. Your photos are probably irreplaceable and your password spreadsheet should probably be a Keepass database. This is personal stuff, work out what is important.

After you've thought about what is important, then you start to look at technologies.

Decide how you need to access your data, when off site. I'll give you a clue: VPN always until you feel proficient to expose your services directly on the internet. IPSEC or OpenVPN or whatevs.

After sorting all that out, why not look into monitoring?

I think we might be writing at cross purposes. The system you had for your mum obviously worked effectively for you and that is the important thing.

POTS provide(s|d) a fixed point of reference - your address is registered against the number for 999 etc; it provides power for a handset or device; Its been like that for a lot of decades! These are cast iron guarantees. A POTS line has guarantees, enshrined in UK law, that mobile etc does not have. POTS is circuit switched (well it was) which means there is a physical path between the ends for the duration of the conversation.

So, by old school, I mean that you currently have important guarantees about telephony in the UK that will evaporate in future. In 2025 or so, we in the UK will have finished migrating from our old school POTS copper lines and will enjoy our smart new SoGEA lines instead. Single Order Generic Ethernet Access. Instead of an emulated circuit switched line we will use VoIP across the entire country. Nothing wrong with that but it probably won't have the guarantees that POTS had.

Red Care is no more - BT have dropped it on the floor as of Feb this year which may indicate that things are not well with our future comms promises. The general system that Red Care was one product of is still available.

This is the important point: Promises (in law) that we used to be able to rely on for comms may (will) be binned.

In the UK at least, the POTS (Plain Old ...) copper phone lines carry an electrical current as well as signals and can power the handset. There are certain guarantees about this so that in an emergency your phone will still work so you can dial 999 (our original emergency number) or 112. Our fire regulations require something like 30 minutes before things should start failing. In the real world, you get out immediately and use your mobile.

We have an emergency alarm monitoring system used by businesses. Its generally known as "Red Care" which was a brand run by BT (British Telecom). You have a small device connected to a phone line (and powered by it) and it will monitor your fire detectors and building access control systems and a 24 hour manned monitoring centre will notify you in the event of an emergency. Nowadays, these devices will use your wifi and internet connection. Sometimes: old school is best.

I know what you mean. You've already read a load of log files on behalf of an "engineer" who seems incapable of doing it themself. You've also eliminated DNS and NTP and laughed at suggestions relating to SFC /SCANNOW. Then you roll up your sleeves and plug into the Matrix ...

Which distro do you use? Ubuntu, Debian, Arch and Gentoo have packages and I've no doubt that most others do too. On Linux you should not have to go to random websites and download stuff and faff around - use the built in distribution packages. If you are not sure what you've got try this at a command prompt and read the output:

$ cat /etc/os-release

As a last resort, you can run tcpdump on nearly anything and dump to .pcap, transfer that and then open that in Wireshark. Note that modern Windows has a OpenSSH client and server available so getting files around via scp is a doddle. Windows can even do NFS too and there is of course Samba - but CIFS/SMB can be tricksy.

Errm, Wireshark. Please bear with me.

Wireshark is a shining example of an open source project completely and utterly crapping on the closed source competition. As a result we all benefit. I recall spending a lot of someone else's money on buying a sort of ruggedized laptop with two ethernet ports to do the job back in the day.

Nowdays, I can run up a tcpdump session on a firewall remotely with some carefully chosen timings and filters and download it to my PC and analyse it with Wireshark.

OK, all so convenient but is it any use?

Say you have a VoIP issue of some sort. The PCAP from tcpdump that you pass to Wireshark can analyse it to the nth degree. Wireshark knows all about SIP and RTP (and IAX) and you can even play back the voice streams or have them graphed so you can see what is wrong or whatever. That's just VoIP, it has loads of other dissectors and decorators built in.

So what?

The UK (for example) will be dispensing with boring old, but reliable, POTS (Plain Old Telephony System) by 2025. Our entire copper telephony and things like RedCare (defunct soon) will go away.

We are swapping out circuit switching for packet switching. To be fair, a lot of the backend is already TCP/UDP/IP that is shielded away from us proles. When SoGEA (Single Order Generic Ethernet Access) really kicks in then the old school electric end to end connection will be lost in favour of packet switching, which never fails (honest guv).

If you are an IT bod of any sort, you really should be conversant with Wireshark.

A quick search comes up with "Phone Link" which only seems to work with Windows on the "PC" end, whereas KDE Connect will work everywhere that KDE works, which includes Windows.

https://www.microsoft.com/en-in/windows/sync-across-your-devices

It really isn't the same as Konnect which is a bloody marvel! I've used it for years.

9th Jan ...

"A hell of an improvement especially for the AMD EPYC servers"

Look closely at the stats in the headers of those three tables of test results. The NICs have different line speeds and the L3 cache sizes are different too. IPv4 and 6 for one and only IPv6 for the other.

Not exactly like for like!

Mmm first releases! Working from home, its nearly close of play. I know ... I'll update my work laptop.

OK I now have LXDE for a fall back WM so I can read stuff rather more easily than using links in a TTY and switched out SDDM for LightDM - I needed sddm-git to get LXDE to start up. SDDM now simply crashes and dumps core - no idea why. Oh and I have switched to Wayland because X11 no longer works for me. I might put off updating the wife's laptop for a while, at least until I've done my work desktop 8)

I must say its all rather pretty and smooth. Scrolling now has drag and acceleration, which is nice. I'm sure I'll get KRDC to talk to the sodding wallet so my 100s of RDP connections will work again. For now I'll call xfreerdp from the konsole. Perhaps I'll get around to configuring KeePassXC and get around to using that instead. I share several rather large .kdbx with the rest of the firm.

atop and htop and glances and several others 8)