Syslog probleme Bug

Syslog probleme Bug

Syslog probleme Bug
Syslog probleme Bug
Tuesday - last edited Tuesday
Tags: #Controller #bug
Hardware Version: V5
Firmware Version: 5.15.8.2 (Écurie)

Hello, I have been using Omada Controller for a long time, hosting on a Synology NAS. Before no problem, but since the update small problem with Syslog and SplunkHello, I have been using Omada Controller for a long time, hosting on a Synology NAS.

 

Before no problem, but since the update small problem with Syslog and Splunk

 

On some information everything is fine, and on others it's nonsense. Do you know if this comes from a Tplink bug?On some information everything is fine, and on others it's nonsense. Do you know if this comes from a Tplink bug?

 

OK :

 

PROBLEM :

Jan 14 18:36:19 172.17.0.1 1 2025-01-14 18:36:17 Omada SDN - - - {"details":{"newValue":"{\"id\":\"6786aea1add0154b5d69dedf\",\"idInt\":899668562,\"index\":4,\"name\":\"yhrherherh\",\"site\":\"6782e8ef1cda89425713863b\",\"wlanId\":\"6782e8f01cda894257138652\",\"band\":3,\"guestNetEnable\":false,\"security\":3,\"broadcast\":true,\"vlanEnable\":false,\"rateLimit\":{\"rateLimitId\":\"6782e9131cda8942571386b9\",\"downLimitEnable\":false,\"upLimitEnable\":false},\"ssidRateLimit\":{\"rateLimitId\":\"6782e9131cda8942571386b9\",\"downLimitEnable\":false,\"upLimitEnable\":false},\"pskSetting\":{\"versionPsk\":2,\"encryptionPsk\":3,\"gikRekeyPskEnable\":false},\"wlanScheduleEnable\":false,\"macFilterEnable\":false,\"rateAndBeaconCtrl\":{\"rate2gCtrlEnable\":false,\"rate5gCtrlEnable\":false,\"rate6gCtrlEnable\":false},\"enable11r\":false,\"pmfMode\":3,\"multiCastSetting\":{\"multiCastEnable\":true,\"channelUtil\":100,\"arpCastEnable\":true,\"ipv6CastEnable\":true,\"filterEnable\":false},\"mloEnable\":false,\"deviceType\":1}","oldValue":"null"},"operation":"New Wireless Network (SSID) yhrherherh created successfully."}

 

Big problem with formatting or sending Omada Controler

 

 

  0      
  0      
#1
Options
4 Reply
Re:Syslog probleme Bug
Wednesday

Hi @Yann77,

 

It's not nonsense, it's just JSON which is quite common and easier to parse (by machines) than traditional log files.  I assume this is what you're seeing in Splunk so you may need to either adjust the log ingestion formatters or the Splunk query that renders the data so it's more appealing to humans.  If you un-escape the quotes and it fails a JSON validation parser, then 'dI call it a bug, otherwise it's probably just a lagit log message.  (I tried parsing but I think some of the lines in the post were truncated.)

 

It appesr like this is logging the creation of a new SSID, so if you have an example of that type of log data in it's raw format before you applied the update, that would help TP-Link team determine if it's a bug or working as designed.

  0  
  0  
#2
Options
Re:Syslog probleme Bug
Wednesday - last edited Wednesday

Hi  @Yann77 

 

Please let us know what kind of configuration did you change at that time?

Better share with a screenshot. Thanks.

 

Also, please share with a screenshot of the the syslog settings page.

Wish you a happy life and smooth network usage! 
  0  
  0  
#3
Options
Re:Syslog probleme Bug
Wednesday

  @Vincent-TP Bonjour a tous , je ne sait pas dire en quelle version de omada controlleur j'avais avant mais c'etait pas du tout l'interface vert que j'ai maintenant.

Certains message recu sont normaux , d'autres ont une syntaxe non correct. donc possiblement un bug de TPLink puisque avant aucun soucis

Voici des exemples de mauvaise syntaxe recu

 

