It appears that there's been some progress in getting the ax.25 stack in the kernel finally fixed. For NetRom usage, it's a matter of a 4 line
Pepper wrote to N1uro <=-
Well that's some good news! Nice to see it may be going in a positive direction now.
Pepper wrote to N1uro <=-
Well that's some good news! Nice to see it may be going in a positive direction now.
We can only hope! Running a 3rd party app with it's own protocol stack works BUT you suffer speed in packet switching because it's 3rd party
and frames still have to pass through the kernel. It'd be better to get the native kernel stack fixed.
On 10-07-21 10:58, N1uro wrote to All <=-
Greetings;
It appears that there's been some progress in getting the ax.25 stack
in the kernel finally fixed. For NetRom usage, it's a matter of a 4
line patch to close previously used (but no longer in use) ax.25
sockets which establishes the virtual circuit required for NetRom to transport under. I'm shocked that the politics of maintaining kernel patches is so deep that it's stalled its repair for so long. When this
is resolved I'll recreate my sourceforge repositories for URONode, axMail-FAX, and htppu convers servers.
Vk3jed wrote to N1uro <=-
Good to hear there seems to be progress at last.
On 12-19-21 20:23, N1uro wrote to Vk3jed <=-
Hello Tony;
Vk3jed wrote to N1uro <=-
Good to hear there seems to be progress at last.
Yes there appears to be a renewed interest in getting things actually fixed. The netrom patch was said to finally been applied but I haven't heard anything about it actually being deployed out. With that however
I did post new releases of all my projects on sf.net URONode still
remains one of the smaller packet binaries available while also being
the fastest: 341116 Oct 22 12:30 /usr/local/sbin/uronode
Vk3jed wrote to N1uro <=-
I might look at kernel packet when the new kernels come out. Will probably have to roll my own, unless everything's modular and
available. :)
On 12-24-21 15:18, N1uro wrote to Vk3jed <=-
Most ham stuff is modular in the kernels but you may be better off
rolling your own. As I understand it, the netrom patch has been
included now but I don't know if current distro's have released it with their flavors. Being in the hospital on and off has kept me away from
the loop.
Vk3jed wrote to N1uro <=-
I've had kernels where the ham stuff wasn't available at all, modular
or otherwise. Certainly wouldn't be the first time I've rolled my own (there was really no choice in the 1.2.x days ;) ).
On 12-25-21 16:42, N1uro wrote to Vk3jed <=-
Hello Tony;
(there was really no choice in the 1.2.x days ;) ).
I recall those days... not only did you have to compile your own for
ham protocols, but also you had to compile in your NIC drivers as well. It's sort of funny in a parallel way that the way kernels and installs were back then compared to say RPi newbies is like comparing DOS and making programs in Debug vs new Windows 10 users!
... Heroes \hee'-rhos\: what a guy in a boat does.
Vk3jed wrote to N1uro <=-
Yep, you had to compile in all of the options for your hardware, and
there was a certain CD-ROM driver that you did NOT want to include,
unless you actually had that drive, because the driver would take ages
to try, before finally quitting. Modules were a godsend.
On 12-26-21 15:59, N1uro wrote to Vk3jed <=-
Those were the good ol' days! There was a couple of NIC drivers as well you didn't want to load unless you had *that* specific NIC. Even
whatever you wanted for other network protocols you had to flag and compile in.
You're 100% correct, modules do make things a LOT simpler.
Vk3jed wrote to N1uro <=-
You're 100% correct, modules do make things a LOT simpler.
Indeed. :)
I wonder how difficult it would be to import [email protected]
in here? At least some of the information posted would get seen by
more than just who's on there. Just a query :)
On 12-28-21 18:55, N1uro wrote to Vk3jed <=-
Hey Tony;
Vk3jed wrote to N1uro <=-
You're 100% correct, modules do make things a LOT simpler.
Indeed. :)
I wonder how difficult it would be to import [email protected]
in here? At least some of the information posted would get seen by
more than just who's on there. Just a query :)
... Counterfeiters \kown-ter-fit-ers\: Workers who put together kitchen Cabinets
On 12-29-21 17:32, deon wrote to N1uro <=-
Re: Re: ax.25 kernel stack
By: N1uro to Vk3jed on Tue Dec 28 2021 06:55 pm
I wonder how difficult it would be to import [email protected]
in here? At least some of the information posted would get seen by
more than just who's on there. Just a query :)
Pretty easy (with Synchronet).
Tony has SBBS so he could set it up, if not, I can.
deon wrote to N1uro <=-
Pretty easy (with Synchronet).
Tony has SBBS so he could set it up, if not, I can.
I have SBBS as well but recently discovered a security flaw with SBBSEcho
so I'll be taking it down.
Re: Re: ax.25 kernel stack
By: N1uro to deon on Wed Dec 29 2021 09:16 am
I have SBBS as well but recently discovered a security flaw with SBBSEcho so I'll be taking it down.
By today's standards, isnt most BBS software insecure?
...����
--- SBBSecho 3.14-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
deon wrote to N1uro <=-
By today's standards, isnt most BBS software insecure?
On 01-02-22 10:07, N1uro wrote to deon <=-
Hello deon;
deon wrote to N1uro <=-
By today's standards, isnt most BBS software insecure?
I may have an old copy of sbbsecho, I don't know. Someone I tried to
set up to feed was able to turn on echos from other nets which were not allowed in my config. This I do not want. It may be sysop error too... just not enough time for me to debug it at the moment.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 00:57:03 |
Calls: | 635 |
Calls today: | 2 |
Files: | 7,638 |
Messages: | 292,266 |