Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

transport_tcp: detect listen addr changes #44

Open
madninja opened this issue Mar 14, 2018 · 5 comments
Open

transport_tcp: detect listen addr changes #44

madninja opened this issue Mar 14, 2018 · 5 comments

Comments

@madninja
Copy link
Member

DHCP based nodes will change their IP address over time.

Have the tcp transport server poll for IP address changes and update ETS as well as notify the peerbook

@Balsteg
Copy link

Balsteg commented Jul 9, 2021

As more nodes are added that use 4G/5G internet connections, I think this continues to be an issue. I'm using a VPN to successfully port-forward around the CGNAT from a 5G carrier. The public IP address issued by the VPN changes often (daily?). The peerbook shows the old IP address for several hours. During this time, the node continues to appear online in Explorer and is able to witness beacons, but the node is unreachable to receive challenges or challenge receipts.

@evanmcc
Copy link
Contributor

evanmcc commented Jul 9, 2021

Thanks for the report. We'll try to bump up the priority on this one.

@Balsteg
Copy link

Balsteg commented Jul 9, 2021

Thanks for the report. We'll try to bump up the priority on this one.

Someone else just posted in Discord #poc-discussion that in their country (Germany) most ISPs reissue IP addresses every 24 hours. Is there a workaround for now? It doesn't seem like power-cycling a miner updates the peerbook, unless there is a min time that it needs to remain offline?

@danggoma
Copy link

Thanks for the report. We'll try to bump up the priority on this one.

Someone else just posted in Discord #poc-discussion that in their country (Germany) most ISPs reissue IP addresses every 24 hours. Is there a workaround for now? It doesn't seem like power-cycling a miner updates the peerbook, unless there is a min time that it needs to remain offline?

I posted it in Discord. Yes, in Germany and other EU countries some or most ISPs reissue IP addr every 24hrs. From my observation listen_addrs lag time to update to a new IP went from 1hr to 12-22hrs in the last 90 days and seems to be increasing still. Power cycling did not help.
I recently removed PF and running a hotspot on relay to see if it leads to better results.

@wolasss
Copy link

wolasss commented Aug 5, 2021

Is there a workaround for now?

To tackle this issue, I have set up a VPS, connected a hotspot to a VPN, and reroute traffic to the hotspot so that it has static IP (VPS' IP). I'll let you know if it yields better results.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants