Networking Forums

Networking Forums > Computer Networking > Linux Networking > Problem bringing up network interfaces with slackware

Reply
Thread Tools Display Modes

Problem bringing up network interfaces with slackware

 
 
Madhusudan Singh
Guest
Posts: n/a

 
      08-09-2004, 07:54 AM
Hi

An excerpt from my modules.conf :

alias eth0 dmfe
alias eth1 hostap_pci
post-install eth1 ip link set wlan0 name eth1
alias ppp0 ppp_generic

I am new to Slackware (running ver 10). I can't seem to find the ifup
scripts that I was used to under RH and Debian(?).

Upon bootup, I find that the only interface up is lo. If I do a modprobe
dmfe, it brings up eth0 and gets a DHCP lease (where is the lease stored -
I do not see a /var/lib/dhcp directory ?). However, modprobe hostap_pci
does not seem to bring up eth1.

How do I automate activation of these interfaces at boot time (some place
where I can put in an "onboot=yes" type of option) ?

Thanks.


 
Reply With Quote
 
 
 
 
Clifford Kite
Guest
Posts: n/a

 
      08-09-2004, 02:20 PM
Madhusudan Singh <spammers-go-(E-Mail Removed)> wrote:

> An excerpt from my modules.conf:


> alias eth0 dmfe
> alias eth1 hostap_pci
> post-install eth1 ip link set wlan0 name eth1
> alias ppp0 ppp_generic


> I am new to Slackware (running ver 10). I can't seem to find the ifup
> scripts that I was used to under RH and Debian(?).


Slackware has always used boot initialization scripts in the BSD
style, a simpler and more hands on approach that SysV style scripts.
I know RH uses SysV and wouldn't be surprised that Debian does too.
There should be a script rc.sysvinit (AFAIK new to Slackware) for 10.0
in /etc/rc.d that will confirm this. There is no ifup script.

> Upon bootup, I find that the only interface up is lo. If I do a modprobe
> dmfe, it brings up eth0 and gets a DHCP lease (where is the lease stored -
> I do not see a /var/lib/dhcp directory ?). However, modprobe hostap_pci
> does not seem to bring up eth1.


Try looking in /etc for DHCP configuration files and in /var/state
for lease files.

> How do I automate activation of these interfaces at boot time (some place
> where I can put in an "onboot=yes" type of option) ?


The necessary on-boot network configurations are usually put in
/etc/rc.d/rc.inet1. AFAIK there is no configuration file for an
"onboot=yes," you must configure the /etc/rc.d files correctly
to get anything configured on-boot. E.g., rc.inet1 is called from
rc.M, which in turn is called by /etc/inittab for run levels 2345.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* "PPPoE has many advantages for DSL service providers, and
practically none for DSL consumers."
- David F. Skoll */
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 10.1 and BCM4401 nic problem Leo Linux Networking 0 03-14-2005 05:03 PM
iptables problem (two network interfaces) crowl Linux Networking 1 07-04-2004 11:22 AM
Slackware 9.1- secondary IP problem Matt Linux Networking 3 06-23-2004 11:03 PM
slackware 9.0 ppp problem Stojan Linux Networking 0 05-27-2004 12:26 AM
weird network problem with slackware Mark Linux Networking 0 09-28-2003 07:52 PM



1 2 3 4 5 6 7 8 9 10 11