Date   
Re: New Years Eve Around the World QSO Party

k9dc
 

Nope, No streaming this year. Last year only a couple of folks used it over the 24 hours, and it would have to be reconfigured to carry 9600 anyway. So I have shut that service down.

-k9dc

On Dec 30, 2019, at 17:57, Dave Parks - WB8ODF via Groups.Io <wb8odf=yahoo.com@groups.io> wrote:

Dave is there a streaming URL?


< Dave Parks ><
WB8ODF@...
http://wb8odf.com
Node: 8139

Re: New Years Eve Around the World QSO Party

 

Dave is there a streaming URL?


>< Dave Parks ><
WB8ODF@...
http://wb8odf.com



On Monday, December 30, 2019, 5:46:45 PM EST, k9dc <dave@...> wrote:



Don’t forget, tomorrow is the day for the QSO party on Reflector 9600 (not 9200).  There are a few nodes that have already connected.  Come one, come all!

-k9dc


> On Dec 21, 2019, at 10:16, Dave Gingrich <dave@...> wrote:
>
>
> The fourteenth annual New Years Eve Around the World QSO Party on Reflector 9600 gets under way officially at 10:30 UTC (05:30 US eastern) Tuesday, December 31.  It continues (officially) until 10:30 UTC Wednesday January 1.  I say “Officially” because you are welcome to connect much earlier than that (now if you want) and stay as long as you like.
>
> Please note: Reflector 9600 is a different location than we have used in past years. 9600 is a relatively new reflector co-located with server4 in Sydney, and has not had a lot of use. It is the same machine used primarily to serve up IRLP VPN clients in Australia, Asia and Africa (for more information on the IRLP VPN service, see https://irlp.groups.io/g/IRLP/files/IRLP%20VPN%20Service).
>
> This is a casual informal party with no net control or designated operators anytime during the event.  Simply stop in, greet your friends, make new ones and simply enjoy yourself as the New Year wends its way around the planet, beginning in New Zealand 11:00 UTC (Dec-31) and ending in Hawaii at 10:00 UTC (Jan-1).
>
> This is an IRLP only event. Please resist the temptation to bridge folks in from other networks just because it sounds like fun. Instead, invite your local friends over to your repeater or encourage them to use a local resource to join in.
>
> Auld lang syne!
>
> Dave K9DC
>



Re: New Years Eve Around the World QSO Party

k9dc
 

Don’t forget, tomorrow is the day for the QSO party on Reflector 9600 (not 9200). There are a few nodes that have already connected. Come one, come all!

-k9dc

On Dec 21, 2019, at 10:16, Dave Gingrich <dave@...> wrote:


The fourteenth annual New Years Eve Around the World QSO Party on Reflector 9600 gets under way officially at 10:30 UTC (05:30 US eastern) Tuesday, December 31. It continues (officially) until 10:30 UTC Wednesday January 1. I say “Officially” because you are welcome to connect much earlier than that (now if you want) and stay as long as you like.

Please note: Reflector 9600 is a different location than we have used in past years. 9600 is a relatively new reflector co-located with server4 in Sydney, and has not had a lot of use. It is the same machine used primarily to serve up IRLP VPN clients in Australia, Asia and Africa (for more information on the IRLP VPN service, see https://irlp.groups.io/g/IRLP/files/IRLP%20VPN%20Service).

This is a casual informal party with no net control or designated operators anytime during the event. Simply stop in, greet your friends, make new ones and simply enjoy yourself as the New Year wends its way around the planet, beginning in New Zealand 11:00 UTC (Dec-31) and ending in Hawaii at 10:00 UTC (Jan-1).

This is an IRLP only event. Please resist the temptation to bridge folks in from other networks just because it sounds like fun. Instead, invite your local friends over to your repeater or encourage them to use a local resource to join in.

Auld lang syne!

Dave K9DC

Re: Open VPN Help - Little Yellow Box as a vpn client

Ed W6YJ
 

And Marshall is running CentOS 4.9. Per Dave K9DC, his VPN solution doesn't play happy with 4.9.

Ed
W6YJ
(no idea why I can't get rid of the bold setting when replying to your posts)


On 12/29/2019 5:21 PM, Teton Amateur Radio Repeater Association (TARRA) wrote:

With a VPN, you don't need to setup all the ports in your router, that is the idea of using a VPN.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Ed W6YJ
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 03:21:31 PM
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Marshall,
>
> I just went through this with my Uverse router (BGW210-700). It seems
> AT&T has the routers configured to block just about everything beyond
> simple web and mail ports.
>
> Within the BGS210-700, there is a section Firewall/Packet Filter that
> you need to adds the TCP & UDP ports you want opened .
>
> This should have been all that is needed, but evidently they have a
> second level of filtering/blocking that you can get around by going into
> Firewall/NAT/Gaming and then you will need to add the ports a second
> time as one or more Application Hosting Entry(s).
>
> Ed
> W6YJ
>
>
>
> On 12/29/2019 1:14 PM, Marshall Oldham wrote:
> >
> > Greetings,
> >
> > Okay this is my first attempt at using the GL-MT300N (little yellow
> > box) at my house running the vpn client which is connected to a
> > virtual machine at Virmach that is  running openVPN.
> >
> > I have an IRLP node connected to the GL-MT300N (little yellow box) at
> > my house which  is attached to the internet via ethernet cable to my
> > ATT-Uverse router.
> >
> > I have followed Craig Davidson's instructions here.
> >
> > http://experimental.irlp.net/YellowBox/
> >
> > I did make separate entries in the advanced setup of the router for
> > every port number that need to be forward in the router for IRLP to
> > work correctly.
> >
> > The GL-MT300N is connecting to the vpn server at Virmach just fine and
> > is providing internet access.
> >
> > I am still having a problem with the port forwarding for IRLP.
> >
> > When I run the troubleshoot-irlp script it tells me that inbound port
> > forwarding is not setup correctly.
> >
> > Anyone have any ideas what I need to change?
> >
> > 73
> >
> > Marshall - ke6pcv
> >
> >
>
>
>
>
--

Re: Open VPN Help - Little Yellow Box as a vpn client

Ed W6YJ
 

Dave,

I have a block of 5 static IPs through Uverse and have had port 25 unblocked at their end.

When I first got Uverse, after the unblock request and adding pass rules to the firewall / packet filter fixed SMTP.

But adding pass rules for IRLP and EchoIRLP didn't.

I initially tried disabling the BGW210-700 firewall and unfortunately for me it didn't help (may have been a cockpit error on my part) with IRLP or EchoIRLP.

In looking around on the Internet for a fix, I found lots of people with the BGW210-700 having the same frustrations.

 After going around a few times with their support people, one of them tried adding the custom application host rules, and that ended up finally allowing IRLP and EchoIRLP data to work.

Why this router has two levels of blocking is beyond me.

Ed
W6YJ

On 12/30/2019 7:20 AM, k9dc wrote:
Most of those restrictions are local to the router in your house, and configurable by the customer. The router I have is the U-Verse Pace 5268AC. I can completely disable the internal firewall and actually extend the AT&T public IP to my router. The only ports they actually block in the network outbound are TCP 25 (SMTP Mail) and 135. They will open port 25 upon request, but most mail servers also run on port 587 which is not blocked.

-k9dc


On Dec 29, 2019, at 17:21, Ed W6YJ <w6yj_lists@...> wrote:

Marshall,

I just went through this with my Uverse router (BGW210-700). It seems AT&T has the routers configured to block just about everything beyond simple web and mail ports.

Within the BGS210-700, there is a section Firewall/Packet Filter that you need to adds the TCP & UDP ports you want opened .

This should have been all that is needed, but evidently they have a second level of filtering/blocking that you can get around by going into Firewall/NAT/Gaming and then you will need to add the ports a second time as one or more Application Hosting Entry(s).

Ed
W6YJ


Re: Open VPN Help - Little Yellow Box as a vpn client

k9dc
 

Most of those restrictions are local to the router in your house, and configurable by the customer. The router I have is the U-Verse Pace 5268AC. I can completely disable the internal firewall and actually extend the AT&T public IP to my router. The only ports they actually block in the network outbound are TCP 25 (SMTP Mail) and 135. They will open port 25 upon request, but most mail servers also run on port 587 which is not blocked.

-k9dc

On Dec 29, 2019, at 17:21, Ed W6YJ <w6yj_lists@...> wrote:

Marshall,

I just went through this with my Uverse router (BGW210-700). It seems AT&T has the routers configured to block just about everything beyond simple web and mail ports.

Within the BGS210-700, there is a section Firewall/Packet Filter that you need to adds the TCP & UDP ports you want opened .

This should have been all that is needed, but evidently they have a second level of filtering/blocking that you can get around by going into Firewall/NAT/Gaming and then you will need to add the ports a second time as one or more Application Hosting Entry(s).

Ed
W6YJ

Re: Open VPN Help - Little Yellow Box as a vpn client

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Marshall,

Just to be sure of a couple of things. Is yours a "V2" and also firmware 3.025? And also to be sure you are going the correct place. From the main page down at the bottom where is says "More Settings" and then clicking on"Advanced" opens a new tab that you have to sign in. Then under "Network" click on "Firewall". And then "Port Forwards". It may look a little different if you don't have anything entered yet.

I think the difference is because the screen shots I was giving you I was in editing mode. I have added a third image that may be helpful and more like what you should be seeing.

http://www.wyocat.com/tarra/yellowbox

Mick - W7CAT
Node 3464

----- Original Message -----
From: Marshall Oldham
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 09:31:59 PM
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Hey Mick,
>
>
>
> Thank you very much for your help. I can see everything now. :)
>
>
>
> Your router looks to have a different setup and menu than the one I am using. But this information is very helpfull.
>
>
>
> 73
>
>
>
> Marshall
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
> Sent: Sunday, December 29, 2019 5:20 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
>
>
> Hello Marshall,
>
> I'm sorry those screen shots didn't work for you. Here is another try. If these pictures aren't worth a thousand words, then I will try to describe it for you.
>
> http://www.wyocat.com/tarra/yellowbox
>
> Mick - W7CAT
> Node 3464
>
> ----- Original Message -----
> From: Marshall Oldham
> To: IRLP@irlp.groups.io
> Sent: Sunday, December 29, 2019 03:33:07 PM
> Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
> > Mick,
> >
> >
> >
> > I can't see any of the information on you attached pictures.
> >
> > The resolution is too low on the photos.
> >
> >
> >
> > Thanks
> >
> >
> >
> > Marshall
> >
> >
> >
> > From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
> > Sent: Sunday, December 29, 2019 1:45 PM
> > To: IRLP@irlp.groups.io
> > Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
> >
> >
> >
> > Here is what mine looks like if this helps.
> >
> > Mick - W7CAT
> > Node 3464
> >
> > ----- Original Message -----
> > From: Marshall Oldham
> > To: IRLP@irlp.groups.io
> > Sent: Sunday, December 29, 2019 02:14:35 PM
> > Subject: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
> >
> > > Greetings,
> > >
> > >
> > >
> > > Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running
> > > the vpn client which is connected to a virtual machine at Virmach that is running openVPN.
> > >
> > >
> > >
> > > I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is
> > > attached to the internet via ethernet cable to my ATT-Uverse router.
> > >
> > >
> > >
> > > I have followed Craig Davidson's instructions here.
> > >
> > >
> > >
> > > http://experimental.irlp.net/YellowBox/
> > >
> > >
> > >
> > > I did make separate entries in the advanced setup of the router for every port number that need
> > > to be forward in the router for IRLP to work correctly.
> > >
> > >
> > >
> > > The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet
> > > access.
> > >
> > >
> > >
> > > I am still having a problem with the port forwarding for IRLP.
> > >
> > >
> > >
> > > When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup
> > > correctly.
> > >
> > >
> > >
> > > Anyone have any ideas what I need to change?
> > >
> > >
> > >
> > > 73
> > >
> > >
> > >
> > > Marshall - ke6pcv
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > --
> >
> >
> >
> >
> >
> >
> >
>
>
>
> --
>
>
>
>
>
>
>
--

Re: Open VPN Help - Little Yellow Box as a vpn client

Marshall Oldham
 

Hey Mick,

 

Thank you very much for your help. I can see everything now. :)

 

Your router looks to have a different setup and menu than the one I am using. But this information is very helpfull.

 

73

 

Marshall

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
Sent: Sunday, December 29, 2019 5:20 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

 

Hello Marshall,

I'm sorry those screen shots didn't work for you. Here is another try. If these pictures aren't worth a thousand words, then I will try to describe it for you.

http://www.wyocat.com/tarra/yellowbox

Mick - W7CAT
Node 3464

----- Original Message -----
From: Marshall Oldham
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 03:33:07 PM
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Mick,
>
>
>
> I can't see any of the information on you attached pictures.
>
> The resolution is too low on the photos.
>
>
>
> Thanks
>
>
>
> Marshall
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
> Sent: Sunday, December 29, 2019 1:45 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
>
>
> Here is what mine looks like if this helps.
>
> Mick - W7CAT
> Node 3464
>
> ----- Original Message -----
> From: Marshall Oldham
> To: IRLP@irlp.groups.io
> Sent: Sunday, December 29, 2019 02:14:35 PM
> Subject: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
> > Greetings,
> >
> >
> >
> > Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running
> > the vpn client which is connected to a virtual machine at Virmach that is running openVPN.
> >
> >
> >
> > I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is
> > attached to the internet via ethernet cable to my ATT-Uverse router.
> >
> >
> >
> > I have followed Craig Davidson's instructions here.
> >
> >
> >
> > http://experimental.irlp.net/YellowBox/
> >
> >
> >
> > I did make separate entries in the advanced setup of the router for every port number that need
> > to be forward in the router for IRLP to work correctly.
> >
> >
> >
> > The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet
> > access.
> >
> >
> >
> > I am still having a problem with the port forwarding for IRLP.
> >
> >
> >
> > When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup
> > correctly.
> >
> >
> >
> > Anyone have any ideas what I need to change?
> >
> >
> >
> > 73
> >
> >
> >
> > Marshall - ke6pcv
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> --
>
>
>
>
>
>
>

--

Re: Open VPN Help - Little Yellow Box as a vpn client

Teton Amateur Radio Repeater Association (TARRA)
 

With a VPN, you don't need to setup all the ports in your router, that is the idea of using a VPN.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Ed W6YJ
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 03:21:31 PM
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Marshall,
>
> I just went through this with my Uverse router (BGW210-700). It seems
> AT&T has the routers configured to block just about everything beyond
> simple web and mail ports.
>
> Within the BGS210-700, there is a section Firewall/Packet Filter that
> you need to adds the TCP & UDP ports you want opened .
>
> This should have been all that is needed, but evidently they have a
> second level of filtering/blocking that you can get around by going into
> Firewall/NAT/Gaming and then you will need to add the ports a second
> time as one or more Application Hosting Entry(s).
>
> Ed
> W6YJ
>
>
>
> On 12/29/2019 1:14 PM, Marshall Oldham wrote:
> >
> > Greetings,
> >
> > Okay this is my first attempt at using the GL-MT300N (little yellow
> > box) at my house running the vpn client which is connected to a
> > virtual machine at Virmach that is  running openVPN.
> >
> > I have an IRLP node connected to the GL-MT300N (little yellow box) at
> > my house which  is attached to the internet via ethernet cable to my
> > ATT-Uverse router.
> >
> > I have followed Craig Davidson's instructions here.
> >
> > http://experimental.irlp.net/YellowBox/
> >
> > I did make separate entries in the advanced setup of the router for
> > every port number that need to be forward in the router for IRLP to
> > work correctly.
> >
> > The GL-MT300N is connecting to the vpn server at Virmach just fine and
> > is providing internet access.
> >
> > I am still having a problem with the port forwarding for IRLP.
> >
> > When I run the troubleshoot-irlp script it tells me that inbound port
> > forwarding is not setup correctly.
> >
> > Anyone have any ideas what I need to change?
> >
> > 73
> >
> > Marshall - ke6pcv
> >
> >
>
>
>
>
--

Re: Open VPN Help - Little Yellow Box as a vpn client

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Marshall,

I'm sorry those screen shots didn't work for you. Here is another try. If these pictures aren't worth a thousand words, then I will try to describe it for you.

http://www.wyocat.com/tarra/yellowbox

Mick - W7CAT
Node 3464

----- Original Message -----
From: Marshall Oldham
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 03:33:07 PM
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Mick,
>
>
>
> I can't see any of the information on you attached pictures.
>
> The resolution is too low on the photos.
>
>
>
> Thanks
>
>
>
> Marshall
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
> Sent: Sunday, December 29, 2019 1:45 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
>
>
> Here is what mine looks like if this helps.
>
> Mick - W7CAT
> Node 3464
>
> ----- Original Message -----
> From: Marshall Oldham
> To: IRLP@irlp.groups.io
> Sent: Sunday, December 29, 2019 02:14:35 PM
> Subject: [IRLP] Open VPN Help - Little Yellow Box as a vpn client
>
> > Greetings,
> >
> >
> >
> > Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running
> > the vpn client which is connected to a virtual machine at Virmach that is running openVPN.
> >
> >
> >
> > I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is
> > attached to the internet via ethernet cable to my ATT-Uverse router.
> >
> >
> >
> > I have followed Craig Davidson's instructions here.
> >
> >
> >
> > http://experimental.irlp.net/YellowBox/
> >
> >
> >
> > I did make separate entries in the advanced setup of the router for every port number that need
> > to be forward in the router for IRLP to work correctly.
> >
> >
> >
> > The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet
> > access.
> >
> >
> >
> > I am still having a problem with the port forwarding for IRLP.
> >
> >
> >
> > When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup
> > correctly.
> >
> >
> >
> > Anyone have any ideas what I need to change?
> >
> >
> >
> > 73
> >
> >
> >
> > Marshall - ke6pcv
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> --
>
>
>
>
>
>
>
--

Re: Open VPN Help - Little Yellow Box as a vpn client

k9dc
 

I don’t think so. But then friends don’t let friends run CentOS 4, HI

-k9dc

On Dec 29, 2019, at 17:30, Marshall Oldham <ke6pcv@...> wrote:

Dave,

Can OpenVPN be installed on an IRLP node running Centos 4.xx?

If so, I will give that a try! :)

Marshall

-----Original Message-----
From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of k9dc
Sent: Sunday, December 29, 2019 1:36 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client


Why don’t you just install OpenVPN on the node, then you won’t have to screw with any port forwarding at all. That is what we suggest for everyone running the IRLP VPN clients. I have one of those yellow box routers and it works fine. But running OpenVPN on the node is far easier.

-k9dc

Re: Open VPN Help - Little Yellow Box as a vpn client

Marshall Oldham
 

Mick,

 

I can't see any of the information on you attached pictures.

The resolution is too low on the photos.

 

Thanks

 

Marshall

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
Sent: Sunday, December 29, 2019 1:45 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

 

Here is what mine looks like if this helps.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Marshall Oldham
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 02:14:35 PM
Subject: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Greetings,
>
>
>
> Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running
> the vpn client which is connected to a virtual machine at Virmach that is running openVPN.
>
>
>
> I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is
> attached to the internet via ethernet cable to my ATT-Uverse router.
>
>
>
> I have followed Craig Davidson's instructions here.
>
>
>
> http://experimental.irlp.net/YellowBox/
>
>
>
> I did make separate entries in the advanced setup of the router for every port number that need
> to be forward in the router for IRLP to work correctly.
>
>
>
> The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet
> access.
>
>
>
> I am still having a problem with the port forwarding for IRLP.
>
>
>
> When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup
> correctly.
>
>
>
> Anyone have any ideas what I need to change?
>
>
>
> 73
>
>
>
> Marshall - ke6pcv
>
>
>
>
>
>
>
>
>
>
>

