Date   

Re: Irlp Custom connect wav files

larry_n7fm
 

Thank you very much Dave M. I will pass the script along.

Dave G. mentioned doing likewise but that script makes it easy for anyone to do it. Very Handy...Thanks.

Larry - N7FM

On 10/10/19 1:23 PM, David McAnally wrote:
Someone with access to the node could run this old script to create
connect files with the default node I'd. This script is in the irlp
group files area.
<https://irlp.groups.io/g/IRLP/files/Scripts%20for%20IRLP%20Nodes//defaultOnOff.txt>
David M.
WD5M


Re: WWAN configuration and 4G Dongles on node 6370

Peter Chaplin <peter@...>
 

Hi Mike/et al,

 

I’ve deployed the node for JOTA, so don’t have access to it at the moment to review the files.

 

Basically, in the  /etc/network/interfaces file I added the below wwan0 interface before the eth0 interface.

 

auto wwan0

allow-hotplug wwan0

iface wwan0 inet dhcp

               dns-nameservers 8.8.8.8 8.8.4.4

 

I swapped the SIM between a couple of different model 4G dongles, Telstra Sierra 320U and another that I don’t have the model at hand and it worked with both.

I can’t say I specifically looked to confirm 4G operation. I will when I get the unit back after JOTA in November.

 

Regards,

Peter

VK3AJ

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Mike Alsop
Sent: Thursday, 10 October 2019 21:18
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] WWAN configuration and 4G Dongles on node 6370

 

Peter

 

Interested to know how you actually got 4G to work?? I have tried everything I know under Debian 9, but just can't get past 3G

 

Mike

VK8MA

 

On Sat, 2019-10-05 at 09:37 +1000, Peter Chaplin wrote:

Well, I finally have everything working.

Thanks Mike, commenting out the eth0 lines brought the dongle up.

What I found is if I put the wwan0 ahead of the eth0 in the interfaces file, it will try for the wwan0 and if it’s not there, move on to the eth0.

 

The node (6370) is now showing up in the IRLP active node list. – That’s a win.

However, when on the 4G dongle, the node VK3RSR-R wasn’t showing up in EchoLINK.

Swap back to eth0 and VK3RSR-R comes straight up in EchoLINK.

I wouldn’t have thought that how the Pi is getting internet would have mattered.

 

While connected on the 4G dongle, I ran the Troubleshooting script in the node and it passed everything except Test 1 – DNS and Test 10 which it’s not expected to pass with EchoIRLP enabled.

I swapped back to eth0 and re-ran the Troubleshoot, it passed Test 1.

This would suggest there is something stopping the DNS service from running when wwan0 is selected.

This is confirmed by NOT being able to Ping any domain name but being able to Ping the IP address for the domain when connected to wwan0.

I’m able to ping both Domain name and IP address when connected to eth0.

 

During bootup, I see a message “A start job is running for Raise network interfaces”

Then I get a “Failed to start Raise network interfaces” when booting up with wwan0.

 

I tried adding dns-nameservers and the IP addresses of my carriers DNS servers to the /etc/network/interfaces file after the WWAN0 interface, but that didn’t make any difference.

I also enabled static DNS addresses in the dongle with my carriers DNS servers to no avail.

I then tried to Ping my carriers DNS servers and found I could not do so.

I changed the static DNS servers in my dongle to 8.8.8.8 and 8.8.4.4 (Google’s public DNS servers) and hey presto, My node comes up in EchoLINK and works fine.

Doing this doesn’t stop the “Failed to start” message, however, I noticed the Google DNS addresses have been inserted into the resolve.conf file from the 4G dongle’s static DNS or elsewhere.

I then went back and added the Google DNS servers into the /etc/network/interfaces file (dns-nameservers 8.8.8.8 8.8.4.4) for the wwan0 interface and tested it. All worked fine.

So, there must be something in Debian or IRLP scripts that causes the Telstra DNS addresses to be blocked.

 

So, in summary, to get it working all I had to do was add a wwan0 interface into the /etc/network/interfaces file and include a line dns-nameservers 8.8.8.8 8.8.4.4 for the wwan0 interface and place the wwan0 interface ahead of the eth0 interface.

 

Either way, I’ve resolved my problem.

Next, just because I like putting myself through mental pain, I’ll try the same with some other model 4G dongles I have laying around and see if they have the same symptoms.

 

Thanks again to all those that offered tips and hints that led me down the learning path of Unix/Linux/Debian/Raspbian/etc

 

Yours gratefully and 73’s for now,

Peter

