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: *

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

Your router is acting as some sort of proxy. Rebuilding won't change this. Dave

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.

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

What is the IP of the node behind the router? What is 192.168.2.1? Dave Cameron

I only have one router, running OpenWRT.  I use OpenVPN as a standby control circuit - it isn't involved in IRLP at all, except that it allows me to control the node from my phone.  The OpenVPN

A debian upgrade would not have changed the way your network routes, so something else has changed. Do you have two routers? You mention OpenVPN - how does it play into this? You need to have one or

Hmm.  OK. Strange that OpenVPN works though.  The port forwards are the same, and it shouldn't have made any changes. I'll play around with the router. Thanks! James KL2ZZ

I think there is a problem with your router. When I attempt to connect to your node on port 15425, it works, but it gives me the wrong IP address repeater@tigger:~$ telnet stn7295 15425 Trying

Hello all - I've been dealing with a bit of a mystery for the past couple of days. I run IRLP node 7295 using a 3.0 board mounted in an HP desktop, running Debian 10.  The node feeds an NHRC-7

Vr1 on my radio was right beside the con6 connector where the jumper to the db9 goes when you modify the radio. Sure enough, it varies the output audio to the db9. Dave Cameron

OK, I'll take a look at CON6 with a scope, be interesting to see what the amplitude is. In the meantime I can experiment with alsamixer. 73, Al

Based on a schematic found here: http://k4nha.com/wp-content/uploads/2018/02/TYT_TH-9000_VHF-220-260MHz_Schematics_2.pdf On page 2, section C1 you will see the 47K variable VR1 that takes a portion

The auto gain has an "OO" in it. Second Mic setting or Capture is set to 44 at the moment. You make an interesting point about the TYT level at the connector. I guess I can put a scope on it at some

One other thought is to make sure you are using 25KHz wide mode in the TYT-9000D for the receiver bandwidth. You can also try 20KHz and 12.5KHz to see if it affects the decode ability. Something is

The software mixer controls do not affect the level seen by the DTMF decoder. It sees the raw audio from the receiver. I think the audio point on the TYT connector is de-emphasized, but I wonder how

David: I am using the TYT-9000D UHF radio for my node. The audio source comes directly from the radio main board (RX Audio) to the mic input to a SYBA USB sound adaptor to the Pi. The alsamixer MIC

If a transmitter is off by 1 or 2+ kHz of TX frequency, that may cause an issue also. Check with a frequency counter the accuracy of the 3 different transmitters. --------------- Regards,

Become familiar with the use of the ‘readinput’ command. Very helpful tool when troubleshooting any dtmf decoding issues. su - repeater readinput Ctrl-C to quit -k9dc