I use PPPoE to dial in to obtain a dynamic public IP address. The IP address automatically changes every three days. Prior to (and including) 7.19.2, the DDNS automatically updated. This week, after upgrading to 7.19.4, the DDNS public address no longer updates automatically. I tried disconnecting the PPPoE connection and dialing again, and while I can get a new dynamic public IP address, the DDNS address doesn't update automatically. To synchronize the two IP addresses again, I need to restart the router. Does anyone know if this is a bug in version 7.19.4? Is my situation unique?
What is the output of:
/ip cloud print
Obfuscate both IP addresses and hostname.
/ip cloud print
ddns-enabled: yes
ddns-update-interval: none
update-time: yes
public-address: 115.192.99.165
dns-name: (This position is the SN code).sn.mynetname.net
status: updated
back-to-home-vpn: revoked-and-disabled
ddns-enabled: yes >
ddns-update-interval: none >
update-time: yes >
dns-name: ***.sn.mynetname.net >
back-to-home-vpn: enabled >
vpn-dns-name: ***.vpn.mynetname.net >
vpn-port: 52392 >
vpn-status: updating relays >
vpn-private-key: 0AVef6kZ74fi8lEvz5zgkJrvttViIIEqYSJ9hxrywE0= >
vpn-public-key: 29MLgosaZXtVMy9L1Pm/XqFfJdtGrfwnpWdC9SVagnw= >
vpn-peer-private-key: qPyJ9aQHNNhdh18gC9XX2oFH7q3AVwfkvZIyvd/8/GA= >
vpn-peer-public-key: Q1lwoQGzeuKvVvcTyfPw1gmRveBazyo6H99TsqeGzm0= >
vpn-interface: back-to-home-vpn >
vpn-wireguard-client-config: [Interface] >
PrivateKey = qPyJ9aQHNNhdh19gC5XX2oFH7q3AVwfkvZIyvd/8/GA= >
Address = 192.168.216.2/32,fc00:0:0:216::2/128 >
DNS = 223.5.5.5 >
[Peer] >
PublicKey = //////////////////////////////////////////8= >
AllowedIPs = 0.0.0.0/32 >
Endpoint = ***.sn.mynetname.net:52392 >
PersistentKeepalive = 15 >
[Peer] >
PublicKey = 28MLgosaZXtVMy9L1Pm/XqFfJdtGrfwnpWdC9SVagnw= >
AllowedIPs = 0.0.0.0/0,::/0 >
Endpoint = ***.vpn.mynetname.net:52392 >
PersistentKeepalive = 15
When back-to-home-vpn is enabled, the DDNS IP address will not be automatically updated.
Excellent find!! Did you report that in a supout, to Mikrotik, it would appear to be a bug..........
The router, in my IP cloud, should ensure the mynetname is resolved to the new address after it has been changed.
The BTH wireguard functionality should ensure that the MT relay server gets the new address as well.
However, I have to ask, if you are getting a public dynamic IP address.....
WHY are you using BTH ??????? ( vice regular wireguard )
Haha, that's a good question :). I can get a public dynamic IP. The reason is simple: turning on BTH also generates a WireGuard config. I simply import this config through WireGuard for Windows and then remotely connect to my home PC, saving me the time of configuring WireGuard. I've downgraded my system to 7.19.2, and everything is back to normal. I'm not sure if this is a real bug; will mikrotik see it?
No, not necessarily. If you have found a bug, report it ASAP so that its fixed for the next firmware etc......
Yes, as I suspected a lazy mans wireguard adaptation. ;-))
Did you not read my great (no bias) dissertation on an improved NORMAL wireguard that utilizes some or the concepts from BTH to do exactly what you ask, generate configs for all client devices !!!
By the way, the BTH config output by the router is really intended for the admins cell phone and from that one generates all the client accounts/settings.
I have not played with using that for a client only or even more interesting perhaps using the settings on another MT router as a client. We are limited however as MT hardcodes some firewall rules into the initial router.........