Date   

Re: Login and Password

Dave K9DC
 

There is no node 2266 in the network. If it has been down for more than 90 days (sounds like years in your case), it may have been deleted.

At the very least, you will need to perform a new installation from scratch. Depending on how old it is, that may not be possible without upgrading the hardware. The very first embedded nodes only had 256 MB of flash onboard and actually ran totally from RAM, using a now antique version of Slackware. Newer embedded nodes came with 2 to 8 GB of flash and ran a conventional IRLP installation.

The user ID to log in will be root. But without the password you will not bae able to get in. There a number of methods to perform a password replacement on boot, but you will need to know what OS is on board to perform a search for the procedure. What does it say on the local console after it boots?

Your best bet may be to reach out (email) to installs@ irlp.net and ask for assistance, DaveC monitors installs email, and he may be able to help you figure out exactly what you have.

-k9dc

On May 23, 2020, at 11:46, Michael Dougherty <m.dougherty@videotron.ca> wrote:

Hello,

I am new to IRLP. A few years ago I purchased a used working imbedded node from a licensed amateur. I had to delay my amateur radio project for health issues. Now that I am back I would like to get my node working. I tried to re-program the node (it will boot) however I cannot login as I do not have the login and password codes. I tried to contact the previous owner and amateur who programmed the node without in success. They may have moved or passed away let alone remember the login and password. When I purchased the node there was a 13 page manual written by Dave VE7LTD with no mention of the login user ID and password.

Any suggestions as to reset the user ID login and password or will I have to re-install the software.

Thank you for any suggestions.

Michael Dougherty
VE2DPD
Node 2266


Re: Login and Password

Rick Szajkowski
 

There is a way to enter  new password I am sure some one will chime up

What OS are you useing ? 

Username will either be root or repeater 



Richard Szajkowski 
VA3 RZS VA3ZJ VE3BTE

On May 23, 2020, at 12:56 PM, John Lorenc <va3xjl@...> wrote:

Hi

I suggest your best course of action is to reinstall the node. The PGP keys will be needed and given you are not likely to have a backup, they may need to be reissued. Suggest reaching out to installs@... for assistance.

John va3wm
IRLP 2931, 2248



On May 23, 2020, at 12:40 PM, Michael Dougherty <m.dougherty@...> wrote:



Hello,

 

I am new to IRLP. A few years ago I purchased a used working imbedded node from a licensed amateur. I had to delay my amateur radio project for health issues. Now that I am back I would like to get my node working. I tried to re-program the node (it will boot)  however I cannot login as I do not have the login and password codes. I tried to contact the previous owner and amateur who programmed the node without in success. They may have moved or passed away let alone remember the login and password. When I purchased the node there was a 13 page manual written by Dave VE7LTD with no mention of the login user ID and password.

 

Any suggestions as to reset the user ID login and password or will I have to re-install the software.

 

Thank you for any suggestions.

 

Michael Dougherty

VE2DPD

Node 2266


Re: Login and Password

John Lorenc
 

Hi

I suggest your best course of action is to reinstall the node. The PGP keys will be needed and given you are not likely to have a backup, they may need to be reissued. Suggest reaching out to installs@... for assistance.

John va3wm
IRLP 2931, 2248



On May 23, 2020, at 12:40 PM, Michael Dougherty <m.dougherty@...> wrote:



Hello,

 

I am new to IRLP. A few years ago I purchased a used working imbedded node from a licensed amateur. I had to delay my amateur radio project for health issues. Now that I am back I would like to get my node working. I tried to re-program the node (it will boot)  however I cannot login as I do not have the login and password codes. I tried to contact the previous owner and amateur who programmed the node without in success. They may have moved or passed away let alone remember the login and password. When I purchased the node there was a 13 page manual written by Dave VE7LTD with no mention of the login user ID and password.

 

Any suggestions as to reset the user ID login and password or will I have to re-install the software.

 

Thank you for any suggestions.

 

Michael Dougherty

VE2DPD

Node 2266


Login and Password

Michael Dougherty
 

Hello,

 

I am new to IRLP. A few years ago I purchased a used working imbedded node from a licensed amateur. I had to delay my amateur radio project for health issues. Now that I am back I would like to get my node working. I tried to re-program the node (it will boot)  however I cannot login as I do not have the login and password codes. I tried to contact the previous owner and amateur who programmed the node without in success. They may have moved or passed away let alone remember the login and password. When I purchased the node there was a 13 page manual written by Dave VE7LTD with no mention of the login user ID and password.

 

