|
Re: IP Address
Rick Szajkowski
Thanks so much Dave !
toggle quoted messageShow quoted text
This helps a lot , again thank you Richard Szajkowski VA3 RZS VA3ZJ VE3BTE
On Jun 15, 2020, at 8:15 PM, David Cameron - IRLP <dcameron@...> wrote:
|
|
|
|
Re: Up address
David Cameron - IRLP
The IP will always have the hostname: stn2120.ip.irlp.net
toggle quoted messageShow quoted text
dcameron@irlp:~$ host stn2120.ip.irlp.net stn2120.ip.irlp.net has address 24.138.163.221 Dave Cameorn
On 15/06/2020 5:12 p.m., Rick Szajkowski wrote:
Trying to find the IP address of my node
|
|
|
|
Up address
Rick Szajkowski
Trying to find the IP address of my node
I am away from the system and would like to know the static public up address of my node Node 2120 Thanks Richard Szajkowski VA3 RZS VA3ZJ VE3BTE_
|
|
|
|
Re: Host name of node not correct number and outgoing audio fails.
Perhaps the also active stn3249 (correct node#) and 3248 is causing a network error at the DNS level? That's a weird one anyway and they're not too far
away from each other. 73,
On 6/15/2020 1:36 PM, k9dc wrote:
To close this out (in case someone else has a similar problem). This turned out to be a typo in the file /etc/hostname which sets the hostname of the machine at boot up. That file was incorrectly set to stn3249 instead of stn3248. Not exactly sure why, but correcting that minor error, fixed everything. -k9dcOn Jun 15, 2020, at 11:50, k9dc <dave@...> wrote:On Jun 15, 2020, at 11:23, Bob Sampson <k6mby@...> wrote: Good day, At some point and in an unknown way the host name of node 3248 has been changed to 3249. Troubleshoot-IRLP runs without errors. Node 3248, however, has a one way audio issue that I have been unable to sort out. I am wondering if the audio issue is being caused by the host name being wrong and how might I go about correcting the name. I have tried correcting the node name in the hosts file but then Troubleshoot_IRLP fails the PGP test.
|
|
|
|
Re: Host name of node not correct number and outgoing audio fails.
k9dc
To close this out (in case someone else has a similar problem).
toggle quoted messageShow quoted text
This turned out to be a typo in the file /etc/hostname which sets the hostname of the machine at boot up. That file was incorrectly set to stn3249 instead of stn3248. Not exactly sure why, but correcting that minor error, fixed everything. -k9dc
On Jun 15, 2020, at 11:50, k9dc <dave@...> wrote:On Jun 15, 2020, at 11:23, Bob Sampson <@k6mby> wrote:
|
|
|
|
Re: Host Refleector
David Cameron - IRLP
IRLP nodes set the RTP NAME and ID in calls to refectors and experimental nodes:
toggle quoted messageShow quoted text
# Modification for integrated reflector - VK3JED March 29 2005. # Set Environment Variables for Speak Freely # NOTE: $REFLECT_PASSWORD currently not used. Reserved for future use export SPEAKFREE_CNAME="${CALLSIGN}" export SPEAKFREE_ID="${CONVERTED_STATIONID} IRLP"::"${REFLECT_PASSWORD}" These show up in the "active_ips" file of IRLP reflectors and somehow in the TLB and TBD programs. You can also use monitors to see what IPs connect. You could do a blanket allow to allow all IRLP IPs by default, or choose what to do as each system connects. Dave Cameron VE7LTD
On 2020-06-14 10:46 p.m., Tony Langdon wrote:
On 13/06/20 13:00, Nosey Nick VA3NNW wrote:k9dc wrote:For all intents and purposes, yes. And yes, the default port (2074) isExperimental nodes/reflector (same thing) are not really part of the IRLP network per se. We simply offer a number, mapped to a specific public IP address or name. There are no keys issued and no security at all. [...]Oooooooooh, I see, it's essentially "just" a regular SpeakFreely host
|
|
|
|
Re: Host name of node not correct number and outgoing audio fails.
k9dc.
Both incoming and outgoing ports test OK using Troubleshoot-IRLP. I did fix an echolink port (5999) that tested bad. Router port configured wrong. I will drop a note to installs. Thanks, Bob K6MBY Sequim, WA
|
|
|
|
Re: Host name of node not correct number and outgoing audio fails.
k9dc
The actual hostname is set with the ‘hostname’ command, and has nothing to do with the hosts file. The IP address of stn3248 = 172.92.92.156, but there appears to be no port forwarding established. Did ’troubleshoot-irlp’ indicate any other problems? (I am expecting the incoming ports to fail). This is fixed by configuring your ROUTER, not the IRLP node itself.
toggle quoted messageShow quoted text
The node number is set in the environment file, and must be consistent with the PGP key, otherwise the PGP test will fail, but again this is not based upon anything in the hosts file. So I agree, something is very wonky with your set up. If you would like someone to log in and take a look at it for you, send a request describing your problem to installs@ irlp.net. -k9dc
On Jun 15, 2020, at 11:23, Bob Sampson <@k6mby> wrote:
|
|
|
|
Host name of node not correct number and outgoing audio fails.
Good day,
At some point and in an unknown way the host name of node 3248 has been changed to 3249. Troubleshoot-IRLP runs without errors. Node 3248, however, has a one way audio issue that I have been unable to sort out. I am wondering if the audio issue is being caused by the host name being wrong and how might I go about correcting the name. I have tried correcting the node name in the hosts file but then Troubleshoot_IRLP fails the PGP test. The audio issue shows up when using the command line "audio_level_test"... The voice response is "clipping zero, audio level zero." I have swapped the Pi, the IRLP board, and the sound card trying to fix the audio issue. Testing using 9990.... connects to the reflector but gives no response back. Any thoughts? Bob K6MBY Sequim, WA Node 3248
|
|
|
|
Re: Host Refleector
On 13/06/20 13:00, Nosey Nick VA3NNW wrote:
k9dc wrote:For all intents and purposes, yes. And yes, the default port (2074) isExperimental nodes/reflector (same thing) are not really part of the IRLP network per se. We simply offer a number, mapped to a specific public IP address or name. There are no keys issued and no security at all. [...]Oooooooooh, I see, it's essentially "just" a regular SpeakFreely host used. IRLP nodes should set the Speak Freely variables when they make the connection. If your experimental reflector runs tbd or tlb, the IRLP nodes will be listed as "stnXXXX" (XXXX being the node number). Other stations (and nodes which aren't setting the variables correctly) will appear as their IP address. I can't comment on how sfreflect sees connections to it from IRLP nodes. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Networking failing using openvpn
On 11/06/20 07:58, David McAnally
wrote:
Thanks David. I thought there was a GitHub out there somewhere, saves me creating one. :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Networking failing using openvpn
On 11/06/20 04:07, David Cameron - IRLP wrote:
Klaus,Thanks Dave, I've got a copy, will have a look. There's a couple of us talking about some updates. I'm not yet in a position to take this on, but I will take a look. First step might be making a GitHub repository (if there isn't already one) then learning how to use it. :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Networking failing using openvpn
On 11/06/20 03:01, David Cameron - IRLP wrote:
To me it is a bit of a "hang"... The VPN drops, but the gateway is notYes, older versions of OpenVPN do seem to get into a state where the tunnel appears to be "up", but it can't pass traffic. I have an old OpenVPN router here, and I manage this with a cron job that runs ever minute. First it checks for connectivity using ping. If connectivity fails, then it kills the active OpenVPN process, waits 30 seconds and restarts OpenVPN. As a result, I've had a reliable tunnel for years. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Experimental nodes
On 09/06/20 09:58, Craig - K1BDX - Node 8724 wrote:
Tony, yes, thanks for pointing that out.I'm happy to help. As a first installment, there's a few things to get you started. To use tlb or tbd as a reflector, the first thing you need to do is enable the Speak Freely protocol. This is the protocol that IRLP audio uses. You do this with: SF_Enable = 1 In addition, I would also set these to the following values: SF_Port = 2074 SF_ReplyPort = 2074 If your server has multiple IP addresses, you should set SFBind2IP = <IP of experimental reflector> If the latter is not set, and the reflector is running on an alias IP, it may reply using the main IP of the interface, which will cause the security mechanisms on the IRLP node to reject the packets. Binding the specific IP ensures that the replies are sent with the correct IP. If you're planning on setting up a conventional style of reflector, you need to tell tbd/tlb what codec the reflector will use, which is done with the CompressionType directive. Here are the possible values CompressionType = 0 #UNCOMP CompressionType = 3 #GSM CompressionType = 5 #ADPCM However, for transcoding, full duplexx reflectors, you have to use tlb, and things are done very differently. You actually disable the standard conference facilities with ConfEnable = 0 And you don't need to bother with CompressionType, because the packet conference is disabled anyway. Instead, the conferencing is handled using the port linking facilities - the same features used to link radio ports. This requires an EventScript that looks for stations that have connected, then connects the new station to all existing ports using the "link" command. On the integrated reflectors, this is done using a pair of scripts. The first is called "linkports" and has the following code. #!/bin/bash if ! [ "$PORT" = "" ]; then ARGS="-p$PORT" ; fi export ARGS "$TBDCMD" $ARGS ..port | xargs -r -l1 "$SCRIPT"/addlink The other script is called "addlink" #!/bin/bash PORTNAME=$1 if [ "$1" = "0" ];then exit 0 ; fi if [ "$1" = "tbdcmd" ];then exit 0 ; fi if [ "$1" = "Available" ];then exit 0 ; fi if [ "$1" = "$NEWCALL" ];then exit 0 ; fi #echo "linking $NEWCALL to $1" >> ./link.log $TBDCMD $ARGS ..link $NEWCALL $1 These scripts were written to run in a specific environment, but the explanation of the extra variables is as follows: $SCRIPT is where you keep your scripts to run the system. $TBDCMD is the path to tlbcmd, usually /usr/local/bin/tlbcmd $PORT is the CmdPort from the configuration file. For most purposes, it can be statically defined if it's not the default (5198). I use a variable, because the scripts can be run on one of 10 configuration files, and the correct value is read from the relevant config file then saved in the $PORT variable locally. $NEWCALL is the callsign of the station that just connected. It is set and exported by the EventScript when it runs on a "connected" event. Here's a sample part of an EventScript that should work. This one can work with both transcoding and non transcoding by looking for the "linkports" script. if [ "$1" = "connected" ]; then # Check for a transcoding conference (presence of ./linkports symlink in curr$ if [ -f ./linkports ]; then NEWCALL=$3 export NEWCALL ./linkports fi fi Another consideration is security. IRLP's experimental reflectors feature, by default, provides no security (see the sample tlb.conf to find out how to disable audio packet passwords). However, if you do want to implement your own security mechanisms, look up the allow commands (allow add, allow delete, etc), which will allow you to enforce a degree of security, similar to how the reflectors do it. But the mechanisms of authentication and issuing the allow commands is for you to work out. :) Anyway, that should get you started. You need to read the README and SCRIPTING files in the tlb archive, they will give you a LOT of useful information, along with the sample tlb.conf.sample and other sample config files. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: APRS script for Debian 10
John wrote:
Not that the irlp status page setting would have any bearing onWell actually... I'm hoping to fix that pretty soon, and was intending to beta-test with all the VE3/VA3 nodes first. Then nobody needs to run these scripts on their nodes, they just update status.irlp.net in the usual way, and within a minute or so it should get to APRS, and *IF* you have any local igates willing to send it back to RF, it will get back to RF too. Not enabled yet, was trying to clarify some details like FROMCALL, TOCALL, etc. I'll announce here as soon as it's online. I believe the O stands for operational, buggered if I recall what UOfficially I0 (india zero) mean IRLP and E0 (echo zero) means EchoLink, /L (slash Lima) means "Link", /r (slash romeo) means "voice repeater" and there are no other official repeater symbols I'm aware of in any official APRS documentation. ... however the most popular undocumented defacto standard seems to use I0 for idle, C0 for connected, B0 for busy, O0 (Oscar zero) for offline. I'm not aware of U being used, at least not for IRLP objects, in any notable numbers, not in my "big data analysis" of all of April/May/June. ... but I think you're referring to something else - the "AVRS Status" field? I never found a good description of what those MEAN, but they are "Open", "Closed", "Assisted", or "Unknown". 73! Nick VA3NNW -- "Nosey" Nick Waterman, VA3NNW/G7RZQ, K2 #5209. use Std::Disclaimer; sig@... You cannot kill time without injuring eternity.
|
|
|
|
Re: Deb 13.03
David Cameron - IRLP
Funny enough, in describing the problem in my reply, I found the reason. The DTMF binary uses the "OSS Method" to mute the sound input, therefore it will not work without being called inside the aoss wrapper. This is going to require a re-write of a number of scripts, which I will work on in the coming days.
toggle quoted messageShow quoted text
Dave Cameron
On 12/06/2020 12:09 p.m., Klaus Rung via groups.io wrote:
I am using the same pc and sound card as I used with the deb 7 that worked fine and muted the audio. The only change is the updated operating system.
|
|
|
|
Re: Deb 13.03
David Cameron - IRLP
There is something weird in the newer kernels that seems to be playing havoc with older sound cards. It also could likely be the same "aoss" issues that we are seeing with other programs.
toggle quoted messageShow quoted text
I rarely use the built in muting for anything any more. Dave Cameron VE7LTD
On 12/06/2020 12:09 p.m., Klaus Rung via groups.io wrote:
I am using the same pc and sound card as I used with the deb 7 that worked fine and muted the audio. The only change is the updated operating system.
|
|
|
|
Re: Node 3288 moribund
David Cameron - IRLP
What is loading that processor? It would usually be about 0.03 if just running IRLP.
toggle quoted messageShow quoted text
Dave Cameorn
On 13/06/2020 12:53 a.m., Ramon Gandia wrote:
I'll go with a Pi3B+ Already downloaded Latest 5/27 Raspbian Lite.
|
|
|
|
Re: APRS script for Debian 10
Chris Pitre
# Run the aprs_status script every 10 minutes, with a random offset
3,13,23,33,43,53 * * * * (/home/irlp/custom/aprs_status >/dev/null 2>&1) That is probably what I should have posted. I am using APRS.FI to check the status Using ver 4.0 of the aprs script Using Debian 10 I run the local IGate and have it configured for NODE 2803 to INET to RF When I run the sh /tmp/post_install_aprs.sh from root SH: 0: Can't open /tmp/post_install_aprs.sh that doesn't seem right to me
|
|
|
|
Re: APRS script for Debian 10
John
now it will update, but not immediately after it is connected. there is a delaywas wondering if something here needs to be adjusted SHELL=/bin/bash TERM=xterm BASH_ENV=/home/irlp/.profile 0 0 1 * * (/home/irlp/scripts/rotatelog > /dev/null 2>&1) 30 3 * * * (/home/irlp/scripts/clean_old_audio > /dev/null 2>&1) 0 3 * * * (/home/irlp/scripts/update_files_cron > /dev/null 2>&1) 0 * * * * (/home/irlp/scripts/process_check > /dev/null 2>&1) */15 * * * * (/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1) 0 */6 * * * (/home/irlp/scripts/statupdate_cron > /dev/null 2>&1) In the 1st case, I might suggest having a word with the iGate operator. What you pasted here looks like the root cron jobs. What is entered in the custom.crons file for the aprs status But the custom cron is used to send a beacon every xx minutes, NOT the status of your node. A search back through the group emails on aprs might reveal a clue. I might search for comments on the iGate operation. Is the same person contactable on air? John
|
|
|
