[arm-allstar] vnc on allstar
ARM Allstar
arm-allstar at hamvoip.org
Tue Nov 10 12:43:33 EST 2020
Thanks Charles for the response. VNC was a suggestion from an IT friend and
ham at Google. I can do better than having to watch on a regular basis to
see if the boogie man is at my door. Firstly don't allow root login.
Secondly I have used node_allow in the past and set the first octet to my
phone cell IP ADDRESS first digits. Home static IP too. The boogie man goes
away very quickly when he is not allowed to knock on the door.
So far I have not seen Russia or other common offenders using US cell phone
block numbers. Have you?
Thanks
KU6V
-----Original Message-----
From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Tuesday, November 10, 2020 9:00 AM
To: arm-allstar at hamvoip.org
Subject: ARM-allstar Digest, Vol 78, Issue 8
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. Second USB Rim-LIte Causes the new one to not pass audio.
(ARM Allstar)
2. Re: Second USB Rim-LIte Causes the new one to not pass audio.
(ARM Allstar)
3. Re: Second USB Rim-LIte Causes the new one to not pass audio.
(ARM Allstar)
4. vncserver and hamvoip software (ARM Allstar)
5. Re: vncserver and hamvoip software (ARM Allstar)
6. Re: Second USB Rim-LIte Causes the new one to not pass audio.
(ARM Allstar)
7. Re: Second USB Rim-LIte Causes the new one to not pass audio.
(ARM Allstar)
----------------------------------------------------------------------
Message: 1
Date: Mon, 9 Nov 2020 09:06:37 -0800
From: ARM Allstar <arm-allstar at hamvoip.org>
To: arm-allstar at hamvoip.org
Subject: [arm-allstar] Second USB Rim-LIte Causes the new one to not
pass audio.
Message-ID: <mailman.335.1604942785.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset="UTF-8"
I'm running a Pi3B with the latest fully upgraded version of HamVOIP.
I followed the steps in the guide to add a second USB FOB. Both are USB-RIM
Lites. I was able to add the second RIM-Lite and set up my second node
number. The second USB RIM-Lite worked for audio receive, and can PTT just
fine. So I know the edits of my iax and rpt and simple usb config files are
all correct. However, when the second RIM-Lite is connected, no audio
passes to the mic input of the second radio, no voice, no tones. just a
carrier when it is keyed. Both will work just fine when one is connected at
a time. For a test, I disconnected the second RIM-LIte, connected my second
harness and radio to the first RIM-Lite and everythng worked fine, PTT,
Audio is passed, the COR worked, everything. I even created a whole new
setup on a seperate Pi and confirmed that the Rim-Lite works on that one as
well. So I know for certain that the RIM-Lite works, the cable is wired
correctly, and the radio works.
I also noticed on the DVSwitch mobile app that when the second RIM-Lite was
connected the audio suffered harshly from the first RIM-Lite, it was cutting
in and out, very choppy, and as soon as I disconnected the second one, the
audio on the first returned to normal. I also had someone connected through
EchoLink and they said the same thing, choppy audio.
I also tried setting up the second RIM-Lite on a different port, again
following the instructions to stop asterisk connect, start asterisk and use
the Asterisk CLI again to activate and tune. Same results as before. No
audio is passed and the first RIM-Lite had degraded audio.
Is this a power issue? Should I try using a powered USB hub? Nothing else
is connected to the origianal Pi besides the RIM-Lites. Too much power draw
is my only guess. The power supply I'm using is outputting 5V 3A.
I appreciate everyones thoughts or ideas as I'd really like to use the same
Pi for both RIM-Lites.
Mike
WG5EEK
------------------------------
Message: 2
Date: Mon, 9 Nov 2020 14:19:32 -0500 (EST)
From: ARM Allstar <arm-allstar at hamvoip.org>
To: "\"ARM Allstar via ARM-allstar\"" <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Second USB Rim-LIte Causes the new one to
not pass audio.
Message-ID: <mailman.336.1604949574.2794.arm-allstar at hamvoip.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mike,
Using two USB fobs on an RPi3B should work fine, I've got many setup this
way. Did you use the simpleusb-tune-menu program to setup the fobs?
The procedure is to plug in only the first fob, select the proper simpleusb
device (menu option 's'), perform setup and save (menu option 'w'). Then,
plug in the second fob as well (both now plugged in), select the second
simpleusb device (menu option 's'), perform setup and save.
Exit out of the simpleusb-tune-menu program and restart....The fobs should
both now be happy.
73, David KB4FXC
On Mon, 9 Nov 2020, "ARM Allstar via ARM-allstar" wrote:
> I'm running a Pi3B with the latest fully upgraded version of HamVOIP.
>
> I followed the steps in the guide to add a second USB FOB. Both are
> USB-RIM Lites. I was able to add the second RIM-Lite and set up my
> second node number. The second USB RIM-Lite worked for audio receive,
> and can PTT just fine. So I know the edits of my iax and rpt and
> simple usb config files are all correct. However, when the second
> RIM-Lite is connected, no audio passes to the mic input of the second
> radio, no voice, no tones. just a carrier when it is keyed. Both will
> work just fine when one is connected at a time. For a test, I
> disconnected the second RIM-LIte, connected my second harness and
> radio to the first RIM-Lite and everythng worked fine, PTT, Audio is
> passed, the COR worked, everything. I even created a whole new setup
> on a seperate Pi and confirmed that the Rim-Lite works on that one as
> well. So I know for certain that the RIM-Lite works, the cable is wired
correctly, and the radio works.
>
> I also noticed on the DVSwitch mobile app that when the second
> RIM-Lite was connected the audio suffered harshly from the first
> RIM-Lite, it was cutting in and out, very choppy, and as soon as I
> disconnected the second one, the audio on the first returned to
> normal. I also had someone connected through EchoLink and they said the
same thing, choppy audio.
>
> I also tried setting up the second RIM-Lite on a different port, again
> following the instructions to stop asterisk connect, start asterisk
> and use the Asterisk CLI again to activate and tune. Same results as
> before. No audio is passed and the first RIM-Lite had degraded audio.
>
> Is this a power issue? Should I try using a powered USB hub? Nothing
> else is connected to the origianal Pi besides the RIM-Lites. Too much
> power draw is my only guess. The power supply I'm using is outputting 5V
3A.
>
> I appreciate everyones thoughts or ideas as I'd really like to use the
> same Pi for both RIM-Lites.
>
> Mike
> WG5EEK
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>
------------------------------
Message: 3
Date: Mon, 9 Nov 2020 11:42:48 -0800
From: ARM Allstar <arm-allstar at hamvoip.org>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Second USB Rim-LIte Causes the new one to
not pass audio.
Message-ID: <mailman.339.1604951062.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset="UTF-8"
I realized I sent this from the wrong email address but I'll press forward
from this one regardless.
David,
Yes I did those steps multiple times just to be sure including restarting
each time as well as following the steps in the config guide starting on
page 10. Both USB fobs are properly detected and work except for passing
audio to the second node and the degradation of audio as described. If I
unplug either one once set up, whichever once is left plugged in behaves
properly. My only guess is some kind of power issue.
Is there any way to see what's happening to the audio from the Asterisk CLI?
Mike
WG5EEK
On Mon, Nov 9, 2020 at 11:19 AM "ARM Allstar via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
>
> Mike,
>
> Using two USB fobs on an RPi3B should work fine, I've got many setup
> this way. Did you use the simpleusb-tune-menu program to setup the fobs?
>
> The procedure is to plug in only the first fob, select the proper
> simpleusb device (menu option 's'), perform setup and save (menu
> option 'w'). Then, plug in the second fob as well (both now plugged
> in), select the second simpleusb device (menu option 's'), perform setup
and save.
> Exit out of the simpleusb-tune-menu program and restart....The fobs
> should both now be happy.
>
> 73, David KB4FXC
>
>
>
> On Mon, 9 Nov 2020, "ARM Allstar via ARM-allstar" wrote:
>
> > I'm running a Pi3B with the latest fully upgraded version of HamVOIP.
> >
> > I followed the steps in the guide to add a second USB FOB. Both are
> USB-RIM
> > Lites. I was able to add the second RIM-Lite and set up my second
> > node number. The second USB RIM-Lite worked for audio receive, and
> > can PTT
> just
> > fine. So I know the edits of my iax and rpt and simple usb config
> > files
> are
> > all correct. However, when the second RIM-Lite is connected, no
> > audio passes to the mic input of the second radio, no voice, no
> > tones. just a carrier when it is keyed. Both will work just fine
> > when one is connected at a time. For a test, I disconnected the
> > second RIM-LIte, connected my second harness and radio to the first
> > RIM-Lite and everythng worked fine, PTT, Audio is passed, the COR
> > worked, everything. I even created a whole new setup on a seperate
> > Pi and confirmed that the Rim-Lite works on that one as well. So I
> > know for certain that the RIM-Lite works, the cable is wired correctly,
and the radio works.
> >
> > I also noticed on the DVSwitch mobile app that when the second
> > RIM-Lite
> was
> > connected the audio suffered harshly from the first RIM-Lite, it was
> > cutting in and out, very choppy, and as soon as I disconnected the
> > second one, the audio on the first returned to normal. I also had
> > someone connected through EchoLink and they said the same thing, choppy
audio.
> >
> > I also tried setting up the second RIM-Lite on a different port,
> > again following the instructions to stop asterisk connect, start
> > asterisk and
> use
> > the Asterisk CLI again to activate and tune. Same results as
> > before. No audio is passed and the first RIM-Lite had degraded audio.
> >
> > Is this a power issue? Should I try using a powered USB hub?
> > Nothing
> else
> > is connected to the origianal Pi besides the RIM-Lites. Too much
> > power draw is my only guess. The power supply I'm using is outputting
5V 3A.
> >
> > I appreciate everyones thoughts or ideas as I'd really like to use
> > the
> same
> > Pi for both RIM-Lites.
> >
> > Mike
> > WG5EEK
> > _______________________________________________
> >
> > 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/4 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/4 web page - http://hamvoip.org
>
------------------------------
Message: 4
Date: Mon, 9 Nov 2020 14:24:05 -0800
From: ARM Allstar <arm-allstar at hamvoip.org>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] vncserver and hamvoip software
Message-ID: <mailman.342.1604961145.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset="us-ascii"
Greetings
Can a vncserver be installed on a hamvoip system? I want to connect from the
outside world and with vncserver I won't need to open ports as am led to
believe.
73
KU6V
------------------------------
Message: 5
Date: Mon, 9 Nov 2020 16:50:02 -0600
From: ARM Allstar <arm-allstar at hamvoip.org>
To: ARM Allstar via ARM-allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] vncserver and hamvoip software
Message-ID: <mailman.345.1604962288.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset=utf-8; format=flowed
To use a VNC server one must install a GUI on the hamvoip.? This adds
overhead to the system that you don't want.? Not only that, I can't think of
a single reason to do it.? The stock interface is more than adequate.? It
still adds the need for an open port, and VNC is a far less secure protocol
than SSH.
You can protect against brute force cracking attacks with a simple script,
and/or by using your router to redirect the SSH port to something
non-standard, placing it where few, if any, will be looking.?
I follow my logs periodically and I have never had an unwanted login attempt
that survives for more than 3 tries.
73,
Charles - NK8O
On 11/9/20 4:24 PM, "ARM Allstar via ARM-allstar" wrote:
> Greetings
>
> Can a vncserver be installed on a hamvoip system? I want to connect
> from the outside world and with vncserver I won't need to open ports
> as am led to believe.
>
> 73
>
> KU6V
>
>
>
>
>
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
------------------------------
Message: 6
Date: Mon, 9 Nov 2020 20:31:17 -0600
From: ARM Allstar <arm-allstar at hamvoip.org>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Second USB Rim-LIte Causes the new one to
not pass audio.
Message-ID: <mailman.348.1604975690.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset=utf-8; format=flowed
*I had a similar issue just last night when adding a second U.R.I. to a Pi
3b+. When using menu item "D" the tone from the second U.R.I. was quite
broken, jittery, and distorted sounding but when using a hand mic on the
repeater TX radio it sounded fine. After a complete reboot, things seemed to
calm down. I'll be revisiting that one again later tomorrow.
N5ZUA
*
On 11/9/2020 1:19 PM, "ARM Allstar via ARM-allstar" wrote:
> Mike,
>
> Using two USB fobs on an RPi3B should work fine, I've got many setup
> this way. Did you use the simpleusb-tune-menu program to setup the fobs?
>
> The procedure is to plug in only the first fob, select the proper
> simpleusb device (menu option 's'), perform setup and save (menu
> option 'w'). Then, plug in the second fob as well (both now plugged
> in), select the second simpleusb device (menu option 's'), perform setup
and save.
> Exit out of the simpleusb-tune-menu program and restart....The fobs
> should both now be happy.
>
> 73, David KB4FXC
------------------------------
Message: 7
Date: Mon, 9 Nov 2020 19:52:18 -0800
From: ARM Allstar <arm-allstar at hamvoip.org>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Second USB Rim-LIte Causes the new one to
not pass audio.
Message-ID: <mailman.351.1604980654.2794.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset="UTF-8"
Interesting! I went ahead and ordered a powered USB hub, should be here on
Wednesday. I'll test that out and see if it makes a difference.
WG5EEK
On Mon, Nov 9, 2020 at 6:34 PM "ARM Allstar via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> *I had a similar issue just last night when adding a second U.R.I. to
> a Pi 3b+. When using menu item "D" the tone from the second U.R.I. was
> quite broken, jittery, and distorted sounding but when using a hand
> mic on the repeater TX radio it sounded fine. After a complete reboot,
> things seemed to calm down. I'll be revisiting that one again later
> tomorrow.
>
> N5ZUA
> *
> On 11/9/2020 1:19 PM, "ARM Allstar via ARM-allstar" wrote:
> > Mike,
> >
> > Using two USB fobs on an RPi3B should work fine, I've got many setup
> > this way. Did you use the simpleusb-tune-menu program to setup the
fobs?
> >
> > The procedure is to plug in only the first fob, select the proper
> > simpleusb device (menu option 's'), perform setup and save (menu
> > option 'w'). Then, plug in the second fob as well (both now plugged
> > in), select the second simpleusb device (menu option 's'), perform setup
and save.
> > Exit out of the simpleusb-tune-menu program and restart....The fobs
> should
> > both now be happy.
> >
> > 73, David KB4FXC
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>
------------------------------
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 78, Issue 8
******************************************
More information about the ARM-allstar
mailing list