Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
DHCP causes boot time to double, net.eth0 failed
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
West201
Tux's lil' helper
Tux's lil' helper


Joined: 22 Dec 2011
Posts: 115

PostPosted: Fri Feb 10, 2012 10:19 pm    Post subject: DHCP causes boot time to double, net.eth0 failed Reply with quote

I went from having a wired connection to wireless. I followed this wiki http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4, and I'm successfully able to use the internet via wireless network. Now when booting the computer I get the following messages.


Code:
no configuration specified switching to DHCP

This also comes up when booting
Code:
net.eth0 failed to start


Keep in mind I'm still able use the internet, it just slows down the boot time by 15-20 seconds

Code:
jesse # ifconfig
eth0      Link encap:Ethernet  HWaddr e0:69:95:c0:0e:fd 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:40 Base address:0xc000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:504 (504.0 B)  TX bytes:504 (504.0 B)

wlan0     Link encap:Ethernet  HWaddr ac:81:12:5f:41:bb 
          inet addr:192.168.1.66  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ae81:12ff:fe5f:41bb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15051 errors:0 dropped:10 overruns:0 frame:0
          TX packets:11511 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15529622 (14.8 MiB)  TX bytes:1622073 (1.5 MiB)


Code:
jesse # /etc/init.d/net.eth0 restart
 * Bringing up interface eth0
 *   No configuration specified; defaulting to DHCP
 *   dhcp ...
 *     Running udhcpc ...
No resolv.conf for interface eth0
No resolv.conf for interface eth0
 *     start-stop-daemon: failed to start `/bin/busybox'                                                                                                          [ !! ]
 * ERROR: net.eth0 failed to start
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23088

PostPosted: Sat Feb 11, 2012 1:04 am    Post subject: Reply with quote

What do you want to do? You have several options. You can have wired networking start only when a root-privileged user explicitly starts the interface, have wired networking start only when a carrier is detected, or maintain the current behavior of always starting DHCP. Additionally, you can get rid of the warning about the configuration if you specify how you want eth0 to be configured.

To make eth0 start only on request, remove it from the runlevel. To make eth0 start, but only acquire a lease if a carrier is present, emerge --noreplace --ask --verbose sys-apps/ifplugd or emerge --noreplace --ask --verbose sys-apps/netplug. Those are the names in the OpenRC documentation. I always have a wired link, so I have not tested them personally.
Back to top
View user's profile Send private message
West201
Tux's lil' helper
Tux's lil' helper


Joined: 22 Dec 2011
Posts: 115

PostPosted: Sat Feb 11, 2012 1:35 am    Post subject: Reply with quote

Hu wrote:
What do you want to do? You have several options. You can have wired networking start only when a root-privileged user explicitly starts the interface, have wired networking start only when a carrier is detected, or maintain the current behavior of always starting DHCP. Additionally, you can get rid of the warning about the configuration if you specify how you want eth0 to be configured.

To make eth0 start only on request, remove it from the runlevel. To make eth0 start, but only acquire a lease if a carrier is present, emerge --noreplace --ask --verbose sys-apps/ifplugd or emerge --noreplace --ask --verbose sys-apps/netplug. Those are the names in the OpenRC documentation. I always have a wired link, so I have not tested them personally.


Thanks for replying. I want a wireless connection (which I already have). But when I boot I get DHCP and net.eth0 messages. It doubles the boot time, even after removing dchcp and net.eth0 from the runlevel. I just want a wireless connection (only wireless), when I boot DHCP will display this "waiting for the carrier" (even after removing DHCP) for 10 seconds, then again for another 10 seconds.

Thanks for your help,
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23088

PostPosted: Sat Feb 11, 2012 4:07 am    Post subject: Reply with quote

What is the output of rc-update show -v ; cat -n /etc/conf.d/eth0 ; eix -I plug?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum