Quality of life question

RouterOS General
1

Okay, it’s not a “quality of life” question but rather a “how do I put a bandaid so I don’t feel this tiny thorn in my back side” question.

I have an IoT device (oil tank level monitor) that very (very!) frequently disconnects and reconnects.

This process and the associated DHCP lease assignment creates these log entries:
Screenshot 2025-02-18 064553.png
I don’t want to see them in my log, but I want to continue to log the INFO topic.

These are the /system/logging settings:

/system logging
set 0 disabled=yes
add topics=event
add topics=account
add topics=firewall
add disabled=yes topics=interface
add disabled=yes topics=ssh
add disabled=yes topics=wireguard
add topics=watchdog
add disabled=yes topics=wireless
add topics=info
add topics=ups

Is there a way to prevent these specific log entries from being logged?

Of course, better if this device didn’t disconnect/connect so frequently, but I don’t think anything can be done about that.

Thanks.

2

To make your “life better” half of that logs could be avoided assigning static IP to the device :slight_smile:

3

Oh, I was going to say, there is lots of room up here if you want to move to Canada and improve your quality of life! :slight_smile:

4

I do not believe there is a way to set a static IP on this device.

If you mean a statically assigned (i.e., remembered) IP handed out by the DHCP server, it already has that.

Screenshot 2025-02-18 101241.png

5

NY is plenty cold enough.

6

Is the behavior normal: Whenever a wifi client disconnects and reconnects, even though the DHCP server sees the assigned (or dedicated or even static) IP, both the wifi dis- and re- connect as well as the DHCP assignment will be logged under topic INFO?

Anything I can do to exclude a single client?

7

By definition DHCP client has to assume network change when connection droos (even by s fraction of a second). So it’ll do it’s job.

When it comes to logging: I don’t think it’s possible to configure logging so that it ignores certain device (e.g. certain MAC address) … but IIRC it’s possible to filter out such logs when print-ing log (but don’t ask me how … real men don’t read logs :laughing:)

8

Makes sense: Network drops, DHCP client needs to make sure it has IP.

I wanna be an extra real man: How do I make full use of logs? (If you say use a log analytics tool, I’ll settle for just-shy-of-a-real-man.)

9

Personally I just read logs whenever happens anything I feel I need to investigate. If I manage to get around the time line, then usually there are not too many log entries around that time so I tend not to filter out anything. Sometimes this proves crucial as things tend to happen in some sequence and the starting event isn’t necessarily from the same general category as the one which triggers my interest.

10

maybe it is disconnecting due to maintaining low power consumption ?

11

I have IoT stuff at home connecting/disconnecting like every 5 to 10 minutes. Somewhere between those intervals. Really small packets to some server I could link to the supplier.
Another device toggles it’s network connection every hour, on the clock.

I simply don’t look at it … those things are on a separate isolated VLAN anyhow where they can only get out and nothing else.

12

Yes, I think that is mostly likely the reason, and it would be by design of the manufacturer.

13

Makes sense.

I’ll continue to ignore the packets (infinitely easier than setting up VLANs).