Re: [systemd-devel] accepting dhcp address only from a specific mask

2025-06-04 Thread daggs
Looks like it is a systemd bug that was fixed in later versions, I've upgraded systemd and the issue didn't resisted Thanks for suggesting it Dagg > Sent: Tuesday, June 03, 2025 at 7:58 AM > From: "Andrei Borzenkov" > To: "daggs" > Cc: systemd

Re: [systemd-devel] accepting dhcp address only from a specific mask

2025-06-02 Thread daggs
> Sent: Monday, June 02, 2025 at 7:09 PM > From: "Andrei Borzenkov" > To: "daggs" > Cc: [email protected] > Subject: Re: [systemd-devel] accepting dhcp address only from a specific mask > > 02.06.2025 18:30, daggs wrote: > &

Re: [systemd-devel] accepting dhcp address only from a specific mask

2025-06-02 Thread daggs
/DUID  DHCPv6 Client DUID: DUID-EN/Vendor:ab11ea37c4793baab851     Sent: Monday, June 02, 2025 at 4:16 PM From: "Mantas Mikulėnas" To: "daggs" Cc: [email protected] Subject: Re: [systemd-devel] accepting dhcp address only from a specific mask The

Re: [systemd-devel] accepting dhcp address only from a specific mask

2025-06-02 Thread daggs
192.168.0.1 dev enp1s0 scope link src 192.168.0.10 metric 1024 > Sent: Monday, June 02, 2025 at 6:16 PM > From: "Andrei Borzenkov" > To: [email protected] > Subject: Re: [systemd-devel] accepting dhcp address only from a specific mask > > 02.06.2025 16:07

[systemd-devel] accepting dhcp address only from a specific mask

2025-06-02 Thread daggs
Greetings, I have a qemu vm which runs a systemd based buildroot image, the vm's nic is virtio, if I configure systemd to auto start the nic, I get two ips for the only nic on the system, a valid one and in invalid one. in this case, I can only connect to local lan but not outside of the last, I

[systemd-devel] triggering a remove handker manually via cmd

2023-06-04 Thread daggs
Greetings, given a rule file which has a add and remove handlers, is there a way to manually trigger the remove handler of that file? Thanks, Dagg

Re: [systemd-devel] udev rule, continue to next rule only if preb failed

2023-05-26 Thread daggs
Greetings, > Sent: Friday, May 26, 2023 at 12:02 PM > From: "daggs" > To: "Lennart Poettering" > Cc: [email protected] > Subject: Re: [systemd-devel] udev rule, continue to next rule only if preb > failed > > Greetings Lennart,

Re: [systemd-devel] udev rule, continue to next rule only if preb failed

2023-05-26 Thread daggs
Greetings Lennart, > Sent: Friday, May 26, 2023 at 11:23 AM > From: "Lennart Poettering" > To: "daggs" > Cc: [email protected] > Subject: Re: [systemd-devel] udev rule, continue to next rule only if preb > failed > > On Do,

[systemd-devel] udev rule, continue to next rule only if preb failed

2023-05-25 Thread daggs
Greetings, I'm trying to implement the following behavior: if a usb is added ot removed, run a script before all other existing rules but continue to existing iff the script failed I've added the following rule to /etc/udev/rules.d/5-usb_vm.rules: ACTION=="add", SUBSYSTEM=="usb", RUN="/usr/local/