When I connect the Pangolin client, I noticed there is a slow reply from devices from the same LAN subnet.
For example, I have a Pangolin client on 192.168.98.20. When I ping 192.168.98.1 it gives this result.
Pinging 192.168.98.1 with 32 bytes of data:
Reply from 192.168.98.1: bytes=32 time=34ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=32ms TTL=64
Ping statistics for 192.168.98.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms
When I disconnect the Pangolin client, the ping results go back to normal.
But when I ping an IP on a different VLAN, say 192.168.10.1 the ping result is normal.
Pinging 192.168.10.1 with 32 bytes of data:
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Any ideas what could be causing this? I also tried this on another machine with the same result.
Note : Using latest Pangolin client (0.7.1) and server version (1.16.2) running on a Racknerd VPS.
Thank you.
Environment
OS Type & Version: (e.g., Ubuntu 22.04)
Pangolin Version:
Gerbil Version:
Traefik Version:
Newt Version:
Olm Version: (if applicable)
To Reproduce
Connect client and ping results in slow response.
Disconnect client and ping results return to normal.
Expected Behavior
Ping should be normal when client is connected.
Originally created by @Discolor3182 on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2610
### Describe the Bug
Hello,
When I connect the Pangolin client, I noticed there is a slow reply from devices from the same LAN subnet.
For example, I have a Pangolin client on 192.168.98.20. When I ping 192.168.98.1 it gives this result.
Pinging 192.168.98.1 with 32 bytes of data:
Reply from 192.168.98.1: bytes=32 time=34ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=32ms TTL=64
Ping statistics for 192.168.98.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms
When I disconnect the Pangolin client, the ping results go back to normal.
But when I ping an IP on a different VLAN, say 192.168.10.1 the ping result is normal.
Pinging 192.168.10.1 with 32 bytes of data:
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Any ideas what could be causing this? I also tried this on another machine with the same result.
Note : Using latest Pangolin client (0.7.1) and server version (1.16.2) running on a Racknerd VPS.
Thank you.
### Environment
- OS Type & Version: (e.g., Ubuntu 22.04)
- Pangolin Version:
- Gerbil Version:
- Traefik Version:
- Newt Version:
- Olm Version: (if applicable)
### To Reproduce
Connect client and ping results in slow response.
Disconnect client and ping results return to normal.
### Expected Behavior
Ping should be normal when client is connected.
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 @Discolor3182 on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2610
Describe the Bug
Hello,
When I connect the Pangolin client, I noticed there is a slow reply from devices from the same LAN subnet.
For example, I have a Pangolin client on 192.168.98.20. When I ping 192.168.98.1 it gives this result.
Pinging 192.168.98.1 with 32 bytes of data:
Reply from 192.168.98.1: bytes=32 time=34ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=31ms TTL=64
Reply from 192.168.98.1: bytes=32 time=32ms TTL=64
Ping statistics for 192.168.98.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms
When I disconnect the Pangolin client, the ping results go back to normal.
But when I ping an IP on a different VLAN, say 192.168.10.1 the ping result is normal.
Pinging 192.168.10.1 with 32 bytes of data:
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Reply from 192.168.10.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Any ideas what could be causing this? I also tried this on another machine with the same result.
Note : Using latest Pangolin client (0.7.1) and server version (1.16.2) running on a Racknerd VPS.
Thank you.
Environment
To Reproduce
Connect client and ping results in slow response.
Disconnect client and ping results return to normal.
Expected Behavior
Ping should be normal when client is connected.