Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3616 - LAN peers unreachable after a few hours #8647

Open
openwrt-bot opened this issue Feb 10, 2021 · 2 comments
Open

FS#3616 - LAN peers unreachable after a few hours #8647

openwrt-bot opened this issue Feb 10, 2021 · 2 comments
Labels

Comments

@openwrt-bot
Copy link

ootrey:

Device: D-Link DIR-882 A1
Version: OpenWrt SNAPSHOT r15710-f5f01bcacd / LuCI Master git-21.029.67968-af1f961

After the router has been booted up for about a day, all LAN peers will become unreachable, but WAN works fine, resulting all LAN applications fail.

I ran a few tests. The Router was 192.168.1.1, a computer assigned 192.168.1.233 and another device 192.168.1.169.

Connection to the router was fine:

tracert 192.168.1.1
Tracing route to OPENWRT.lan [192.168.1.1]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms OPENWRT.lan [192.168.1.1]
Trace complete.

Connection to itself was fine:

tracert 192.168.1.233
Tracing route to WINDOWS.lan [192.168.1.233]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms WINDOWS.lan [192.168.1.233]
Trace complete.

Connection to peer failed. It returned the address of itself:

tracert 192.168.1.169
Tracing route to ANDROID.lan [192.168.1.169]
over a maximum of 30 hops:
1 WINDOWS.lan [192.168.1.233] reports: Destination host unreachable.
Trace complete.

ping 192.168.1.169
Pinging 192.168.1.169 with 32 bytes of data:
Reply from 192.168.1.233: Destination host unreachable.
Reply from 192.168.1.233: Destination host unreachable.
Reply from 192.168.1.233: Destination host unreachable.
Reply from 192.168.1.233: Destination host unreachable.
Ping statistics for 192.168.1.169:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

System reboot can solve the problem temporarily. All LAN applications back online:

ping 192.168.1.169
Pinging 192.168.1.169 with 32 bytes of data:
Reply from 192.168.1.169: bytes=32 time=4ms TTL=64
Reply from 192.168.1.169: bytes=32 time=5ms TTL=64
Reply from 192.168.1.169: bytes=32 time=4ms TTL=64
Reply from 192.168.1.169: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.169:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms

@openwrt-bot
Copy link
Author

ootrey:

I will disable hardware flow offloading to see if it's related

@openwrt-bot
Copy link
Author

ootrey:

Still exists when hardware flow offloading or software flow offloading is disabled.

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

No branches or pull requests

1 participant