Date: Sun, 30 May 2004 16:00:42 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Marco Beishuizen <marco@beishuizen.info> Cc: FreeBSD questions mailing list <questions@freebsd.org> Subject: Re: ifconfig in rc.conf network problems Message-ID: <20040530155610.B72548@wonkity.com> In-Reply-To: <Pine.BSF.4.60.0405302144360.29310@yokozuna.bsd> References: <Pine.BSF.4.60.0405302144360.29310@yokozuna.bsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 May 2004, Marco Beishuizen wrote: > I used to have two ifconfig lines in my rc.conf: > ifconfig_dc0="DHCP" > ifconfig_dc0="media autoselect" > > The first to enable DHCP and the second to set my networkcard to 100BaseTX > full duplex. Can rc.conf work that way? rc.conf is just a shell script, and you're assigning values to variables, so the second declaration would overwrite the first. As to why that would have worked for you... After dhclient runs successfully once, some of the information is kept on disk (resolv.conf, default route). Maybe it was enough? > Now after an upgrade to 4.10-release this doesn't work anymore. When I put > both lines in rc.conf only the second line is effective and overrides the > first, but I want to use both DHCP and 100BaseTX. I need to use the "media > autoselect" because the networkcard defaults to 10BaseT but I want to use > 100Mbit. When I don't use DHCP the network is unreachable. Pinging then gives > a "no route to host". There's an example of specifying media type in the dhclient.conf man page. -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040530155610.B72548>