Results 1 to 5 of 5

Thread: AP is recognized but can't ping it

  1. #1

    Default AP is recognized but can't ping it

    Hi there,
    I new to Linux, just installed OpenSuse 11.4 on my laptop and now I'm trying to get my wireless to work.
    I read the two stickies posted in this section, so I'll now try to give all the information that is needed. If anything is missing, let me know and I'll update it asap.


    II. My device is RTL8187B_WLAN_Adapter and the kernel driver is listed as: rtl8187


    III. Do I need external firmware? With "dmesg | grep firmware", I found the following, although I'm not sure if that pertains to the wireless or something else:

    [ 0.116670] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored: line 238
    [ 0.130165] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness: line 248
    [ 2.193386] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness: line 285
    [ 2.194664] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness: line 286


    IV. With the command "sudo /usr/sbin/iwlist scan", I get the following:

    wlan0 Scan completed :
    Cell 01 - Address: 00:04:E2:AE:E1:60
    Channel:6
    Frequency:2.437 GHz (Channel 6)
    Quality=70/70 Signal level=-39 dBm
    Encryption keyn
    ESSID:"SMC"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
    36 Mb/s; 48 Mb/s; 54 Mb/s
    Mode:Master
    Extra:tsf=0000023deca7dbfa
    Extra: Last beacon: 24584ms ago
    IE: Unknown: 0003534D43
    IE: Unknown: 010482848B96
    IE: Unknown: 030106
    IE: Unknown: 2A0100
    IE: Unknown: 32080C1218243048606C
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : TKIP
    Authentication Suites (1) : PSK


    V. Encryption: I entered the right encryption details under Network settings. I double and triple checked this, so I'm sure there isn't a typo.


    VI. The command "/usr/sbin/iwconfig" gives me this:

    wlan0 IEEE 802.11bg ESSID:"SMC"
    Mode:Managed Frequency:2.437 GHz Access Point: 00:04:E2:AE:E1:60
    Bit Rate=1 Mb/s Tx-Power=20 dBm
    Retry long limit:7 RTS thrff Fragment thrff
    Power Managementff
    Link Quality=70/70 Signal level=-39 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:10 Missed beacon:0


    I think everything up to this point works as it should. Trying to access the internet via firefox doesn't work though.


    VII. First using "/sbin/ifconfig" I get this:

    wlan0 Link encap:Ethernet HWaddr 00:17:C4:6F:05:14
    inet addr:192.168.2.102 Bcast:192.168.2.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
    RX packets:878 errors:0 dropped:0 overruns:0 frame:0
    TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:208313 (203.4 Kb) TX bytes:5621 (5.4 Kb)


    The line inet addr and so on is there, so this does not seem to be the problem either. Next I tried to ping the AP and this did not work:

    ping -c 5 66.70.73.150 --> connect: Network is unreachable


    Anyone know what I can do to resolve this? Did I forget to configure something?

    Additional information from the other sticky:

    /sbin/lspci :
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
    Bus 002 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
    Bus 007 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth

    Looking for the hardware with dmesg:
    [ 1.144626] usb 1-3: Product: RTL8187B_WLAN_Adapter

    Found another line in there saying this:
    [ 48.818656] ADDRCONF(NETDEV_UP): wlan0: link is not ready


    Thanks in advance,
    ~Arch

  2. #2
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: AP is recognized but can't ping it

    On 04/12/2011 03:36 AM, Archangelic wrote:
    >
    > Hi there,
    > I new to Linux, just installed OpenSuse 11.4 on my laptop and now I'm
    > trying to get my wireless to work.
    > I read the two stickies posted in this section, so I'll now try to give
    > all the information that is needed. If anything is missing, let me know
    > and I'll update it asap.
    >
    >
    > II. My device is RTL8187B_WLAN_Adapter and the kernel driver is listed
    > as: rtl8187
    >
    >
    > III. Do I need external firmware? With "dmesg | grep firmware", I found
    > the following, although I'm not sure if that pertains to the wireless or
    > something else:
    >
    > [ 0.116670] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored:
    > line 238
    > [ 0.130165] [Firmware Bug]: ACPI: No _BQC method, cannot determine
    > initial brightness: line 248
    > [ 2.193386] [Firmware Bug]: ACPI: No _BQC method, cannot determine
    > initial brightness: line 285
    > [ 2.194664] [Firmware Bug]: ACPI: No _BQC method, cannot determine
    > initial brightness: line 286


    Your RTL8187B does not need external firmware. It is built into the device.
    Those messages appear to originate with your graphics device. In any case, ACPI
    problems do not affect rtl8187.

    > IV. With the command "sudo /usr/sbin/iwlist scan", I get the
    > following:
    >
    > wlan0 Scan completed :
    > Cell 01 - Address: 00:04:E2:AE:E1:60
    > Channel:6
    > Frequency:2.437 GHz (Channel 6)
    > Quality=70/70 Signal level=-39 dBm
    > Encryption keyn
    > ESSID:"SMC"
    > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
    > Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24
    > Mb/s
    > 36 Mb/s; 48 Mb/s; 54 Mb/s
    > Mode:Master
    > Extra:tsf=0000023deca7dbfa
    > Extra: Last beacon: 24584ms ago
    > IE: Unknown: 0003534D43
    > IE: Unknown: 010482848B96
    > IE: Unknown: 030106
    > IE: Unknown: 2A0100
    > IE: Unknown: 32080C1218243048606C
    > IE: WPA Version 1
    > Group Cipher : TKIP
    > Pairwise Ciphers (1) : TKIP
    > Authentication Suites (1) : PSK


    If the above is your AP, then this looks good.

    > V. Encryption: I entered the right encryption details under Network
    > settings. I double and triple checked this, so I'm sure there isn't a
    > typo.
    >
    >
    > VI. The command "/usr/sbin/iwconfig" gives me this:
    >
    > wlan0 IEEE 802.11bg ESSID:"SMC"
    > Mode:Managed Frequency:2.437 GHz Access Point:
    > 00:04:E2:AE:E1:60
    > Bit Rate=1 Mb/s Tx-Power=20 dBm
    > Retry long limit:7 RTS thrff Fragment thrff
    > Power Managementff
    > Link Quality=70/70 Signal level=-39 dBm
    > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    > Tx excessive retries:0 Invalid misc:10 Missed beacon:0


    You have associated and authenticated, thus your encryption key is correct. The
    clues are that the MAC address and ESSID for the AP are filled in.

    > I think everything up to this point works as it should. Trying to
    > access the internet via firefox doesn't work though.
    >
    >
    > VII. First using "/sbin/ifconfig" I get this:
    >
    > wlan0 Link encap:Ethernet HWaddr 00:17:C4:6F:05:14
    > inet addr:192.168.2.102 Bcast:192.168.2.255
    > Mask:255.255.255.0
    > UP BROADCAST RUNNING MULTICAST MTU:576 Metric:1
    > RX packets:878 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:208313 (203.4 Kb) TX bytes:5621 (5.4 Kb)


    You have an IP, thus DHCP is working.


    > The line inet addr and so on is there, so this does not seem to be the
    > problem either. Next I tried to ping the AP and this did not work:
    >
    > ping -c 5 66.70.73.150 --> connect: Network is unreachable


    That is not your AP - that is mail.samba.org; however, we now know that routing
    is not working. Please post the output of

    Code:
    /sbin/route -n
    To ping your AP, the most probable command is

    Code:
    ping -c 5 192.168.2.1
    Try that ping as well and report the results.

  3. #3

    Default Re: AP is recognized but can't ping it

    I wrote down the ping wrong, i did indeed ping my AP with "ping -c 5 192.168.2.1", which gave the result: connect: Network is unreachable
    If i ping mail.samba.org I get the same message though.


    Using "/sbin/route -n I get the following:

    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
    169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
    127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

    Thanks for helping, Arch

  4. #4
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: AP is recognized but can't ping it

    On 04/13/2011 07:06 AM, Archangelic wrote:
    >
    > I wrote down the ping wrong, i did indeed ping my AP with "ping -c 5
    > 192.168.2.1", which gave the result: connect: Network is unreachable
    > If i ping mail.samba.org I get the same message though.
    >
    >
    > Using "/sbin/route -n I get the following:
    >
    > Kernel IP routing table
    > Destination Gateway Genmask Flags Metric Ref Use
    > Iface
    > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
    > wlan0
    > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
    > wlan0
    > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
    > lo


    The idea behind ping testing is to crawl first, walk next, and then finally try
    running. If pinging the AP doesn't work, none of the others will.

    Your immediate problem is that you have no global routing entry in the table.
    For example, my system has

    Code:
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 wlan0
    0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0
    To add the necessary line (the one with the UG flags), use the command

    Code:
    sudo /sbin/route add default gw 192.168.2.1
    Then retry the pings - AP first, external IP number next, and domain name last.

  5. #5

    Default Re: AP is recognized but can't ping it

    I did what you said and now it work

    Thanks a lot, I really appreciate it!

    ~Arch

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •