• Packet Radio

    From SetiOp@21:4/140 to All on Tuesday, January 05, 2021 00:03:44
    Hello everyone! I am curious if anyone has packet radio being used in their local area for something other than APRS? Packet has pretty much disappeared here in Ontario, Canada, although APRS is still active. I appreciate your
    time.

    73
    Scott
    VE3CGN

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From Avon@21:1/101 to SetiOp on Tuesday, January 05, 2021 21:56:13
    On 05 Jan 2021 at 12:03a, SetiOp pondered and said...

    Hello everyone! I am curious if anyone has packet radio being used in their local area for something other than APRS? Packet has pretty much disappeared here in Ontario, Canada, although APRS is still active. I appreciate your time.

    73
    Scott
    VE3CGN

    Hi Scott.

    Here in Dunedin we have APRS but packet has disappeared also. :(

    A future hope of mine is to try and get my Mystic BBS on the air and
    accessible via packet and TCP/IP connection.

    Best, Paul
    ZL4PH

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to SetiOp on Tuesday, January 05, 2021 21:13:00
    On 01-05-21 00:03, SetiOp wrote to All <=-

    Hello everyone! I am curious if anyone has packet radio being used in their local area for something other than APRS? Packet has pretty much disappeared here in Ontario, Canada, although APRS is still active. I appreciate your time.

    Not here that I know of, though I have a project on slow burn to setup a packet BBS "just because". :)


    ... A life? Where can I download that?
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From SetiOp@21:4/140 to Avon on Tuesday, January 05, 2021 06:27:13
    Thanks for the reply! I miss the traditional packet BBS and related infrastructure. I have been collecting TNCs just in case I can revive the
    mode. Setting up a packet gateway sounds like fun. :)

    Scott

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From SetiOp@21:4/140 to Vk3jed on Tuesday, January 05, 2021 06:35:16
    Thanks for the reply! I loved the BBS I had back in the day running FBB. I
    was planning on moving to a Linux-based platform but it never happened. My biggest problem getting packet running here has been antenna height, I need to put up a good digipeater before I can do much else to attract users. Sounds like an interesting project. I would be interested to see what you put together. :)

    73
    Scott

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From Blue White@21:4/134 to Avon on Tuesday, January 05, 2021 13:13:13
    Avon wrote to SetiOp <=-

    A future hope of mine is to try and get my Mystic BBS on the air and accessible via packet and TCP/IP connection.

    Do you have to be a HAM in order to make your BBS accessible in this manner?



    ... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From Avon@21:1/101 to Blue White on Wednesday, January 06, 2021 09:57:17
    On 05 Jan 2021 at 01:13p, Blue White pondered and said...

    A future hope of mine is to try and get my Mystic BBS on the air and accessible via packet and TCP/IP connection.

    Do you have to be a HAM in order to make your BBS accessible in this manner?

    If you're asking about sending echomail over radio, then I would say yes,
    given that the packet radio gear needs to be run by a licensed amateur radio operator. The frequencies you can use will also vary between countries somewhat.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From SetiOp@21:4/140 to lu8fjh on Tuesday, January 19, 2021 17:44:55
    In Argentina have many BBS in packet radio via intenet and RF.

    I wish I could find out how to get people interested in it here in Canada again. We had quite a good network in our area at one time. I am happy to see that people are still using it and I might be able send traffic to others via RF. I am still deciding what to set up here, but I am looking forward to
    having something on the air.

    Scott VE3CGN

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From tenser@21:1/101 to SetiOp on Wednesday, January 20, 2021 14:27:03
    On 19 Jan 2021 at 05:44p, SetiOp pondered and said...

    In Argentina have many BBS in packet radio via intenet and RF.

    I wish I could find out how to get people interested in it here in Canada again. We had quite a good network in our area at one time. I am happy
    to see that people are still using it and I might be able send traffic
    to others via RF. I am still deciding what to set up here, but I am looking forward to having something on the air.

    So it's an odd thing. Having recently gone through the hassle
    of setting up a packet station _and_ an AMPRNet subnet, I've
    got some thoughts.

    First, packet. So an initial observation is that the thrill of
    packet for _most_ users just isn't going to be there. What does
    it really offer? The ability to send email and exchange files?
    At the whopping speed of 1200 BAUD? Yeah, that's just not that
    cool. Digital modes like FT8 and FT4 at least let you earn awards
    and work DX; but packet is just like talking on the local repeater:
    no one is going to get a certificate to hang on one's wall for it.
    So the remaining uses end up being special-purpose, like traffic
    handling. Hey, there's nothing wrong with that, but let's be
    honest: if you're not a traffic handler, you're unlikely to find
    it particularly interesting. C'est la vie; the heaviest use of
    my local repeaters seems to be the nightly traffic nets. Hmm.

    Another issue is that the node software has bitrotted to the point
    of often not working. I've fixed lots of bugs in mine; it now
    "works", to a point, but is disappointingly fragile. It's clear
    that that code hasn't gotten a lot of love in the modern era.

    AMPRNet is more interesting, but what do people want to run on it?
    Standard Internet services, just over an RF circuit? Well, that's
    cool, I guess. I set up a Unix machine as a timesharing "host"
    on my AMPRNet subnet, and wrote a routing daemon, and documented
    how to set up an AMPRNet gateway on OpenBSD. That was all fun,
    but as many accounts as I can give out to local hams, what are they
    going to login and do? Play `adventure`? Hunt the wumpus? I
    guess that's fine, but only holds so much interest. The inevitable
    conclusion is that the only real reason to use it is some kind of special-purpose use, like traffic handling. But the local traffic
    handlers are all used to use FBB or BPQ or JNOS or node or whatever;
    should I write special code for those folks that's just gratuitously
    different? Hmm.

    Which goes back to the point of bugs and such in the software we're
    all using on e.g. AX.25. Arguably all of that should be rewritten
    in a modern, type- and memory-safe language, but then one wonders,
    what's the point? Why go to that effort for supporting low-speed
    AX.25?

    What we really need, I think, to make data on amateur radio really
    interesting, is an embrace of the new. Something like IPv6 over a
    better link-layer protocol (perhaps 6LoWPAN?) and then things like
    HamWan and the BBHN stuff (which seems to have basically shut down).
    Then we can start to do some cool stuff.

    But we've got to get folks interested first. That's the hard part.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From deon@21:2/116 to tenser on Wednesday, January 20, 2021 15:10:45
    Re: Re: Packet Radio
    By: tenser to SetiOp on Wed Jan 20 2021 02:27 pm

    Howdy,

    But we've got to get folks interested first. That's the hard part.

    So I'm with you there.

    I would love to get data flowing over the air - with no ongoing costs to a 3rd party, even if it was a slow speed. Building out (or optimising) a protocol to support this slow speed would be fun...

    But to get to that point, I first need to invest in some equipment - which I'm willing to do.

    Then I need to get licensed, which I'm willing to do too.

    And if I figure out how to glue it all together, if nobody else uses it (and I cant use it to connect with somebody else), then I'm thinking its not worth the
    effort :(

    I believe range is low - so if I cant get traffic more than a few 100klms away, then the opportunity to find interest seems low too...

    ...ëîåï

    ... It is more rational to sacrifice one life than six. Spock, stardate 2822.3 --- SBBSecho 3.11-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Vk3jed@21:1/109 to SetiOp on Wednesday, January 06, 2021 19:30:00
    On 01-05-21 06:35, SetiOp wrote to Vk3jed <=-

    Thanks for the reply! I loved the BBS I had back in the day running
    FBB. I was planning on moving to a Linux-based platform but it never happened. My biggest problem getting packet running here has been
    antenna height, I need to put up a good digipeater before I can do much else to attract users. Sounds like an interesting project. I would be interested to see what you put together. :)

    Yeah, initially it'll just be a simple BPQ mailbox under LinBPQ, but I'll see what my options are eventually.


    ... I have closed my consciousness to all further discussions on that.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Blue White@21:4/134 to Avon on Wednesday, January 06, 2021 13:07:29
    Avon wrote to Blue White <=-

    On 05 Jan 2021 at 01:13p, Blue White pondered and said...

    A future hope of mine is to try and get my Mystic BBS on the air and accessible via packet and TCP/IP connection.

    Do you have to be a HAM in order to make your BBS accessible in this manner?

    If you're asking about sending echomail over radio, then I would say
    yes, given that the packet radio gear needs to be run by a licensed amateur radio operator. The frequencies you can use will also vary
    between countries somewhat.

    Actually I meant allowing it to be accessed by hams via packet / TCP/IP.
    Of course, I guess once they log on I would be broadcasting, so that may
    have answered my question. :)


    ... The number you have dailed...Nine-one-one...has been changed.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From Avon@21:1/101 to Blue White on Thursday, January 07, 2021 15:13:45
    On 06 Jan 2021 at 01:07p, Blue White pondered and said...

    A future hope of mine is to try and get my Mystic BBS on the air accessible via packet and TCP/IP connection.

    Do you have to be a HAM in order to make your BBS accessible in this manner?


    If you're asking about sending echomail over radio, then I would say yes, given that the packet radio gear needs to be run by a licensed amateur radio operator. The frequencies you can use will also vary between countries somewhat.

    Actually I meant allowing it to be accessed by hams via packet / TCP/IP. Of course, I guess once they log on I would be broadcasting, so that may have answered my question. :)

    I sorta follow, if a HAM spins up a BBS and makes it available via their
    packet gear then it stands to reason that any other HAM with packet gear
    should be able to access the BBS assuming it's an open system.

    Likewise if someone logins into a BBS via telnet etc. over the Internet and that BBS is linked to packet gear then their messages are going to be sent
    out both via BinkP etc. and radio waves around the same time.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From tenser@21:1/101 to tenser on Thursday, January 14, 2021 04:40:47
    On 10 Jan 2021 at 01:26p, tenser pondered and said...

    Indeed, it's exciting; I just got things hooked up so I can
    gateway to 'telnet' to my Unix host when connecting into my
    packet computer via AX.25, which is kind of cool. Sadly,
    there doesn't seem to be a loopback interface for AX.25, so
    to test it I connected to a local digipeater and then back
    to myself. That works but is imperfect. Oddly, when running
    a command that emits lots of text, I've found some goes missing;
    I suspect I'm writing more text than will fit in a single
    AX.25 packet; perhaps I'll pay with MTUs.

    So after playing around with the gateway software a bit,
    I have this working pretty reliably now; in particular,
    I don't seem to be dropping text, which is nice.

    It's kind of cool to login over packet and send email to
    other folks. It occurs to me that one could build a
    better traffic BBS out of this.

    Pretty cool.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From vorlon@21:1/195.1 to tenser on Thursday, January 21, 2021 11:47:32
    On 19 Jan 2021 at 05:44p, SetiOp pondered and said...

    In Argentina have many BBS in packet radio via intenet

    So it's an odd thing. Having recently gone through the hassle
    of setting up a packet station _and_ an AMPRNet subnet, I've
    got some thoughts.
    [...]

    I used to run a Packet BBS (FBB), a DX Node (DX Spider), a RF to Internet
    APRS gate, a IRLP node. The use of 1200 is a low hurdel that everyone can
    get working due to the small bandwith that the radio passes. I did look
    at going 9600bps, but that required radios that could do it (Limited
    radios pre 2009), and a lot of find tuning.

    I only had one radio that could do it, but that was running the APRs
    gate. #-(

    The interactive user base though had already droped to the less than 10,
    The APRS was getting more use, but was still limited.

    In the end it wasn't worth the effort of re-setting it all up when I
    moved. It was also all running of a old Pentium 3 system running Centos3.

    The AX25 support then was a mess, and hodged with sticky tape and wire to
    keep it all running.


    But kudos to you for getting something working.I still have the radio's,
    TNC's etc, but as you said the software state is a mess. I doubt it would
    even work on todays linux versions.




    \/orlon
    VK3HEG


    --- MagickaBBS v0.15alpha (Linux/armv6l)
    * Origin: \/orlon Empire: Sector 550 (21:1/195.1)
  • From lu8fjh@21:1/209 to Vk3jed on Thursday, January 14, 2021 14:42:42
    In Argentina have many BBS in packet radio via intenet and RF.
    I have F6FBB via radio and internet telnet lu8fjh.dyndns.org:6300 lu8fjh.dyndns.org:3694 Uronode Netrom tcpip Node
    Two system acces via my Mystic bbs lu8fjh.dyndns.org

    Juan (lu8fjh)

    lu8fjh.ampr.org Web page
    lu8fjh.dyndns.org:23 Mystic
    lu8fjh.dyndns.org:3694
    lu8fjh-c64.ddns.net:6400 Petscii BBS Commodore 64
    lu8fjh-c64.ddns.net:6401 Image 2.0 Ansi/Petscii bbs Commdore 64

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
    * Origin: LU8FJH BBS * lu8fjh.dyndns.org:23 (21:1/209)
  • From Avon@21:1/101 to deon on Thursday, January 21, 2021 19:35:12
    On 20 Jan 2021 at 03:10p, deon pondered and said...

    I would love to get data flowing over the air - with no ongoing costs to
    a 3rd party, even if it was a slow speed. Building out (or optimising) a protocol to support this slow speed would be fun...

    I too would like to do this. I'm hot on building communications resiliency
    and I like the idea of a ascii BBS running contemporary bbs software
    available to folks to access over RF.

    I've not really played with the older 'built by hams for packet radio bbs' software but from what I've seen I'm not sure I would really like it.

    My ideal would be (as part of a wider plan of communications resilience) to have bbs FTN running over RF packet as a wider option for people to connect should TCP/IP over 'mainstream' internet channels be taken down due to act of god or man etc..

    We really are too dependent on the interent to handle all our global communications. It's a pity modems and copper cables have gone / are going
    the way of the dodo.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From MeaTLoTioN@21:1/158 to Avon on Thursday, January 21, 2021 11:05:02
    communications. It's a pity modems and copper cables have gone / are goingthe way of the dodo.

    We still have copper cables here in the UK! Most of the time, it feels like we're still in the dark ages with connectivity, internet and communications etc.

    We finally got Fibre to the Property here some months ago, although it is crazy expensive to get the full package, so as much as I really wanted it, I am gonna have to let it go.

    I am also looking into getting my BBS hooked up to packet radio so it can be reached over the air too. I think it will be great, as long as the speed can be at least 2400 bps, I think any slower than that, it would need to be a different theme entirely, just plain ascii or something and very cut down.

    ---
    |14Best regards,
    |11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

    |07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
    |07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

    --- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)
  • From Andre@21:3/117 to SetiOp on Thursday, January 21, 2021 08:32:40
    On 19 Jan 2021, SetiOp said the following...

    I wish I could find out how to get people interested in it here in Canada again. We had quite a good network in our area at one time.

    That's the trouble with a lot of amateur radio, and really some of the
    trouble I see with some of the people who think they're going to start
    a revival with their novel BBS.

    The nostalgia is briefly interesting, but then people move on. The only reason APRS is so popular is because it's built in to radios and takes zero effort to setup. On the other hand, packet radio is a absolute nightmare just to get the hardware/radio working right, even more so to try to have a successful
    contact.

    There just isn't any benefit or usefulness to packet radio anymore... Other systems like winlink or olivia do it much better. And there isn't any sort of pushing the envelop of technology with it either, like there is with things like mesh.

    As my elmer said to me, "You missed the boat by about twenty-five years." I wish it weren't true, and I'll probably try to set something up for the Milwaukee metro area this year, but I know it's all in vain.


    Andre
    WT9X

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Runaan BBS (21:3/117)
  • From Warpslide@21:3/110 to SetiOp on Thursday, January 21, 2021 13:50:11
    On 19 Jan 2021, SetiOp said the following...

    I wish I could find out how to get people interested in it here in Canada again.

    I just took a HAM radio course online through RAC & Annapolis Valley Amateur Radio Club. I had no idea what I was getting myself into... It was way more complicated than I expected.

    By the end of the course the teacher was telling us that we should be getting ready to write our exams & I'm just sitting there blinking with a dull look on my face.

    I'll need to go over all of the material again and do a few more practice exams before I feel I'm ready. One of these days I'll be VE3<something> and be able to press talk on this handy talky that I have...


    Jay

    --- Mystic BBS v1.12 A47 2021/01/16 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From tenser@21:1/101 to Andre on Friday, January 22, 2021 08:40:15
    On 21 Jan 2021 at 08:32a, Andre pondered and said...

    On 19 Jan 2021, SetiOp said the following...

    I wish I could find out how to get people interested in it here in Ca again. We had quite a good network in our area at one time.

    That's the trouble with a lot of amateur radio, and really some of the trouble I see with some of the people who think they're going to start
    a revival with their novel BBS.

    I think people conflate things. There's going back
    to the salad days of AX.25 packet BBSes and things like
    that, and yes, that's just not coming back.

    But I think there's room for experimentation with data
    and digital modes. Things like NPR ("New Packet Radio")
    are good examples of what _can_ be done, if we had a
    more experimental mindset.

    The nostalgia is briefly interesting, but then people move on. The only reason APRS is so popular is because it's built in to radios and takes zero effort to setup. On the other hand, packet radio is a absolute nightmare just to get the hardware/radio working right, even more so to try to have a successful contact.

    ^^ This. More generally, the problem is hams. Here in
    the US, the symbol-rate limit is an unnecessary barrier
    to experimenting with newer modulation types and building
    higher throughput systems. But when I scan through the
    comments on the ARRL proposal to eliminate the symbol rate
    limits from the rules governing the amateur radio service,
    instead using _bandwidth_ limits (which frankly makes a
    lot more sense) much of the argument is against the proposal
    and much of the reason for that are septuagenarians and
    older mad about PACTOR III. "What's wrong with AX.25?!"
    Nothing is _wrong_ with it, but we're supposed to be a
    service that is dedicated in large part to _improving_ the
    state of the radio art.

    There just isn't any benefit or usefulness to packet radio anymore... Other systems like winlink or olivia do it much better. And there isn't any sort of pushing the envelop of technology with it either, like there is with things like mesh.

    Yup. You're right. AX.25-style packet is basically dead,
    aside from APRS. I'm much more interested in things like
    HamWan (http://www.hamwan.org/index.html) and the Pugent
    Sound Data Ring forming a high-speed metro-area RF network,
    and coming up with something new and innovative for slow/medium
    speed devices to connect in. AX.25 ain't it. Something like
    6LoWPAN and https://destevez.net/ipv6-for-amateur-radio/ might
    be.

    As my elmer said to me, "You missed the boat by about twenty-five
    years." I wish it weren't true, and I'll probably try to set something
    up for the Milwaukee metro area this year, but I know it's all in vain.

    I'm cool with that. It's what comes next that I'm really
    interested in.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Andre@21:3/117 to tenser on Thursday, January 21, 2021 15:44:49
    But I think there's room for experimentation with data
    and digital modes. Things like NPR ("New Packet Radio")

    Hadn't heard of it before now, but it looks pretty fascinating. A hell of a
    lot more interesting then AX.25.

    lot more sense) much of the argument is against the proposal
    and much of the reason for that are septuagenarians and
    older mad about PACTOR III. "What's wrong with AX.25?!"

    That describes literally every aspect of the ham radio community. ARRL and every club are so worried about losing the old guys with outdated interests that they keep wasting all their resources on that fear. Talk to any of the kids under twenty-five and they couldn't care less about EmComm, packet, Facebook groups, etc. They want to experiment and tinker and innovate and build, communicate about it on Discord... and send memes on SSTV.

    That "when all else fails" mantra is fear-based too. "Please don't take our non-profit tax-free status and don't sell off our freqency allocations." We should be selling governments, youth, hackers, makers, and whoever else on
    the notion that we can be innovators again.

    I don't know why I'm ranting. I started this reply merely to mention that I find your posts, Tenser, to be really valuable.


    Thanks,
    Andre
    WT9X

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Runaan BBS (21:3/117)
  • From Avon@21:1/101 to MeaTLoTioN on Friday, January 22, 2021 12:31:02
    On 21 Jan 2021 at 11:05a, MeaTLoTioN pondered and said...

    We still have copper cables here in the UK! Most of the time, it feels like we're still in the dark ages with connectivity, internet and communications etc.

    As they roll out fibre here they are pulling copper cables out of homes :(
    They are also decommissioning the analogue gear at the exchanges as they go.

    An issue for m with fibre is if the powers goes off at home and the NTU dies then your VoiP goes with it :(

    the speed can be

    at least 2400 bps, I think any slower than that, it would need to be a different theme entirely, just plain ascii or something and very cut
    down.

    If I ever make progress on this idea here then yes, ascii only and simple
    menus at best would be my advice :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to tenser on Sunday, January 10, 2021 19:34:00
    On 01-10-21 04:41, tenser wrote to SetiOp <=-

    Personally, I think every Ham should grab an AMPRNet allocation:
    either we use that space or we lose it. The sale of the /10 to
    Amazon a couple of years ago was a huge boon for the community,
    in that it gave ARDC a pile of money that it could use for grants
    etc, but ironically also shows that we're underutilizing our
    available resources. Using an HT to call into the local FM
    repeater is great and all, but not really all that interesting.

    I have 2 /24s, so I'm doing my bit. :)

    I did get my stuff working again, and I updated my 44net routing
    software (my router runs OpenBSD, sadly, so the stock solutions
    for Linux didn't work for me) and wrote up instructions on the
    AMPRNet portal:

    https://github.com/dancrossnyc/44ripd https://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenBSD

    Good work, adding to the documentation base. :)

    I have a timesharing host on my subnet (finger @kz2x.ampr.org
    to see if anyone is logged in...). I also have a RockPi4
    (quad-core aarch64 with 4GiB of RAM, an NVMe SSD, and a real
    ethernet PHY/MAC, not a USB bridge) running Raspbian that
    connects to a 2m rig through a Tigertronics Signalink USB
    soundcard. The RockPi runs direwolf, and what I'd like to do
    now is configure ax25d so that connection to some AX.25 SSID
    will automatically telnet to the timesharing machine (that
    part could be SSH, since it doesn't go over the air, but who
    cares?), then someone can use `axcall` or another AX.25
    terminal to connect into my Unix machine and have access to
    AMPRNet. This should be easy, except that, ironically, line
    endings are causing problems. I'll probably hack up `axspawn`
    to make it run telnet instead of invoking a shell.

    My utilisation of my space is still in itd early days, but I eventually hope to have something up on packet running AX.25 and IP at a minimum. I used to run KA9Q NOS in the old days. :)


    ... Misspelled? Impossible. My modem is error correcting.
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Pepper@21:1/187 to tenser on Sunday, January 10, 2021 10:26:05
    On 09 Jan 2021 at 12:39p, SetiOp pondered and said...
    The cool thing about AMPRNet is that you don't need to your
    ISP to route anything to you; you can do it all over tunnels.
    That's what 44ripd does; it reads AMPR RIP packets and sets
    up subnet tunnels and routes. Definitely check it out!

    I've had a logon to AMPRNet for a number of years with the intention to do something and register a few IPs. I should get my finger out and do something about it! Off to read some more of the Wiki :)

    -=Pepper=-

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Cosmik Debris BBS (21:1/187)
  • From SetiOp@21:4/140 to tenser on Sunday, January 10, 2021 12:04:59

    The cool thing about AMPRNet is that you don't need to your
    ISP to route anything to you; you can do it all over tunnels.
    That's what 44ripd does; it reads AMPR RIP packets and sets

    Interesting! I was just looking at the AMPR website and joined the mailing list. I want to build a network in our county, so I think I will
    probably get a subnet and play around with it. I'll let you know how I make
    out with it.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From x1pepe@21:1/150 to Avon on Monday, January 11, 2021 19:48:54
    Hi!
    I have a lot interest in that too! :)
    Maybe you could make a cool how-to-Mystic(os whatever)packet-radio video!!! \<(")/

    telnet sotanomsxbbs.org:23
    *The last Msx user in Ibiza*

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Sotano Msx BBS (21:1/150)
  • From tenser@21:1/101 to SetiOp on Friday, January 08, 2021 18:02:57
    On 05 Jan 2021 at 12:03a, SetiOp pondered and said...

    Hello everyone! I am curious if anyone has packet radio being used in their local area for something other than APRS? Packet has pretty much disappeared here in Ontario, Canada, although APRS is still active. I appreciate your time.

    I have a setup I can use for packet, and there is packet
    traffic in my area, but not much. Here in the US, traffic
    handlers associated with the NTS still use it, but it's
    not very popular otherwise.

    APRS has taken over as the dominant AX.25-based packet
    protocol. I can see why; packet is slow and frustratingly
    fragile. 1200 BAUD AFSK with no FEC isn't just low bandwidth,
    it's also very high latency and really lossy. For APRS you
    don't generally notice so much, but for anything approaching
    interactive use, it's rough.

    However, over the last week I got my AMPRNet (https://www.ampr.org/)
    and my 44net allocation is back on the Internet; I put a random
    Unix machine on the subnet and want to see if I can have a colleague
    connect to it from across town by packet. That should be kind of
    fun. Who needs a packet BBS when you've got a whole multiuser
    host computer?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to lu8fjh on Friday, January 15, 2021 19:46:00
    On 01-14-21 14:42, lu8fjh wrote to Vk3jed <=-

    In Argentina have many BBS in packet radio via intenet and RF.
    I have F6FBB via radio and internet telnet lu8fjh.dyndns.org:6300 lu8fjh.dyndns.org:3694 Uronode Netrom tcpip Node
    Two system acces via my Mystic bbs lu8fjh.dyndns.org

    Packet here is pretty dead, other than APRS, AFAIK. But I'd like to have something up at some stage.


    ... I'm not the one that misplaced the Deltivid asteroid belt!
    === MultiMail/Win v0.51
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to tenser on Friday, January 22, 2021 21:29:00
    On 01-20-21 14:27, tenser wrote to SetiOp <=-

    First, packet. So an initial observation is that the thrill of
    packet for _most_ users just isn't going to be there. What does
    it really offer? The ability to send email and exchange files?
    At the whopping speed of 1200 BAUD? Yeah, that's just not that

    Other than a few corner cases, I'd agree. Packet these days survives mainly to support APRS it seems. That said, I'll still eventually put something up, just coz I can.

    cool. Digital modes like FT8 and FT4 at least let you earn awards
    and work DX; but packet is just like talking on the local repeater:

    Now that's where my eyes glaze over - I don't really care about DX or awards. I've never claimed an award in my life, paper chasing doesn't thrill me at all.
    I know what I've worked, and I don't care whether you believe me or not. When I really want proof, I make audio recordings. :)

    no one is going to get a certificate to hang on one's wall for it.
    So the remaining uses end up being special-purpose, like traffic
    handling. Hey, there's nothing wrong with that, but let's be
    honest: if you're not a traffic handler, you're unlikely to find
    it particularly interesting. C'est la vie; the heaviest use of
    my local repeaters seems to be the nightly traffic nets. Hmm.

    No such beasts here, relly.

    Another issue is that the node software has bitrotted to the point
    of often not working. I've fixed lots of bugs in mine; it now
    "works", to a point, but is disappointingly fragile. It's clear
    that that code hasn't gotten a lot of love in the modern era.

    Which software exactly?

    AMPRNet is more interesting, but what do people want to run on it? Standard Internet services, just over an RF circuit? Well, that's
    cool, I guess. I set up a Unix machine as a timesharing "host"
    on my AMPRNet subnet, and wrote a routing daemon, and documented

    There used to be Jabber servers that were useful (ham only), but the one I was using disappeared years ago. :(

    What we really need, I think, to make data on amateur radio really interesting, is an embrace of the new. Something like IPv6 over a
    better link-layer protocol (perhaps 6LoWPAN?) and then things like
    HamWan and the BBHN stuff (which seems to have basically shut down).
    Then we can start to do some cool stuff.

    Yeah, some data that has useful speed and/or range (and can be made to optimise said tradeoff).

    But we've got to get folks interested first. That's the hard part.

    Always.


    ... Behind every successful man is an astonished mother-in-law.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From JF@21:2/110 to Avon on Friday, January 22, 2021 03:48:50
    My ideal would be (as part of a wider plan of communications resilience) to have bbs FTN running over RF packet as a wider option for people to connect should TCP/IP over 'mainstream' internet channels be taken down due to act of god or man etc..

    Amen! I'm very interested in this, and I've been pondering about it for a while. What I imagine is something equivalent to how BBS used to work: mail would be transferred from BBS to BBS over the phone lines, from point to
    point, in such a way as to avoid any long distance charges. The same could be done with RF: transfer FTN messages from one VHF station to the other (or
    maybe even HF), so that we don't necessarily depend on the internet in
    case of an emergency. Mail could be routed via different mediums, and there would be a mechanism in place to avoid duplicates and figure out the best
    path (Internet, phone, HF, VHF, etc.).

    JF

    --- Mystic BBS v1.12 A46 2020/03/29 (Windows/32)
    * Origin: TELNET://INKTWO/where?=CovinaCA : bbs.inktwo.com (21:2/110)
  • From SetiOp@21:4/140 to Warpslide on Friday, January 22, 2021 12:30:26
    practice exams before I feel I'm ready. One of these days I'll be VE3<something> and be able to press talk on this handy talky that I have...

    I wish you luck on your exam. It is a lot of work but it can provide a
    lifetime of enjoyment. The first time I keyed my radio was about thirty years ago! A lot has changed over the years with ham radio but a lot has stayed the same as well. :)

    73
    Scott VE3CGN

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From SetiOp@21:4/140 to Andre on Friday, January 22, 2021 12:41:37
    The nostalgia is briefly interesting, but then people move on. The only reason APRS is so popular is because it's built in to radios and takes zero effort to setup. On the other hand, packet radio is a absolute nightmare just to get the hardware/radio working right, even more so to

    Yes I agree with you. There are enough of us still interested to build a network, but it does need to have a new twist to keep people interested.
    Packet has always seemed a bit complicated to me and it didn't seem to evolve like other technology, maybe because of the limitations on VHF radio
    bandwidth.

    There just isn't any benefit or usefulness to packet radio anymore...

    I would agree partially with that. The same could be said for phone modes as well now that we have cell phone technology. It isn't really a fault of the technology as much as what we choose to do with it. APRS is a good example.


    Scott VE3CGN

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From SetiOp@21:4/140 to tenser on Friday, January 22, 2021 13:08:01
    First, packet. So an initial observation is that the thrill of
    packet for _most_ users just isn't going to be there. What does

    Yeah, it is a bit complicated to set up the infrastructure and it is slow. Those of us who are comfortable in text-only modes are going to be the
    primary users of such a system.

    So the remaining uses end up being special-purpose, like traffic
    handling. Hey, there's nothing wrong with that, but let's be

    Yes, traffic handling and emergency communications are two possibilities. Situational awareness (APRS) is another possibility. In my area
    emergencies requiring amateur radio are pretty scarce so keeping interest in maintaining infrastructure and maintaining overall interest is difficult. The problem I see is that for traffic handling on packet we need some important traffic to pass on a regular basis.

    AMPRNet is more interesting, but what do people want to run on it?

    This is something I am learning as well. I need a better understanding of how the 44 network ties in and what people are doing with it currently. I
    requested my block, but I haven't heard anything back yet.

    Which goes back to the point of bugs and such in the software we're
    all using on e.g. AX.25. Arguably all of that should be rewritten
    in a modern, type- and memory-safe language, but then one wonders,

    I agree. The last time I installed a BBS it only ran on Windows 95 and I
    ended up with a virus on the machine somehow. We need something modern,
    secure and that serves a modern purpose.

    What we really need, I think, to make data on amateur radio really interesting, is an embrace of the new. Something like IPv6 over a

    I agree totally. I was thinking if end users could connect via wifi on their laptops and use a simple client they would be more apt to use packet even if
    it was slow. Give them something they are familiar with to interface with and leave the RF infrastructure to those who want to dive deeper into that area. Maybe some kind of ham radio social media app of some kind. :)

    Mesh networking is interesting to me as well.

    Scott VE3CGN

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From Vk3jed@21:1/109 to JF on Saturday, January 23, 2021 06:33:00
    On 01-22-21 03:48, JF wrote to Avon <=-

    Amen! I'm very interested in this, and I've been pondering about it for
    a while. What I imagine is something equivalent to how BBS used to
    work: mail would be transferred from BBS to BBS over the phone lines,
    from point to point, in such a way as to avoid any long distance
    charges. The same could be done with RF: transfer FTN messages from one VHF station to the other (or maybe even HF), so that we don't
    necessarily depend on the internet in case of an emergency. Mail could
    be routed via different mediums, and there would be a mechanism in
    place to avoid duplicates and figure out the best path (Internet,
    phone, HF, VHF, etc.).

    Now that sounds like an interesting project.


    ... Find a safe part and use it as an anchor
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to JF on Saturday, January 23, 2021 08:37:42
    On 22 Jan 2021 at 03:48a, JF pondered and said...

    Amen! I'm very interested in this, and I've been pondering about it for a while. What I imagine is something equivalent to how BBS used to work: mail would be transferred from BBS to BBS over the phone lines, from
    point to point, in such a way as to avoid any long distance charges. The same could be done with RF: transfer FTN messages from one VHF station
    to the other (or maybe even HF), so that we don't necessarily depend on the internet in case of an emergency. Mail could be routed via different mediums, and there would be a mechanism in place to avoid duplicates and figure out the best path (Internet, phone, HF, VHF, etc.).

    Yep it feels like this is a 2-3 part problem. Probably the first part if just bolting old protocols and software together with the newer BBS stuff. That I think won't be overly hard. But the bigger issue is how to scale it in a way that others can jump on board and do the same. Without nodes in a mesh you don't have much resilience going on if you can only chat with yourself or 1-2 others locally.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From SetiOp@21:4/140 to Vk3jed on Friday, January 22, 2021 15:48:34
    charges. The same could be done with RF: transfer FTN messages from o VHF station to the other (or maybe even HF), so that we don't necessarily depend on the internet in case of an emergency. Mail coul be routed via different mediums, and there would be a mechanism in place to avoid duplicates and figure out the best path (Internet, phone, HF, VHF, etc.).

    Now that sounds like an interesting project.

    I agree. This type of project is something I could jump on board with.

    Scott VE3CGN

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From JF@21:2/110 to Avon on Friday, January 22, 2021 13:58:02
    Hi Avon --

    scale it in a way that others can jump on board and do the same. Without nodes in a mesh you don't have much resilience going on if you can only chat with yourself or 1-2 others locally.

    What we need is a "RF-Mesh-As-A-Service". If we could use a protocol that is already working, onto which we could add FTN as a second layer on top, then most of the hard work would be done. I've heard of projects like AREDN, AMPRNET and HF ALE; I don't know much about them, but I think some of them can provide you with IP connectivity. So yes, below the IP layer there are nodes and
    radios and antennas and a mesh network, but as far as the applications are concerned, they only see IP. This way, we could even keep delivering FTN messages via BinkD... That said, I don't know how well that would work.

    So many possibilities. But you're right, the trick is to make it approachable so that others could easily get onboard.

    JF

    --- Mystic BBS v1.12 A46 2020/03/29 (Windows/32)
    * Origin: TELNET://INKTWO/where?=CovinaCA : bbs.inktwo.com (21:2/110)
  • From SetiOp@21:4/140 to tenser on Friday, January 08, 2021 22:38:45
    Hi Tenser, sorry for the delay replying, I had issues with upgrading the BBS here, which I hope are now sorted out. I used to have AMPR address space many years ago and was looking to set something up again a few years ago but there was very little interest in what I was trying to do. I am interested in
    seeing what you can put together!

    73
    Scott

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From tenser@21:1/101 to SetiOp on Sunday, January 10, 2021 04:41:04
    Hi Tenser, sorry for the delay replying, I had issues with upgrading the BBS here, which I hope are now sorted out. I used to have AMPR address space many years ago and was looking to set something up again a few
    years ago but there was very little interest in what I was trying to do.
    I am interested in seeing what you can put together!

    Personally, I think every Ham should grab an AMPRNet allocation:
    either we use that space or we lose it. The sale of the /10 to
    Amazon a couple of years ago was a huge boon for the community,
    in that it gave ARDC a pile of money that it could use for grants
    etc, but ironically also shows that we're underutilizing our
    available resources. Using an HT to call into the local FM
    repeater is great and all, but not really all that interesting.

    I did get my stuff working again, and I updated my 44net routing
    software (my router runs OpenBSD, sadly, so the stock solutions
    for Linux didn't work for me) and wrote up instructions on the
    AMPRNet portal:

    https://github.com/dancrossnyc/44ripd https://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenBSD

    I have a timesharing host on my subnet (finger @kz2x.ampr.org
    to see if anyone is logged in...). I also have a RockPi4
    (quad-core aarch64 with 4GiB of RAM, an NVMe SSD, and a real
    ethernet PHY/MAC, not a USB bridge) running Raspbian that
    connects to a 2m rig through a Tigertronics Signalink USB
    soundcard. The RockPi runs direwolf, and what I'd like to do
    now is configure ax25d so that connection to some AX.25 SSID
    will automatically telnet to the timesharing machine (that
    part could be SSH, since it doesn't go over the air, but who
    cares?), then someone can use `axcall` or another AX.25
    terminal to connect into my Unix machine and have access to
    AMPRNet. This should be easy, except that, ironically, line
    endings are causing problems. I'll probably hack up `axspawn`
    to make it run telnet instead of invoking a shell.

    It occurs to me that I might be better having folks telnet into
    a plan9 machine, since someone might try to run `vi` or something
    over AX.25, which is ... not going to work.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From SetiOp@21:4/140 to tenser on Saturday, January 09, 2021 12:39:57
    It sounds like you have been busy! I really need to look into AMPRNet again
    and check out the links you sent (thanks for that!). It sounds like a lot of fun for sure. Now that I have the BBS back up, I want to do some kind of gateways into different networks/machines as well. I am not sure how
    successful I will be getting my ISP to route a subnet to me, but maybe. It
    has been a long while since I did that kind of stuff myself, so I would be learning it all over again. Great to hear packet and ham radio alive and well in your area. :)

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From tenser@21:1/101 to SetiOp on Sunday, January 10, 2021 13:26:01
    On 09 Jan 2021 at 12:39p, SetiOp pondered and said...

    It sounds like you have been busy! I really need to look into AMPRNet again and check out the links you sent (thanks for that!). It sounds
    like a lot of fun for sure. Now that I have the BBS back up, I want to
    do some kind of gateways into different networks/machines as well. I am not sure how successful I will be getting my ISP to route a subnet to
    me, but maybe.

    The cool thing about AMPRNet is that you don't need to your
    ISP to route anything to you; you can do it all over tunnels.
    That's what 44ripd does; it reads AMPR RIP packets and sets
    up subnet tunnels and routes. Definitely check it out!

    It has been a long while since I did that kind of stuff
    myself, so I would be learning it all over again. Great to hear packet
    and ham radio alive and well in your area. :)

    Indeed, it's exciting; I just got things hooked up so I can
    gateway to 'telnet' to my Unix host when connecting into my
    packet computer via AX.25, which is kind of cool. Sadly,
    there doesn't seem to be a loopback interface for AX.25, so
    to test it I connected to a local digipeater and then back
    to myself. That works but is imperfect. Oddly, when running
    a command that emits lots of text, I've found some goes missing;
    I suspect I'm writing more text than will fit in a single
    AX.25 packet; perhaps I'll pay with MTUs.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From JF@21:1/139 to JF on Saturday, January 23, 2021 08:21:44
    An afterthought...

    like AREDN, AMPRNET and HF ALE; I don't know much about them, but I
    think some of them can provide you with IP connectivity. So yes, below

    I believe AMPRNET is not that easy to setup, because you're using directional antennas that need to be lined up properly. (GHz range)

    I've read something to the effect of IP being used over AX.25 (don't really know what I'm talking about) but apparently it's excruciating slow.

    There's also Winlink that is interesting... though that doesn't provide
    you with an IP-layer, it's just straight up messaging.

    There's satellite, but that's probably far-fetched.

    JF

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: bitHaven BBS (21:1/139)
  • From tenser@21:1/101 to Andre on Sunday, January 24, 2021 03:05:39
    On 21 Jan 2021 at 03:44p, Andre pondered and said...

    But I think there's room for experimentation with data
    and digital modes. Things like NPR ("New Packet Radio")

    Hadn't heard of it before now, but it looks pretty fascinating. A hell
    of a lot more interesting then AX.25.

    Indeed. I think there are some folks who want to double
    down on old technology like AX.25, but ... why? I mean,
    I got it running here at my QTH and that was kind of fun,
    but no one uses it for anything.

    lot more sense) much of the argument is against the proposal
    and much of the reason for that are septuagenarians and
    older mad about PACTOR III. "What's wrong with AX.25?!"

    That describes literally every aspect of the ham radio community. ARRL
    and every club are so worried about losing the old guys with outdated interests that they keep wasting all their resources on that fear. Talk
    to any of the kids under twenty-five and they couldn't care less about EmComm, packet, Facebook groups, etc. They want to experiment and tinker and innovate and build, communicate about it on Discord... and send
    memes on SSTV.

    It was telling to me that KB6NU noted that there was too much
    emphasis on public service in the ARRL's latest mission on the
    purpose of amateur radio. I agree with him: we are simply too
    focused on that as a mission, without understanding that the
    agencies that are being served frankly don't need us.

    Much ado was made about the 50 hams who went down to Puerto
    Rico after Hurricane Maria and passed traffic, but it's
    important to note that they exclusively passed health and
    welfare traffic.

    The places where amateur radio really serve the public as a
    communications of last resort mechanism are almost entirely
    in the developing world, and that's certainly useful, but in
    order to participate (at least from the US....) you pretty
    much have to have HF privileges.

    The kerfuffle around the league proposing expanded HF privileges
    for technicians is so representative: it's mostly gatekeeping
    by old guys who fear that their contesting stations are going
    to be drowned out by a bunch of lids, but what I think all of
    these things fail to understand is that most techs have no
    interested in HF: "talking on the radio" just isn't that
    interesting. What _is_ interesting is telemetry, remote
    instrumentation control, interfacing with computers and robots,
    and tinkering with radios. All of that can be done with a
    tech license, but why bother jumping through the hoops and
    getting yelled at by a bunch of angry old men when you can just
    buy a Zigbee hat for an arduino or raspberry pi and avoid all
    of that, instead?

    That "when all else fails" mantra is fear-based too. "Please don't take our non-profit tax-free status and don't sell off our freqency allocations." We should be selling governments, youth, hackers, makers, and whoever else on the notion that we can be innovators again.

    I totally agree. The innovation is just not there.

    I don't know why I'm ranting. I started this reply merely to mention
    that I find your posts, Tenser, to be really valuable.

    Thank you! I appreciate that. I'm afraid I succumbed to the rant
    urge myself.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From tenser@21:1/101 to Vk3jed on Sunday, January 24, 2021 03:14:31
    On 22 Jan 2021 at 09:29p, Vk3jed pondered and said...

    Another issue is that the node software has bitrotted to the point
    of often not working. I've fixed lots of bugs in mine; it now "works", to a point, but is disappointingly fragile. It's clear
    that that code hasn't gotten a lot of love in the modern era.

    Which software exactly?

    Approximately all of it, but I'm referring specifically to
    the AX.25 tools and apps for Linux. An interesting example
    is, "axspawn": this lets hams log into the local (Linux)
    host, automatically creating accounts for them if such don't
    already exist. The issue is that it's broken, and loses
    data: the Linux AX.25 stack in connected only supports sending
    data using the SEQPACKET socket type, which means that
    individual write(2) calls must limit the amount of data they
    send to fit into a single AX.25 frame. But the `axspawn`
    program doesn't do that; it spawns a pseudo-TTY pair and
    runs a shell on the child end, and just writes whatever comes
    down the parent side to the socket. It's easy enough to fix;
    one simply chunks those writes up in a loop. There was also
    some hokey rate-limiting stuff built around alarm(3), but it
    seemed straight up broken.

    I ended up rewriting it to `telnet` to the Dragonfly machine
    on my local AMPRNet subnet, so when users connect to my host
    they're really `telnet`ing into my host machine, and had to
    fix all of that.

    Another issue was in the `ttylinkd` daemon: this is basically
    an interface to the venerable talkd(8), and speaks the same
    weird undocumented protocol. But its handling of that protocol
    was broken (it didn't talk to the local daemon on the right
    interface) so I had to fix it. That was really annoying.

    I attribute all of this to this software being overly complex
    and essentially unmaintained. I could fix it locally, but
    its tedious.

    Who knows what bugs are lurking in the kernel AX.25 implementation?

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to SetiOp on Sunday, January 24, 2021 07:32:00
    On 01-22-21 15:48, SetiOp wrote to Vk3jed <=-

    charges. The same could be done with RF: transfer FTN messages from o VHF station to the other (or maybe even HF), so that we don't necessarily depend on the internet in case of an emergency. Mail coul be routed via different mediums, and there would be a mechanism in place to avoid duplicates and figure out the best path (Internet, phone, HF, VHF, etc.).

    Now that sounds like an interesting project.

    I agree. This type of project is something I could jump on board with.

    I'm not sure of the legalities of passing non ham traffic (third party trsffic rules apply?). But as a test, there's a simple option, setup a dedicated ham network to test out the technology, sort out the legalities later. :)


    ... This is one sick group. I feel that I've finally found my home.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to tenser on Sunday, January 24, 2021 08:07:00
    On 01-24-21 03:14, tenser wrote to Vk3jed <=-

    Approximately all of it, but I'm referring specifically to
    the AX.25 tools and apps for Linux. An interesting example

    Yeah, the kernel stuff looks well and truly bit rotted. I have been playing with LinBPQ, which seems to work

    Another issue was in the `ttylinkd` daemon: this is basically
    an interface to the venerable talkd(8), and speaks the same
    weird undocumented protocol. But its handling of that protocol
    was broken (it didn't talk to the local daemon on the right
    interface) so I had to fix it. That was really annoying.

    Hmm, yeah that would be a problem. :)

    I attribute all of this to this software being overly complex
    and essentially unmaintained. I could fix it locally, but
    its tedious.

    Who knows what bugs are lurking in the kernel AX.25 implementation?

    A lot of people use non kernel implementations like JNOS and LinBPQ these days.


    ... Aviation Lie Ä I thought YOU took care of that.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to SetiOp on Sunday, January 24, 2021 08:22:00
    On 01-22-21 12:41, SetiOp wrote to Andre <=-

    The nostalgia is briefly interesting, but then people move on. The only reason APRS is so popular is because it's built in to radios and takes zero effort to setup. On the other hand, packet radio is a absolute nightmare just to get the hardware/radio working right, even more so to

    Yes I agree with you. There are enough of us still interested to build
    a network, but it does need to have a new twist to keep people
    interested. Packet has always seemed a bit complicated to me and it
    didn't seem to evolve like other technology, maybe because of the limitations on VHF radio bandwidth.

    There just isn't any benefit or usefulness to packet radio anymore...

    I would agree partially with that. The same could be said for phone
    modes as well now that we have cell phone technology. It isn't really a fault of the technology as much as what we choose to do with it. APRS
    is a good example.

    Maybe packet of the future needs to leverage modern SDR hardware, and ditch the limitations of VHF voice radios altogether? Could start playing on 70cm. This might also help improve SDR software, which often lacks poor integration with legacy systems - for example, try building a SDR based repeater or linking a SDR transceiver to something like Echolink, without jumping through a heap of hoops.

    No reason the system can't be capable of being run in voice mode or data - it would be SOFTWARE defined radio, afterall. :)


    ... NEW! John Bobbitt doll. Some disassembly required.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From tenser@21:1/101 to Avon on Sunday, January 24, 2021 15:05:56
    On 21 Jan 2021 at 07:35p, Avon pondered and said...

    On 20 Jan 2021 at 03:10p, deon pondered and said...

    I would love to get data flowing over the air - with no ongoing costs a 3rd party, even if it was a slow speed. Building out (or optimising protocol to support this slow speed would be fun...

    I too would like to do this. I'm hot on building communications
    resiliency and I like the idea of a ascii BBS running contemporary bbs software available to folks to access over RF.

    I've not really played with the older 'built by hams for packet radio
    bbs' software but from what I've seen I'm not sure I would really like
    it.

    My ideal would be (as part of a wider plan of communications resilience) to have bbs FTN running over RF packet as a wider option for people to connect should TCP/IP over 'mainstream' internet channels be taken down due to act of god or man etc..

    I think people make a bit of a mistake here by throwing
    the proverbial baby out with the bathwater. The Internet
    was _designed_ for resiliency; it's not like the phone
    company that had to engineer in massive redundancies and
    controls because it was centralized; by design it's
    decentralized and packet routing allows one to get around
    broken links etc.

    I can understand the desire for communications infrastructure
    that doesn't rely on commercial providers: the providers
    themselves can fail, and if that's the only provider, then
    redundancy at the protocol level is just a distinction
    without a difference.

    But the solution here isn't to revert to ancient technology
    (AX.25 and packet BBSes) but rather to build something
    better that provides IP routing on top of autonomous,
    redundant RF links. AMPRNet is a step in the right direction;
    things like AREDN and Hamwan are existence proofs to emulate.
    The next step is a framing format for putting IPv6 datagrams
    directly on the air and doing something with globally
    routable IP spaces.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Pepper@21:1/187 to lu8fjh on Friday, February 12, 2021 06:18:09
    On 14 Jan 2021, lu8fjh said the following...
    I have F6FBB via radio and internet telnet lu8fjh.dyndns.org:6300 lu8fjh.dyndns.org:3694 Uronode Netrom tcpip Node

    What's the differences between UroNode and JNOS? There does not seem to be
    much documentation that I can find.
    I like how you've tied them all together, via the BBS.
    I had a quick look last night at your BBS, I'll have a wander more around
    this weekend.
    de k1ymi

    -=Pepper=-

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Cosmik Debris BBS (21:1/187)
  • From lu8fjh@21:1/209 to Pepper on Friday, February 12, 2021 19:14:16
    Hi. The difference between JNOS and URONODE is that jnos is a BBS with
    the TCPIP protocol over ax25 and uronode is a netrom node that also supports the tcpip protocol wich allows you to do this type of communication via
    telnet for example.

    73s

    Juan (lu8fjh)

    --- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
    * Origin: LU8FJH BBS * lu8fjh.dyndns.org:23 (21:1/209)
  • From tenser@21:1/101 to mobbyg on Monday, May 03, 2021 04:50:56
    On 22 Mar 2021 at 04:23a, mobbyg pondered and said...

    Is AMPRNet still a thing? I thought I had seen somewhere that it was
    kind of going out.

    AMPRNet is still very much a thing, but it's a massively
    underutilized resource and more people should get allocations.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From mobbyg@21:1/101 to All on Monday, March 22, 2021 04:23:31
    Is AMPRNet still a thing? I thought I had seen somewhere that it was kind of going out.

    I did love playing with NOS on my Amiga 500 back in the day using my
    Kamtronics KPC-3 with some of my friends. We had one guy in the next county over helped us getit up and working and we did a lot of cool stuff with it. I had the software which I downloaded from Aminet, but n clue how to really use it.

    I wouldn't mind doing something with packet again. I have an MFJ TNC-2 just sitting here under my Zoom v.32bis and USR 56K modems just itching to get on the air.

    73.
    de Rich, KB2MOB

    |04---- |15Rich Lawrence, KB2MOB
    |14//// |15SysOp of Radio Freqs & Geeks BBS
    |01--v|10/// |07-Ham/Shortwav Radio, Tabletop Gaming and General Geekery- |11\\|02xx/ |08mobbyg@gmail.com

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Nkeck72@21:3/122 to SetiOp on Monday, May 03, 2021 06:38:04
    SetiOp wrote:
    Hello everyone! I am curious if anyone has packet radio being used in their local area for something other than APRS? Packet has pretty much disappeared here in Ontario, Canada, although APRS is still active. I appreciate your time.

    Here in east Tennessee we have a few Winlink nodes as well as quite a
    few APRS digipeaters and even a couple weather stations. We don't have
    any AX.25 nodes but I plan to change that here in the near future. :P
    --- SBBSecho 3.11-Win32
    * Origin: Final Zone BBS - finalzone.ddns.net (21:3/122)
  • From Vk3jed@21:1/109 to tenser on Monday, May 03, 2021 21:54:00
    On 05-03-21 04:50, tenser wrote to mobbyg <=-

    AMPRNet is still very much a thing, but it's a massively
    underutilized resource and more people should get allocations.

    I've already got 2 /24s. :)


    ... We spared no expense.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Roen@21:4/10 to SetiOp on Monday, March 22, 2021 23:01:00
    Re: Re: Packet Radio
    By: SetiOp to Roen on Fri Mar 19 2021 09:29 pm

    Hi Scott,

    A pleasure to chat with you and these other fine hams as well!

    so I can start setting something up. I am hoping to link into Ohio since I am only 5 minutes from Lake Erie.
    I'm certain they'd love to have a Canadian on their network. We used to get a thrill seeing DX contacts crawling our nodes from New Brunswick, and they loved seeing us make our way up.

    Sadly, the infrastructure between Southern Maine and them had been taken down, but others are starting to rebuild. Midcoast Maine is still going strong, we just need to reconnect to them, and then northward!

    Thats pretty cool. I have a radio telescope in my back yard so I wrote a door to access statistics and get the status of it. At one point I had it so
    A radio telescope? Cool! Most I've done with space is download SSTV from the ISS and images from NOAA, and the one contact via the ISS repeater.

    73 de KC1JMH
    Brad

    ---
    þ Synchronet þ El Burro Diablo - elburrodiablo.com
    * Origin: fsxNet FTN<>QWK Gateway (21:4/10)
  • From SetiOp@21:4/140 to Nkeck72 on Wednesday, May 05, 2021 20:01:09
    Here in east Tennessee we have a few Winlink nodes as well as quite a
    few APRS digipeaters and even a couple weather stations. We don't have
    any AX.25 nodes but I plan to change that here in the near future. :P

    Thanks for the reply! I just picked up another TNC last week myself, hoping to put up one port on the Ohio network frequency and one on a local frequency to link the two. We'll have to see how that works out. Keep me in the loop on
    your progress getting AX.25 running! I am starting from scratch in this area
    as well. Best of luck!

    Scott

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From SetiOp@21:4/140 to Vk3jed on Wednesday, May 05, 2021 20:04:22
    underutilized resource and more people should get allocations.

    I haven't had any luck reaching any coordinators here in Ontario. I used to have an allocation years ago but I lost it at some point. I'll have to try harder I guess. For now I am going to focus on getting the RF running here.

    Scott

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)
  • From Vk3jed@21:1/109 to SetiOp on Wednesday, May 12, 2021 19:14:00
    On 05-08-21 17:02, SetiOp wrote to Vk3jed <=-

    underutilized resource and more people should get allocations.
    I haven't had any luck reaching any coordinators here in Ontario. I
    Bummer. If you can't raise your coordinator, it's work asking on the 44net mailing list.

    Yeah I admit I haven't tried that, I'll have to do that. I am sure
    there is some coordinator looking after the block who can help on the list. I'll try that.

    If all else fails, the global coordinator should see your post.


    ... ALIMONY: The cost of leaving.
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/143 to SetiOp on Friday, May 07, 2021 19:25:00
    On 05-05-21 20:04, SetiOp wrote to Vk3jed <=-

    underutilized resource and more people should get allocations.

    I haven't had any luck reaching any coordinators here in Ontario. I
    used to have an allocation years ago but I lost it at some point. I'll have to try harder I guess. For now I am going to focus on getting the
    RF running here.

    Bummer. If you can't raise your coordinator, it's work asking on the 44net mailing list.


    ... OK Scotty, NOW! Detonate and energize! I mean.......
    === MultiMail/Win v0.52
    --- SBBSecho 3.10-Linux
    # Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (432:1/101)
    * Origin: Ham Inter-network Echomail Gateway. (21:1/143.0)
  • From SetiOp@21:4/140 to Vk3jed on Saturday, May 08, 2021 17:02:09
    underutilized resource and more people should get allocations.
    I haven't had any luck reaching any coordinators here in Ontario. I
    Bummer. If you can't raise your coordinator, it's work asking on the 44net mailing list.

    Yeah I admit I haven't tried that, I'll have to do that. I am sure there is some coordinator looking after the block who can help on the list. I'll try that.

    Thanks
    Scott

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Redshift BBS (21:4/140)