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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Simply says unassociated, but I'll take it. I'll attempt to actually connect to my wireless network when I get home tonight. Thanks everyone, I really appreciate this. The inability to use my wireless connection before was why I abandoned Slackware in the past. If this works, I'll never switch again.
One question, how do I get both my wireless and wired connections working at once? The wireless card is grabbing eth0, so my wired connection won't work. Any way I can force the wireless, or wired, to eth1?
You could add 'alias eth1 <modulename>'
for your wired connection.
Now, take a look at /etc/rc.d/rc.inet1.conf
You'll find entries for each device
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
Simply change USE_DHCP[1] to yes and both should be brought up on boot via dhcp.
The hotplug module sees my intel (wired) ethernet bus, even if there is no cable connected to it.
It then loads the proper module for it (eepro100) and the eepro100 module
assigns it self to eth0.
ipw2100 then goes to eth1.
Normally, this should work straightforward.
Be sure that you have the hotplug module running.
(/etc/rc.d/rc.hotplug)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.