Feature Changing advertised ip and ports on the fly

[zackherbert]

I would like to use teku (and also besu) behind a VPN configured with port forwarding.

Once the VPN connection is active, I have the public ip and a dynamically provided port that I could use to set the following options:

• p2p-advertised-ip
• p2p-advertised-port
• p2p-advertised-udp-port

If the VPN connection fails, another VPN connection is made to another server and I have new values for these options.

Is there a way with teku to change those values on the fly without needing to restart my teku container with new values?

[rolfyone]

Hey - this is a good idea, but probably due to electra things we've not got much of an easy answer currently....

The one thing potentially we'd have is if the ports aren't defined or the advertised ip or anything, then you might be able to enable upnp.... i'm not sure if it will detect and correctly handle the ip address change ,but its the only feature we currently do have that potentially would solve it... This would basically mean not specifying any of the ports / ip address above, and using https://docs.teku.consensys.io/how-to/find-and-connect/specify-nat and specifying NAT mode. I don't have a high degree of confidence that this will fix your issue without some changes, but you could try it... Meanwhile I'll put this on our backlog and we'll keep it in mind once our main electra push is done...