Wireguard not automatically connecting

Cellular Modems
1
Hi 

I am having a problem with Wireguard connecting after a reboot or power loss on my IR302 that I have recently purchased.

The Wireguard status shows random settings after each reboot with a different port each time eg.

interface: wg0
  listening port: 42716

The settings stay correct and I can view and click save the tunnel connects successfully eg.

interface: wg0
  public key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  private key: (hidden)
  listening port: 51820

peer: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  endpoint: xx.xx.xx.xx:51820
  allowed ips: 0.0.0.0/0
  latest handshake: 21 seconds ago
  transfer: 124 B received, 180 B sent
  persistent keepalive: every 25 seconds


I am on firmware V3.5.78, and have tried downgrading to V3.5.77.

Any suggestions on what could be causing this and workarounds? The IR302 is of no use to me if this cannot automatically reconnect to the Wireguard tunnel.

Thank you 
2
Hi,

  Is the Wireguard VPN peer address a domain name?

  When the network is not back to normal, wireguard VPN does fail to establish a VPN tunnel due to domain name resolution failures, and the connection status ports you see are random;

The current bug is a known bug;

We will fix this issue in the next release;

Thank you for your feedback!
3
Hi,

      Regarding the issue of configuring domain names for Wireguard VPN and the inability to automatically reconnect; we have resolved it in version 3.5.89. Please download it from the following path: 
      https://www.inhand.com/en/resources-center/#/IndustrialDigitalization/InRouter/IR302
4
Hi, 

I have an issue where the inhand drops the route to my allowed IP subnet from its routing table after a certain period of time. Re-initiating the tunnel resolves this. Is there an solution to this? unfortunately the wireguard interface does not show up on the GUI static route option so I cannot add it that way either.