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.
Hi all, need some help getting wicd to work. OR if anyone knows an easier way to do what I'm trying, that'd be find too.
Quick background, my area does not have broadband, but I am able to get 3G on my cell phone. So, I've been tethering it to my laptop when needed, but what I'd like to do is set up my Slackware 13.0 box (which is configured to run as firewall/router/dhcp server so that I can just turn on my phone's wireless router program, and then share it out over the whole network in my house.
I'm using a Gigabyte b/g wireless card, which has the RT61 chipset in it. I have NO problems at all getting the wireless card to work with just setting up rc.inet1.conf. The only problem here is when I need to take my cell phone with me, I will not be able to simply turn it back into a WAP, and have my Slackware box auto reconnect to it.
This is why I started looking into using WICD. I do NOT run X, so that's why WICD fits the bill, since it has a cli version.
first I tried installing the version that came on the CD. No dice there. I removed that package, and tried the 1.7 package that's on the mirrors under current. I used slackpkg to install it.
WICD will run, see wlan0, sees my WAP and a few others, but it fails to connect. It attempts to up the interface, and use dhcp to get an ip, but it fails everytime.
My phone's WAP program only does WEP, but I can't get WICD to get an IP with our without WEP enabled.
I made sure that my rc.inet1.conf file does not reference any interfaces.
So you did revert '/etc/rc.d/rc.inet1.conf' to the original state? What about setting a static IP for the system?
When you have the Slackware system up try 'ifconfig -a', 'route -n' and post the output.
I commented out everything in rc.inet1.conf, as offhand I don't remember the original state. IIR would the 4 interfaces being uncommented, and the debug option be the original, with everything else commented?
Let me see about getting that output for you, as I have to do some trickery to get it, without connecting the wireless using rc.inet1.conf. But as a quickie, I do have eth0, eth1, loop, wlan0, wmaster in ifconfig.
Sorry, I've been busy with other issues. What does your 'dmesg' show when you attempt to use the wlan device? What about the 'wicd' logs? You can look at 'wicd.net' forum for some troubleshooting aids.
I've always wanted to turn my phone into a wap as well, so I would like to help. However there are a few details I was hoping you could clarify.
When you say
Quote:
I can just turn on my phone's wireless router program
, I take it that your phone has 802.11 capabilities, and when you tether your laptop, you are doing so over wi-fi, and not with any physical cables...
When you say
Quote:
and then share it out over the whole network in my house
, you are talking about your slack 13 box that acts as the firewall / dhcp server sharing it's connection to your phone with the rest of your home network. Is this also done over 802.11? or is your home network wired?
The reason I ask is because, before even getting to the wep issue, and regardless of whether or not the slack box is connecting correctly, I don't think you can use the 802.11 card in the slack box as both a client (to get internet from phone) and host ap (to share with house) simultaneously.
If you are physically tethering phone to slackbox (when I plug my phone's usb into my laptop, it acts as ethernet, and shows up as eth1, which I can then configure), then you could share your ethernet connection from phone with your wifi on the slackbox, using nat and dhcp.
The routing portion of this I have already done. If I configure my slack box to connect to the wifi on my phone using rc.inet1.conf, I have no problems sharing the connection out through a 100Mb NIC. My iptables is already set up, along with dhcpd.
The only problems I'm having is getting WICD to connect to the WAP. If it helps at all, the WAP can only be a WEP enabled, ADHOC network. I have already installed the latest WICD, and wpa-supplicant packages to no avail. I'm thinking the problem with with wpa-supplicant though, as when I try to use wpa-supplicant -dd -i wlan0 -c /usr/local/wicd/configuration/00xxxxxxx (this is just off the top of my head, I can't remember without looking where wicd stores its wpa-supplicant config) it will not connect, stating that there are no valid APs found, even though it shows up in the list of WAPs it finds.
I'll try and get some logs posted in a bit, have to turn on the box, and square away some work stuff first.
The only problem here is when I need to take my cell phone with me, I will not be able to simply turn it back into a WAP, and have my Slackware box auto reconnect to it.
1.
tail -f /var/log/wicd/wicd.log
tail -f /var/log/messages
2.
Try again.
3.
Post the logs here.
I already have the latest wicd package, and wpa supplicant installed.
Here are some log outputs:
wicd.log
2010/03/17 13:47:11 :: Connecting to wireless network Whapp1
2010/03/17 13:47:11 :: iwconfig wlan0
2010/03/17 13:47:11 :: /sbin/dhcpcd -k wlan0
2010/03/17 13:47:11 :: ifconfig wlan0 0.0.0.0
2010/03/17 13:47:11 :: /sbin/ip route flush dev wlan0
2010/03/17 13:47:11 :: ifconfig wlan0 down
2010/03/17 13:47:11 :: ifconfig wlan0 up
2010/03/17 13:47:11 :: wpa_cli -i wlan0 terminate
2010/03/17 13:47:11 :: /sbin/dhcpcd -k eth0
2010/03/17 13:47:11 :: ifconfig eth0 0.0.0.0
2010/03/17 13:47:11 :: /sbin/ip route flush dev eth0
2010/03/17 13:47:11 :: ifconfig eth0 down
2010/03/17 13:47:11 :: ifconfig eth0 up
2010/03/17 13:47:11 :: Putting interface down
2010/03/17 13:47:11 :: ifconfig wlan0 down
2010/03/17 13:47:11 :: Releasing DHCP leases...
2010/03/17 13:47:11 :: /sbin/dhcpcd -k wlan0
2010/03/17 13:47:11 :: Setting false IP...
2010/03/17 13:47:11 :: ifconfig wlan0 0.0.0.0
2010/03/17 13:47:11 :: Stopping wpa_supplicant
2010/03/17 13:47:11 :: wpa_cli -i wlan0 terminate
2010/03/17 13:47:11 :: Flushing the routing table...
2010/03/17 13:47:11 :: /sbin/ip route flush dev wlan0
2010/03/17 13:47:11 :: iwconfig wlan0 mode Ad-Hoc
2010/03/17 13:47:11 :: Putting interface up...
2010/03/17 13:47:11 :: ifconfig wlan0 up
2010/03/17 13:47:13 :: iwconfig wlan0
2010/03/17 13:47:13 :: enctype is wep-hex
2010/03/17 13:47:13 :: Attempting to authenticate...
2010/03/17 13:47:13 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/0224943e1c36', '-D', 'wext']
2010/03/17 13:47:13 :: ['iwconfig', 'wlan0', 'essid', 'Whapp1']
2010/03/17 13:47:13 :: iwconfig wlan0 channel 1
2010/03/17 13:47:13 :: iwconfig wlan0 ap 02:24:94:3E:1C:36
2010/03/17 13:47:13 :: WPA_CLI RESULT IS DISCONNECTED
2010/03/17 13:47:14 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:15 :: iwconfig wlan0
2010/03/17 13:47:15 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:16 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:17 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:17 :: iwconfig wlan0
2010/03/17 13:47:18 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:19 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:19 :: iwconfig wlan0
2010/03/17 13:47:20 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:21 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:22 :: iwconfig wlan0
2010/03/17 13:47:22 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:23 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:24 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:24 :: iwconfig wlan0
2010/03/17 13:47:25 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:26 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:26 :: iwconfig wlan0
2010/03/17 13:47:27 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:28 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:28 :: iwconfig wlan0
2010/03/17 13:47:29 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:30 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:31 :: iwconfig wlan0
2010/03/17 13:47:31 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:32 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:33 :: iwconfig wlan0
2010/03/17 13:47:33 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:34 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:35 :: iwconfig wlan0
2010/03/17 13:47:35 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:36 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:37 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:38 :: iwconfig wlan0
2010/03/17 13:47:39 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:40 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:40 :: iwconfig wlan0
2010/03/17 13:47:41 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:42 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:42 :: iwconfig wlan0
2010/03/17 13:47:43 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:44 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:44 :: iwconfig wlan0
2010/03/17 13:47:45 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:46 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:47 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:47 :: iwconfig wlan0
2010/03/17 13:47:48 :: WPA_CLI RESULT IS SCANNING
2010/03/17 13:47:49 :: wpa_supplicant authentication may have failed.
2010/03/17 13:47:49 :: connect result is Failed
2010/03/17 13:47:49 :: exiting connection thread
2010/03/17 13:47:49 :: Sending connection attempt result bad_pass
2010/03/17 13:47:49 :: ifconfig eth0
2010/03/17 13:47:49 :: ifconfig wlan0
2010/03/17 13:47:49 :: iwconfig wlan0
2010/03/17 13:47:49 :: Autoconnecting...
2010/03/17 13:47:49 :: Starting wired autoconnect...
2010/03/17 13:47:49 :: found default in configuration 1
2010/03/17 13:47:49 :: Reading wired profile wired-default
2010/03/17 13:47:49 :: found afterscript in configuration None
2010/03/17 13:47:49 :: found dhcphostname in configuration sparky
2010/03/17 13:47:49 :: found postdisconnectscript in configuration None
2010/03/17 13:47:49 :: found dns_domain in configuration None
2010/03/17 13:47:49 :: found broadcast in configuration None
2010/03/17 13:47:49 :: found netmask in configuration None
2010/03/17 13:47:49 :: found predisconnectscript in configuration None
2010/03/17 13:47:49 :: found gateway in configuration None
2010/03/17 13:47:49 :: found use_global_dns in configuration False
2010/03/17 13:47:49 :: found dns3 in configuration None
2010/03/17 13:47:49 :: found dns2 in configuration None
2010/03/17 13:47:49 :: found search_domain in configuration None
2010/03/17 13:47:49 :: found lastused in configuration True
2010/03/17 13:47:49 :: found use_static_dns in configuration False
2010/03/17 13:47:49 :: found default in configuration 1
2010/03/17 13:47:49 :: found ip in configuration None
2010/03/17 13:47:49 :: found beforescript in configuration None
2010/03/17 13:47:49 :: found profilename in configuration wired-default
2010/03/17 13:47:49 :: found dns1 in configuration None
2010/03/17 13:47:49 :: /sbin/dhcpcd -k wlan0
2010/03/17 13:47:49 :: ifconfig wlan0 0.0.0.0
2010/03/17 13:47:49 :: /sbin/ip route flush dev wlan0
2010/03/17 13:47:49 :: ifconfig wlan0 down
2010/03/17 13:47:49 :: ifconfig wlan0 up
2010/03/17 13:47:49 :: wpa_cli -i wlan0 terminate
messages
Mar 17 13:50:20 sparky dhcpcd[4756]: wlan0: exiting
Mar 17 13:50:20 sparky kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 17 13:50:20 sparky dhcpcd[4762]: eth0: sending signal 1 to pid 4655
Mar 17 13:50:20 sparky dhcpcd[4655]: eth0: received SIGHUP, releasing lease
Mar 17 13:50:20 sparky dhcpcd[4655]: eth0: removing default route via 192.168.4.1 metric 0
Mar 17 13:50:20 sparky dhcpcd[4655]: eth0: removing route to 169.254.0.0/16 metric 0
Mar 17 13:50:20 sparky dhcpcd[4655]: eth0: removing IP address 192.168.4.238/24
Mar 17 13:50:20 sparky dhcpcd[4655]: eth0: exiting
Mar 17 13:50:20 sparky dhcpcd[4762]: eth0: exiting
Mar 17 13:50:20 sparky kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 17 13:50:20 sparky kernel: e100: eth0 NIC Link is Up 100 Mbps Half Duplex
Mar 17 13:50:20 sparky kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 17 13:50:20 sparky dhcpcd[4769]: wlan0: exiting
Mar 17 13:50:20 sparky kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 17 13:50:48 sparky ntpd[2676]: Deleting interface #3 eth0, 192.168.4.238#123, interface stats: received=0, sent=0, dropped=0, active_time=1200 secs
Mar 17 13:50:59 sparky dhcpcd[4836]: wlan0: exiting
Mar 17 13:50:59 sparky kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 17 13:50:59 sparky dhcpcd[4842]: eth0: exiting
Mar 17 13:50:59 sparky kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 17 13:50:59 sparky kernel: e100: eth0 NIC Link is Up 100 Mbps Half Duplex
Mar 17 13:50:59 sparky kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 17 13:50:59 sparky dhcpcd[4849]: eth0: exiting
Mar 17 13:50:59 sparky kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 17 13:50:59 sparky kernel: e100: eth0 NIC Link is Up 100 Mbps Half Duplex
Mar 17 13:50:59 sparky kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 17 13:51:00 sparky dhcpcd[4853]: wlan0: exiting
Mar 17 13:51:00 sparky kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 17 13:51:00 sparky kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 17 13:51:01 sparky dhcpcd[4859]: eth0: exiting
Mar 17 13:51:01 sparky kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mar 17 13:51:01 sparky kernel: e100: eth0 NIC Link is Up 100 Mbps Half Duplex
Mar 17 13:51:01 sparky kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: dhcpcd 3.2.3 starting
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: hardware address = 00:03:47:3b:ef:d2
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: DUID = 00:01:00:01:13:25:2a:12:00:03:47:3b:ef:d2
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: broadcasting for a lease
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: offered 192.168.4.238 from 192.168.7.50
Mar 17 13:51:01 sparky dhcpcd[4865]: eth0: checking 192.168.4.238 is available on attached networks
Mar 17 13:51:02 sparky dhcpcd[4865]: eth0: leased 192.168.4.238 for 28800 seconds
Mar 17 13:51:02 sparky dhcpcd[4865]: eth0: adding IP address 192.168.4.238/24
Mar 17 13:51:02 sparky dhcpcd[4865]: eth0: adding default route via 192.168.4.1 metric 0
Mar 17 13:51:02 sparky dhcpcd[4865]: eth0: adding route to 169.254.0.0/16 metric 0
Mar 17 13:51:02 sparky dnsmasq[2762]: reading /etc/resolv.conf
Mar 17 13:51:02 sparky dnsmasq[2762]: using nameserver 192.168.7.48#53
Mar 17 13:51:02 sparky dnsmasq[2762]: using nameserver 192.168.7.50#53
Mar 17 13:51:02 sparky dhcpcd[4865]: eth0: exiting
i had a lot of difficulty getting WICD to work. i copied a plain vanilla rc.inet1.conf in place of the one i had and WICD began working. you can find a plain vanilla copy of it in the slackware n package group, inside inetd-(version).tgz (or .txz for slack 13, but ark won't open a .txz), in /etc/rc.d/inetd.conf.new
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
