AX25 Node problem - please help
Hi
I've been trying to post full details of this problem to the mailing list but my messages don't seem to be getting through. Perhaps there's something in the body of the message that the system doesn't like so here is a summary in the hope that someone may recognise the problem.
I've recently noticed that a particular set of events can cause the node to go into an endless loop. I have noticed this with node-0.3.2-4 on Fedora 9 and node-0.3.2-14 on Fedora 20 so I'm assuming that it's a bug which has always been there. Note that these are the distribution (unpatched) versions.
Does this sound familiar to anyone? Has it been reported before and is there a patch available? I'm happy to correspond directly with someone with full details including strace info etc. in order to get this fixed, but I don't know who is looking after the node software these days.
Many thanks
Roger G3ZFR
Hi again
Many thanks to those who have replied to me personally on this.
It would appear to be a known problem. Brian N1URO has fixed it in URONode but I believe that it's still a problem in the original node.
Anyone who notices the node going into a loop and using unnecessary resources should consider using URONode instead.
Thanks again
Roger G3ZFR
Quoted 17 lines · Roger Harris
Hi
I've been trying to post full details of this problem to the mailing list but my messages don't seem to be getting through. Perhaps there's something in the body of the message that the system doesn't like so here is a summary in the hope that someone may recognise the problem.
I've recently noticed that a particular set of events can cause the node to go into an endless loop. I have noticed this with node-0.3.2-4 on Fedora 9 and node-0.3.2-14 on Fedora 20 so I'm assuming that it's a bug which has always been there. Note that these are the distribution (unpatched) versions.
Does this sound familiar to anyone? Has it been reported before and is there a patch available? I'm happy to correspond directly with someone with full details including strace info etc. in order to get this fixed, but I don't know who is looking after the node software these days.
Many thanks
Roger G3ZFR
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Roger,
Quoted 3 lines
It would appear to be a known problem. Brian N1URO has fixed it in URONode but I believe that it's still a problem in the original node.
Anyone who notices the node going into a loop and using unnecessary resources should consider using URONode instead.
Though I too recommend UroNode, could you tell us more about what you're seeing in this "looping" issue with LinuxNode? If it's a real bug, we should try to get it fixed as that software is still commonly used and available in various Linux distributions:
Ubuntu: http://packages.ubuntu.com/lucid/hamradio/node
Fedora: http://koji.fedoraproject.org/koji/packageinfo?packageID=6606
Debian: https://packages.debian.org/stable/hamradio/node
etc
yet UroNode is *not* included in most distribution packages per the request of the developer.
--David
KI6ZHD
Hi David
Not being a regular contributor on here, I'm unsure how wise it would be to give too much away about how to crash the system, especially as this forum becomes public when it gets archived.
I'll email you directly with the details. Please feel free to post it if you feel that it won't do any harm.
I'll do the same for any other developers who want the details.
Cheers
Roger
Quoted 24 lines · David Ranch
Hello Roger,
Quoted 3 lines
It would appear to be a known problem. Brian N1URO has fixed it in URONode but I believe that it's still a problem in the original node.
Anyone who notices the node going into a loop and using unnecessary resources should consider using URONode instead.
Though I too recommend UroNode, could you tell us more about what you're seeing in this "looping" issue with LinuxNode? If it's a real bug, we should try to get it fixed as that software is still commonly used and available in various Linux distributions:
Ubuntu: http://packages.ubuntu.com/lucid/hamradio/node
Fedora: http://koji.fedoraproject.org/koji/packageinfo?packageID=6606
Debian: https://packages.debian.org/stable/hamradio/node
etcyet UroNode is *not* included in most distribution packages per the request of the developer.
--David
KI6ZHDSignature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 2 lines · David Ranch
yet UroNode is *not* included in most distribution packages per the request of the developer.
Okay, what's the logic in that? If UroNode fixes a lot of the problems in the original "node" package, why package it up in the distributions where it will get wider visibility and coverage?
I'll admit I hadn't even heard of it until Brian Rogers mentioned it in an earlier thread, with a link to it on an obscure FTP site.
If this is Brian's whish we can not argue.
BTW: Brian Rogers = N1URO = author of UroNode, in case the link is not clear.
73s, Marius, YO2LOJ
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Stuart Longland VK4MSL
Sent: Sunday, April 06, 2014 23:36
To: [email protected]
Subject: Re: AX25 Node problem - please help
Quoted 2 lines · David Ranch
yet UroNode is *not* included in most distribution packages per the request of the developer.
Okay, what's the logic in that? If UroNode fixes a lot of the problems in the original "node" package, why package it up in the distributions where it will get wider visibility and coverage?
I'll admit I hadn't even heard of it until Brian Rogers mentioned it in an earlier thread, with a link to it on an obscure FTP site.
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 2 lines
Okay, what's the logic in that? If UroNode fixes a lot of the problems in the original "node" package, why package it up in the distributions where it will get wider visibility and coverage? I'll admit I hadn't even heard of it until Brian Rogers mentioned it in an earlier thread, with a link to it on an obscure FTP site.
I had an email thread with Brian many months ago where he previously had some personal objections of how some distributions compiled things incorrectly, created specific support issues, etc. I think previous versions of UroNode called out those objections in the LICENSE file but it seems both 2.0 and 2.1 have that file removed in their respective archive: ftp://ftp.n1uro.net/packet/
It might be work asking him again as his UroNode software really is a significant improvement over the old LinuxNode package.
--David
KI6ZHD