VK3AJ

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Mike Alsop
Sent: Friday, 4 October 2019 11:02
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] WWAN configuration and 4G Dongles on node 6370

 

I am pretty sure if you comment out any entries in /etc/network/interfaces relating to eth0 and then reboot, you should be on the dongle.

 

Mike

 

On Thu, 2019-10-03 at 09:00 -0500, k9dc wrote:

IRLP will use whatever interface is chosen by the Linux routing table.  What does the command ‘ip route show' reveal?  

 

-k9dc

 

On Oct 3, 2019, at 07:04, Peter Chaplin <

 

peter@...

 

 

> wrote:

 

Thanks to everyone who has provided tips for this.

 

From these tips, I have been able to get wwan0 showing up when i run ifconfig

 

This has led to getting the 4G dongle working and showing up an IP address in the netconfig application, but IRLP want's to use eth0 instead of wwan0 as it's interface, which of course eth0 is unplugged.

 

How do I get the IRLP node to use wwan0 instead of eth0.

 

I've tried changing the adaptor in /etc/network/interfaces but that doesn't seem to make a difference.

 

 

 

 


Re: Irlp Custom connect wav files

David McAnally
 

Someone with access to the node could run this old script to create connect files with the default node I'd. This script is in the irlp group files area. <https://irlp.groups.io/g/IRLP/files/Scripts%20for%20IRLP%20Nodes//defaultOnOff.txt>

David M.
WD5M


Re: Irlp Custom connect wav files

larry_n7fm
 

Thanks for that explanation Dave.
It isn't a crisis issue and the overwrite will just have to do.

However some way to return to original would be a nice function when we screw up and try something and find we don't like it.

Were it not for the new owner living 800 miles away I would have helped him reload from scratch. As it is, it needed to be already operational when he received it.

Regards
Larry - N7FM

On 10/10/19 12:03 PM, David Cameron - IRLP wrote:
Larry,
The key has to be removed for the audio files to be removed. So in the case of a "recycled node number", as long as the key is removed for at least 24 hours, so will the audio files. Have a look at the repeater user crontab and the script clean_audio_files on your node.
The issue in your case is you sold the node with a node number, so the key was never removed, so the script has no way of knowing to remove your audio files.
If it makes it easier, there is a lesser-known script to record the audio files right on the node itself:
/home/irlp/scripts/record_my_ids
This uses the radio to record the audio files, and performs all the conversions and such without having to deal with the files themselves.
David Cameron
VE7LTD
On 2019-10-09 22:28, larry_n7fm wrote:
I recently sold one of my IRLP nodes.
Sadly when I was new to IRLP years ago. I didn't realize that creating
a custom connect wav file would become a problem.

I was foolish enough to created a custom connect wav file which
included my callsign not realizing once it was activated there was no
option to stop or revert back to normal.
Bet most everyone reading this is already thinking "Dummy" and can
visualize my problem.
Yup ... when the new owner I sold the node to.connects ... it
announces/identifies on the other end with my callsign.

I do realize creating a new custom file will replace my problem file.
However the new owner would like the node to revert to original
connect messages.
Which it can't as long as a stnxxxx wave file exists.

Has anyone come up with a way to reverse or stop the custom
stn(node_number) from spreading to other newly connected nodes?
Is it possible for IRLP support to delete custom stnxxxx wav files if
requested?
Once deleted from the IRLP server it would stop any FURTHER
propagation of that particular custom connect file.

Suggestions or solution? New install with a New number isn't something
he wants or is able to do.

What would really be nice ... is a script mod with an option flag "IF
EXIST delete" when checking for a new stnxxxx files for those of us
who want to revert back.

Larry - N7FM



Links:
------
[1] https://irlp.groups.io/g/IRLP/message/76137
[2] https://groups.io/mt/34471826/500965
[3] https://irlp.groups.io/g/IRLP/post
[4] https://irlp.groups.io/g/IRLP/editsub/500965
[5] https://irlp.groups.io/g/IRLP/leave/defanged


Re: Interesting Node Problem

Teton Amateur Radio Repeater Association (TARRA)
 

Good idea, except that I can't SSH into the computer.

Mick - W7CAT
Node 3464

----- Original Message -----
From: Jim MacKenzie
To: IRLP@irlp.groups.io
Sent: Thursday, October 10, 2019 01:07:27 PM
Subject: Re: [IRLP] Interesting Node Problem