--

Re: Open VPN Help - Little Yellow Box as a vpn client

Marshall Oldham
 

Dave,

Can OpenVPN be installed on an IRLP node running Centos 4.xx?

If so, I will give that a try! :)

Marshall

-----Original Message-----
From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of k9dc
Sent: Sunday, December 29, 2019 1:36 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Open VPN Help - Little Yellow Box as a vpn client


Why don’t you just install OpenVPN on the node, then you won’t have to screw with any port forwarding at all. That is what we suggest for everyone running the IRLP VPN clients. I have one of those yellow box routers and it works fine. But running OpenVPN on the node is far easier.

-k9dc


On Dec 29, 2019, at 16:14, Marshall Oldham <ke6pcv@...> wrote:

Greetings,

Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running the vpn client which is connected to a virtual machine at Virmach that is running openVPN.

I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is attached to the internet via ethernet cable to my ATT-Uverse router.

I have followed Craig Davidson's instructions here.

http://experimental.irlp.net/YellowBox/

I did make separate entries in the advanced setup of the router for every port number that need to be forward in the router for IRLP to work correctly.

The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet access.

I am still having a problem with the port forwarding for IRLP.

When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup correctly.

Anyone have any ideas what I need to change?

73

Marshall - ke6pcv

Re: Open VPN Help - Little Yellow Box as a vpn client

