Remote logging from OC200 to Synology NAS issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Remote logging from OC200 to Synology NAS issues

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Remote logging from OC200 to Synology NAS issues
Remote logging from OC200 to Synology NAS issues
2022-09-08 19:55:46
Model: OC200  
Hardware Version: V1
Firmware Version: 5.5.7

I started remote logging from my OC200 to my Synology NAS 920+

 

I am getting some information but it does not appear to contain everything.  The 1st part of the log is cut off (MAC address or hostname) so I am not sure who is connecting or disconnecting from the network. 

 

 

Date Time Level Host Name Category Program Messages
2022-09-08 19:21:27 Info OC200_57B070 local1   is connected to [ap:AP_Basement:E4-C3-2A-E5-A5-A8] with SSID "snorky2" on channel 1.
2022-09-08 19:20:52 Info OC200_57B070 local1   is disconnected from SSID "snorky2" on [ap:AP_Basement:E4-C3-2A-E5-A5-A8] (27m connected, 96.73KB).
2022-09-08 18:56:17 Info OC200_57B070 local1   is roaming from [ap:AP_LivingRoom:28-EE-52-44-C9-E6][Channel 6] to [ap:AP_Basement:E4-C3-2A-E5-A5-A8][channel 153] with SSID snorky2
2022-09-08 18:47:45 Info OC200_57B070 local1   is connected to [ap:AP_Basement:E4-C3-2A-E5-A5-A8] with SSID "snorky2" on channel 1.
2022-09-08 18:47:45 Info OC200_57B070 local1   was disconnected from network "HOME-VLAN-30" on [osw:SW_LivingRoom:C0-06-C3-F2-60-60](connected time:16m connected, traffic: 0Bytes).
2022-09-08 18:47:35 Info OC200_57B070 local1   is connected to [osw:SW_LivingRoom:C0-06-C3-F2-60-60] on HOME-VLAN-30 network.
2022-09-08 18:45:22 Info OC200_57B070 local1   is disconnected from SSID "snorky2" on [ap:AP_LivingRoom:28-EE-52-44-C9-E6] (8m connected, 15.47KB).
2022-09-08 18:31:26 Info OC200_57B070 local1   is connected to [ap:AP_LivingRoom:28-EE-52-44-C9-E6] with SSID "snorky2" on channel 6.
2022-09-08 18:25:52 Info OC200_57B070 local1   is disconnected from SSID "snorky2" on [ap:AP_LivingRoom:28-EE-52-44-C9-E6] (17m connected, 60.06KB).
2022-09-08 18:03:46 Info OC200_57B070 local1   is connected to [ap:AP_LivingRoom:28-EE-52-44-C9-E6] with SSID "snorky2" on channel 6.
2022-09-08 18:03:46 Info OC200_57B070 local1   was disconnected from network "HOME-VLAN-30" on [osw:SW_LivingRoom:C0-06-C3-F2-60-60](connected time:31m connected, traffic: 0Bytes).
2022-09-08 17:59:13 Info OC200_57B070 local1   is connected to [osw:SW_LivingRoom:C0-06-C3-F2-60-60] on HOME-VLAN-30 network.
2022-09-08 17:57:52 Info OC200_57B070 local1   is disconnected from SSID "snorky2" on [ap:AP_LivingRoom:28-EE-52-44-C9-E6] (27m connected, 181.20KB).

 

I am also seeing a syslog that the Synology cannot properly process.

 

Date Time Level Host Name Category Program Messages
2022-09-08 14:04:23 Error 192.168.0.10 syslog syslog-ng Error processing log message: <142>1 2022-09-08T18:04:22.867Z OC200_57B070 - - - [client:Yoga Book:48-88-CA-98-8F-8>@<3] is disconnected from SSID "snorky2" on [ap:AP_Basement:E4-C3-2A-E5-A5-A8] (6h5m connected, 34.06MB).

 

 

I have my Synology set up to capture IETF formatted information. @Fae perhaps you can determine why my syslog server is not liking what the OC200 is sending.  No other devices I monitor for SYSLOG has this issue so I think it may be a formatting issue with how the OC200 is putting out SYSLOG data on UDP 514.  

 

I never realy paid too much attention to them but now I want to see how the network is behaving due to the recent upgrades that I performed on the hardware.  

 

  0      
  0      
#1
Options
4 Reply
Re:Remote logging from OC200 to Synology NAS issues
2022-09-09 09:55:36

  @Fleegle61 

 

What is your syslog software specifically?
What is the software that reads the information from the table you provided?

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Remote logging from OC200 to Synology NAS issues
2022-09-09 12:18:35

  @Virgo Synology has their own suite of tools built into the NAS.  The app is called LOG CENTER.  It allows for me to receive syslog entries either IETF or BSD.  I also have the option to set up a custom format provided I know what that format is. 

 

I would need to know from other Synology users what format they use or, if TP-LINK has a special format and if so, what is the syntax so that I can add that to my syslog server and get the messages in the proper format.  

 

RIght now I am just playing with the BSD format but usually, most sends would want to use the IETF format (Internet Engineering Task Force)

  0  
  0  
#3
Options
Re:Remote logging from OC200 to Synology NAS issues
2022-09-14 06:38:15

  @Fleegle61 

 

You can try port mirroring and grabbing the packets with wireshark to see what's going on.
You should be able to see what format or syntax tplink is using by grabbing the packets with the protocol "syslog". I remember that syslog packets are not encrypted.

Just striving to develop myself while helping others.
  0  
  0  
#4
Options
Re:Remote logging from OC200 to Synology NAS issues
2022-09-14 17:34:10

  @Virgo Right now I have the NAS set to BSD and it appears to be receiving properly formatted information.  I will be changing that to IETF to see if I start to see the errors.  Thats the only 2 canned options the NAS provides for.  I can do customer but I would need TP-Link to tell me what their formatting is. 

 

Unfortunately Synology does not provide for multi-protocol so that I could receive from different devices using different formats.  Its more of you set Synology to one format and tell everyone else to use that format to send to Synology..

 

Testing continues.......

  0  
  0  
#5
Options