To me it is a bit of a "hang"... The VPN drops, but the gateway is not returned to the local LAN. It gets stuck on the VPN, but can not reconnect. I think the only solution is to have an external

So are you saying I should wait until the update to see if things stay working?

Ok thanks for the dns info to use the router dns and see if that fixes the problem. Klaus

Its in a comment in ipupdate, and I recently fixed the script for the find_best_server. It will be in the next update. I also updated the web DYNDNS timeout to 5 seconds. It is not a time critical

Thank you. I was able to give the board to the first emailer. Jeff K2SDR

On my node 3288, that IP address is hard coded into ~/scripts/ipupdate ~/scripts/bind_best_server It seems that if there is poor connectivity, it defaults to that IP address. With good connectivity,

A big problem is that the server you are showing doesn't exist any more (142.103.194.4). We need to figure out why that is also. Somewhere, that ip is hard coded. Sounds like openvpn is losing the

This is probably because your DNS 1.1.1.1 is not accessible after the tunnel drops. With DNS dead, your node will not be able to lookup vpn01.irlp.net. I would suggest using your local router for DNS

I have a deb 7 jessie node that has the openvpn installed. The openvpn work fine when booted and gets the 44. ip and works normally for a day or so. When the provider releases the wan ip it appears

Goops. Forgot de k9dc

There are a couple of ways to handle this. First is to create and use the lockout_list file. If the file exists, it contains a list of nodes and reflectors you do not want to connect, both outgoing

VK4DAK wrote: Well... You could just give it a DIFFERENT NUMBER, EG: if [ "${1}" = "9999" ]; then exit 1 ; fi # having done nothingif [ "${1}" = "ABC123" ]; then

Hi all! I am hoping you may be able to assist with some scripting ..... I have a problem where some locals think its great to key up REF9999 (Parrot) and leave it connected. The problem is that it

What are you asking for it ? Richard Szajkowski VA3RZS,VA3ZJ,VE3BTE

I have a 3.0 board, from an older desktop, if anyone needs one. Jeff K2SDR jkelly@...

Just a few changes to the PiRLP4 to announce: 1) There is a new channel carved into the case to allow viewing of the power and activity lights from the outside. This is just at the bottom right of

Tony, yes, thanks for pointing that out. Where can we get some introductory tutelage on how to set up and operate a "linkbox" reflector? I have always wanted to learn how to do that. And anyone

We figured this out when he booted the old node and every thing worked Just waiting on if he found the problem Most likely the password was on lower case ( I hope ) Richard Szajkowski VA3 RZS

For everyone's information, any references to port forwarding are a red herring with regards to the OP's question.  Port forwarding issues causes a totally DIFFERENT error.  Specifically: The

I think he means "not on a Pi - using PC hardware". -- 73 de Tony VK3JED/VK3IRLhttp://vkradio.com