> You might want to run the diagnostic scripts – they will tell you if something is broken.
>
>
>
> It will be pretty easy to tell if you have SD card issues by looking at the output of ‘dmesg’. Mmcblk0px (where x is a number) will be partitions of the main SD card (probably only SD card :) ).
>
>
>
> 73
>
> Jim VE5EV
>
>
>
> From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
> Sent: Thursday, October 10, 2019 1:04 PM
> To: IRLP@irlp.groups.io
> Subject: Re: [IRLP] Interesting Node Problem
>
>
>
> Hello Dave,
>
> It took a little bit of time to figure out where to reboot. Finally found it and rebooted. The node had rebooted this morning at 3:50 AM per the schedule in my router.
>
> The reboot of the router didn't help. I also just rebooted the node computer as well. Still not working.
>
> One other interesting detail, my node is set up to email me whenever a connection has been made, not getting any emails.
>
> Mick - W7CAT
> Node 3464
>
> ----- Original Message -----
> From: k9dc
> To: IRLP@irlp.groups.io
> Sent: Thursday, October 10, 2019 12:39:49 PM
> Subject: Re: [IRLP] Interesting Node Problem
>
> >
> > Can you reboot the router? Its port forwarding might just be constipated.
> >
> > -k9dc
> >
> > > On Oct 10, 2019, at 14:30, Teton Amateur Radio Repeater Association (TARRA) wrote:
> > >
> > > ?
> > > Hello Dave & Dave,
> > >
> > > I can log into the router and it looks like everything is the way it should be. It is showing the IRLP computer as being connected to the router. Also all of the port information is there and looks okay.
> > >
> > > I am using a cellular connection with a public static IP address. No VPN. I haven't done anything with the node computer other than change a cron setting a couple weeks ago. Because of not having access to the site, I have been extremely careful about making any changes. Besides, if it isn't broke, no need to fix it. Although now it is broken. May not be much I can do with it remotely.
> > >
> > > Not sure of which SD card may be in there right now. I have been using a SanDisk Extreme SD card. The power is supplied from the repeater power supply to an add on board (that has been there for years) which supplies the power to the Pi.
> > >
> > > Mick - W7CAT
> > > Node 3464
> >
> >
> >
> >
>
>
>
> --
>
>
>
>
>
>
>
--


Re: Interesting Node Problem

Jim MacKenzie
 

You might want to run the diagnostic scripts – they will tell you if something is broken.

 

It will be pretty easy to tell if you have SD card issues by looking at the output of ‘dmesg’.  Mmcblk0px (where x is a number) will be partitions of the main SD card (probably only SD card J ).

 

73

Jim VE5EV

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
Sent: Thursday, October 10, 2019 1:04 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Interesting Node Problem

 

Hello Dave,

It took a little bit of time to figure out where to reboot. Finally found it and rebooted. The node had rebooted this morning at 3:50 AM per the schedule in my router.

The reboot of the router didn't help. I also just rebooted the node computer as well. Still not working.

One other interesting detail, my node is set up to email me whenever a connection has been made, not getting any emails.

Mick - W7CAT
Node 3464

----- Original Message -----
From: k9dc
To: IRLP@irlp.groups.io
Sent: Thursday, October 10, 2019 12:39:49 PM
Subject: Re: [IRLP] Interesting Node Problem

>
> Can you reboot the router? Its port forwarding might just be constipated.
>
> -k9dc
>
> > On Oct 10, 2019, at 14:30, Teton Amateur Radio Repeater Association (TARRA) wrote:
> >
> > ?
> > Hello Dave & Dave,
> >
> > I can log into the router and it looks like everything is the way it should be. It is showing the IRLP computer as being connected to the router. Also all of the port information is there and looks okay.
> >
> > I am using a cellular connection with a public static IP address. No VPN. I haven't done anything with the node computer other than change a cron setting a couple weeks ago. Because of not having access to the site, I have been extremely careful about making any changes. Besides, if it isn't broke, no need to fix it. Although now it is broken. May not be much I can do with it remotely.
> >
> > Not sure of which SD card may be in there right now. I have been using a SanDisk Extreme SD card. The power is supplied from the repeater power supply to an add on board (that has been there for years) which supplies the power to the Pi.
> >
> > Mick - W7CAT
> > Node 3464
>
>
>
>

--


Re: Interesting Node Problem

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Dave,

It took a little bit of time to figure out where to reboot. Finally found it and rebooted. The node had rebooted this morning at 3:50 AM per the schedule in my router.

The reboot of the router didn't help. I also just rebooted the node computer as well. Still not working.

One other interesting detail, my node is set up to email me whenever a connection has been made, not getting any emails.

Mick - W7CAT
Node 3464

----- Original Message -----
From: k9dc
To: IRLP@irlp.groups.io
Sent: Thursday, October 10, 2019 12:39:49 PM
Subject: Re: [IRLP] Interesting Node Problem