Any suggestions as to reset the user ID login and password or will I have to re-install the software.

 

Thank you for any suggestions.

 

Michael Dougherty

VE2DPD

Node 2266


Re: Log time

David Cameron - IRLP
 

You need to set the timezone correctly. Since your system is running Debian, the proper command is:

dpkg-reconfigure tzdata

On IRLP nodes, usually there is a script timeconfig that is linked to that same feature.

Dave Cameron

On 2020-05-21 9:32 a.m., G4CJC wrote:
For whatever reason I just noticed my log times are BST (daylight saving for UK). IRLPvCon reports correctly what UTC time is and what local time is but all the log files are shown in local (BST) time. Not a big deal but I'd like them all to be in UTC. This node is a RaspberryPi. How can I do this?
Tony G4CJC
Node 5600


Log time

Tony Dixon G4CJC
 

For whatever reason I just noticed my log times are BST (daylight saving for UK). IRLPvCon reports correctly what UTC time is and what local time is but all the log files are shown in local (BST) time. Not a big deal but I'd like them all to be in UTC. This node is a RaspberryPi. How can I do this?
Tony G4CJC
Node 5600


Re: node 7401 Problems

James Hertel
 

If not on IRLPVPN service, Do go that route, It solved all of my modem issues... which what it sounds like your issue.. Thank you Dave K9dc and David Cameron..

N6kmr Jim 7966 & 3832

On 5/19/2020 6:51 PM, k9dc wrote:

What is troubleshoot-irlp telling you?  Do all the test pass ok?  See http://www.irlp.net/ts.html

-k9dc


On May 19, 2020, at 20:16, N7SWW@... wrote:

Hi not sure why my node is not working on audio In running ft-8800 or FTM-100 analog I have tried using F5 on Capture doesn't work he cord ohms out just fine so you didnt change wires so must be software. Any help please..




Re: node 7401 Problems

Dave K9DC
 


What is troubleshoot-irlp telling you?  Do all the test pass ok?  See http://www.irlp.net/ts.html

-k9dc


On May 19, 2020, at 20:16, N7SWW@... wrote:

Hi not sure why my node is not working on audio In running ft-8800 or FTM-100 analog I have tried using F5 on Capture doesn't work he cord ohms out just fine so you didnt change wires so must be software. Any help please..



_._,_._,_


node 7401 Problems

N7SWW@...
 

Hi not sure why my node is not working on audio In running ft-8800 or FTM-100 analog I have tried using F5 on Capture doesn't work he cord ohms out just fine so you didnt change wires so must be software. Any help please..


Re: Garbled voice and missing DTMF

Leslie Meade
 

Morning Fred,

 

Many thanks on pointing me in the right way 😊

 

  1. This is on a PC
  2. The radio that I am using is a Tait TM8110
  3. I am very new to this radio and I have not looked ( to be honest do not know where to look)
  4. My call sign is vk4les and the node is stn6064

 

Leslie

 

 

From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of Fred via groups.io
Sent: Saturday, May 16, 2020 11:17 PM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Garbled voice and missing DTMF

 

Leslie, 

 

Are you installing this on a pi or other computer?

 

What type of node radio are you using?

 

Have you checked your audio settings?

 

What’s your callsign and node number?

 

It’s very possible that your audio settings are off is what may be causing this.    Anyone trying to help you on this forum will need a little more info than what you put in your email, which is why I asked you these questions.   

 

Fred

W5MGM

Node 7845 plus 4 other nodes.

 

From: Leslie Meade
Sent: Saturday, May 16, 2020 2:10 AM
To: IRLP@irlp.groups.io
Subject: [IRLP] Garbled voice and missing DTMF

 

I obtained a card and cable installed the IRLP software and going through the steps on configuration.
I have a few issues that I am not sure on.  running Debian 10 with latest updates..

1. I seem not able to send DTMF to the platform? I see the DTMF light board light up when i enter DMTF on the handheld, but do not hear the far end node respond.
2. If i run this command

repeater@stn6064:~/scripts$ $SCRIPT/decode 1147