Ed W6YJ
 

Marshall,

I just went through this with my Uverse router (BGW210-700). It seems AT&T has the routers configured to block just about everything beyond simple web and mail ports.

Within the BGS210-700, there is a section Firewall/Packet Filter that you need to adds the TCP & UDP ports you want opened .

This should have been all that is needed, but evidently they have a second level of filtering/blocking that you can get around by going into Firewall/NAT/Gaming and then you will need to add the ports a second time as one or more Application Hosting Entry(s).

Ed
W6YJ



On 12/29/2019 1:14 PM, Marshall Oldham wrote:

Greetings,

 

Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running the vpn client which is connected to a virtual machine at Virmach that is  running openVPN.

 

I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which  is attached to the internet via ethernet cable to my ATT-Uverse router.

 

I have followed Craig Davidson's instructions here.

 

http://experimental.irlp.net/YellowBox/

 

I did make separate entries in the advanced setup of the router for every port number that need to be forward in the router for IRLP to work correctly.

 

The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet access.

 

I am still having a problem with the port forwarding for IRLP.

 

When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup correctly.

 

Anyone have any ideas what I need to change?

 

73

 

Marshall - ke6pcv

 

 

 

Re: Open VPN Help - Little Yellow Box as a vpn client

Teton Amateur Radio Repeater Association (TARRA)
 

Here is what mine looks like if this helps.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Marshall Oldham
To: IRLP@irlp.groups.io
Sent: Sunday, December 29, 2019 02:14:35 PM
Subject: [IRLP] Open VPN Help - Little Yellow Box as a vpn client

