You are not logged in.
Pages: 1
I've been searching through the wiki and forums to try to fix this, but so far I haven't found anything.
I can start up my internet with:
ifconfig ath0 up
sudo iwconfig ath0 essid <> key <>
sudo dhcpcd ath0
once it's booted up, but I can't seem to get it configured properly to sign on when I boot up the computer.
Since I only need to configure it for one network, I've just been doing it in rc.conf instead of using network profiles:
Moderator Note: I removed your essid and key, for safekeeping. I do not know if they were real or not, but seemed fairly legit. Security FTW!
-phrakture
lo="lo 127.0.0.1"
eth0="dhcp"
ath0="dhcp"
wlan_ath0="ath0 essid <> key <>"
INTERFACES=(lo !eth0 ath0)gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
For awhile it was working, but now it just fails every time. Between it working and failing, I installed some programs and added a few things to the list of daemons to boot:
DAEMONS=(syslog-ng !hotplug !pcmcia iptables network netfs crond sensors alsa)
Could the order of the daemons have something to do with it?
Also, is there any way that iptables could cause this problem? (it's the only program I installed that seems like it might have somethind to do with it)
Thanks for any help, this is getting very frustrating.
Offline
you could try a wireless tool like wifi-radar or wlanassistant
Offline
Yeah, but I'd much rather try to get it set up this way. Or at least figure out why it doesn't work.
Also, forgot to mention, I did a scan with the ath0 device and it shows my network, so I don't think it's a problem with the AP.
Edit: Thanks for removing the essid/key. I had cut one of them, but forgot the other.
Offline
How did you install madwifi?
If you've built it yourself, you'll have to do it most times when the kernel is upgraded.
If you install madwifi from extra, there seems to be a hole, to me, too in that if you upgraded your system, and grabbed a new kernel before madwfi was upgraded in testing, you could run into the same problem.
Then, I guess, you'd have to connect via hardwire to finish the update.
"In theory, there's no difference between theory and practice, but in practice there is."
Offline
I installed it from extra.
Also, I think I've narrowed down the problem. While I can start it up manually, there's a long delay when I execute the dhcpcd ath0 command (time reports from 28s. to 1m. 4s. real time). For some reason, with X running, it executes almost immediatly (less than 1s. real time).
So it would seem that the execution is exceeding the 30s. timeout of dhcpcd.
What are possible causes of such a long delay?
Offline
It would be timing out as the wireless isnt connected,
Try using network profiles. take the template in /etc/network-profles/template and edit it.
then you can just run 'netcfg profilename' where profilename is what you named the edited template. To have it start on boot, add it to NET_PROFILES=() in rc.conf.
James
Offline
I like the network profiles; a lot more organized.
Right now, it's still not connecting when I boot up, and it won't connect if I restart the network daemon before startx, but it does connect if I restart it once X is running.
Edit: I just realized I'm using the madwifi-ng packages from unstable, not the ones from extra. I'll go fix that now.
Offline
Okay, I think it's working pretty consistantly now. iwlist was showing that it was running in Master mode whenever I had it on, but the IWOPTS line in my network profile had mode set to managed.
Are you supposed to be able to change the mode on that line? Everytime I switched to something else (master, Master, ad-hoc, Ad Hoc, etc.) I'd get an invalid parameter argument when I reset the daemon. I ended up just deleting the mode specification altogether.
Thanks for the help everyone, it was really bothering me.
If a mod could edit solved into the title, I'd be most appreciative (it won't let me edit it).
Edit: The problem was with the wifi card; it's no longer usable.
Offline
Pages: 1