Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Currently, I have a media PC running Ubuntu 10.04 that I am trying to connect via a wired network cable directly to a NAS box, and wirelessly to the router.

This works no problem after I run sudo /etc/init.d/networking restart but I can't get both interfaces to come up on system startup.

My /etc/network/interfaces file reads as follows:

auto eth0
iface eth0 inet static
    address 10.0.1.2
    netmask 255.255.254.0
    broadcast 10.0.1.255
    network 10.0.1.0

auto wlan2
iface wlan2 inet dhcp

As I say, I know this works, because I can get it to work by restarting the network interfaces, but I can't bring them both up on system startup. Does anyone know why this might be?

share|improve this question

closed as off-topic by MDMarra, Falcon Momot, Michael Hampton Jan 5 at 23:44

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – MDMarra, Falcon Momot, Michael Hampton
If this question can be reworded to fit the rules in the help center, please edit the question.

1  
You say "you can't bring them both up on system startup"... so what does happen on system startup? –  pjz May 27 '10 at 18:01
    
It brings up the wired interface only. –  Gary Chambers May 29 '10 at 13:56
    
What address does wireless network have? If wired and wireless networks are bridged then that might be an issue. –  0xFF Oct 22 '11 at 10:12
    
Did you ever resolve this problem? –  Chris S Feb 20 '13 at 14:37

1 Answer 1

System startup just calls 'ifup -a' ; does this work correctly (bringing them both up) after the system has started?

  • If not, figure out why.
  • If so, then the issue may be that an interface (like the wifi interface) may not be ready for configuration immediately upon startup ; one solution might be to put in a delay with something like 'pre-up sleep 5' under the wlan2 iface entry.
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.