> Greetings,
>
>
>
> Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running
> the vpn client which is connected to a virtual machine at Virmach that is running openVPN.
>
>
>
> I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is
> attached to the internet via ethernet cable to my ATT-Uverse router.
>
>
>
> I have followed Craig Davidson's instructions here.
>
>
>
> http://experimental.irlp.net/YellowBox/
>
>
>
> I did make separate entries in the advanced setup of the router for every port number that need
> to be forward in the router for IRLP to work correctly.
>
>
>
> The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet
> access.
>
>
>
> I am still having a problem with the port forwarding for IRLP.
>
>
>
> When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup
> correctly.
>
>
>
> Anyone have any ideas what I need to change?
>
>
>
> 73
>
>
>
> Marshall - ke6pcv
>
>
>
>
>
>
>
>
>
>
>
--

Re: Open VPN Help - Little Yellow Box as a vpn client

k9dc
 

Why don’t you just install OpenVPN on the node, then you won’t have to screw with any port forwarding at all. That is what we suggest for everyone running the IRLP VPN clients. I have one of those yellow box routers and it works fine. But running OpenVPN on the node is far easier.

-k9dc

On Dec 29, 2019, at 16:14, Marshall Oldham <ke6pcv@...> wrote:

Greetings,

Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running the vpn client which is connected to a virtual machine at Virmach that is running openVPN.

I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which is attached to the internet via ethernet cable to my ATT-Uverse router.

I have followed Craig Davidson's instructions here.

http://experimental.irlp.net/YellowBox/

I did make separate entries in the advanced setup of the router for every port number that need to be forward in the router for IRLP to work correctly.

The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet access.

I am still having a problem with the port forwarding for IRLP.

When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup correctly.

Anyone have any ideas what I need to change?

73

Marshall - ke6pcv

Open VPN Help - Little Yellow Box as a vpn client

Marshall Oldham
 

Greetings,

 

Okay this is my first attempt at using the GL-MT300N (little yellow box) at my house running the vpn client which is connected to a virtual machine at Virmach that is  running openVPN.

 

I have an IRLP node connected to the GL-MT300N (little yellow box) at my house which  is attached to the internet via ethernet cable to my ATT-Uverse router.

 

I have followed Craig Davidson's instructions here.

 

http://experimental.irlp.net/YellowBox/

 

I did make separate entries in the advanced setup of the router for every port number that need to be forward in the router for IRLP to work correctly.

 

The GL-MT300N is connecting to the vpn server at Virmach just fine and is providing internet access.

 

I am still having a problem with the port forwarding for IRLP.

 

When I run the troubleshoot-irlp script it tells me that inbound port forwarding is not setup correctly.

 

Anyone have any ideas what I need to change?

 

73

 

Marshall - ke6pcv

 

 

 

Re: New install

Teton Amateur Radio Repeater Association (TARRA)
 

Are you (or someone you know and can trust) able to follow back from pin 15 and see if you can see anything wrong, such as a bad solder connection or broken trace? Looking for something in the area where Dave told you to look. It may not be all that bad for you to repair. You have certainly put a lot into trying to find the problem.

Mick - W7CAT
Node 3464

----- Original Message -----
From: William Phillips
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 09:18:58 PM
Subject: Re: [IRLP] New install

