[App_rpt-users] Node Blocking

[Jeff Carrier]

I can see how traffic management could be an issue.  I've had several folks
connecting from out of state and just (for lack of a better term) "lurking"
because we can be pretty entertaining at times.  I put up the radio
reference feed to help alleviate some of that, I think its working.

73 de K0JSC


On Fri, Aug 30, 2013 at 11:28 AM, David Osborn <david.osborn at manx.net>wrote:

> The duuuude has spoken – gulp.****
>
> ** **
>
> There isn’t a problem with interference or naughtiness, just one of
> traffic management. ****
>
> ** **
>
> However, I will abide by the rules and stop trying to break things.****
>
> ** **
>
> I’ll go and stand in the corner for a while.****
>
> ** **
>
> *From:* Jim Duuuude [mailto:telesistant at hotmail.com]
> *Sent:* 30 August 2013 18:22
> *To:* David Osborn; Bryan D. Boyle
> *Cc:* app_rpt mailing list
> *Subject:* RE: [App_rpt-users] Node Blocking****
>
> ** **
>
> It is the policy of Allstar Link to require *ALL* Allstar nodes to accept
> connections from
> and allow connections to *ALL* Allstar nodes. PERIOD.
>
> If someone's node is somehow causing you interference or problems, you are
> intended
> to make an "official" complaint, and it *WILL* be dealt with.
>
> Jim WB6NIL
>
> ****
> ------------------------------
>
> From: david.osborn at manx.net
> To: bdboyle at bdboyle.com
> Date: Fri, 30 Aug 2013 17:47:37 +0100
> CC: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] Node Blocking****
>
> Interesting idea.****
>
>  ****
>
> I’ve done a bit of AWK’ing in the past to parse out stats from the log of
> who connected when and how many times, but I’ve slept since then and will
> have to learn it all over again J****
>
>  ****
>
> I guess that this will need to run regularly (cron?) in order to prevent a
> newly downloaded node list from unblocking the user.****
>
>  ****
>
> I’ll look further at that. Thanks****
>
>  ****
>
>  ****
>
> *From:* Bryan D. Boyle [mailto:bdboyle at bdboyle.com <bdboyle at bdboyle.com>]
> *Sent:* 30 August 2013 17:41
> *To:* David Osborn
> *Cc:* <app_rpt-users at ohnosec.org>
> *Subject:* Re: [App_rpt-users] Node Blocking****
>
>  ****
>
> write an awk (or PERL or ?) script to grok through the nodelist that gets
> downloaded on a regular basis and remove the node in question.  ****
>
>  ****
>
> that will, in essence, prevent the node from being listed as a valid node
> and prevent connection.****
>
>  ****
>
> I assume you are talking about allstar nodes vs individual users via the
> web transceiver...
>
> --****
>
> Bryan****
>
> Sent from my iPhone 5...small****
>
> keyboard, big fingers...please****
>
> forgive misspellings...****
>
>  ****
>
>  ****
>
>
> On Aug 30, 2013, at 12:06, "David Osborn" <david.osborn at manx.net> wrote:**
> **
>
> Hi Group,****
>
>  ****
>
> I’m convinced I’ve seen talk of this before, but having trawled the
> archives, I’m darned if I can find it.****
>
>  ****
>
> Is there a method of blocking specific AllStar nodes from connecting? I
> know we’re all friends here and wouldn’t dream of being unpleasant to each
> other, but there are occasions when it may be necessary to temporarily stop
> another node from linking. How would this be achieved?****
>
>  ****
>
> Thanks****
>
>  ****
>
> David****
>
>  ****
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users****
>
>
> _______________________________________________ App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users****
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130830/6315a57f/attachment.html>