>
> Can you reboot the router? Its port forwarding might just be constipated.
>
> -k9dc
>
> > On Oct 10, 2019, at 14:30, Teton Amateur Radio Repeater Association (TARRA) wrote:
> >
> > ?
> > Hello Dave & Dave,
> >
> > I can log into the router and it looks like everything is the way it should be. It is showing the IRLP computer as being connected to the router. Also all of the port information is there and looks okay.
> >
> > I am using a cellular connection with a public static IP address. No VPN. I haven't done anything with the node computer other than change a cron setting a couple weeks ago. Because of not having access to the site, I have been extremely careful about making any changes. Besides, if it isn't broke, no need to fix it. Although now it is broken. May not be much I can do with it remotely.
> >
> > Not sure of which SD card may be in there right now. I have been using a SanDisk Extreme SD card. The power is supplied from the repeater power supply to an add on board (that has been there for years) which supplies the power to the Pi.
> >
> > Mick - W7CAT
> > Node 3464
>
>
>
>
--


Re: Irlp Custom connect wav files

David Cameron - IRLP
 

Larry,

The key has to be removed for the audio files to be removed. So in the case of a "recycled node number", as long as the key is removed for at least 24 hours, so will the audio files. Have a look at the repeater user crontab and the script clean_audio_files on your node.

The issue in your case is you sold the node with a node number, so the key was never removed, so the script has no way of knowing to remove your audio files.

If it makes it easier, there is a lesser-known script to record the audio files right on the node itself:
/home/irlp/scripts/record_my_ids

This uses the radio to record the audio files, and performs all the conversions and such without having to deal with the files themselves.

David Cameron
VE7LTD

On 2019-10-09 22:28, larry_n7fm wrote:
I recently sold one of my IRLP nodes.
Sadly when I was new to IRLP years ago. I didn't realize that creating
a custom connect wav file would become a problem.
I was foolish enough to created a custom connect wav file which
included my callsign not realizing once it was activated there was no
option to stop or revert back to normal.
Bet most everyone reading this is already thinking "Dummy" and can
visualize my problem.
Yup ... when the new owner I sold the node to.connects ... it
announces/identifies on the other end with my callsign.
I do realize creating a new custom file will replace my problem file.
However the new owner would like the node to revert to original
connect messages.
Which it can't as long as a stnxxxx wave file exists.
Has anyone come up with a way to reverse or stop the custom
stn(node_number) from spreading to other newly connected nodes?
Is it possible for IRLP support to delete custom stnxxxx wav files if
requested?
Once deleted from the IRLP server it would stop any FURTHER
propagation of that particular custom connect file.
Suggestions or solution? New install with a New number isn't something
he wants or is able to do.
What would really be nice ... is a script mod with an option flag "IF
EXIST delete" when checking for a new stnxxxx files for those of us
who want to revert back.
Larry - N7FM
Links:
------
[1] https://irlp.groups.io/g/IRLP/message/76137
[2] https://groups.io/mt/34471826/500965
[3] https://irlp.groups.io/g/IRLP/post
[4] https://irlp.groups.io/g/IRLP/editsub/500965
[5] https://irlp.groups.io/g/IRLP/leave/defanged


Re: Interesting Node Problem

k9dc
 


Can you reboot the router?  Its port forwarding might just be constipated. 

-k9dc

On Oct 10, 2019, at 14:30, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:



Hello Dave & Dave,

I can log into the router and it looks like everything is the way it should be. It is showing the IRLP computer as being connected to the router. Also all of the port information is there and looks okay.

I am using a cellular connection with a public static IP address. No VPN. I haven't done anything with the node computer other than change a cron setting a couple weeks ago. Because of not having access to the site, I have been extremely careful about making any changes. Besides, if it isn't broke, no need to fix it. Although now it is broken. May not be much I can do with it remotely.

Not sure of which SD card may be in there right now. I have been using a SanDisk Extreme SD card. The power is supplied from the repeater power supply to an add on board (that has been there for years) which supplies the power to the Pi.

Mick - W7CAT
Node 3464


Re: Interesting Node Problem

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Dave & Dave,

I can log into the router and it looks like everything is the way it should be. It is showing the IRLP computer as being connected to the router. Also all of the port information is there and looks okay.

I am using a cellular connection with a public static IP address. No VPN. I haven't done anything with the node computer other than change a cron setting a couple weeks ago. Because of not having access to the site, I have been extremely careful about making any changes. Besides, if it isn't broke, no need to fix it. Although now it is broken. May not be much I can do with it remotely.

