@gooksin
Its a bit two sides off a coin, I might use the dnsmasq to serve DHCP service, but don't want to use the DNS because I wanted the Bind9 do this job for me.
That means the dnsmasq will listen for dhcp requests, not start without any purpose from libvirt.
And, no I havedn't set dns enable="no" but give that a try.
This works but I run in an other pitfall:I solved this by add LIBVIRT_XXX to my firewall rules.
Now I can say problem is solved. (Still left a bad taste in my mouth, that a rolling release update from same Major changes the runtime behavior, and break a system runs for 6 Years with the legacy config!)
-Chis
Its a bit two sides off a coin, I might use the dnsmasq to serve DHCP service, but don't want to use the DNS because I wanted the Bind9 do this job for me.
That means the dnsmasq will listen for dhcp requests, not start without any purpose from libvirt.
And, no I havedn't set dns enable="no" but give that a try.
This works but I run in an other pitfall:
Code:
error: Failed to start network VN_NET1error: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr1 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name.Now I can say problem is solved. (Still left a bad taste in my mouth, that a rolling release update from same Major changes the runtime behavior, and break a system runs for 6 Years with the legacy config!)
-Chis
Statistics: Posted by ruehlchris — 2025-01-20 02:31