Connecting to a wireless AP [SOLVED]

mtrivs · 2005-12-26 00:46:36

I believe i have set up my wlan0 device to be fecognized by linux, however i dont know how to connect to an AP. Can someone tell me how i can check and se if i have my wireless device set up properly and also how to connect to an AP?

My SSID is "home" and i turned off the WEP encryption...

tomk · 2005-12-26 00:58:59

Have you read all this stuff?

mtrivs · 2005-12-26 12:22:01

Yes i have, and while in KDE i go to the wireless network settings and it shows i am connected to my wireless, however when i try to pull up a web page, it doesnt respong. I have also tryed pinging a few sites, but nothing works. What could be the proble

rayjgu3 · 2005-12-26 12:35:20

what are out puts of

ifconfig
iwconfig

do you have the settings of your router?
essid , wep , etc

if you dont have wlan0 or wifi0 from

 ifconfig -a

chances are you havent got it setup right
if you do have one of these go into

 /etc/rc.conf

then add it it to NETWORK section
then try

iwconfig --help   &  man iwconfig

mtrivs · 2005-12-26 13:42:02

output of ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:0F:B0:70:13:E8
          inet addr:192.168.1.45  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:b0ff:fe70:13e8/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:288 errors:0 dropped:0 overruns:0 frame:0
          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:302802 (295.7 Kb)  TX bytes:26558 (25.9 Kb)
          Interrupt:19 Base address:0x6400

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1000 (1000.0 b)  TX bytes:1000 (1000.0 b)

Output of iwconfig:

lo        no wireless extensions.

sit0      no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11g  ESSID:off/any
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:00:00:00:00:00
          Bit Rate:54 Mb/s   Tx-Power:25 dBm
          RTS thr:2347 B   Fragment thr:2346 B
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth1      no wireless extensions.

output of ifconfig -a :

eth0      Link encap:Ethernet  HWaddr 00:0F:B0:70:13:E8
          inet addr:192.168.1.45  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:b0ff:fe70:13e8/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:238396 (232.8 Kb)  TX bytes:20286 (19.8 Kb)
          Interrupt:19 Base address:0x6400

eth1      Link encap:UNSPEC  HWaddr 55-3F-02-00-6A-F0-40-64-00-00-00-00-00-00-00-00
          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)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1000 (1000.0 b)  TX bytes:1000 (1000.0 b)

sit0      Link encap:UNSPEC  HWaddr 00-00-00-00-31-00-00-00-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:90:4B:EB:2F:13
          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:21 Memory:b0204000-b0206000

and i have already added the following to the NETWORK section of rc.conf :

#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid home"
INTERFACES=(lo eth0)

jerem · 2005-12-26 14:00:31

Add wlan0 to the INTERFACES() array in rc.conf

mtrivs · 2005-12-26 15:18:05

did that, then connected to the same AP and still can't ping/pull up web pages

jerem · 2005-12-26 19:58:47

The problem is that wlan0 is not bound to an IP.
Try a dhcpcd wlan0 and if this does not work, disable all the interfaces but wlan0 and loopback.

mtrivs · 2005-12-26 23:29:24

OK i have already ran the dhcpcd and comes up with the same result, however i dont know how to disable devices or start a loopback...Can you explain this to me, or point me to a page that explains it?

Thanks!

postlogic · 2005-12-27 11:17:42

ifconfig <interface> down
is the command to disable an interface, atleast until you reboot. Your loopback device is already there, called 'lo'.

After you connect, does iwconfig wlan0 display anything special on ESSID, or is it set to "off/any"?
And, do you know for sure that your router is connected to the modem, and working properly?
Take note that if your router is set up with mac level access lists or similar, make sure that you get the right IP and that the MAC address is correct. Otherwise, you'll connect, but that's all.

mtrivs · 2005-12-29 02:20:23

Yea after i connect to the AP, it shows the ESSID to be that of my DSL modem/wireless router. And my router does not have MAC filtering enabled... Anyone know why i would be able to connect, but not able to ping/bring up web pages?

Arch Linux

#1 2005-12-26 00:46:36

Connecting to a wireless AP [SOLVED]

#2 2005-12-26 00:58:59

Re: Connecting to a wireless AP [SOLVED]

#3 2005-12-26 12:22:01

Re: Connecting to a wireless AP [SOLVED]

#4 2005-12-26 12:35:20

Re: Connecting to a wireless AP [SOLVED]

#5 2005-12-26 13:42:02

Re: Connecting to a wireless AP [SOLVED]

#6 2005-12-26 14:00:31

Re: Connecting to a wireless AP [SOLVED]

#7 2005-12-26 15:18:05

Re: Connecting to a wireless AP [SOLVED]

#8 2005-12-26 19:58:47

Re: Connecting to a wireless AP [SOLVED]

#9 2005-12-26 23:29:24

Re: Connecting to a wireless AP [SOLVED]

#10 2005-12-27 11:17:42

Re: Connecting to a wireless AP [SOLVED]

#11 2005-12-29 02:20:23

Re: Connecting to a wireless AP [SOLVED]

Board footer