bruce
April 17, 2025, 3:01am
46
Hello,
Regarding users with Flint 1 with v4.7.0 WAN or LAN port abnormality, R&D has guessed this possibility, if you are the users who encounter this abnormal, please help verify.
Will there be any improvement after disable the network port eee save energy?
SSH to the router, and execute the commands:
ethtool --set-eee eth1 eee off
ethtool --set-eee eth0 eee off
R&D and I did not reproduce the WAN port issue "down -> up" local Flint1 (s), and running for about 24 hours.
TIA!
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Hi,
All of them
Below is the ping result from a device connected via Ethernet cable.
The router simply becomes unreachable
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
logread (2).tar (126.5 KB)
bruce
April 18, 2025, 10:36am
48
Hi,
What is the MAC of this device that performs ping
?
We did not find any exceptions in the syslogs, and the DHCP renewal of all clients is normal.
Could you please share the router with us via GoodCloud, and PM me the router MAC and the Web UI login password.
bruce
May 8, 2025, 1:47am
49
Hello all,
Regarding the network port issue, is this issue improved with these commands?
bruce:
Regarding users with Flint 1 with v4.7.0 WAN or LAN port abnormality, R&D has guessed this possibility, if you are the users who encounter this abnormal, please help verify.
Will there be any improvement after disable the network port eee save energy?
SSH to the router, and execute the commands:
ethtool --set-eee eth1 eee off
ethtool --set-eee eth0 eee off