mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-05-19 10:58:08 +02:00
5a7b83ea0a
Currently if an error is encountered during a send() of a message, the client fails and there is no possibility of recover, since no timers are armed after a failed event dispatch. An easy way to reproduce a failure is to add a firewall rule like: iptables -A OUTPUT -p udp --dport 67 -j REJECT which makes the send() fail with EPERM during the renew. In such case, the client should continue (failing) until it reaches the rebind phase at T2, when it will be able to renew the lease using the packet socket. In general, a failure to send a packet should not cause the failure of the client. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/419 https://bugzilla.redhat.com/show_bug.cgi?id=1806516 |
||
|---|---|---|
| .. | ||
| util | ||
| libndhcp4.sym | ||
| meson.build | ||
| n-dhcp4-c-connection.c | ||
| n-dhcp4-c-lease.c | ||
| n-dhcp4-c-probe.c | ||
| n-dhcp4-client.c | ||
| n-dhcp4-incoming.c | ||
| n-dhcp4-outgoing.c | ||
| n-dhcp4-private.h | ||
| n-dhcp4-s-connection.c | ||
| n-dhcp4-s-lease.c | ||
| n-dhcp4-server.c | ||
| n-dhcp4-socket.c | ||
| n-dhcp4.h | ||
| test-api.c | ||
| test-connection.c | ||
| test-message.c | ||
| test-run-client.c | ||
| test-socket.c | ||
| test.h | ||