I hear the node respond but it is garbled to the point i can not understand that is being said. ( i do know what it is saying used it before building my node)

I am thinking it could be the cable? Any ideas of where i should be looking at?
Talking from the IRLP radio to other handsets give clear voice.


Leslie

 

 


Re: Debian upgrade breaks IRLP?

James <james@...>
 

Oh I'm sorry.  Was there some advice on steps to take with my node that I missed?

I didn't recall getting any - I will go back through the online archives to see if there was mail I didn't get.


Thanks for all the help guys!


73,


James

KL2ZZ

On 5/15/20 6:10 PM, k9dc wrote:
In that case, suit yourself. It’s a waste of time, but then, what do I know. Good luck
-k9dc


Re: Garbled voice and missing DTMF

Fred
 

Leslie, 

 

Are you installing this on a pi or other computer?

 

What type of node radio are you using?

 

Have you checked your audio settings?

 

What’s your callsign and node number?

 

It’s very possible that your audio settings are off is what may be causing this.    Anyone trying to help you on this forum will need a little more info than what you put in your email, which is why I asked you these questions.   

 

Fred

W5MGM

Node 7845 plus 4 other nodes.

 

From: Leslie Meade
Sent: Saturday, May 16, 2020 2:10 AM
To: IRLP@irlp.groups.io
Subject: [IRLP] Garbled voice and missing DTMF

 

I obtained a card and cable installed the IRLP software and going through the steps on configuration.
I have a few issues that I am not sure on.  running Debian 10 with latest updates..

1. I seem not able to send DTMF to the platform? I see the DTMF light board light up when i enter DMTF on the handheld, but do not hear the far end node respond.
2. If i run this command

repeater@stn6064:~/scripts$ $SCRIPT/decode 1147

I hear the node respond but it is garbled to the point i can not understand that is being said. ( i do know what it is saying used it before building my node)

I am thinking it could be the cable? Any ideas of where i should be looking at?
Talking from the IRLP radio to other handsets give clear voice.


Leslie

 

 


Garbled voice and missing DTMF

Leslie Meade
 

I obtained a card and cable installed the IRLP software and going through the steps on configuration.
I have a few issues that I am not sure on.  running Debian 10 with latest updates..

1. I seem not able to send DTMF to the platform? I see the DTMF light board light up when i enter DMTF on the handheld, but do not hear the far end node respond.
2. If i run this command

repeater@stn6064:~/scripts$ $SCRIPT/decode 1147

I hear the node respond but it is garbled to the point i can not understand that is being said. ( i do know what it is saying used it before building my node)

I am thinking it could be the cable? Any ideas of where i should be looking at?
Talking from the IRLP radio to other handsets give clear voice.


Leslie

 


Re: Debian upgrade breaks IRLP?

Dave K9DC
 

In that case, suit yourself. It’s a waste of time, but then, what do I know. Good luck
-k9dc

On May 15, 2020, at 21:34, James <james@zuelow.net> wrote:

Oh I'm too lazy to tcpdump or even wireshark. I used to use tools like that but I over the years I find I rarely need to actually look at a packet. I am usually more interested in where a packet is going and why. I find I can get almost all of the information I need just by something like:

iptables -A INPUT -i eth0 -j LOG --log-prefix "IRLP: " (This one is a shotgun, it will log every packet arriving at eth0.)

Then I follow up with a tail -f /var/log/syslog | grep IRLP | grep -v ip.address.of.my.ssh.client | (other greps and awks as appropriate)

When I say I can see packets, I see them in real time as they get logged. Two terminals is great - one to run the script, one to watch the packets as they arrive.

If I need to go back and look at the logs, they're still there until logrotate clears them out.


Two mysteries:


1) why can I play local WAVs, but I can't hear IRLP audio?

2) why can I see the node computer send and receive traffic when I do the test, but not when I connect to an actual node?


This is why I'm about ready to wipe the disk, install new, and restore settings from backup. There is something seriously wrong with the node computer and it is acting inconsistently.


On 5/15/20 11:44 AM, k9dc wrote:
Yes the new router NAT appears to be working now. I see my IP anyway. I do not understand how you are using iptables to check for traffic though. I would use a tool more like tcpdump (CLI version of wireshark).

Did you try the echo reflector (9990-9999) ?

-k9dc


