2e0sips_packet_musings
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
2e0sips_packet_musings [2023/01/22 13:30] – created 2e0sip | 2e0sips_packet_musings [2023/04/17 22:13] (current) – 2e0sip | ||
---|---|---|---|
Line 1: | Line 1: | ||
A collection of some thoughts about Packet Radio. Not anticipated for direct consumption but I might find it useful to refer to them in future. | A collection of some thoughts about Packet Radio. Not anticipated for direct consumption but I might find it useful to refer to them in future. | ||
- | # Security | + | ====== |
- | ## Authentication | + | ===== Authentication |
Currently authentication in packet radio is somewhat lacking. Passwords are sent in the clear over RF and could be intercepted by anyone. One exception is BPQ's SYSOP password tool that sends a string of characters over the air similar to a [[https:// | Currently authentication in packet radio is somewhat lacking. Passwords are sent in the clear over RF and could be intercepted by anyone. One exception is BPQ's SYSOP password tool that sends a string of characters over the air similar to a [[https:// | ||
Line 9: | Line 9: | ||
Whilst this works I'd love to see a more generalised method, and I'd suggest the use of [[https:// | Whilst this works I'd love to see a more generalised method, and I'd suggest the use of [[https:// | ||
- | ## Signing | + | ===== Signing |
In current packet radio usage there' | In current packet radio usage there' | ||
+ | |||
+ | ====== Visual presentation ====== | ||
+ | |||
+ | It's no secret that I'm a big fan of [[https:// | ||
+ | |||
+ | I think it's a great candidate to send data over packet radio with slightly richer formatting whilst still maintaining minimal overheads, and the method of entering numbers to access different pages also lends itself to packet. | ||
+ | |||
+ | For an example of how it can work see [[https:// | ||
+ | |||
+ | |||
+ | ======= App Improvements ====== | ||
+ | |||
+ | ====== General ====== | ||
+ | |||
+ | * It would be great if things were easily " | ||
+ | |||
+ | |||
+ | ====== Routing ====== | ||
+ | |||
+ | I would like to: | ||
+ | |||
+ | * Distribute routes with a max-forwards parameter, limiting them being distributed more than X hops | ||
+ | * Force a route, but still over an L4 protocol? | ||
+ | * Add " | ||
+ | * Include a parameter to indicate if the route is over IP, HF etc | ||
+ | * Include a VLAN type indication. Perhaps a route is for management only. | ||
+ | |||
+ | |||
+ | ====== Chat ====== | ||
+ | |||
+ | The chat built into BPQ is fairly basic and missing some features that would significantly increase usability. I would like to see the following improvements to a new chat application: | ||
+ | |||
+ | * Some visual clue that a sent message has been acknowledged, | ||
+ | * Timestamp / Sequence sent with message so they can re-ordered | ||
+ | |||
+ | |||
+ | ====== BBS / Mail ====== | ||
+ | |||
+ | The BBS built into BPQ has basic POP3 functionality but most web based email clients etc expect IMAP. It would be ideal if IMAP functionality could be added one way or another, to support new clients and also add functionality like marking a message as read. | ||
+ | |||
+ | I've looked at ways to do this without changing BPQ and there' | ||
+ | |||
+ | I suspect the answer might be to write a new BBS.... | ||
+ | |||
+ | ======= New Software ====== | ||
+ | |||
+ | * Packet Parse - Something that " | ||
+ | * Mailing List Server - It looks like [[https:// | ||
2e0sips_packet_musings.1674394230.txt.gz · Last modified: 2023/01/22 13:30 by 2e0sip