[arm-allstar] ARM-allstar Digest, Vol 63, Issue 14

Tue Aug 6 23:30:35 EDT 2019

Yes, I went back and read it. Yes that would work. It would deny anyone
from connecting to that node directly from his. This would also have the
effect of not allowing that node to connect incoming which I suspect is
what you would want. However that doesn't stop someone from outside from
connecting and then also connecting to that node. There are always ways
around it.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Tue, Aug 6, 2019 at 11:25 PM "Danny Siminiuk via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I didn't see where he asked that only a specific RF user to be blocked
> from connecting to node X.
>
> Chris has a good idea though. Define node X as a local node and set the IP
> address to 127.0.0.1 on a UDP port that is not open or available. Node X
> will never connect.
>
> Danny
> K5CG
>
> ----- Original Message -----
> From: "ARM Allstar" <arm-allstar at hamvoip.org>
> To: "ARM Allstar" <arm-allstar at hamvoip.org>
> Cc: "wa3dsp" <wa3dsp at gmail.com>
> Sent: Tuesday, August 6, 2019 9:34:44 PM
> Subject: Re: [arm-allstar] ARM-allstar Digest, Vol 63, Issue 14
>
> But he I believe he just wants to block one person from doing that not
> everyone. How about telling the person not to connect to that node and if
> they don't comply ban them. That is what I would do. Is this a guy who
> comes in on RF on your repeater? In that case there is really nothing you
> can do. There is no way to know who it is. You could change the connect
> commands (and others) and only share it then with authorized users but
> anyone can listen on the air and mimic the tones.
>
> BTW there is a guy on your repeater W3YT who just about every night tries
> to connect somewhere and we hear his tones which means they are not
> working. He never gives up we finally have to tell him it is not going to
> work!
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Tue, Aug 6, 2019 at 10:25 PM "Chris via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > What about defining the node at the bottom of the rpt.conf but give it a
> > bogus IP address. If anyone tried to connect to that node, rpt would call
> > on a bad address and just not do anything.
> >
> > Would that work?
> >
> > Chris
> > WB4ULK
> >
> > > On Aug 6, 2019, at 6:31 PM, Steve Liggett via ARM-allstar <
> > arm-allstar at hamvoip.org> wrote:
> > >
> > > Doug:
> > >
> > > "I would like to call a script that will prohibit local users from
> > connecting to a certain node.”
> > >
> > > The node-ban-allow blocks a distant node from connecting to me
> (incoming
> > block), correct? I want to not allow a LOCAL user of the repeater/node
> from
> > connecting to a certain distant node. So, the aim is to restrict an
> > outbound-originated connection.
> > >
> > > steve
> > > W3RX
> > >
> > >
> > >
> > >> On Aug 6, 2019, at 7:26 PM, arm-allstar-request at hamvoip.org wrote:
> > >>
> > >> Send ARM-allstar mailing list submissions to
> > >>    arm-allstar at hamvoip.org
> > >>
> > >> To subscribe or unsubscribe via the World Wide Web, visit
> > >>    http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >> or, via email, send a message with subject or body 'help' to
> > >>    arm-allstar-request at hamvoip.org
> > >>
> > >> You can reach the person managing the list at
> > >>    arm-allstar-owner at hamvoip.org
> > >>
> > >> When replying, please edit your Subject line so it is more specific
> > >> than "Re: Contents of ARM-allstar digest..."
> > >>
> > >>
> > >> Today's Topics:
> > >>
> > >>  1. Prohibit connection (Steve Liggett)
> > >>  2. Re: Prohibit connection (Doug Crompton)
> > >>  3. TK8180 FOB interfacing (Doug Crompton)
> > >>
> > >>
> > >> ----------------------------------------------------------------------
> > >>
> > >> Message: 1
> > >> Date: Tue, 6 Aug 2019 12:12:26 -0400
> > >> From: Steve Liggett <sbliggett2 at gmail.com>
> > >> To: arm-allstar at hamvoip.org
> > >> Subject: [arm-allstar] Prohibit connection
> > >> Message-ID: <0FC40B0F-6032-4729-939F-D4487E8E480F at gmail.com>
> > >> Content-Type: text/plain;    charset=us-ascii
> > >>
> > >> I would like to call a script that will prohibit local users from
> > connecting to a certain node. I do not believe that this is currently a
> > feature, is it?
> > >>
> > >> steve
> > >> W3RX
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 2
> > >> Date: Tue, 6 Aug 2019 12:51:00 -0400
> > >> From: Doug Crompton <wa3dsp at gmail.com>
> > >> To: ARM Allstar <arm-allstar at hamvoip.org>
> > >> Subject: Re: [arm-allstar] Prohibit connection
> > >> Message-ID:
> > >>    <
> CAMp6vssKPzuiVEXj43RTqELDU3bSNvgG6x+TFWELjY2s3pHuug at mail.gmail.com>
> > >> Content-Type: text/plain; charset="UTF-8"
> > >>
> > >> Steve,
> > >>
> > >> Not sure exactly what you want but there is a node ban (or allow) in
> > >> Supermon called restrict and also a stand-alone script
> > node-ban-allow.sh
> > >> which would ban a node from connecting.. What is it exactly you want
> to
> > do?
> > >>
> > >>
> > >> *73 Doug*
> > >>
> > >> *WA3DSP*
> > >>
> > >> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >>
> > >>
> > >>
> > >> On Tue, Aug 6, 2019 at 12:47 PM "Steve Liggett via ARM-allstar" <
> > >> arm-allstar at hamvoip.org> wrote:
> > >>
> > >>> I would like to call a script that will prohibit local users from
> > >>> connecting to a certain node. I do not believe that this is
> currently a
> > >>> feature, is it?
> > >>>
> > >>> steve
> > >>> W3RX
> > >>> _______________________________________________
> > >>>
> > >>> ARM-allstar mailing list
> > >>> ARM-allstar at hamvoip.org
> > >>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >>>
> > >>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >>>
> > >>
> > >>
> > >> ------------------------------
> > >>
> > >> Message: 3
> > >> Date: Tue, 6 Aug 2019 19:26:13 -0400
> > >> From: Doug Crompton <wa3dsp at gmail.com>
> > >> To: ARM Allstar <arm-allstar at hamvoip.org>
> > >> Subject: [arm-allstar] TK8180 FOB interfacing
> > >> Message-ID:
> > >>    <CAMp6vsuss1m=e9S=2S1eP8gobmkWx4UQdW4mQt-vg3iq=
> ee3BA at mail.gmail.com>
> > >> Content-Type: text/plain; charset="utf-8"
> > >>
> > >> From: Kevin Halton <khalton at cox.net>
> > >>
> > >>
> > >> So I've been trying to build an allstar node for some time now. I only
> > get
> > >> 20-30 minutes at a time to work on it. That said, I've tried 2
> different
> > >> USB interfaces and I still can't seem to get the damn thing to work.
> > >>
> > >>
> > >>
> > >> I'm currently using a TK-8180 as the radio because it has a 25 pin
> > >> accessory connector on the back which should (theoretically) make
> things
> > >> easy. If I can get that to work I have lots of ideas for interfacing
> > other
> > >> radios and I'm more than willing to futz around with usb fobs.
> > >>
> > >>
> > >>
> > >> Anyway, here's a diagram of the pinout for the radio from the service
> > >> manual (7180 is the same as 8180):
> > >>
> > >> [image: image.png]
> > >>
> > >>
> > >>
> > >> I've tried connecting to this radio using a USB-Rim Lite
> > >> <http://www.repeater-builder.com/products/usb-rim-lite.html> and a
> > Radio
> > >> Farm Projects VOIP CM119B Interface
> > >> <https://sites.google.com/site/radiofarmprojects/home/voip-interface
> >.
> > >>
> > >>
> > >>
> > >> The RIM Lite doesn't appear to pull down the PTT I/O enough to stay
> > keyed
> > >> and I can't seem to get any audio in or out of it (using SimpleUSB
> > Tune).
> > >>
> > >>
> > >>
> > >> The CM119B Interface seems to do a fine job doing PTT but again, no
> > audio
> > >> in or out as far as I can tell.
> > >>
> > >>
> > >>
> > >> I'm using these pins on the radio:
> > >>
> > >> 5 - DI - Data Input
> > >>
> > >> 7 - Ground
> > >>
> > >> 12 - IO7 - Configured for COS
> > >>
> > >> 13 - IO6 - Configured for PTT
> > >>
> > >> 19 - DEO - Discriminator External Output
> > >>
> > >>
> > >>
> > >> Any ideas as to where I'm going wrong? Any feedback is appreciated
> > >> -------------- next part --------------
> > >> An HTML attachment was scrubbed...
> > >> URL: <
> >
> http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20190806/e67bcc92/attachment.html
> > >
> > >> -------------- next part --------------
> > >> A non-text attachment was scrubbed...
> > >> Name: image001.png
> > >> Type: image/png
> > >> Size: 12611 bytes
> > >> Desc: not available
> > >> URL: <
> >
> http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20190806/e67bcc92/attachment.png
> > >
> > >>
> > >> ------------------------------
> > >>
> > >> Subject: Digest Footer
> > >>
> > >> _______________________________________________
> > >> ARM-allstar mailing list
> > >> ARM-allstar at hamvoip.org
> > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >>
> > >>
> > >> ------------------------------
> > >>
> > >> End of ARM-allstar Digest, Vol 63, Issue 14
> > >> *******************************************
> > >
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org