I have a router that I've set to randomise the MAC address every 3 days. When that happens the interface gets dropped for a moment to apply the changes. When it comes back online, Newt fails to reconnect, and does its consecutive pings. WARN: 2026/04/09 00:31:22 Periodic ping failed (15 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
I checked with to make sure it had nothing to do with the MAC randomisation, and sure enough, a simple router reboot causes Newt to go into stasis.
I have two servers running on the same network, with different Newt versions, they both go into stasis.
Environment
OS Type & Version: DietPi 0.6.2
Pangolin Version: 1.17.0 (happened on 1.15.x as well)
Newt Version: 1.9.0 and 1.11.0
To Reproduce
Have a working instance of pangolin, with Newt running, then restart the interface that Newt is connected to.
Expected Behavior
Newt should be able to identify the interface has probably restarted, and attempt to initiate some kind of reconnection.
Originally created by @Frost-4X on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2815
### Describe the Bug
I have a router that I've set to randomise the MAC address every 3 days. When that happens the interface gets dropped for a moment to apply the changes. When it comes back online, Newt fails to reconnect, and does its consecutive pings.
`WARN: 2026/04/09 00:31:22 Periodic ping failed (15 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout`
I checked with to make sure it had nothing to do with the MAC randomisation, and sure enough, a simple router reboot causes Newt to go into stasis.
I have two servers running on the same network, with different Newt versions, they both go into stasis.
### Environment
- OS Type & Version: DietPi 0.6.2
- Pangolin Version: 1.17.0 (happened on 1.15.x as well)
- Newt Version: 1.9.0 and 1.11.0
### To Reproduce
Have a working instance of pangolin, with Newt running, then restart the interface that Newt is connected to.
### Expected Behavior
Newt should be able to identify the interface has probably restarted, and attempt to initiate some kind of reconnection.
I've turned of my randomisation schedule, so this will affect me less. However, its still an inconvenience if my router ever gets power cycled, I lose my Pangolin connections. Then I have to connect to my server via other tunnelling services, and restart both instances of Newt.
<!-- gh-comment-id:4210677511 -->
@Frost-4X commented on GitHub (Apr 9, 2026):
I've turned of my randomisation schedule, so this will affect me less. However, its still an inconvenience if my router ever gets power cycled, I lose my Pangolin connections. Then I have to connect to my server via other tunnelling services, and restart both instances of Newt.
@oschwartz10612 commented on GitHub (Apr 9, 2026):
Would you be able to do a power cycle and provide the whole newt log?
<!-- gh-comment-id:4210909108 -->
@oschwartz10612 commented on GitHub (Apr 9, 2026):
Would you be able to do a power cycle and provide the whole newt log?
I assume you mean the router. I'll attach a log later.
<!-- gh-comment-id:4210959707 -->
@Frost-4X commented on GitHub (Apr 9, 2026):
Power cycle what?
I assume you mean the router. I'll attach a log later.
@github-actions[bot] commented on GitHub (Apr 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:4309620962 -->
@github-actions[bot] commented on GitHub (Apr 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@AstralDestiny commented on GitHub (Apr 24, 2026):
Curious why the mac randomization? Don't want isp to track you or something even though no matter how much time the public ip changes they have something that will always point to you as a customer and your past given ip's handed out..
As for newt put it into --log-level debug and restart and let us know what the logs say. Just know logs might contain your domain and other stuff.
<!-- gh-comment-id:4309643116 -->
@AstralDestiny commented on GitHub (Apr 24, 2026):
Curious why the mac randomization? Don't want isp to track you or something even though no matter how much time the public ip changes they have something that will always point to you as a customer and your past given ip's handed out..
As for newt put it into --log-level debug and restart and let us know what the logs say. Just know logs might contain your domain and other stuff.
My router is a subnet router under another router that's connecting to the WAN. By Randomising, it makes the traffic seem like different devices, though its pretty evident where its coming from. It just something I setup once and forgot to disable. The problem has nothing to do with randomisation, that's just the trigger.
I'll try remember to get around to posting some debug logs, pretty busy at present.
<!-- gh-comment-id:4309665587 -->
@Frost-4X commented on GitHub (Apr 24, 2026):
My router is a subnet router under another router that's connecting to the WAN. By Randomising, it makes the traffic seem like different devices, though its pretty evident where its coming from. It just something I setup once and forgot to disable. The problem has nothing to do with randomisation, that's just the trigger.
I'll try remember to get around to posting some debug logs, pretty busy at present.
I been experiencing (what I assume to be) the same issue for about 2 months now.
Everything works great, then at some point over the weeks running non-stop newt will start throwing these logs non-stop:
WARN: 2026/05/02 02:01:46 Periodic ping failed (1131 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
At that point I won't be able to reach any public resource from outside the network anymore.
As soon as I restart newt everything goes back to work.
I had this happen 3 times in a 2 months period now.
<!-- gh-comment-id:4362751470 -->
@dougmaitelli commented on GitHub (May 2, 2026):
I been experiencing (what I assume to be) the same issue for about 2 months now.
Everything works great, then at some point over the weeks running non-stop newt will start throwing these logs non-stop:
```
WARN: 2026/05/02 02:01:46 Periodic ping failed (1131 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeout
```
At that point I won't be able to reach any public resource from outside the network anymore.
As soon as I restart newt everything goes back to work.
I had this happen 3 times in a 2 months period now.
services:newt:container_name:newtimage:fosrl/newt:1.12.0environment:- PANGOLIN_ENDPOINT=https://pangolin.${DOMAIN}- NEWT_ID=${NEWT_ID}- NEWT_SECRET=${NEWT_SECRET}- LOG_LEVEL=debug# This restart:unless-stopped
..?
<!-- gh-comment-id:4364119360 -->
@AstralDestiny commented on GitHub (May 2, 2026):
You got any logs prior to the issue?
also can you add
```yml
services:
newt:
container_name: newt
image: fosrl/newt:1.12.0
environment:
- PANGOLIN_ENDPOINT=https://pangolin.${DOMAIN}
- NEWT_ID=${NEWT_ID}
- NEWT_SECRET=${NEWT_SECRET}
- LOG_LEVEL=debug # This
restart: unless-stopped
```
..?
I have all the logs still, but I don't see anything on them besides the normal startup messages and then followed by thousands of repeats of this same warning. I can upload them if needed but I did go over it twice already and there is nothing there.
I will add the LOG_LEVEL now and let's see how long it will take for it to fail again, last time took 4 days.
EDIT: Worth mentioning, I am running newt 1.12.0 and I did not update it yet so we can try to get the logs for the original issue without risking an update to fix it
<!-- gh-comment-id:4364650214 -->
@dougmaitelli commented on GitHub (May 2, 2026):
> You got any logs prior to the issue?
>
> also can you add
>
> services:
> newt:
> container_name: newt
> image: fosrl/newt:1.12.0
> environment:
> - PANGOLIN_ENDPOINT=https://pangolin.${DOMAIN}
> - NEWT_ID=${NEWT_ID}
> - NEWT_SECRET=${NEWT_SECRET}
> - LOG_LEVEL=debug # This
> restart: unless-stopped
>
> ..?
I have all the logs still, but I don't see anything on them besides the normal startup messages and then followed by thousands of repeats of this same warning. I can upload them if needed but I did go over it twice already and there is nothing there.
I will add the LOG_LEVEL now and let's see how long it will take for it to fail again, last time took 4 days.
EDIT: Worth mentioning, I am running newt 1.12.0 and I did not update it yet so we can try to get the logs for the original issue without risking an update to fix it
So far yeah, still monitoring it every day to wait for it to happen again
<!-- gh-comment-id:4400633164 -->
@dougmaitelli commented on GitHub (May 7, 2026):
> Take it it's been happy so far then?
So far yeah, still monitoring it every day to wait for it to happen again
I was able to induce a failure by restarting the ISP modem. I assume that what happens is that when my ISP rotates my external IP or my external link has a downtime and newt loses connection it is never able to recover on it's own unless it is manually restarted.
Yeah, I was keeping it on 1.12.0 in order to test / debug the behavior if necessary.
I checked the issue you linked and it looks like the same problem I have. I updated it yesterday to 1.12.4 and I could not reproduce the issue now anymore.
<!-- gh-comment-id:4416420458 -->
@dougmaitelli commented on GitHub (May 10, 2026):
Yeah, I was keeping it on 1.12.0 in order to test / debug the behavior if necessary.
I checked the issue you linked and it looks like the same problem I have. I updated it yesterday to 1.12.4 and I could not reproduce the issue now anymore.
@LaurenceJJones commented on GitHub (May 11, 2026):
Classing as complete, if you hit anymore issues please comment on the linked newt issue 👍🏻
<!-- gh-comment-id:4419353150 -->
@LaurenceJJones commented on GitHub (May 11, 2026):
Classing as complete, if you hit anymore issues please comment on the linked newt issue 👍🏻
Happens to me too. Newt just fails to reconnect until I manually restart it.
Newt version 1.12.5
<!-- gh-comment-id:4535975147 -->
@roimpro commented on GitHub (May 25, 2026):
Happens to me too. Newt just fails to reconnect until I manually restart it.
Newt version 1.12.5
Happens to me too. Newt just fails to reconnect until I manually restart it. Newt version 1.12.5
Same here
<!-- gh-comment-id:4545954146 -->
@dennido commented on GitHub (May 26, 2026):
> Happens to me too. Newt just fails to reconnect until I manually restart it. Newt version 1.12.5
Same here
@oschwartz10612 commented on GitHub (May 26, 2026):
@roimpro and @dennido interesting... could you attach a full log output
to investigate further?
<!-- gh-comment-id:4546480225 -->
@oschwartz10612 commented on GitHub (May 26, 2026):
@roimpro and @dennido interesting... could you attach a full log output
to investigate further?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Frost-4X on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2815
Describe the Bug
I have a router that I've set to randomise the MAC address every 3 days. When that happens the interface gets dropped for a moment to apply the changes. When it comes back online, Newt fails to reconnect, and does its consecutive pings.
WARN: 2026/04/09 00:31:22 Periodic ping failed (15 consecutive failures): all 4 ping attempts failed, last error: failed to read ICMP packet: i/o timeoutI checked with to make sure it had nothing to do with the MAC randomisation, and sure enough, a simple router reboot causes Newt to go into stasis.
I have two servers running on the same network, with different Newt versions, they both go into stasis.
Environment
To Reproduce
Have a working instance of pangolin, with Newt running, then restart the interface that Newt is connected to.
Expected Behavior
Newt should be able to identify the interface has probably restarted, and attempt to initiate some kind of reconnection.
@Frost-4X commented on GitHub (Apr 9, 2026):
I've turned of my randomisation schedule, so this will affect me less. However, its still an inconvenience if my router ever gets power cycled, I lose my Pangolin connections. Then I have to connect to my server via other tunnelling services, and restart both instances of Newt.
@oschwartz10612 commented on GitHub (Apr 9, 2026):
Would you be able to do a power cycle and provide the whole newt log?
@Frost-4X commented on GitHub (Apr 9, 2026):
Power cycle what?
I assume you mean the router. I'll attach a log later.
@github-actions[bot] commented on GitHub (Apr 24, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@AstralDestiny commented on GitHub (Apr 24, 2026):
Curious why the mac randomization? Don't want isp to track you or something even though no matter how much time the public ip changes they have something that will always point to you as a customer and your past given ip's handed out..
As for newt put it into --log-level debug and restart and let us know what the logs say. Just know logs might contain your domain and other stuff.
@Frost-4X commented on GitHub (Apr 24, 2026):
My router is a subnet router under another router that's connecting to the WAN. By Randomising, it makes the traffic seem like different devices, though its pretty evident where its coming from. It just something I setup once and forgot to disable. The problem has nothing to do with randomisation, that's just the trigger.
I'll try remember to get around to posting some debug logs, pretty busy at present.
@dougmaitelli commented on GitHub (May 2, 2026):
I been experiencing (what I assume to be) the same issue for about 2 months now.
Everything works great, then at some point over the weeks running non-stop newt will start throwing these logs non-stop:
At that point I won't be able to reach any public resource from outside the network anymore.
As soon as I restart newt everything goes back to work.
I had this happen 3 times in a 2 months period now.
@AstralDestiny commented on GitHub (May 2, 2026):
Container bound or host bound?
@dougmaitelli commented on GitHub (May 2, 2026):
Not sure what you mean, but I am running newt inside docker using compose:
@AstralDestiny commented on GitHub (May 2, 2026):
You got any logs prior to the issue?
also can you add
..?
@dougmaitelli commented on GitHub (May 2, 2026):
I have all the logs still, but I don't see anything on them besides the normal startup messages and then followed by thousands of repeats of this same warning. I can upload them if needed but I did go over it twice already and there is nothing there.
I will add the LOG_LEVEL now and let's see how long it will take for it to fail again, last time took 4 days.
EDIT: Worth mentioning, I am running newt 1.12.0 and I did not update it yet so we can try to get the logs for the original issue without risking an update to fix it
@AstralDestiny commented on GitHub (May 7, 2026):
Take it it's been happy so far then?
@dougmaitelli commented on GitHub (May 7, 2026):
So far yeah, still monitoring it every day to wait for it to happen again
@dougmaitelli commented on GitHub (May 8, 2026):
I was able to induce a failure by restarting the ISP modem. I assume that what happens is that when my ISP rotates my external IP or my external link has a downtime and newt loses connection it is never able to recover on it's own unless it is manually restarted.
@oschwartz10612 commented on GitHub (May 8, 2026):
Are you running the latest 1.12.4? We introduced some fixes
@oschwartz10612 commented on GitHub (May 8, 2026):
https://github.com/fosrl/newt/issues/284
@dougmaitelli commented on GitHub (May 10, 2026):
Yeah, I was keeping it on 1.12.0 in order to test / debug the behavior if necessary.
I checked the issue you linked and it looks like the same problem I have. I updated it yesterday to 1.12.4 and I could not reproduce the issue now anymore.
@LaurenceJJones commented on GitHub (May 11, 2026):
Classing as complete, if you hit anymore issues please comment on the linked newt issue 👍🏻
@roimpro commented on GitHub (May 25, 2026):
Happens to me too. Newt just fails to reconnect until I manually restart it.
Newt version 1.12.5
@oschwartz10612 commented on GitHub (May 25, 2026):
@roimpro even on the latest version?
@roimpro commented on GitHub (May 25, 2026):
Yes
@dennido commented on GitHub (May 26, 2026):
Same here
@oschwartz10612 commented on GitHub (May 26, 2026):
@roimpro and @dennido interesting... could you attach a full log output
to investigate further?
@dennido commented on GitHub (May 27, 2026):
@oschwartz10612 Yes, sure. I hope this helps:
After a restart of the newt connector everything just worked fine: