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)

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)

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)

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)

132

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)

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)

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)

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)

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)

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)

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)

132
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)

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)

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)

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)

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)

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)

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)

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)

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)

Boy, I wish I had linked up fsxNet sooner, I missed a great conversation! I spent all evening last night reading this thread. All great, valid points.

Packet is alive and well here in Maine, and we're linked into New Hampshire and Canada via Houlton, but you're right: it's a very niche market. It's primarily EMAs and hospitals linked with club ECTs and ARES groups. Most of the folks around me in Southern Maine that are tinkering with it here seem to be retired folks with the time to constantly tweak audio levels and mail forwarding rules. I'm one of a few exceptions, age-wise, at 41 years old. However, I'm in it for the emcomm as well.

I brought up the idea of AREDN out here, but was told the elmers had already done the path studies and found we're too hilly. If we could get to the top of a couple commercial / emergency services towers on a couple of choice mountains, we may be able to set up an AREDN backbone, but then it gets political. I think things are shifting a little in our favor, but who knows when we'll see the results.

I also found on Facebook that North Carolina has a massive network with guys chatting with each other over the nodes. I'm not sure what their core purpose is, but they are having fun with it. For an introvert like me, and an insomniac that "plays radio" at night when the family is asleep, digital text is a great tool. I wouldn't mind seeing it come back to what I'm told is packet's original glory.

For giggles, I set up a security level for known hams on my board, and set up telnet links in the Doors menu to the nodes I'm a sysop for: WS1EC at the Cumberland County EMA, and W1YCA at the York County EMA; and their respective emergency communications teams (ham clubs). I'd love to have a radio link into my BBS, but sadly it'd just be me, and it def needs 9600 to be barely tolerable and still color ANSI.

Anyway, fun chat - it's great to see others out there with similar interests!

73 de KC1JMH
Brad

---
þ Synchronet þ El Burro Diablo - elburrodiablo.com
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

On 14 Mar 2021, Roen said the following...

Packet is alive and well here in Maine, and we're linked into New Hampshire and Canada via Houlton, but you're right: it's a very niche market. It's primarily EMAs and hospitals linked with club ECTs and ARES groups. Most of the folks around me in Southern Maine that are tinkering with it here seem to be retired folks with the time to constantly tweak audio levels and mail forwarding rules. I'm one of a few exceptions, age-wise, at 41 years old. However, I'm in it for the emcomm as well.

There's not much around here, though I saw somewhere in the next county over from me (Clay county, I'm in Duval, Jacksonville to be specific) there is Winlink, but that's about the extent of it.

For giggles, I set up a security level for known hams on my board, and
set up telnet links in the Doors menu to the nodes I'm a sysop for:
WS1EC at the Cumberland County EMA, and W1YCA at the York County EMA;
and their respective emergency communications teams (ham clubs). I'd
love to have a radio link into my BBS, but sadly it'd just be me, and it def needs 9600 to be barely tolerable and still color ANSI.

That sounds cool, will have to check that out.

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

On 03-14-21 11:25, Roen wrote to SetiOp <=-

Boy, I wish I had linked up fsxNet sooner, I missed a great
conversation! I spent all evening last night reading this thread. All great, valid points.

Sounds like it's all happening out your way. Other than APRS, there's not a lot of packet around here that I know of, but I would like to get something up, just for the hell of it. :)


... This tagline is donationware; send money to register it.
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

In article <60531E2D.149.fsx_ham@finalzone.ddns.net>
"Vk3jed" <vk3jed@21:1/109> writes:

Other than APRS, there's not a
lot of packet around here that I know of

I'm sort of in the same situation, we have APRS and WinLink on VHF, but
not much else in the way of packet.

Having an RF BBS sounds like it would be awesome, though.
-----
-nkeck72 (Mac Plus)
--- SBBSecho 3.11-Win32
* Origin: Final Zone BBS - finalzone.ddns.net (21:3/122)

On 03-18-21 07:47, Nkeck72 wrote to Vk3jed <=-

In article <60531E2D.149.fsx_ham@finalzone.ddns.net>
"Vk3jed" <vk3jed@21:1/109> writes:

Other than APRS, there's not a
lot of packet around here that I know of

I'm sort of in the same situation, we have APRS and WinLink on VHF, but not much else in the way of packet.

Having an RF BBS sounds like it would be awesome, though.

Yeah, will consider my options. I may be setting up a system for a club, in which case, I could make it accessible via packet radio and ham mesh
etworking.


... A man's incomplete until married; then he's finished!
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Boy, I wish I had linked up fsxNet sooner, I missed a great
conversation! I spent all evening last night reading this thread. All

Always happy to continue the conversation where packet is involved! :)

Packet is alive and well here in Maine, and we're linked into New

Not much in my area of Canada, but across the lake in Ohio there appears to
be some activity. I just ordered a couple of very nice but pricey TNC cables
so I can start setting something up. I am hoping to link into Ohio since I am only 5 minutes from Lake Erie.

For giggles, I set up a security level for known hams on my board, and
set up telnet links in the Doors menu to the nodes I'm a sysop for:

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 I
could move the dish elevation remotely.

I thought about maybe setting up a door as a ham gateway myself, even if it
is just me that uses it. :)

Nice to her from you!

73
Scott VE3CGN

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

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

Re: Re: Packet Radio
By: Vk3jed to Nkeck72 on Fri Mar 19 2021 05:01 pm

Do you or anyone know what software to use to connect a regular DOS BBS up on packet radio with a KISS TNC? or would you need a fancier TNC?

---
þ Synchronet þ Havens BBS havens.synchro.net
* Origin: fsxNet FTN<>QWK Gateway (21:4/10)

On 06-13-21 22:30, Phigan wrote to Vk3jed <=-

Re: Re: Packet Radio
By: Vk3jed to Nkeck72 on Fri Mar 19 2021 05:01 pm

Do you or anyone know what software to use to connect a regular DOS BBS
up on packet radio with a KISS TNC? or would you need a fancier TNC?

I haven't done it myself, but there are people who know how to do it. Might me something 'd like to try at some stage. Would need a dedicated heme.


... This tagline is donationware; send money to register it.
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Hello Phigan;

Phigan wrote to Vk3jed <=-

Do you or anyone know what software to use to connect a regular DOS BBS
up on packet radio with a KISS TNC? or would you need a fancier TNC?

What BBS software are you looking to use? Most of them have migrated over to linux. For DOS, I can think of 2 you may desire to look at:

MFNOS - which will also give you TCP/IP functions and a NetRom node
MSYS - which will give you a NetRom node.

I have the last versions of each available if you need them. MFNOS will
require Borland C to compile which I also may have a copy floating
around.

For linux, I'll suggest URONode and LinFBB. You can get both of those on sourceforge.

... Don't sweat petty things, or pet sweaty things
--- MultiMail/Linux v0.52
* Origin: Carnage - risen from the dead now on SBBS (21:4/107)

On 06-13-21 22:30, Phigan wrote to Vk3jed <=-

Re: Re: Packet Radio
By: Vk3jed to Nkeck72 on Fri Mar 19 2021 05:01 pm

Do you or anyone know what software to use to connect a regular DOS BBS
up on packet radio with a KISS TNC? or would you need a fancier TNC?

It has been done, but I'm not up with the details.


... Honest Ma, I got it from a toilet seat...
=== 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)