@guyd2 

The log comes from the router. It is a new feature added to the Omada V5.15 which tons of users requested on the forum for a more granular and detailed log for everything like DHCP. 

More detailed log will come to the future Omada Controller.

The majority of these logs are not concerning or useful for most users. It can serve a diagnosis purpose unless you know what you need to distill from them. 

I am not sure how accurate your script is. 

If you could provide more details and monitor the actual connectivity on these mentioned, and "problematic" devices. I don't think that would be a concern unless this part has bee confirmed and verified. 

  @Clive_A 

 

Thank you for your kindly reply.

1. It it possible to disable this log feature ?

2. After exported logs to CSV file, I filter to certain IP, and I witness 2 major issues(see attached image):

• One IP (Android TV), connected using cable holds 40% of all entries. It has a 1 minutes apart. Do you have any guess why is it ?
• Some entries of same IP happens in seconds apart. Is it still expected behaviour of DHCP server ?

 

Regarding my Python script - I can share it if you want.

In general - it pings APs and Switch every few seconds.

 

Appreciate any thought/ lead.

 

Guy

 

 

  @guyd2 

guyd2 wrote

  @Clive_A 

 

Thank you for your kindly reply.

1. It it possible to disable this log feature ?

2. After exported logs to CSV file, I filter to certain IP, and I witness 2 major issues(see attached image):

• One IP (Android TV), connected using cable holds 40% of all entries. It has a 1 minutes apart. Do you have any guess why is it ?
• Some entries of same IP happens in seconds apart. Is it still expected behaviour of DHCP server ?

 

Regarding my Python script - I can share it if you want.

In general - it pings APs and Switch every few seconds.

 

Appreciate any thought/ lead.

 

Guy

 

 

 

1. You should Wireshark and see how the TV reacts to the DHCP.

I don't have a guess on that. I am not responsible for any other products and I don't know how they work. I only know the DHCP would work fine on the Omada gears most of the time. 

2. Note this, the DHCP requires two parts to work together. The DHCP server and the DHCP client. You cannot call the server a problem before you verify the behavior of the client is normal. 

For anything else, in networking, it is likewise. 

3. The python script is a simple ping test to the clients. Do you read the actual results or the debug log of it? If the pinged device is a wireless one, it could lose a packet. It does not mean it is a problem with the DHCP server. 

If there is a delay, or you set the ping with certain parameters, and it is delayed in responding, it would be considered a loss. 

But that does not mean anything for a DHCP server. It assigns the IP and that's it. The rest of the network interaction does not involve too much of the DHCP. 

  @Clive_A 

 

1. OK - I'll have to lear a bit how to work with it.

2. Totaly understood. I have to say that set it to static (on TV side), stopped DHCP re-allocation.

3. I ping only APs (that are wired). Networrk tools (part of Omada's interface) verified that all cable are as needed (in case that you still don't rely on the end device that verifies that all, including shielding was OK). 

 

Attached ping function. Feel free to advice.

 

 

my concern is that some disconnects happen.

 

Best,

Guy

Can you please construct how to disable logging that specific entries ?