Re: Debian upgrade breaks IRLP?

James <james@...>
 

Oh I'm too lazy to tcpdump or even wireshark.  I used to use tools like that but I over the years I find I rarely need to actually look at a packet.  I am usually more interested in where a packet is going and why.  I find I can get almost all of the information I need just by something like:

iptables -A INPUT -i eth0 -j LOG --log-prefix "IRLP: "  (This one is a shotgun, it will log every packet arriving at eth0.)

Then I follow up with a tail -f /var/log/syslog | grep IRLP | grep -v ip.address.of.my.ssh.client | (other greps and awks as appropriate)

When I say I can see packets, I see them in real time as they get logged.  Two terminals is great - one to run the script, one to watch the packets as they arrive.

If I need to go back and look at the logs, they're still there until logrotate clears them out.


Two mysteries:


1) why can I play local WAVs, but I can't hear IRLP audio?

2) why can I see the node computer send and receive traffic when I do the test, but not when I connect to an actual node?


This is why I'm about ready to wipe the disk, install new, and restore settings from backup.  There is something seriously wrong with the node computer and it is acting inconsistently.

On 5/15/20 11:44 AM, k9dc wrote:
Yes the new router NAT appears to be working now. I see my IP anyway. I do not understand how you are using iptables to check for traffic though. I would use a tool more like tcpdump (CLI version of wireshark).

Did you try the echo reflector (9990-9999) ?

-k9dc


Re: Debian upgrade breaks IRLP?

Dave K9DC
 

Yes the new router NAT appears to be working now. I see my IP anyway. I do not understand how you are using iptables to check for traffic though. I would use a tool more like tcpdump (CLI version of wireshark).

Did you try the echo reflector (9990-9999) ?

-k9dc

On May 15, 2020, at 14:04, James <james@zuelow.net> wrote:

You should be able to telnet to TCP 15425 and get your correct external IP in the response header. Hopefully we can rule out the router at this point.


I'm back to my original question:

* scripts/troubleshoot-irlp runs successfully. (See below)

* scripts/audio_level_test runs successfully, so I believe I have the right microphone selected in the sound system, and audio from the Kenwood is reaching the node computer.

* I can hear the local files (connected to, or files I play with key/unkey) so I know that the node is sending audio out to the Kenwood.


But if I connect to a reflector, there is no audio. Further, I can watch network traffic with iptables and there are no UDP packets arriving at the node. (But I can see the UDP packets arriving when I run the troubleshoot-irlp script.) There are some TCP packets coming in when I connect/disconnect. And the IRLP status page reflects these changes immediately, so I assume that's part of the traffic.

So it is like the node says it is connecting, but is not actually connecting.


Thanks!

James
KL2ZZ


Re: Debian upgrade breaks IRLP?

James <james@...>
 

You should be able to telnet to TCP 15425 and get your correct external IP in the response header.  Hopefully we can rule out the router at this point.


I'm back to my original question:

* scripts/troubleshoot-irlp runs successfully.  (See below)

* scripts/audio_level_test runs successfully, so I believe I have the right microphone selected in the sound system, and audio from the Kenwood is reaching the node computer.

* I can hear the local files (connected to, or files I play with key/unkey) so I know that the node is sending audio out to the Kenwood.


But if I connect to a reflector, there is no audio.  Further, I can watch network traffic with iptables and there are no UDP packets arriving at the node.  (But I can see the UDP packets arriving when I run the troubleshoot-irlp script.)  There are some TCP packets coming in when I connect/disconnect.  And the IRLP status page reflects these changes immediately, so I assume that's part of the traffic.

So it is like the node says it is connecting, but is not actually connecting.


Thanks!

James
KL2ZZ


-----


**********************************
*TCP and UDP Port Forwarding Test*
**********************************

Performing INBOUND UDP and TCP Port Forwarding Test
Detecting Incoming IP = 24.237.7.242
Testing TCP and UDP ports .. done.

-----------------------------------------------------------------------------
TEST No. 2a REPORT - TCP PASS - TCP port 15425 is forwarded correctly.
Waiting 4 seconds .... done.
TEST No. 2b REPORT - UDP PASS - UDP ports 2074-2093 are forwarded correctly.
TEST No. 2c REPORT - EchoLink UDP ERROR - The following UDP port(s):
 5198  5199  is/are not forwarded correctly.