Not sure of which SD card may be in there right now. I have been using a SanDisk Extreme SD card. The power is supplied from the repeater power supply to an add on board (that has been there for years) which supplies the power to the Pi.

Mick - W7CAT
Node 3464


----- Original Message -----
From: David Cameron - IRLP
To: IRLP@irlp.groups.io
Sent: Thursday, October 10, 2019 11:59:58 AM
Subject: Re: [IRLP] Interesting Node Problem

> Mick,
>
> I am going to wager a guess that the device that assigns IPs to the Pi
> node on the mountain has reset, and any specific port forwarding that
> might be set up.
>
> If the IP of the node behind the router changes, then it breaks any
> forwarding. BUT, if you are seeing a valid time stamp from the status
> page, then the node is still there and running. I just checked yours
> though, and it is showing the last valid timestamp as "Last heard from
> Node: 18:22:09 on Oct 09 2019 MDT". That was quite a while ago.
>
> If that is BEFORE you started having issues, then I agree the node is
> probably not responding. Could be a variety of reasons, but SD card is a
> good place to check first.
>
> You can't offload the bandwidth to a VPS... You still need to talk into
> and out of the node. To be honest, adding a VPN or some other "go
> between" will only increase the bandwidth use, not reduce it. However,
> this may allow you to run on a cheaper Cellular option, as you will not
> need a routable IP address to the cellular modem. You would use a VPN
> client in the node, and then connect (free) to an IRLP VPN server and
> get an AMPR.NET 44. IP address from there. No matter what your port
> forwarding says, as long as you can "get out" on the internet, it should
> work.
>
> Dave Cameron
> VE7LTD
>
> On 2019-10-10 10:31, Teton Amateur Radio Repeater Association (TARRA)
> wrote:
> > Hello Group,
> >
> > I tried to SSH into my node this morning and couldn't. Looking at the
> > status page listing it shows that it is up and running and has been
> > running. When I reload the status page it shows a time update. I can
> > log into the remote modem so it would appear that I have an internet
> > connection. I can also connect to the test reflector, but no audio
> > from a test, but I do have the connect and disconnect messages.
> > Finally, I did a reboot of the node and it rebooted. After the reboot,
> > the same situation. I'm guessing that with it being a Pi node, it is
> > probably a corrupted SD card. Any thoughts other than get away from
> > the Pi? I do not have access to the site, so I can't get there.
> >
> > Thinking about the above situation and lately working with a VPN/VPS,
> > it has me wondering if some of the computer load and operations could
> > be moved to a VPS? Lighten the load on the local computer as well as
> > my (cellular) internet connection. Just wondering . . .
> >
> > Mick - W7CAT
> > Node 3464
> > --
> > Untitled Document
> >
> >
> >
> > Links:
> > ------
> > [1] https://irlp.groups.io/g/IRLP/message/76146
> > [2] https://groups.io/mt/34477678/500965
> > [3] https://irlp.groups.io/g/IRLP/post
> > [4] https://irlp.groups.io/g/IRLP/editsub/500965
> > [5] https://irlp.groups.io/g/IRLP/leave/defanged
>
>
>
>
>
--


Re: Interesting Node Problem

k9dc
 

Your current setup is lightest possible load on the node. Static Public IP from your cellco, no magical stuff happening to make it work. Anything involving a VPN will increase CPU load due to the required encryption open the VPN tunnel.

-k9dc

On Oct 10, 2019, at 13:31, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:

Thinking about the above situation and lately working with a VPN/VPS, it has me wondering if some of the computer load and operations could be moved to a VPS? Lighten the load on the local computer as well as my (cellular) internet connection. Just wondering . . .

Mick - W7CAT
Node 3464


Re: Interesting Node Problem

k9dc
 

Was it running on a VPN previously? When it was last heard from, it was coming from 166.140.234.202 which is a Verizon Wireless IP. Probably a static assignment.

If you can connect anywhere (whether it works or not) your SD card is fine, obviously the node is working, or it would not respond to dtmf. Does it show up as an active client in your router? I assume you can normally access your router.

-k9dc

On Oct 10, 2019, at 13:31, Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:

Hello Group,

I tried to SSH into my node this morning and couldn't. Looking at the status page listing it shows that it is up and running and has been running. When I reload the status page it shows a time update. I can log into the remote modem so it would appear that I have an internet connection. I can also connect to the test reflector, but no audio from a test, but I do have the connect and disconnect messages. Finally, I did a reboot of the node and it rebooted. After the reboot, the same situation. I'm guessing that with it being a Pi node, it is probably a corrupted SD card. Any thoughts other than get away from the Pi? I do not have access to the site, so I can't get there.

