[Bug 241792] dhclient/dhclient-script: dhclient default route not working when given a /32 netmask
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 05 Oct 2022 10:25:59 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241792 --- Comment #3 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=fd6ecc184dbc64b9b3f7866b34812fb93df62925 commit fd6ecc184dbc64b9b3f7866b34812fb93df62925 Author: Kristof Provost <kp@FreeBSD.org> AuthorDate: 2022-10-05 10:11:07 +0000 Commit: Kristof Provost <kp@FreeBSD.org> CommitDate: 2022-10-05 10:24:31 +0000 dhclient-script: cope with /32 address leases On certain cloud platforms (Google Cloud, Packet.net and others) the DHCP server offers a /32 address. This makes adding the default route fail since it is not reachable via any interface. Linux's dhclient-script seem to usually have a special case for that and explicitly adds an interface route to the router's address. FreeBSD's dhclient-script already has a special case for when the router address is the same as the leased address. Now also add one for when it's a different address that doesn't fall in the interface's subnet. PR: 241792 Event: Aberdeen hackathon 2022 Submitted by: sigsys@gmail.com Reviewed by: dch, kp, bz (+1 on the idea, not reviewed), thj MFC after: 1 week sbin/dhclient/dhclient-script | 4 ++++ 1 file changed, 4 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.