From owner-freebsd-bugs@freebsd.org Mon Jan 16 03:50:24 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 920C1C65189 for ; Mon, 16 Jan 2017 03:50:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 81D271BB7 for ; Mon, 16 Jan 2017 03:50:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0G3oO6N019770 for ; Mon, 16 Jan 2017 03:50:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 216130] Installer: Network: breaks if cancelled Date: Mon, 16 Jan 2017 03:50:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: eekee57@fastmail.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2017 03:50:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216130 Bug ID: 216130 Summary: Installer: Network: breaks if cancelled Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: eekee57@fastmail.fm Created attachment 178944 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178944&action= =3Dedit ifconfig Hi, I'm just installing FreeBSD for the first time. I ran into a bug in the installer; in network setup. The installer is the one on this image: FreeBSD-11.0-RELEASE-i386-dvd1.iso The machine is Qemu; a simple setup with one virtio network interface and Qemu's 'soft' networking which provides a DHCP server.(*) The bug is there's no way to cancel ipv6 setup without leaving ipv4 setup in an inconsistent state, if you first chose DHCP for IPv4. I suspect the fix is fairly simple: when an interface is chosen for configuration, if there's a DHCP client on that interface, shut it down at that point. Here's what I did: I first chose to set up ipv4 with dhcp, then when asked "Would you like to configure IPv6 for this interface", I chose "Yes". I know very little about IPv6, I was just curious to see if autoconfiguration would succeed; it might be nice to have it. I answered "Yes" to the next question too, "Would you like to try SLAAC...?" I guess it failed, because after a little delay, "Resolver Configuration" popped up with a lot of blank fields. I had no idea what to enter, so I pressed escape. This took me back to the beginning of network configuration. (That's a good choice; jumping straight to the next component would have confused me.) I again requested IPv4 be set up with DHCP. This time, it responded with "DHCP lease acquisition failed," repeating this message if I tried for DHCP again. The only way forward was to say "No" to DHCP. I cancelled static setup and resolver configuration, and cancelled the network configuration too. At the Final Configuration menu I selected network, again choosing DHCP, and again the response was, "DHCP lease acquisition failed." In the installed system (after reboot), the interface is active but has no ip address. Using nc to make connections to port 80 on various machines fails silently if given an ip address, hostnames are "not known". Screenshot attached, "ifconfig". I have a VM image just for this bug, so if you want to see any config files before I change anything at all, I can extract them from it. (*): I always install to a virtual machine before installing to real hardware. It's a safe environment in which to find which Typical Installer Bugs I'm going to run into, such as this one. :) I'm glad I only found the one. I've used many far worse installers years ago, declared to be "easy to use" but full of bugs and stumbling blocks. --=20 You are receiving this mail because: You are the assignee for the bug.=