WIFI dongle doesn’t work
Home › Forums › GeeXboX on ARM SoCs › WIFI dongle doesn’t work
This topic contains 11 replies, has 2 voices, and was last updated by
skelos 1 month ago.
-
AuthorPosts
-
September 9, 2012 at 09:45 #4433
Hi all,
I have a problem configuring my WIFI Dongle. USR9106 is my DSLModem+wifi router with static 192.168.144.1 and (for now) my security is based only on MAC address
I have this device :# lsusb
Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapterand I installed package
http://download.openbricks.org/cubox/packages/firmware-nic-wifi-realtek_r1.80-1_armv7.opk
When I insert device i saw:
# usb 2-1: new high-speed USB device number 2 using orion-ehci
rtl8192cu: Chip version 0×10
rtl8192cu: MAC address: 00:e0:4c:08:29:7e
rtl8192cu: Board Type 0
rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin
rtlwifi: wireless switch is on
rtl8192cu: MAC auto ON okay!
rtl8192cu: Tx queue select: 0×05.. and I insert 00:e0:4c:08:29:7e in trusted MAC address on my router WIFI.
After that, edited /etc/network file as :
# Network configuration
# Backend software to use for network management (e.g. “connman”)
NETWORK_BACKEND=”connman”# “LAN” or “WLAN” or “” (default is “” <-> “LAN”)
NETWORK=”WLAN”# Network interface name or address (e.g. “eth0″ or “00:0d:56:ec:ba:0c”)
#IFACE=”eth0″
IFACE=”wlan0″# Static IP address (“” for DHCP) in CIDR format (e.g. “192.168.1.1/24″)
#ADDRESS=”192.168.144.200/24″
ADDRESS=”192.168.144.201/24″# Network gateway (e.g. “192.168.1.254″)
GATEWAY=”192.168.144.1″# List of DNS servers (e.g. “192.168.1.253 192.168.1.254″)
# This will override the DNS servers from DHCP
DNS_SERVER=”192.168.144.1″SSID=”USR9106″
# “true” or “”
HIDDEN=”false”# “WEP” or “PSK” or “” or “RSN”
SECURITY=”NONE”PASSPHRASE=””
# set to “” to disable NTP
TIMESERVERS=”0.geexbox.pool.ntp.org 1.geexbox.pool.ntp.org 2.geexbox.pool.ntp.or# Services to be started at boot time
TELNET_SERVER=”true”
FTP_SERVER=”true”
HTTP_SERVER=”true”
SAMBA_SERVER=”true”# Use Zeroconf service discovery
ZEROCONF=”true”# Static Samba shares can be defined as shown in the commented examples below,
# where <%>,<@>,<&>,<#> field separators must be present as shown (Note that
# the password cannot contain these special delimiters):#STATIC_SMB=”username<%>password<@>ip<&>myservername<#>share1<#>share2<#>share3″
#STATIC_SMB=”<%><@>ip<&>myservername<#>share1″WAIT_FOR_SLOW_DEVICE=”true”
For my all is fully configured but my cubox out of my network.
Anyone have ideas?
Thank you a lot.
September 9, 2012 at 09:58 #4434what returns iwconfig ?
and sorry to ask but which version do you use ? latest cubox snapshot includes this firmware , no ?
-
This reply was modified 1 month ago by
tomlohave.
September 9, 2012 at 10:28 #4436iwconfig results:
# iwconfig
lo       no wireless extensions.wlan0    IEEE 802.11bgn ESSID:”USR9106″
         Mode:Managed Frequency:2.427 GHz Access Point: 00:C0:49:E8:27:D0
         Bit Rate=18 Mb/s  Tx-Power=20 dBm
         Retry long limit:7  RTS thr=2347 B  Fragment thr:off
         Encryption key:off
         Power Management:off
         Link Quality=59/70 Signal level=-51 dBm
         Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
         Tx excessive retries:0 Invalid misc:0  Missed beacon:0eth0     no wireless extensions.
I use geexbox-devel-20120903-r15039.cubox.tar.bz2 version and sorry, I don’t saw the firmware but they are included.Â
I ping 192.168.144.201 from other windows 7 machine and it doesn’t replies.
Skelos
September 9, 2012 at 10:30 #4437from what i see, you are connected
ifconfig ?
for ping , we don’t disable it on geexbox
-
This reply was modified 1 month ago by
tomlohave.
September 9, 2012 at 10:36 #4440Ifconfig command:
# ifconfig
eth0     Link encap:Ethernet HWaddr 00:50:43:00:04:02
         UP BROADCAST RUNNING 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:29lo       Link encap:Local Loopback
         inet addr:127.0.0.1 Mask:255.0.0.0
         UP LOOPBACK RUNNING MTU:16436 Metric:1
         RX packets:276 errors:0 dropped:0 overruns:0 frame:0
         TX packets:276 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:67794 (66.2 KiB) TX bytes:67794 (66.2 KiB)wlan0    Link encap:Ethernet HWaddr 00:E0:4C:08:29:7E
         inet addr:192.168.144.201 Bcast:192.168.144.255 Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
         RX packets:3682 errors:0 dropped:1045 overruns:0 frame:0
         TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:864860 (844.5 KiB) TX bytes:45756 (44.6 KiB)I said that it doesn’t work because I manage my XBMC from my Android device: on Lan0 all is ok but on Wlan connection can’t be estabilished….
September 9, 2012 at 10:39 #4442Same for samba connection.
– called Samba as \192.168.144.201 no response
– Android XBMC control can’t estabilish connecttion
– no ping
on wlan0, on lan0 all works fine.
September 9, 2012 at 10:39 #4443can you ping from geexbox another machine ?
ping -c3 http://www.google.com
wlan0    Link encap:Ethernet HWaddr 00:E0:4C:08:29:7E
inet addr:192.168.144.201Â Bcast:192.168.144.255Â Mask:255.255.255.0
UP BROADCAST RUNNING MULTICASTÂ MTU:1500Â Metric:1
RX packets:3682 errors:0 dropped:1045 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:864860 (844.5 KiB)Â TX bytes:45756 (44.6 KiB)looks good, ip ok, RX and TX too
September 9, 2012 at 10:41 #4445# ping -c3 http://www.google.com
ping: bad port spec ‘http://www.google.com’This appears bad…
September 9, 2012 at 10:42 #4446check you mail box please
September 9, 2012 at 10:44 #4447Same for my DLSmodem+Wifi accesspoint:
# ping -c3 192.168.144.1
PING 192.168.144.1 (192.168.144.1): 56 data bytes— 192.168.144.1 ping statistics —
3 packets transmitted, 0 packets received, 100% packet lossSeptember 9, 2012 at 10:57 #4448I checked. Nothing found. Why you asked me this?
September 10, 2012 at 01:01 #4449lsusb said “RTL8188CUS” but device is recognized as “rtl8192cu“. May be this difference the cause of this problem?
-
This reply was modified 1 month ago by
-
AuthorPosts
You must be logged in to reply to this topic.