Thinking about the above situation and lately working with a VPN/VPS, it has me wondering if some of the computer load and operations could be moved to a VPS? Lighten the load on the local computer as well as my (cellular) internet connection. Just wondering . . .

Mick - W7CAT
Node 3464


Re: Interesting Node Problem

David Cameron - IRLP
 

I concur with BOTH of these below. I would actually put "power" first. It is usually a bad power bump that takes out the SD card.

I started using SanDisk Ultra, and now Sandisk EDGE micro SD cards. They are far and above better than any others I have used in the past. I get very few reports of these cards going bad, and I have three of them running for over 4 years now.

Dave Cameron

On 2019-10-10 10:55, Jim MacKenzie wrote:
If it is indeed an SD-card-related issue, the best solutions seem to
be:
- Use a better-quality SD card. Most of my problems have
gone away by doing this.
- Upgrade the power supply to provide more amperage.
73
Jim VE5EV


Re: Interesting Node Problem

David Cameron - IRLP
 

Mick,

I am going to wager a guess that the device that assigns IPs to the Pi node on the mountain has reset, and any specific port forwarding that might be set up.

If the IP of the node behind the router changes, then it breaks any forwarding. BUT, if you are seeing a valid time stamp from the status page, then the node is still there and running. I just checked yours though, and it is showing the last valid timestamp as "Last heard from Node: 18:22:09 on Oct 09 2019 MDT". That was quite a while ago.

If that is BEFORE you started having issues, then I agree the node is probably not responding. Could be a variety of reasons, but SD card is a good place to check first.

You can't offload the bandwidth to a VPS... You still need to talk into and out of the node. To be honest, adding a VPN or some other "go between" will only increase the bandwidth use, not reduce it. However, this may allow you to run on a cheaper Cellular option, as you will not need a routable IP address to the cellular modem. You would use a VPN client in the node, and then connect (free) to an IRLP VPN server and get an AMPR.NET 44. IP address from there. No matter what your port forwarding says, as long as you can "get out" on the internet, it should work.

Dave Cameron
VE7LTD

On 2019-10-10 10:31, Teton Amateur Radio Repeater Association (TARRA) wrote:
Hello Group,
I tried to SSH into my node this morning and couldn't. Looking at the
status page listing it shows that it is up and running and has been
running. When I reload the status page it shows a time update. I can
log into the remote modem so it would appear that I have an internet
connection. I can also connect to the test reflector, but no audio
from a test, but I do have the connect and disconnect messages.
Finally, I did a reboot of the node and it rebooted. After the reboot,
the same situation. I'm guessing that with it being a Pi node, it is
probably a corrupted SD card. Any thoughts other than get away from
the Pi? I do not have access to the site, so I can't get there.
Thinking about the above situation and lately working with a VPN/VPS,
it has me wondering if some of the computer load and operations could
be moved to a VPS? Lighten the load on the local computer as well as
my (cellular) internet connection. Just wondering . . .
Mick - W7CAT
Node 3464
--
Untitled Document
Links:
------
[1] https://irlp.groups.io/g/IRLP/message/76146
[2] https://groups.io/mt/34477678/500965
[3] https://irlp.groups.io/g/IRLP/post
[4] https://irlp.groups.io/g/IRLP/editsub/500965
[5] https://irlp.groups.io/g/IRLP/leave/defanged


Re: Interesting Node Problem

Jim MacKenzie
 

If it is indeed an SD-card-related issue, the best solutions seem to be:

-          Use a better-quality SD card.  Most of my problems have gone away by doing this.

-          Upgrade the power supply to provide more amperage.

 

73

Jim VE5EV

 

From: IRLP@irlp.groups.io [mailto:IRLP@irlp.groups.io] On Behalf Of Teton Amateur Radio Repeater Association (TARRA)
Sent: Thursday, October 10, 2019 11:31 AM
To: IRLP@irlp.groups.io
Subject: [IRLP] Interesting Node Problem

 

Hello Group,

I tried to SSH into my node this morning and couldn't. Looking at the status page listing it shows that it is up and running and has been running. When I reload the status page it shows a time update. I can log into the remote modem so it would appear that I have an internet connection. I can also connect to the test reflector, but no audio from a test, but I do have the connect and disconnect messages. Finally, I did a reboot of the node and it rebooted. After the reboot, the same situation. I'm guessing that with it being a Pi node, it is probably a corrupted SD card. Any thoughts other than get away from the Pi? I do not have access to the site, so I can't get there.

