===[sting@StingMobile] ~ # iwconfig eth1
eth1 no wireless extensions.
8(
]]># iwconfig eth1 essid <whatever>
# iwconfig eth1
check the output, see if essid is right
# ifconfig eth1 up
# dhcpcd eth1
# ifconfig eth1
check for ip address
see if you get any errors in there
]]>so this is where I'm at now.
When i boot up the computer and i have wired plugged in, my wireless gets an IP. when i dont have wired plugged in, then it does not get an IP.
after booting up un-wired, i tried getting wireless going
i did the following:
ifconfig eth1 down //to make sure wireless is down
/etc/rc.d/wireless stop
/etc/rc.d/wireless profile sting up
/etc/rc.d/wireless restart
this is the output from restart it:
Stopping Wireless Profile [sting] on eth1
Loading Wireless Profile [sting] on eth1
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 : Operation not supported
Error for wireless request "Set ESSID" (8B2A) :
SET failed on device eth1 : Operation not supported
also, just a strange thing i thought i would note:
My routers IP is 192.168.2.1 so i put that as the gateway in my rc.conf
when im on wired, the IP it gets is 192.168.1.x
where as my wireless get an IP of 192.168.2.x
dunno if thats a problem too...
EDIT:
Sorry, phrak was faster than me
heh, that happens alot... I'm like a post-ninja
]]>when you are in /etc/rc.d
type: ./wireless start
notice the ./
othervice /etc/rc.d/wireless start would work too
EDIT:
Sorry, phrak was faster than me
]]> /etc/rc.d/wireless profile X up
/etc/rc.d/network restart
or
cd /etc/rc.d
./wireless profile X up
./network start
this works because you're specifying the location of the commands to run. In the second case, the "./" in the beginning says "it's in the current directory"
]]>also, this is what happens when i do the following:
===[sting@StingMobile] /etc/rc.d # wireless start
bash: wireless: command not found
so i checked like 1000x to make sure the file exists, and the permissions are right. but for some reason it doesnt see that the wireless command exists....
and if this helps, this is from my ifconfig for eth0 and eth1
eth0 Link encap:Ethernet HWaddr 00:12:F0:40:F4:0E
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1648 errors:0 dropped:0 overruns:0 frame:0
TX packets:992 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:785138 (766.7 Kb) TX bytes:132504 (129.3 Kb)
Interrupt:5 Base address:0x8000 Memory:faffd000-faffdfff
eth1 Link encap:Ethernet HWaddr 00:11:43:57:97:6B
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11
Ok, wireless.... let's continue. I'm going to assume the module is loaded (run lsmod to check).
Now, if you're using my wireless scripts, you should have (this is the minimum):
/etc/rc.d/wireless <--- main script
/etc/conf.d/wireless_profiles/MyProfile/config <--- MyProfile can be any name
The minimum profile config file should look like this:
#! /bin/sh
INTERFACE="wlan0"
IFOPTS="dhcp"
ESSID="MyEssid"
you should know the ESSID of your wireless router... keep the IFOPTS set to dhcp, it's easier for now... the INTERFACE value may need to be changed (to whatever ipw2200 brings up - it's either eth1 or wlan0... not sure, check /dev and see which file is there, eth1 or wlan0)
also, don't forget to run "chmod 755 /etc/rc.d/wireless" as root [this changes the permissions on the wireless script so you can run it, otherwise the system thinks it's just a text file]
now, you need to be root to do this... there's two ways (just like module loading) to start up wireless... for now, we'll just test it.
run /etc/rc.d/wireless profile MyProfile up
(replace up with down to turn it off)
after this, check "ifconfig wlan0" (or eth1) to see if you have an ip address... if not, check "iwconfig wlan0" (or eth1) [note the "w" for wireless] - post the output of both
assuming wireless works fine (you get an ip), you can then add WIRELESS_PROFILES=('MyProfile') in rc.conf so it will start wireless on boot
]]>I noticed on startup i get this
Starting Hotplug Daemon
... cant load module shpchp
missing kernel or user mode driver shpchp
... cant load module shpchp
missing kernel or user mode driver shpchp
and it does it twice because its listed twice in my rc.conf
1) is this supposed to happen?
2) should it happen twice?
ummm yeah, i really dont know how to "turn on wireless" to even check if it works. so I need some help with that now 8)
---Edit---
I just restarted my comp, cause thats the only way I know to get it to "turn on" wireless
in the loading network part of start up it failed 8(
so wireless is not working yet. my wired still loaded up fine, however.
another weird thing, when i am just at a console prompt
and i try to use the network command, i get
bash: network: command not found
i think that is kinda weird too...
02:03.0 Network controller: Intel Corp.|PRO/Wireless 2915ABG MiniPCI Adapter (ipw2200)
that's in extra... so the following:
pacman -S ipw2200
modprobe ipw2200
don't forget to add "ipw2200" to rc.conf
about the wireless profiles... yes, create the "wireless-profiles" directory there... each profile has an arbitrary name... and it's based on the dir...
i can make /etc/conf.d/wireless-profiles/some_obscure_name for a profile named "some_obscure_name"
change the proper values in the profile directory and add "WIRELESS_PROFILES=('some_obscure_name')" somewhere into rc.conf (order doesn't matter)
on a side note: you shouldn't do much as root... you have a chance to oddly screw up your machine... for instance, a common one is doing "rm -R .*" which, you'd think, matches all "." (hidden) files... however, it also matches ".." which goes one dir up.... same thing there, and after a time it can wipe your whole drive
when you build a standard project, like madwifi, the commands work as follows:
configure - sets up the build so it works on your machine
make - compiles the source code into binary
make install - copies the files where they need to be
doing this as non-root is important, as you can overwrite system files... once it's done, you can remove all the files you downloaded, as the "make install" copies what you need (you should still have ath_pci somewhere... try "find / -name ath_pci.ko"
ok, enough rambling... you sound like you're picking this up extremely fast... so good job.
let me know if there's any other issues
]]>thanks and sorry for being such a noob 8 )
]]>You need to switch the interface to "ath0" and switch the ESSID parameter, at the very minimum (other params should be self explainatory, check "man iwconfig" for details).
So im not 100% clear on what this is saying. when you say i need to switch the interface to ath0, and switch the ESSID parameter, is this in the wireless script? or the profile script? and what exactly am I changing?
thanks again
--Edit--
So im a moron, i take it you mean in the profile file, now that i actually looked at it. so im switching
INTERFACE="wlan0"
to
INTERFACE="ath0"
and i also need to change
ESSID="SAMPLE"
to something else. i dont know what to change this to, so some insight would be very helpful 8¬)
So if i have WEP on my wireless router, then in my profile I would have to uncomment this (the KEY part)
# Encryption Key (see `man iwconfig` for extended information
# KEY="00000000000000000000000000"
and put in the actuall WEP
i think im getting the hang of this 8 )
]]>