Mick <michaelkintz...@gmail.com> writes: > On Saturday 03 Aug 2013 06:52:46 Harry Putnam wrote: >> I was off gentoo for a few mnths... apparently something has changed >> in the naming of the network devices. >> >> So far I've read several accounts of it... but the install handbook >> has apparently not been brought up to date. >> >> Doing a fresh install, and following the contents of the manual >> concerning conf.d/net... is not working, of course. >> >> Renaming the device in /etc/init.d to net.enp0s3 and using that name >> in conf.d/net doesn't work either. At least not during boot. >> >> I can start the network by hand with /etc/init.d/net.enp0s3 start >> >> No problems there. But what, exactly, is supposed to go in >> conf.d/net? >> >> I've found quite a lot of confusing information on google but not a >> solution that works for me. >> >> If I start the network by hand as above then things like sshd blow up >> from trying to restart them again and using the wrong names. >> >> Can someone point me to concise documentation about how this new setup >> is supposed to work? > > In /etc/conf.d/net you should replace the previously named eth0 > directives to your new NIC name, e.g. instead of: > > config_eth0="dhcp" > > you will use the new name: > > config_enp0s3="dhcp" >
Well, yeah, thanks. Of course, that was the first thing I tried... and it does start the interface. >From /etc/conf.d/net: ,---- | # config_eth0="192.168.1.22 netmask 255.255.255.0 brd 192.168.1.255" | # routes_eth0="default via 192.168.1.1" | | config_enp0s3="192.168.1.22/24" | routes_enp0s3="default via 192.168.1.1" `---- However any attempt to start sshd tries to call eth0 instead of enp0s3. But I finally discovered I still had an net.eth0 in /etc/init.d... once I removed that, leaving only net.enp0s3... it all began to work... Thanks again.