Jan 14 22:35:57 172.17.0.1 1 2025-01-14 22:35:55 Omada SDN - - - {"details":{"newValue":"{\"type\":0,\"wanPortSetting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"wanPortIpv4Setting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"proto\":\"dhcp\",\"vlanId\":100,\"supportQosTagEnable\":true,\"supportInternetVlan\":true,\"qosTagEnable\":false,\"vlanPriority\":0,\"ipv4Dhcp\":{\"unicast\":\"off\",\"mtu\":1500}},\"wanPortIpv6Setting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"enable\":1,\"proto\":\"bridge\"},\"wanPortMacSetting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"method\":\"set\",\"mac\":\"38-07-16-24-4D-D6\"}}}","oldValue":"{\"type\":0,\"wanPortSetting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"portName\":\"WAN2\",\"wanPortIpv4Setting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"proto\":\"dhcp\",\"protoType\":1,\"vlanId\":100,\"qosTag\":0,\"supportQosTagEnable\":true,\"supportInternetVlan\":true,\"supportDslMer\":false,\"qosTagEnable\":false,\"vlanPriority\":0,\"ipv4Dhcp\":{\"unicast\":\"off\",\"mtu\":1500}},\"wanPortIpv6Setting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"enable\":1,\"proto\":\"bridge\",\"protoType\":4},\"wanIpv6Comptent\":1,\"wanPortMacSetting\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\",\"method\":\"set\",\"mac\":\"38-07-16-24-4D-D6\"}}}"},"operation":"WAN WAN2 configured successfully."}

 

 

 

Jan 14 22:35:17 172.17.0.1 1 2025-01-14 22:35:15 Omada SDN - - - {"details":{"newValue":"{\"id\":\"6782e8f01cda894257138643\",\"site\":\"6782e8ef1cda89425713863b\",\"name\":\"Default\",\"purpose\":\"interface\",\"interfaceIds\":[\"1_eb2b73c1bb024207b7048c72f71d19cb\",\"3_c3493fe6e3ee48a88791660657045c92\",\"4_c08d18ef776b4a169268129d59cc4f44\",\"5_71e9bcb2ba61462cacff42789abac5e8\",\"6_8f60ec8fdfca4a89961ff861bdce122f\"],\"vlanType\":0,\"vlan\":1000,\"gatewaySubnet\":\"192.168.0.1/24\",\"dhcpSettings\":{\"enable\":true,\"ipRangePool\":[{\"ipaddrStart\":\"192.168.0.1\",\"ipaddrEnd\":\"192.168.0.254\"}],\"ipRangeStart\":3232235520,\"ipRangeEnd\":3232235775,\"dhcpns\":\"auto\",\"leasetime\":120,\"gateway\":\"192.168.0.47\",\"options\":[]},\"igmpSnoopEnable\":false,\"mldSnoopEnable\":false,\"dhcpv6Guard\":{\"enable\":false},\"dhcpL2RelayEnable\":false,\"dhcpGuard\":{\"enable\":false},\"lanNetworkIpv6Config\":{\"proto\":\"passthrough\",\"enable\":1,\"passthrough\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\"}},\"allLan\":false,\"interface\":true}","oldValue":"{\"id\":\"6782e8f01cda894257138643\",\"site\":\"6782e8ef1cda89425713863b\",\"name\":\"Default\",\"purpose\":\"interface\",\"interfaceIds\":[\"1_eb2b73c1bb024207b7048c72f71d19cb\",\"3_c3493fe6e3ee48a88791660657045c92\",\"4_c08d18ef776b4a169268129d59cc4f44\",\"5_71e9bcb2ba61462cacff42789abac5e8\",\"6_8f60ec8fdfca4a89961ff861bdce122f\"],\"vlanType\":0,\"application\":0,\"vlan\":1000,\"gatewaySubnet\":\"192.168.0.1/24\",\"dhcpSettings\":{\"enable\":true,\"ipRangePool\":[{\"ipaddrStart\":\"192.168.0.1\",\"ipaddrEnd\":\"192.168.0.254\"}],\"ipRangeStart\":3232235520,\"ipRangeEnd\":3232235775,\"dhcpns\":\"auto\",\"leasetime\":120,\"gateway\":\"192.168.0.46\",\"options\":[]},\"igmpSnoopEnable\":false,\"mldSnoopEnable\":false,\"dhcpv6Guard\":{\"enable\":false},\"dhcpL2RelayEnable\":false,\"dhcpGuard\":{\"enable\":false},\"lanNetworkIpv6Config\":{\"proto\":\"passthrough\",\"enable\":1,\"passthrough\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\"}},\"allLan\":false,\"interface\":true}"},"operation":"Lan Network Default edited successfully."}

 