> Well looks like it’s the board. If I send that pin to ground at the board While I press the dtmf tone I want it will report the correct ones.
> > On Dec 22, 2019, at 4:13 PM, David Cameron - IRLP wrote:
> >
> > Yes, this says that there is something wrong in the logic of the D0 bit. Have a close look at U1 (largest chip, MT8870 DTMF decoder and U3 (7408 Quad and gate). Those are used to send the logic of DTMF to the computer. Run readinput, and then try flexing the board or pressing on those two ICs to move things around to rule out a cold solder joint.
> >
> > Dave Cameron
> >
> >
> >> On 2019-12-22 3:52 p.m., William Phillips wrote:
> >> I have continuity from the pi to the irlp board. The board shows same voltage as pi. I put a small jumper from bottom of irlp board to bottom of pi. No change. When I take pin 7 on the pi to ground it sends dtmf tone 1 on readinput on my screen. Do you think the irlp board could be broke?
> >>
> >>
> >>> On Dec 22, 2019, at 1:29 PM, David Cameron - IRLP > wrote:
> >>>
> >>> It should be 0v when the logic pin is low. 3.3v is the high state.
> >>>
> >>> Dave Cameron
> >>>
> >>> -------- Original message --------
> >>> From: Craig - K1BDX - Node 8724 >
> >>> Date: 12/22/19 1:08 PM (GMT-08:00)
> >>> To: IRLP@irlp.groups.io
> >>> Subject: Re: [IRLP] New install
> >>>
> >>> That voltage is not changing in a significant way
> >>>
> >>> If the initial voltage is high (around 3.26 volts) then the
> >>> "asserted" voltage (low) should be down around 1 volt or less.
> >>>
> >>>
> >>> On 12/22/19, William Phillips > wrote:
> >>> >
> >>> > That pin varies between 3.26 to 3.29 when dtmf tone sent. I checked it on
> >>> > the pi as well as the irlp board it was the same on both ends.
> >>> >>
> >>> >>
> >>> >> On Dec 22, 2019, at 6:22 AM, Craig - K1BDX - Node 8724
> >>> >> > wrote:
> >>> >>
> >>> >> The first binary bit D0 seems to be stuck in the "asserted" condition.
> >>> >>
> >>> >> I'm wondering if the wire between the pi and the irlp interface board is
> >>> >> broken
> >>> >>
> >>> >> According to Dave Cameron's diagram
> >>> >>
> >>> >> D0 is pin number 7 or the Raspberry Pi header
> >>> >>
> >>> >> monitor the voltage on that pin while you send tones and see if it
> >>> >> changes state properly
> >>> >>
> >>> >>
> >>> >>> On 12/22/19, William Phillips > wrote:
> >>> >>>
> >>> >>> Well I tried a different raspberry 4 did an install all works except the
> >>> >>> dtmf tones are incorrect and the same as before
> >>> >>>
> >>> >>> Pressed : Seen
> >>> >>> 1:nothing
> >>> >>> 2:3 when released 1
> >>> >>> 3:3 when released 1
> >>> >>> 4:5 when released 1
> >>> >>> 5:5 when released 1
> >>> >>> 6:7 when released 1
> >>> >>> 7:7 when released 1
> >>> >>> 8:9 when released 1
> >>> >>> 9:9 when released 1
> >>> >>
> >>>
> >>>
> >
> >
> >
>
>
>
>
--

Re: New install

William Phillips
 

Well looks like it’s the board. If I send that pin to ground at the board While I press the dtmf tone I want it will report the correct ones.

On Dec 22, 2019, at 4:13 PM, David Cameron - IRLP <dcameron@...> wrote:

Yes, this says that there is something wrong in the logic of the D0 bit. Have a close look at U1 (largest chip, MT8870 DTMF decoder and U3 (7408 Quad and gate). Those are used to send the logic of DTMF to the computer. Run readinput, and then try flexing the board or pressing on those two ICs to move things around to rule out a cold solder joint.

Dave Cameron


On 2019-12-22 3:52 p.m., William Phillips wrote:
I have continuity from the pi to the irlp board. The board shows same voltage as pi. I put a small jumper from bottom of irlp board to bottom of pi. No change. When I take pin 7 on the pi to ground it sends dtmf tone 1 on readinput on my screen. Do you think the irlp board could be broke?


On Dec 22, 2019, at 1:29 PM, David Cameron - IRLP <dcameron@... <mailto:dcameron@...>> wrote:

It should be 0v when the logic pin is low. 3.3v is the high state.

Dave Cameron

-------- Original message --------
From: Craig - K1BDX - Node 8724 <k1bdx.craig@... <mailto:k1bdx.craig@...>>
Date: 12/22/19 1:08 PM (GMT-08:00)
To: IRLP@irlp.groups.io <mailto:IRLP@irlp.groups.io>
Subject: Re: [IRLP] New install

That voltage is not changing in a significant way

If the initial voltage is high (around 3.26 volts) then the
"asserted" voltage (low) should be down around 1 volt or less.


On 12/22/19, William Phillips <bphillips.nnh@... <mailto:bphillips.nnh@...>> wrote:

That pin varies between 3.26 to 3.29 when dtmf tone sent. I checked it on
the pi as well as the irlp board it was the same on both ends.


On Dec 22, 2019, at 6:22 AM, Craig - K1BDX - Node 8724
<k1bdx.craig@... <mailto:k1bdx.craig@...>> wrote:

The first binary bit D0 seems to be stuck in the "asserted" condition.

I'm wondering if the wire between the pi and the irlp interface board is
broken

According to Dave Cameron's diagram

D0 is pin number 7 or the Raspberry Pi header

monitor the voltage on that pin while you send tones and see if it
changes state properly


On 12/22/19, William Phillips <bphillips.nnh@... <mailto:bphillips.nnh@...>> wrote:

Well I tried a different raspberry 4 did an install all works except the
dtmf tones are incorrect and the same as before

Pressed : Seen
1:nothing
2:3 when released 1
3:3 when released 1
4:5 when released 1
5:5 when released 1
6:7 when released 1
7:7 when released 1
8:9 when released 1
9:9 when released 1

Re: Custom Decode Now Working

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Dave,

It looks like the custom_decode is working now. Thank you so much for your help and sticking with me through this. I think I finally have almost everything back working again. Just need to figure out the mail yet, but I won't ask you for that one.

Thank you again!

Mick - W7CAT
Node 3464

----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Sunday, December 22, 2019 08:14:16 PM
Subject: Re: [IRLP] Custom Decode Not Working

> Try putting the repeater line at the end of the file. And change it to:repeater ALL=(ALL) NOPASSWD: ALL Dave 
>
>
>
>
> -------- Original message --------From: "Teton Amateur Radio Repeater Association (TARRA)" Date: 12/22/19 7:00 PM (GMT-08:00) To: IRLP@irlp.groups.io Subject: Re: [IRLP] Custom Decode Not Working
> The first time was looking at it with WinSCP. For some reason
> when it show it it puts those extra characters in there. When I
> opened it in Putty with nano, those characters aren't there. I do
> all of my editing with nano.
>
> # This file MUST be edited with the 'visudo' command as root.
> #
> # Please consider adding local content in /etc/sudoers.d/ instead
> of
> # directly modifying this file.
> #
> # See the man page for details on how to write a sudoers file.
> #
> Defaults        env_reset
> Defaults        mail_badpass
> Defaults       
> secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
>
> # Host alias specification
>
> # User alias specification
>
> # Cmnd alias specification
>
> # User privilege specification
> root    ALL=(ALL:ALL) ALL
> repeater  ALL=NOPASSWD: /sbin/shutdown
>
> # Allow members of group sudo to execute any command
> %sudo   ALL=(ALL:ALL) ALL
>
> # See sudoers(5) for more information on "#include" directives:
>
> #includedir /etc/sudoers.d
>
> Here is what I get:
>
> repeater@stn3464:~/$ sudo /sbin/shutdown
> [sudo] password for repeater:
> repeater is not in the sudoers file.  This incident will be
> reported.
> repeater@stn3464:~/$ sudo  /sbin/shutdown
> [sudo] password for repeater:
> repeater is not in the sudoers file.  This incident will be
> reported.
> repeater@stn3464:~/$
>
> Mick - W7CAT
> Node 3464
>
>
>
> ----- Original Message -----
>
> From: David Cameron - IRLP
>
> To: IRLP@irlp.groups.io
>
> Sent: Sunday, December 22, 2019 06:42:32 PM
>
> Subject: Re: [IRLP] Custom Decode Not Working
>
>
> > You need to remove the sudo /sbin/shutdown from /etc/sudoers.
> You misread the directions. The lube with repeater looks fine, but
> i saw there were extra characters in the first time you posted
> it. How are you editing the file?When logged in as repeater, what
> do you see when you runsudo  /sbin/shutdownDave Cameron 
>
> >
> >
> >
> >
> > -------- Original message --------From: "Teton Amateur Radio
> Repeater Association (TARRA)" Date: 12/22/19
> 5:28 PM (GMT-08:00) To: IRLP@irlp.groups.io Subject: Re: [IRLP]
> Custom Decode Not Working
> > This is a better look at it:
>
> >
> > #
>
> > # This file MUST be edited with the 'visudo' command as
> root.
>
> > #
>
> > # Please consider adding local content in /etc/sudoers.d/
> instead
>
> > of
>
> > # directly modifying this file.
>
> > #
>
> > # See the man page for details on how to write a sudoers
> file.
>
> > #
>
> > Defaults        env_reset
>
> > Defaults        mail_badpass
>
> > Defaults       
>
> >
> secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
> >
> > # Host alias specification
>
> >
> > # User alias specification
>
> >
> > # Cmnd alias specification
>
> >
> > # User privilege specification
>
> > root    ALL=(ALL:ALL) ALL
>
> > repeater  ALL=NOPASSWD:  /sbin/shutdown
>
> >
> > # Allow members of group sudo to execute any command
>
> > %sudo   ALL=(ALL:ALL) ALL
>
> > sudo /sbin/shutdown
>
> >
> > # See sudoers(5) for more information on "#include"
> directives:
>
> >
> > #includedir /etc/sudoers.d
>
> >
> >
> > Mick - W7CAT
>
> > Node 3464
>
> >
> > ----- Original Message -----
>
> >
> > From: David Cameron - IRLP
> >
> > To: IRLP@irlp.groups.io
>
> >
> > Sent: Sunday, December 22, 2019 05:09:26 PM
>
> >
> > Subject: Re: [IRLP] Custom Decode Not Working
>
> >
> >
> > > if [ "$1" = "SABC" ] ; then (/usr/bin/sudo
> /sbin/shutdown -r
>
> > now) ; exit
> > > 1 ; fi
>
> >
> > >
> > > Well that command would require that the repater user
> be
>
> > added to the
> > > /etc/sudoers file to have root permissions. This is
> dangerous
>
> > though,
> > > and not really recommended. But for individual
> programs it is
>
> > not a big
> > > deal:
>
> >
> > >
> > > In the file /etc/sudoers, add
>
> >
> > >
> > > repeater  ALL=NOPASSWD:  /sbin/shutdown
>
> >
> > >
> > > Then the command
>
> >
> > >
> > > sudo /sbin/shutdown
>
> >
> > >
> > > can be run with root permissions from the repeater
> user.
>
> >
> > >
> > > Dave Cameron
>
> >
> > >
> > > On 2019-12-22 3:33 p.m., Teton Amateur Radio Repeater
>
> > Association
> > > (TARRA) wrote:
>
> >
> > > >
>
> >
> > > > Yes, certainly easy when you know what to do.
> That took
>
> > care of that
> > > > and it is working now.
>
> >
> > > >
>
> >
> > > > As for the other, for example, if I send *ABC,
> nothing
>
> > happens. It
> > > > isn't acting on the DTMF command. The other
> commands
>
> > don't respond.
>
> >
> > > >
>
> >
> > > > Mick - W7CAT
>
> >
> > > > Node 3464
>
> >
> > > >
>
> >
> > > > ----- Original Message -----
>
> >
> > > > From: David Cameron - IRLP
>
> >
> > > > To: IRLP@irlp.groups.io
>
> >
> > > > Sent: Sunday, December 22, 2019 04:26:09 PM
>
> >
> > > > Subject: Re: [IRLP] Custom Decode Not Working
>
> >
> > > >
>
> >
> > > > > Easy:
>
> >
> > > > >
>
> >
> > > > > in dtmffastdial, change
>
> >
> > > > >
>
> >
> > > > > /home/irlp/bin/dial --tone-time 105 --volume
> 30
>
> > --silent-time 105 "$1"
>
> >
> > > > >
>
> >
> > > > > to
>
> >
> > > > >
>
> >
> > > > > aoss /home/irlp/bin/dial --tone-time 105
> --volume
>
> > 30 --silent-time
> > > > 105 "$1"
>
> >
> > > > >
>
> >
> > > > > On 2019-12-22 3:24 p.m., Teton Amateur Radio
>
> > Repeater Association
>
> >
> > > > > (TARRA) wrote:
>
> >
> > > > > >
>
> >
> > > > > > Okay, hopefully these attachments work.
> It
>
> > isn't working to
> > > > receive or
>
> >
> > > > > > send DTMF commands or tones.
>
> >
> > > > > >
>
> >
> > > > > > Mick - W7CAT
>
> >
> > > > > > Node 3464
>
> >
> > > > > >
>
> >
> > > > > > ----- Original Message -----
>
> >
> > > > > > From: David Cameron - IRLP
>
> >
> > > > > > To: IRLP@irlp.groups.io
>
> >
> > > > > > Sent: Sunday, December 22, 2019
> 03:48:55 PM
>
> >
> > > > > > Subject: Re: [IRLP] Custom Decode Not
> Working
>
> >
> > > > > >
>
> >
> > > > > > > The reason i ask is that ALL dtmf
> codes
>
> > are processed through
>
> >
> > > > > > custom_decode. So if nothing works,
> then there
>
> > is something causing
>
> >
> > > > > > errors in the custom_decode script. You
> are
>
> > going to have to post
> > > > this
>
> >
> > > > > > sync_rc210 script and we can help you
> find
>
> > where you need to
> > > > modify it
>
> >
> > > > > > to work on the newer systems. Dave
> Cameron
>
> >
> > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > -------- Original message
> --------From:
>
> > "Teton Amateur Radio
>
> >
> > > > > > Repeater Association (TARRA)" Date:
> 12/22/19
>
> > 2:29 PM (GMT-08:00) To:
>
> >
> > > > > > IRLP@irlp.groups.io Subject: Re: [IRLP]
> Custom
>
> > Decode Not Working
>
> >
> > > > > > > The sync program does it by
> sending DTMF
>
> > tones.
>
> >
> > > > > > >
>
> >
> > > > > > > I can connect to the test
> reflectors and
>
> > other nodes. I don't
>
> >
> > > > > > > consider those as "custom". The
> commands
>
> > that I do have in my
>
> >
> > > > > > > custom_decode aren't working. For
>
> > example, sending a set of DTMF
>
> >
> > > > > > > tones to cause the time to be set,
> no
>
> > DTMF tones are sent but
>
> >
> > > > > > > there is a couple of PTT at the
> end of
>
> > the script.
>
> >
> > > > > > >
>
> >
> > > > > > > Mick - W7CAT
>
> >
> > > > > > > Node 3464
>
> >
> > > > > > >
>
> >
> > > > > > > ----- Original Message -----
>
> >
> > > > > > >
>
> >
> > > > > > > From: David Cameron - IRLP
>
> >
> > > > > > >
>
> >
> > > > > > > To: IRLP@irlp.groups.io
>
> >
> > > > > > >
>
> >
> > > > > > > Sent: Sunday, December 22, 2019
> 03:17:14
>
> > PM
>
> >
> > > > > > >
>
> >
> > > > > > > Subject: Re: [IRLP] Custom Decode
> Not
>
> > Working
>
> >
> > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > Well you have not explained
> what the
>
> > script exactly does
>
> >
> > > > > > > besides syncing
>
> >
> > > > > > > > the time on the controller.
> Does it
>
> > do it via serial port or
>
> >
> > > > > > > using DTMF
>
> >
> > > > > > > > audio somehow?
>
> >
> > > > > > >
>
> >
> > > > > > > >
>
> >
> > > > > > > > Using aoss is not too hard -
> you
>
> > just prefix any command that
>
> >
> > > > > > > throws an
>
> >
> > > > > > > > error about /dev/dsp with
> aoss. If
>
> > you attach the script,
>
> >
> > > > > > > that is a start.
>
> >
> > > > > > >
>
> >
> > > > > > > >
>
> >
> > > > > > > > You mention an issue with
>
> > custom_decode, but you didn't
>
> >
> > > > > > > answer the
>
> >
> > > > > > > > questions I was asking. If
> you enter
>
> > a code like 9990, what
>
> >
> > > > > > > happens?
>
> >
> > > > > > > > What is not working with
> DTMF?
>
> >
> > > > > > >
>
> >
> > > > > > > >
>
> >
> > > > > > > > Dave Cameron
>
> >
> > > > > > >
>
> >
> > > > > > > >
>
> >
> > > > > > > > On 2019-12-22 2:13 p.m.,
> Teton
>
> > Amateur Radio Repeater
>
> >
> > > > > > > Association
>
> >
> > > > > > > > (TARRA) wrote:
>
> >
> > > > > > >
>
> >
> > > > > > > > > I haven't found anything
> that
>
> > works.
>
> >
> > > > > > >
>
> >
> > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > Not sure how much needs
> to be
>
> > changed to use aoss or
>
> >
> > > > > > > aplay. Does it
>
> >
> > > > > > > > > matter which one of the
> two?
>
> >
> > > > > > >
>
> >
> > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > The updating of the node
> has
>
> > broken enough things that I
>
> >
> > > > > > > may just go
>
> >
> > > > > > > > > back to the old computer
> and
>
> > software that worked.
>
> >
> > > > > > >
>
> >
> > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > Mick - W7CAT
>
> >
> > > > > > >
>
> >
> > > > > > > > > Node 3464
>
> >
> > > > > > >
>
> >
> > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > ----- Original Message
> -----
>
> >
> > > > > > >
>
> >
> > > > > > > > > From: David Cameron -
> IRLP
>
> >
> > > > > > >
>
> >
> > > > > > > > > To: IRLP@irlp.groups.io
>
> >
> > > > > > >
>
> >
> > > > > > > > > Sent: Sunday, December
> 22, 2019
>
> > 02:34:48 PM
>
> >
> > > > > > >
>
> >
> > > > > > > > > Subject: Re: [IRLP]
> Custom
>
> > Decode Not Working
>
> >
> > > > > > >
>
> >
> > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > > Does nothing work
> on the
>
> > node, or just one code?
>
> >
> > > > > > > Sending the
>
> >
> > > > > > >
>
> >
> > > > > > > > > > custom_decode
> script would
>
> > tell a lot.
>
> >
> > > > > > >
>
> >
> > > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > > That sync_rc210
> script
>
> > will need to be rewritten to
>
> >
> > > > > > > support aoss or use
>
> >
> > > > > > >
>
> >
> > > > > > > > > > aplay. It looks
> like it is
>
> > trying to write direct
>
> >
> > > > > > > to /dev/dsp.
>
> >
> > > > > > >
>
> >
> > > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > > David Cameron
>
> >
> > > > > > >
>
> >
> > > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > > On 2019-12-22 1:04
> p.m.,
>
> > Teton Amateur Radio
>
> >
> > > > > > > Repeater Association
>
> >
> > > > > > >
>
> >
> > > > > > > > > > (TARRA) wrote:
>
> >
> > > > > > >
>
> >
> > > > > > > > > > >
>
> >
> > > > > > >
>
> >
> > > > > > > > > > > I s
--