Date: Sun, 12 Dec 2021 10:10:24 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 260353] net/dual-dhclient: incapable of resolving IPv4 DHCP response correctly Message-ID: <bug-260353-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260353 Bug ID: 260353 Summary: net/dual-dhclient: incapable of resolving IPv4 DHCP response correctly Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: cperciva@FreeBSD.org Reporter: ohartmann@walstatt.org Flags: maintainer-feedback?(cperciva@FreeBSD.org) Assignee: cperciva@FreeBSD.org On notebooks running 13-STABLE within a dual stack network, we use the port net/dual-dhclient. In /etc/rc.conf the replacement according to instructions on how to use net/dual-dhclient has been made according to: [...] #dhclient_program=3D"/sbin/dhclient" # Path to dhcp client program. dhclient_program=3D"/usr/local/sbin/dual-dhclient" dhclient_flags=3D"" # Extra flags to pass to dhcp client. This doesn't work as expected. In almost every scenario, network we hooked = up to and every network config, this port misses the IPv4 offers of the DHCP server when it comes to DNS. /etc/resolv.conf then only contains the line "nameserver "IPv6-address" - noting more. The DHCP's domain or search offering and in 9 of 10 cases the = IPv4 nameservice is missing.=20 The IPv4 itself is properly received and applied to the appropriate NIC - s= ame with IPv6. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260353-7788>