I bought a refurbished Thinkpad T400. This is my first laptop and first wireless device.

I am unable to get wireless to function. Problems likely are between my ears because I always have used static IP addresses in my home LAN and never before used NetworkManager or wireless.

In the beginning I configured rc.inet1.conf with the usual static IP address. No problems with a wired connection. I used only rc.inet1.conf for several days while I installed and tweaked Slackware 14.0.

Next I enabled rc.networkmanager, configured for a manual wired connection using the same static IP address as rc.inet1.conf.

NetworkManager always overwrites /etc/resolv.conf with an empty file. I found two clunky work-arounds: 1) a script (https://bbs.archlinux.org/viewtopic.php?id=45394) and 2) chattr +i. Yet I still had no problem connecting wired.

Next the great chasm, wireless.

The router is a Linksys WRT54GL 1.1. I'm using DD-WRT v24 preSP2. I have been using the router and DD-WRT for several years. I enabled the router wireless radio.

Nothing I did allowed me to ping when I pulled the cable and used only wireless, despite popup dialogs that the connection was established.

Help appreciated. I haven't been this confused in a long time. Please start with the basics.

Thanks.

are you sure you need to go Arch way? ubuntu should be easier on that task.

4 ways to get wifi working on linux

Thanks but I have no idea what you're talking about. This is the Slackware forum.

Perhaps you should revert rc.inet1.conf (and any other network configuration files) to their original states and let networkmanager or wicd do their jobs. Might there be some clashes? I might be wrong but I think you're overcomplicating things a bit. I've actually never used NetworkManager but have been using wicd for both wired and wireless connections for a long time. As long as the network card is detected, it should be as easy as this:

At this point a GUI program will pop up where you'll be able to choose your wifi network (edit the settings) and connect to it.

That's all I always do after installing a fresh Slackware system.

HTH.

On a separate note, make sure you've got the correct settings for DNS/Gateway etc.

You can issue "iwconfig" to list the wireless interfaces on your laptop.

Then try "iwlist <interface> scanning" to make sure your laptop wireless NIC is able to pick up your router's broadcast. For example, "iwlist eth1 scanning", if eth1 is your wireless interface. If you get nothing from iwlist, then check to make sure the laptop wireless radio is turned on. There's usually a hard switch or a special function key soft switch to toggle it on or off.

Make sure you have an active dhcp server somewhere on your network, probably on your router.

Verify your router's wireless access point is enabled and configured with an ssid and security keys (preferably wpa2).

There's more than one way to configure your wireless setup. Here is how I do it:

Turn off networkmanager and/or wicd. (I don't use them, so I don't know anything about them.) Edit rc.inet1.conf and set USE_DHCP(n) to "yes" for your wireless interface. Leave the other parameters null, except perhaps DHCP_HOSTNAME(n) if you want. Verify that you have the address of your gateway specified in the GATEWAY parameter.

Make sure /etc/rc.d/rc.wireless is executable.

In /etc/rc.d/rc.wireless.conf, make sure this section near the top is NOT commented out:

Configure any specific wireless settings pertinent to your network in /etc/wpa_supplicant.conf. Here is an example for a network with ssid "eatmorepizza":

Make sure the /etc/wpa_supplicant.conf is rw for root only.

Let me know if any of that helps.

2 members found this post helpful.

I ran netconfig to empty rc.inet1.conf and use NM. Rebooting with the cable pulled resulted in no network.

I tried wicd. I was successful once. After rebooting I could not again get wicd to connect.

I ran ifconfig to find three interfaces: eth0, lo, and wlan0.

I ran iwconfig and I see some information about wlan0.

I ran 'iwlist wlan0 scanning' and I receive a message the interface doesn't support scanning because the network is down.

I don't have the router configured that way. I always have used static IP addresses with my home LAN. Is there no way to use static IP addresses with wireless?

If I have to configure the router as a DHCP server, I want the laptop to use the same IP address wired or wireless. Is that possible?

Whether using NM, wicd, or rc.wireless, I don't want to login and start the desktop just to get wireless working. I have system scripts that need networking that I run in rc.local for auto updates of various system files. Whether the system is using wired or wireless I want those scripts to run before any logins. I want the laptop to use wired when available but to otherwise first look for wireless.

I haven't ever done that, but I think you can. Just specify the IP address in rc.inet1.conf in the IPADDR(n) parameter, set the NETMASK(n) for your network, and change USE_DHCP(n) to null or NO.

Yes, you can do that. You would set up the DHCP server to assign a particular IP address based on the MAC of the wireless NIC. If you decide you want to do that, I can give you an example dhcpd.conf. I run dhcpd on my desktop, not in my router, but the dhcp server on many of the routers I've used could be configured that way too.

On my Thinkpad T43, dhcpcd (note, not dhcpd the server, but rather dhcpcd, the client) runs sometime before rc.local and solicits an IP address from my dhcp server.

You don't have to start a desktop to have NM start your connection. I have a T510 and NM starts just fine when I boot. I use dispatcher.d to start some stuff, like mounting NFS shares, when booting. I know rc.nfs can do that, but I don't want it to try to mount on hostile networks. One thing I would look at, is firmware. What chipset are you using, and do you need to load any firmware for it? You can also try nmcli and see if you can see any of the networks.

Much of the configuring of the laptop has gone well, despite being my first laptop and me wanting to configure some special things because of the laptop's mobility. The last day and half trying to get wireless running has been mind numbing.

With the above responses I think I have something working. After I ran netconfig, which wiped the rc.inet1.conf (as somewhat hinted by sycamorex) and also wiped my /etc/hosts (not nice Pat ) I then disabled rc.wicd and re-enabled rc.networkmanager. With the cable pulled I rebooted and the wireless network now seems to be working, also with static IP addresses defined in NetworkManager.

So at least one problem would seem to have been a conflict between NM and rc.inet1? Is this written somewhere and I missed getting the memo?

I have rebooted a couple of times now, but I notice wireless seems to initialize in steps, or very slowly. When my rc.local attempts to run my auto updating scripts, they all fail. During that period the laptop wireless LED is blinking. After many seconds the LED goes solid. When the LED goes solid I then can manually run the same set of auto updating scripts.

Apparently I need some kind of wireless test before running the scripts in rc.local. Are there any programmatic ways to validate the wireless network is up and stable and not just initialized?

Related, how do I programmatically detect which interface the laptop is using (eth0/wlan0)?

Another question: should rc.inet1 be disabled when using rc.networkmanager?

RE: rc.inet1: Mine is still executable and I don't have any issues at all. Instead of testing for connection then running rc.local, check out /etc/NetworkManager/dispatcher.d.

Another question: iwconfig lists Bit Rate=1 Mb/s. Should that be 54 Mb/s or at least something close to that?

You missed the memo. From the email to root titled ' Welcome to Linux (Slackware 14.0)!'
As mentioned by manwichmakesameal, you can setup scripts in /etc/NetworkManager/dispatcher.d
For example: http://www.linuxquestions.org/questi...1/#post4579765

BTW - Did you see this in CHANGES_AND_HINTS.TXT?

Sigh. So much to read. So little remembered.

Yes, I ran into that same problem. The rc.firewall script runs from rc.inet2 but the NM script runs from rc.M.

The challenge is running rc.firewall in rc.inet2 works just fine in any wired system. Only the new laptop hiccups with that and only when I use NM.

Why is the NM script launched in rc.M rather than rc.inet2?

Nope, missed that too. Or I should say, ignored because at the time I never owned a laptop. I added pci=reboot as a kernel parameter and saw a message about unknown option. I'm not seeing any delay when rebooting. Perhaps the problem is resolved with newer kernels?

I came up with the following kludge:

Because DBus isn't running when rc.inet2 is executed.

1 members found this post helpful.

No matter where I go, there I am.

Okay, thanks.

Perhaps add a comment in rc.M so other dweebs like me don't ask again?