Thinking about the above situation and lately working with a VPN/VPS, it has me wondering if some of the computer load and operations could be moved to a VPS? Lighten the load on the local computer as well as my (cellular) internet connection. Just wondering . . .

Mick - W7CAT
Node 3464

--


Interesting Node Problem

Teton Amateur Radio Repeater Association (TARRA)
 

Hello Group,

I tried to SSH into my node this morning and couldn't. Looking at the status page listing it shows that it is up and running and has been running. When I reload the status page it shows a time update. I can log into the remote modem so it would appear that I have an internet connection. I can also connect to the test reflector, but no audio from a test, but I do have the connect and disconnect messages. Finally, I did a reboot of the node and it rebooted. After the reboot, the same situation. I'm guessing that with it being a Pi node, it is probably a corrupted SD card. Any thoughts other than get away from the Pi? I do not have access to the site, so I can't get there.

Thinking about the above situation and lately working with a VPN/VPS, it has me wondering if some of the computer load and operations could be moved to a VPS? Lighten the load on the local computer as well as my (cellular) internet connection. Just wondering . . .

Mick - W7CAT
Node 3464

--


Re: Irlp Custom connect wav files

k9dc
 

That is correct. Most node numbers in .US have been used before, so there is a very good chance you may end up with someone else's old files even if you get a new number assignment. That is why the After-Install instructions call for everyone to make up a new set of files for their own node.

-k9dc

On Oct 10, 2019, at 04:19, larry_n7fm <larry@...> wrote:

Thanks Dale,

You are correct. Just not what the new owner wants but may have to live with. Either that or do a rebuild with a new node number.

Make me curious how they dealt with the reclaimed node numbers that had custom connect files that propagated previously. Maybe some fellow in Canada was issued a reclaimed node number that has a stnxxxx file that propagated saying he lives in Miami and he doesn't know it.

Larry - N7FM


Re: Irlp Custom connect wav files

dale.tongue
 

Larry,
Well, I ran into that problem myself and just got it fixed. My node WAV file was telling people I was in England instead of Korea. And since I'm moving it to the states soon, I'll have to do it again. Good luck.
Dale

-----Original Message-----
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of larry_n7fm
Sent: Thursday, October 10, 2019 5:19 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Irlp Custom connect wav files

Thanks Dale,

You are correct. Just not what the new owner wants but may have to live with. Either that or do a rebuild with a new node number.

Make me curious how they dealt with the reclaimed node numbers that had custom connect files that propagated previously. Maybe some fellow in Canada was issued a reclaimed node number that has a stnxxxx file that propagated saying he lives in Miami and he doesn't know it.

Larry - N7FM

On 10/9/19 11:31 PM, dale.tongue wrote:
If you create/edit a file for stnXXXXon and stnxxxxoff and do the
upload per the manual, it will take care of it for you if I’m not mistaken.
It’ll wipe your other files and add the new files, which will get
populated through the network..

Dale

http://wiki.irlp.net/doku.php?id=recording_audio_files

*From:*IRLP@irlp.groups.io <IRLP@irlp.groups.io> *On Behalf Of
*larry_n7fm
*Sent:* Thursday, October 10, 2019 2:28 PM
*To:* IRLP@irlp.groups.io
*Subject:* [IRLP] Irlp Custom connect wav files

I recently sold one of my IRLP nodes.
Sadly when I was new to IRLP years ago. I didn't realize that creating
a custom connect wav file would become a problem.

I was foolish enough to created a custom connect wav file which
included my callsign not realizing once it was activated there was no
option to stop or revert back to normal.
Bet most everyone reading this is already thinking "Dummy" and can
visualize my problem.
Yup ... when the new owner I sold the node to.connects ... it
announces/identifies on the other end with my callsign.

I do realize creating a new custom file will replace my problem file.
However the new owner would like the node to revert to original
connect messages.
Which it can't as long as a stnxxxx wave file exists.

Has anyone come up with a way to reverse or stop the custom
stn(node_number) from spreading to other newly connected nodes?
Is it possible for IRLP support to delete custom stnxxxx wav files if
requested?
Once deleted from the IRLP server it would stop any *further*
propagation of that particular custom connect file.

Suggestions or solution? New install with a New number isn't something
he wants or is able to do.

What would really be nice ... is a script mod with an option flag "IF
EXIST delete" when checking for a new stnxxxx files for those of us
who want to revert back.

Larry - N7FM


Re: Irlp Custom connect wav files

John VK4JJW
 

On 10/10/2019 4:31 pm, dale.tongue wrote:
If you create/edit a file for stnXXXXon and stnxxxxoff and do the upload per the manual, it will take care of it for you if I’m not mistaken.  It’ll wipe your other files and add the new files, which will get populated through the network..

