[App_rpt-users] Node Blocking

[David Osborn]

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] 
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130830/cfd4209e/attachment.html>