All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Harris <linham@mybunker.plus.com>
To: linux-hams@vger.kernel.org
Subject: Re: AX25 Node problem - please help
Date: Sun, 06 Apr 2014 21:04:37 +0100	[thread overview]
Message-ID: <5341B355.4010802@mybunker.plus.com> (raw)
In-Reply-To: <5341ADD0.2050303@trinnet.net>

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

On 06/04/2014 20:41, David Ranch wrote:
>
> Hello Roger,
>
>
>> 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
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2014-04-06 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 10:40 AX25 Node problem - please help Roger Harris
2014-04-06 17:44 ` Roger Harris
2014-04-06 19:41   ` David Ranch
2014-04-06 20:04     ` Roger Harris [this message]
2014-04-06 20:35     ` Stuart Longland VK4MSL
2014-04-06 20:58       ` Marius Petrescu
2014-04-06 21:31       ` David Ranch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5341B355.4010802@mybunker.plus.com \
    --to=linham@mybunker.plus.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.