I am using Asterisk/Hamvoip on a Pi4 and on boot up it did get my IP address announced on my radio node correctly. ie “IP Address 192.168.1.10”
Now, I have added a VK44.net VPN and all is good there, but my IP announcement is now cut short!
Is there a timeout delay somewhere? Maybe it’s doing other stuff and times out? Is the Pi running out of steam?
You have gathered I’m not an expert!
73, Gary.
Gary, I would go ask this to the Hamvoip people. Reason I say this, Hamvoip doesn’t release their source code back into the Linux community, so it’s closed sourced. With that being said, it’s very unlikely you’ll find an answer on this forum.
It’s also worth pointing out that HamVoIP’s mailing list has been offline since May, and they’re not doing updates anymore either, it seems. Wish I could help, though I still do have a couple of HamVoIP nodes, I’ve never experienced that particular issue.
Thanks for that, didn’t realise! We live and learn.
73, Gary, VK6GC.
By ‘cut short’ I assume you mean it says “IP ADDRESS…” and then no data? It’s related to your VPN because at the time it’s trying to read back the IP address there’s no IP assigned conventionally. Look in /usr/local/sbin/sayip.sh to see if you can get it to look at your VPN adapter address
I have a couple of HamVoIP nodes using Wireguard VPN clients, and they speak the VPN-assigned IP address at startup with no modification, for what it’s worth. I have never used OpenVPN, ZeroTier or any of the others with HamVoIP.
Thanks, I’ll check that out.
Sometimes I get only “IP Address”, sometimes just “192”. Once I got the full internal IP address!"
It does seem like the Pi is busy doing other stuff at the time.
Interesting that yours announces the VPN assigned IP.
I would be happier with the internal IP, just in case I can’t find it on the network.
Maybe I’ll turn it off as the router assigns it anyway but it’s always nice the learn what’s happeng.