Hi,
I just got the Flint 3 and it’s a great improvement but i’m having major issues with my network switch.
I have 7 devices connected via a TP Link managed switch. All devices are using static IP and this shows correctly on the client list of the Flint 3. However, some devices will suddenly go offline, come back up either in a few minutes or around an hour later and other devices then repeat the same issue as if they are all taking it in turns.
Another issue is that some devices that show offline are sometimes still accessible from the LAN.
I have tried resetting the switch, switching ports and DCHP is disabled on the switch so everything should pass through to the router to deal with.
Has anyone had similar issues and hopefully a simple fix?
The “online/offline” status is not related to the Ethernet link status, but to the traffic from each client actually flowing through your Flint. If they’re not sending/receiving traffic through it, they’ll be shown as “offline.”
Are you actually having issues with the clients sending/receiving data through the flint or just making a post about what you are seeing on the flint?
As said above, it is due to how the traffic flows, also if the devices are set to static this happens more because clients function uses ARP to find online clients, however static clients do not use ARP anymore, this means it relies more on traffic activity from the client to the Flint 3 which can be a bit inaccurate measure, but it is by design.
1 Like
@xize11
Sorry, but this “static clients do not use ARP anymore“ is incorrect. ARP is used regardless how the IPv4 address is acquired (IPv6 doesn’t use ARP).
Perhaps you meant to say “static clients do not use DHCP anymore“?
Let me explain it differently:
It is static arp, where arp broadcasts no longer happen other than only once, that was what I ment to explain.
Just wrong wording.
Sorry, but it’s still wrong wording. There’s no such thing as “static ARP.” The term doesn’t exist.
ARP is by definition, a broadcast protocol, used by Ethernet hosts to associate IP addresses to MAC addresses.
I believe what you’re trying to describe is what’s known as an “ARP Probe,” or “gratuitous ARP”, where the sending host is trying to determine whether its assigned IP address may also be used by another host, in which case, it can’t use that IP, rendering it unable to function on the network. ARP broadcasts are also used to determine the MAC address for a default router IP address. The responses to both are cached for a period, then refreshed later, using the same message structure as was used initially.
Alright you are correct I have googled and I was mistaken, I have no interest to bother into this further.