On 2023-04-30 12:18, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-04-30 11:42, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-04-30 08:46, Per Jessen wrote:
It's a dhcp client looking for a dhcp server - what to do with it is up to you, depends on your context.
But thinking aloud, what is best to do with them? And how?
You have to consider the context. Single machine that runs a dhcp server or not?
Only the router should manage dhcp.
So, can we conclude that this machine does _not_ run a dhcp server? If so, you have to ask why it should be interested in dhcp client broadcasts.
It wouldn't. I wasn't sure they were dhcp client broadcasts, though.
But in the past I found that I had to open dhcp port on some clients for dhcp assignment to work.
Yep, I would expect that to be true.
* if you need them, they should obviously be accepted.
I don't know if I need them.
In that case, you just drop them and wait for something to break.
Right.
* if you're not sure if you need then, reject but log
It's a lot of noise.
Is that a problem?
For me, yes! I don't like noise in the logs. Hate it, actually.
(resources are also disk space. I want logs only with important things, entries use *my* time.)
That makes sense, disk space is growing more and more expensive every day. The other day I saw Sfr14/Tb, that's outrageous.
:-DD You forget that each entry causes a sector write in an SSD, which has a limited life. >:-P And if it were rotating rust, it impedes the disk going to sleep ;-p
Can dropping them cause an issue for this machine?
I would ask the admin. :-)
The admin doesn't know.
systemctl polish crystalball
Ok. I'll try drop instead of accept. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)