Flint 2 suddenly lost forwarding to specific static IP

Hello, i suddenly lost forwarding to one of my vm (in bridge mode, ip assigned by router).

  • Routing still work fine will on the same subnet (for example 192.168.1.7 reach with no issues 192.168.1.9)
  • routing work fine when i tested to change affected static IP from 192.168.1.9 to 192.168.1.10 (but it is not the desirable solution).
  • routing from WAN, router VPN server, zerotier or tailscale does not work at all

Command: ip neigh show 192.168.1.9

Target Result
192.168.1.9 (Empty)

Traceroute: 192.168.1.9

Hop Host IP Latency 1 Latency 2 Latency 3
1 console.gl-inet.com 192.168.7.1 3.356 ms 2.890 ms 2.611 ms
2 10.0.0.1 10.0.0.1 16.310 ms 17.917 ms 17.376 ms
3 10.0.0.1 10.0.0.1 1394.365 ms 1394.078 ms (IH) 1393.769 ms (IH)

Traceroute: 192.168.1.8

Hop Host IP Latency 1 Latency 2 Latency 3
1 console.gl-inet.com 192.168.7.1 10.763 ms 9.999 ms 9.550 ms
2 10.0.0.1 10.0.0.1 24.307 ms 23.591 ms 23.043 ms
3 ai.lan 192.168.1.8 22.622 ms 22.031 ms 21.594 ms

Traceroute: 192.168.1.7

Hop Host IP Latency 1 Latency 2 Latency 3
1 console.gl-inet.com 192.168.7.1 2.213 ms 3.105 ms 4.287 ms
2 10.0.0.1 10.0.0.1 17.978 ms 18.965 ms 16.230 ms
3 192.168.1.7 192.168.1.7 16.548 ms 18.622 ms 18.022 ms

Flint 2 4.8.4
that happened without any modification of configs, during work session via vpn and zerotier (from 2 different devices).
I tried to reboot, clear cache, nothing helped.

Maybe it's an IP conflict? Have you checked if any other device is using 192.168.1.9?

Hi,

According to the traceroute result, the forwarding issue appears to occur between 10.0.0.1 and 192.168.1.9. The traffic can reach 10.0.0.1, but it cannot be forwarded successfully to the VM at 192.168.1.9.

To help us better understand the network path:

  1. Could you please provide a simple network topology showing how the Flint 2, the VM, and the device running the traceroute are connected?
  2. Could you also clarify what device or interface the 10.0.0.1 address belongs to in the traceroute result?

Have you configured any custom routing rules, firewall rules, or forwarding settings related to the 192.168.1.9 address?
Thank you for your understanding and cooperation.