Date: Mon, 18 Jan 2016 16:00:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-sysinstall@FreeBSD.org Subject: [Bug 206355] Installer interferes with manual network setup, preventing netinstall from succeeding Message-ID: <bug-206355-2920-BnlrN1iC5N@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206355-2920@https.bugs.freebsd.org/bugzilla/> References: <bug-206355-2920@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206355 --- Comment #3 from Allan Jude <allanjude@FreeBSD.org> --- (In reply to Sevan Janiyan from comment #2) "But the installer is incapable of adding the route back in for the gateway= in this scenario. As the gateway IP address is in another subnet, you first ne= ed a route to reach the gateway IP address before you are able to use that IP address as the default gateway." We probably should do this, but for now, you'd just say 'no' when asked to configure the network and let it keep using your existing configuration. I would first like to focus on how/why your resolv.conf was getting clobber= ed. It looks like both 'auto' and 'script' entirely remove /tmp/bsdinstall_tmp = when they start, and since /etc/resolv.conf is a symlink to /tmp/bsdinstall_tmp/resolv.conf on the boot media, this is where things are going wrong. I suppose it could backup resolv.conf if it exists first, then restore it. --=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-206355-2920-BnlrN1iC5N>