-----------------------------------------------------------------------------

Performing OUTBOUND Port Test
Testing OUTBOUND TCP and UDP ports ........................... done.

------------------------------------------------------------------------------
TEST No. 3 REPORT - PASS - All the ports are working OUTBOUND correctly
------------------------------------------------------------------------------

Press ENTER to continue :

On 5/14/20 9:01 PM, James wrote:
OK. I'll install a new router.  I'm pretty sure I have an old Linksys around with commercial firmware in it.

Amazing coincidence that the upgrade and router malfunction occurred at the same time.  That's puzzling to me.  But if it's the router, it's the router.


On 5/14/20 8:30 PM, David Cameron - IRLP wrote:
Your router is acting as some sort of proxy.

Rebuilding won't change this.

Dave


Re: Debian upgrade breaks IRLP?

James <james@...>
 

OK.  I'll install a new router.  I'm pretty sure I have an old Linksys around with commercial firmware in it.

Amazing coincidence that the upgrade and router malfunction occurred at the same time.  That's puzzling to me.  But if it's the router, it's the router.

On 5/14/20 8:30 PM, David Cameron - IRLP wrote:
Your router is acting as some sort of proxy.

Rebuilding won't change this.

Dave


Re: Debian upgrade breaks IRLP?

David Cameron - IRLP
 

Your router is acting as some sort of proxy. 

Rebuilding won't change this. 

Dave

-------- Original message --------
From: k9dc <Dave@...>
Date: 5/14/20 9:16 PM (GMT-08:00)
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] Debian upgrade breaks IRLP?


Your router needs to NAT outbound to your public IP 24.237.7.242.  But it should leave inbound connections alone and not NAT to your router address of 192.168.2.1. That appears to be what it is doing.  Sorry I do not use OpenWRT here, so I cannot help much beyond that.

Using IRLP VPN would also probably fix it, but that should not be necessary. As DaveC said, nothing about upgrading Debian would affect your routing.

-k9dc


> On May 15, 2020, at 00:03, James <james@...> wrote:
>
> 192.168.2.1 is the OpenWRT router.
>
> 192.168.2.10 is the node.
>
>
> I tried turning off NAT on the OpenWRT router, and internet doesn't work at all.  So I think it is designed to do that.
>
> I did the telnet test, and I get reliable 2-way communication. (Well, sort of.  I don't know how to interact beyond prompting the node to challenge me and then disconnect.)
>
> And as I mentioned, the troubleshoot_irlp script reports success. It says that inbound TCP and UDP are good.
>
>
> I'm not sure the NAT issue would have come up at exactly the same time as the node was updated.  Perhaps I'll download the IRLP Debian 10 image and start over, but it is frustrating as everything seems to work.
>
>
> On 5/14/20 7:38 PM, David Cameron - IRLP wrote:
>> What is the IP of the node behind the router? What is 192.168.2.1?
>>
>> Dave Cameron
>>
>>






Re: Debian upgrade breaks IRLP?

Dave K9DC
 

Your router needs to NAT outbound to your public IP 24.237.7.242. But it should leave inbound connections alone and not NAT to your router address of 192.168.2.1. That appears to be what it is doing. Sorry I do not use OpenWRT here, so I cannot help much beyond that.

Using IRLP VPN would also probably fix it, but that should not be necessary. As DaveC said, nothing about upgrading Debian would affect your routing.

-k9dc

On May 15, 2020, at 00:03, James <james@zuelow.net> wrote:

192.168.2.1 is the OpenWRT router.

192.168.2.10 is the node.


I tried turning off NAT on the OpenWRT router, and internet doesn't work at all. So I think it is designed to do that.

I did the telnet test, and I get reliable 2-way communication. (Well, sort of. I don't know how to interact beyond prompting the node to challenge me and then disconnect.)

And as I mentioned, the troubleshoot_irlp script reports success. It says that inbound TCP and UDP are good.


I'm not sure the NAT issue would have come up at exactly the same time as the node was updated. Perhaps I'll download the IRLP Debian 10 image and start over, but it is frustrating as everything seems to work.


On 5/14/20 7:38 PM, David Cameron - IRLP wrote:
What is the IP of the node behind the router? What is 192.168.2.1?

Dave Cameron

1221 - 1240 of 78395