search

richonguzman / LoRa_APRS_iGate

LoRa APRS iGATE for ESP32 Based Board with Rx + Tx capabilities
MIT License
208 stars 65 forks source link

Syslog messages don't show up in Visual Syslog Server nor WinSyslog #121

Closed davidebeatrici closed 3 months ago

davidebeatrici commented 3 months ago

Using WireShark I noticed unprintable characters and a wrong timestamp:

Possibly related: lora-aprs/LoRa_APRS_iGate#227

iw2ejh commented 3 months ago

what you see after CRC-ERROR are the data not correctly decoded by the LoRa Radio, it include any kind of characters as it is not parsed. These data are useful for debuging. If you notice, the station you are receiving is IK2UUJ and the level is -142dBm, very marginal. This CRC-ERROR is due to the location and distance, in other cases if you see the level higher it may be due to disturb or colision. You will see these message clearly in the syslog Virtualsyslog_2024-06-25 141339

davidebeatrici commented 3 months ago

Alright, that's what I thought.

According to your screenshot you're receiving the messages just fine in Visual Syslog Server. Is there anything that you had to change in the configuration? Perhaps the filters?

richonguzman commented 3 months ago

Alright, that's what I thought.

According to your screenshot you're receiving the messages just fine in Visual Syslog Server. Is there anything that you had to change in the configuration? Perhaps the filters?

I guess the problem with timestamp is on the syslog server more than on the igate firmware as it just uploads the log but the log does not push time to it. Its the syslog server that saves his own timestamp into the log.

davidebeatrici commented 3 months ago

Yeah, but ideally iGate should send its own timestamp. That way the Syslog server knows exactly (as long as the date/time is correct on the firmware) when the message was generated.

richonguzman commented 3 months ago

as far as I've tested and others told me, the timestamp is added on the syslog server side.

not on yours?

davidebeatrici commented 3 months ago

Right now I don't see any messages from iGate, but I'm pretty sure the timestamp is indeed added by the Syslog server.

However, appending the timestamp from the firmware's side would be useful as a reference, especially when there's high latency involved.

richonguzman commented 3 months ago

Right now I don't see any messages from iGate, but I'm pretty sure the timestamp is indeed added by the Syslog server.

However, appending the timestamp from the firmware's side would be useful as a reference, especially when there's high latency involved.

how much latency are you experimenting?

davidebeatrici commented 3 months ago

Nothing too extreme, but in certain environments it may be useful to know exactly when an event happens.

It's just a suggestion, not something I actually need.

richonguzman commented 3 months ago

will save this idea for later (when I add NTP server time to igate)

meanwhile I'll close it.

davidebeatrici commented 3 months ago

Sounds good!