Dale
That's the way!

And I'm sure there are any number of us out here that would be happy to record generics for this if you don't feel you can do it yourself.

Even one of the text-to-speech web sites would work OK.

Ask, and you will receive :-)

JW

--

EchoIRLP
IRLP Node 6527
EchoLink Node 96527

DMR 5054314


http://www.vk4jjw.info


Re: WWAN configuration and 4G Dongles on node 6370

Mike Alsop
 

Peter

Interested to know how you actually got 4G to work?? I have tried everything I know under Debian 9, but just can't get past 3G

Mike
VK8MA

On Sat, 2019-10-05 at 09:37 +1000, Peter Chaplin wrote:

Well, I finally have everything working.

Thanks Mike, commenting out the eth0 lines brought the dongle up.

What I found is if I put the wwan0 ahead of the eth0 in the interfaces file, it will try for the wwan0 and if it’s not there, move on to the eth0.

 

The node (6370) is now showing up in the IRLP active node list. – That’s a win.

However, when on the 4G dongle, the node VK3RSR-R wasn’t showing up in EchoLINK.

Swap back to eth0 and VK3RSR-R comes straight up in EchoLINK.

I wouldn’t have thought that how the Pi is getting internet would have mattered.

 

While connected on the 4G dongle, I ran the Troubleshooting script in the node and it passed everything except Test 1 – DNS and Test 10 which it’s not expected to pass with EchoIRLP enabled.

I swapped back to eth0 and re-ran the Troubleshoot, it passed Test 1.

This would suggest there is something stopping the DNS service from running when wwan0 is selected.

This is confirmed by NOT being able to Ping any domain name but being able to Ping the IP address for the domain when connected to wwan0.

I’m able to ping both Domain name and IP address when connected to eth0.

 

During bootup, I see a message “A start job is running for Raise network interfaces”

Then I get a “Failed to start Raise network interfaces” when booting up with wwan0.

 

I tried adding dns-nameservers and the IP addresses of my carriers DNS servers to the /etc/network/interfaces file after the WWAN0 interface, but that didn’t make any difference.

I also enabled static DNS addresses in the dongle with my carriers DNS servers to no avail.

I then tried to Ping my carriers DNS servers and found I could not do so.

I changed the static DNS servers in my dongle to 8.8.8.8 and 8.8.4.4 (Google’s public DNS servers) and hey presto, My node comes up in EchoLINK and works fine.

Doing this doesn’t stop the “Failed to start” message, however, I noticed the Google DNS addresses have been inserted into the resolve.conf file from the 4G dongle’s static DNS or elsewhere.

I then went back and added the Google DNS servers into the /etc/network/interfaces file (dns-nameservers 8.8.8.8 8.8.4.4) for the wwan0 interface and tested it. All worked fine.

So, there must be something in Debian or IRLP scripts that causes the Telstra DNS addresses to be blocked.

 

So, in summary, to get it working all I had to do was add a wwan0 interface into the /etc/network/interfaces file and include a line dns-nameservers 8.8.8.8 8.8.4.4 for the wwan0 interface and place the wwan0 interface ahead of the eth0 interface.

 

Either way, I’ve resolved my problem.

Next, just because I like putting myself through mental pain, I’ll try the same with some other model 4G dongles I have laying around and see if they have the same symptoms.

 

Thanks again to all those that offered tips and hints that led me down the learning path of Unix/Linux/Debian/Raspbian/etc

 

Yours gratefully and 73’s for now,

Peter

VK3AJ

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Mike Alsop
Sent: Friday, 4 October 2019 11:02
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] WWAN configuration and 4G Dongles on node 6370

 

I am pretty sure if you comment out any entries in /etc/network/interfaces relating to eth0 and then reboot, you should be on the dongle.

 

Mike

 

On Thu, 2019-10-03 at 09:00 -0500, k9dc wrote:

IRLP will use whatever interface is chosen by the Linux routing table.  What does the command ‘ip route show' reveal?  
 
-k9dc
 
On Oct 3, 2019, at 07:04, Peter Chaplin <

peter@...

 

> wrote:
 
Thanks to everyone who has provided tips for this.
From these tips, I have been able to get wwan0 showing up when i run ifconfig
This has led to getting the 4G dongle working and showing up an IP address in the netconfig application, but IRLP want's to use eth0 instead of wwan0 as it's interface, which of course eth0 is unplugged.
How do I get the IRLP node to use wwan0 instead of eth0.
I've tried changing the adaptor in /etc/network/interfaces but that doesn't seem to make a difference.