[SOLVED] how to stop automatically bringing up a network interface at boot
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
how to stop automatically bringing up a network interface at boot
Hi!
So far when I boot Slackware(-current) it brings up all my network devices.
Can I configure it somehow to not bring up any network interface at boot, so I can manually enable them (be it wireless or wired)?
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
chmod -x /etc/rc.d/rc.inet1
The problem with this is that /etc/rc.d/rc.inet1 also brings up the loopback interface with 127.0.0.1. I don't think it's a good idea to not have this in place. If you must keep all interfaces down I think you'd be better editing /etc/rc.d/rc.inet1.conf to remove both DHCP and static IP assignments which will keep the interfaces down.
Can he just turn it off on rc.local, like adding /etc/rc.d/rc.inet1 eth0_stop? Same for dhcpd and IP? I think he'll need loopback (127.0.0.1) locally, but it's not mandatory. My newbiness keeps bugging me with direct messing with rc.inet1, as for most time I just edited rc.inet1.conf...
Distribution: Gentoo (all servers at work are openSUSE)
Posts: 6,938
Rep:
Quote:
Originally Posted by danielldaniell
Hi!
So far when I boot Slackware(-current) it brings up all my network devices.
Can I configure it somehow to not bring up any network interface at boot, so I can manually enable them (be it wireless or wired)?
If that is your goal, perhaps wicd is what you'd prefer to use.
Be sure to read README.SLACKWARE so you set it up properly.
Once wicd is running, you can tell it to automatically connect,
or not to do so.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Can he just turn it off on rc.local, like adding /etc/rc.d/rc.inet1 eth0_stop?
Yes he could add "/etc/rc.d/rc.inet1 stop" to send them all down but it just seems a little strange sending them up - waiting for DHCP (if that's how the interfaces are set up) and then sending them down again ! Maybe, as Bruce Hill says, wicd is the way to go. There are lots of ways to control this - Slackware never forces you into one way of doing things !!
Perhaps I'm missing something, but can't one just edit /etc/rc.d/rc.inet1.conf and set IPADDR, NETMASK and USE_DHCP to "" for each network interface?
I believe that will activate loopback and nothing else. Then one could use WICD or the like to manage the interfaces.
My $0.02
Unfortunatelly, this is not working for me. I've added both my eth0 and wlan0 device (with IFNAME) and left everything empty, but during boot, both of my devices are coming up.
What doesn't work?
What happens and what did you want to happen?
Edit /etc/rc.d/rc.inet1.conf is the right way because you still need the loopback device.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
Unfortunatelly, this is not working for me. I've added both my eth0 and wlan0 device (with IFNAME) and left everything empty, but during boot, both of my devices are coming up.
This is the standard way of doing things. The interface will not be brought up unless /etc/rc.d/rc.inet1.conf has USE_DHCP[x]="yes" or IPADDR[x]="An.ip.address.set" where [x] is interface number "An.ip.address.set" is an IP address, obviously.
Note that you do not need IFNAME set for eth0 - just setup the IPADDR[0] stanza as the [0] implies eth0.
Perhaps you mean the devices themselves being detected - this is not what's usually termed "coming up". This is a setting on the device when it is put into an active state via /sbin/ifconfig (or other means). This is indicated when you run /sbin/ifconfig -a by an "UP" flag against the device.
Please - if you haven't already - check out Alien Bob's page on this subject and all will be revealed.
Despite of this, on every boot, the wlan0 device will come up, which means:
$ ifconfig wlan0
wlan0 Link encap:Ethernet
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)
How can I stop this behavior, and keep the wlan interface down?
(I'm not using wicd)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.