Jan 14 22:22:36 172.17.0.1 1 2025-01-14 22:22:31 Omada SDN - - - {"details":{"newValue":"{\"id\":\"6782e8f01cda894257138643\",\"site\":\"6782e8ef1cda89425713863b\",\"name\":\"Default\",\"purpose\":\"interface\",\"interfaceIds\":[\"1_eb2b73c1bb024207b7048c72f71d19cb\",\"3_c3493fe6e3ee48a88791660657045c92\",\"4_c08d18ef776b4a169268129d59cc4f44\",\"5_71e9bcb2ba61462cacff42789abac5e8\",\"6_8f60ec8fdfca4a89961ff861bdce122f\"],\"vlanType\":0,\"vlan\":1000,\"gatewaySubnet\":\"192.168.0.1/24\",\"dhcpSettings\":{\"enable\":true,\"ipRangePool\":[{\"ipaddrStart\":\"192.168.0.1\",\"ipaddrEnd\":\"192.168.0.254\"}],\"ipRangeStart\":3232235520,\"ipRangeEnd\":3232235775,\"dhcpns\":\"manual\",\"priDns\":\"8.8.8.8\",\"sndDns\":\"8.8.4.4\",\"leasetime\":120,\"gateway\":\"192.168.0.46\",\"options\":[]},\"igmpSnoopEnable\":false,\"mldSnoopEnable\":false,\"dhcpv6Guard\":{\"enable\":false},\"dhcpL2RelayEnable\":false,\"dhcpGuard\":{\"enable\":false},\"lanNetworkIpv6Config\":{\"proto\":\"passthrough\",\"enable\":1,\"passthrough\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\"}},\"allLan\":false,\"interface\":true}","oldValue":"{\"id\":\"6782e8f01cda894257138643\",\"site\":\"6782e8ef1cda89425713863b\",\"name\":\"Default\",\"purpose\":\"interface\",\"interfaceIds\":[\"1_eb2b73c1bb024207b7048c72f71d19cb\",\"3_c3493fe6e3ee48a88791660657045c92\",\"4_c08d18ef776b4a169268129d59cc4f44\",\"5_71e9bcb2ba61462cacff42789abac5e8\",\"6_8f60ec8fdfca4a89961ff861bdce122f\"],\"vlanType\":0,\"application\":0,\"vlan\":1000,\"gatewaySubnet\":\"192.168.0.1/24\",\"dhcpSettings\":{\"enable\":true,\"ipRangePool\":[{\"ipaddrStart\":\"192.168.0.1\",\"ipaddrEnd\":\"192.168.0.254\"}],\"ipRangeStart\":3232235520,\"ipRangeEnd\":3232235775,\"dhcpns\":\"manual\",\"priDns\":\"8.8.8.8\",\"sndDns\":\"8.8.4.4\",\"leasetime\":120,\"gateway\":\"192.168.0.47\",\"options\":[]},\"igmpSnoopEnable\":false,\"mldSnoopEnable\":false,\"dhcpv6Guard\":{\"enable\":false},\"dhcpL2RelayEnable\":false,\"dhcpGuard\":{\"enable\":false},\"lanNetworkIpv6Config\":{\"proto\":\"passthrough\",\"enable\":1,\"passthrough\":{\"portUuid\":\"2_783636d670f0469995c38eb4e30cbaea\"}},\"allLan\":false,\"interface\":true}"},"operation":"Lan Network Default edited successfully."}

 

Jan 15 11:44:41 172.17.0.1 1 2025-01-15 11:44:41 Omada SDN - - - {"details":{},"operation":"General Settings edited successfully."}

  0  
  0  
#4
Options
Re:Syslog probleme Bug
Wednesday

@Yann77, I have an oc200 (2.17.6 Build 20241101 Rel.44787 (Stable)).  My syslogs generated similiar data but the details was just an empty string.

 

Ex: {"details":{},"operation":"Wireless Network (SSID) xxxxxxxx edited successfully."} 


The 5.14.32.4 Release notes mentions a change to the logging that seems to match what you're seeing so it's a new feature and not a bug. 

 

 

 

I was able to parse the json you posted w/o errors, so you should be able to omit the data in Splunk if you don't want to see it.  I actually like the ability to see exactly what changed.  The compare below is from your posted log message.

 

 

  0  
  0  
#5
Options