Quantcast
Channel: PirateBox Forum - Raspberry Pi(rate)Box
Viewing all 1863 articles
Browse latest View live
↧

Re: Temporary Fix for solving problems with ALFA devices

April 11, 2013, 11:03 pm
$
0
0
I installed version 0.6E on an sd for my raspberry
This works fine with the wifi key w541u
But with my USB wifi Realtek RTL8187L it well recognized
To boot (flashing LED) but the network piratebox not visible?
↧
Search

Re: Temporary Fix for solving problems with ALFA devices

April 11, 2013, 11:36 pm
$
0
0
Matthias Wrote:
-------------------------------------------------------
> Realtek RTL8187L ?
> can you please post the output of the command "iw"
> . It seems that chipset is not supported for
> AP-mode (refering to
> [wireless.kernel.org] )

I believe RTL8187L does not support ap mode
↧
↧

Re: Temporary Fix for solving problems with ALFA devices

April 12, 2013, 12:02 am
$
0
0
iwconfig
wlan0 IEEE 802.11bg ESSID : off/any
mode :managed access point: not-associated tx-power=20dbm
Retry long limit :7 rts thr:off Fragment thr :off
Power Management :off
:S
↧

Re: Temporary Fix for solving problems with ALFA devices

April 12, 2013, 12:05 am
↧

Re: Temporary Fix for solving problems with ALFA devices

April 12, 2013, 12:15 am
$
0
0
I how to copy the list (in linux) iw as the result and send it to you?
↧
↧

Re: Temporary Fix for solving problems with ALFA devices

April 12, 2013, 12:17 am
$
0
0
"iw list" > iw_output.txt

Then everything is in iw_output.txt :)
↧

Re: RaspberryPI USB wifi compatibility list

April 12, 2013, 1:52 am
$
0
0
The 'WIPI' adapter from cpc.co.uk works straight out of the box. Mine has FCC ID: OYR-COMFAST88 written on it.
↧

Re: RaspberryPI USB wifi compatibility list

April 12, 2013, 2:16 am
$
0
0
Thanks for sharing this!
I added it to the wiki
↧
Search

Re: Temporary Fix for solving problems with ALFA devices

April 12, 2013, 9:29 am
$
0
0
root@raspberrypi:/home/pi# iw list
Wiphy phy0
Band 1:
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (passive scanning, no IBSS)
* 2472 MHz [13] (20.0 dBm) (passive scanning, no IBSS)
* 2484 MHz [14] (20.0 dBm) (passive scanning, no IBSS)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* managed
* monitor
software interface modes (can always be added):
* monitor
interface combinations are not supported
Supported commands:
* new_interface
* set_interface
* new_key
* new_beacon
* new_station
* new_mpath
* set_mesh_params
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* action
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
Device supports RSN-IBSS.
root@raspberrypi:/home/pi#
↧
↧

Re: Temporary Fix for solving problems with ALFA devices

April 13, 2013, 11:57 pm
$
0
0
Do you have a solution to my problem?8-)
↧

Re: Temporary Fix for solving problems with ALFA devices

April 14, 2013, 9:41 pm
$
0
0
Yeah, you need a different device.

Look at this output, I marked the lines your devices misses:


pi@raspberrypi ~ $ sudo iw phy
Wiphy phy0
Band 1:
Capabilities: 0x172
HT20/HT40
Static SM Power Save
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT RX MCS rate indexes supported: 0-7, 32
TX unequal modulation not supported
HT TX Max spatial streams: 1
HT TX MCS rate indexes supported may differ
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (passive scanning, no IBSS)
* 2472 MHz [13] (20.0 dBm) (passive scanning, no IBSS)
* 2484 MHz [14] (20.0 dBm) (passive scanning, no IBSS)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
software interface modes (can always be added):
* AP/VLAN
* monitor
interface combinations are not supported
Supported commands:
* new_interface
* set_interface
* new_key
* new_beacon
* new_station
* new_mpath
* set_mesh_params
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* action
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
↧

Re: Temporary Fix for solving problems with ALFA devices

April 14, 2013, 10:36 pm
$
0
0
I advise you that as a key wifi or I can solve the problem with a file?
↧

Re: Temporary Fix for solving problems with ALFA devices

April 14, 2013, 10:44 pm
↧
↧

Re: Temporary Fix for solving problems with ALFA devices

April 17, 2013, 11:04 pm
$
0
0
I installed under xwindows wicd and my rtl8187 card works but not always visible PirateBox I think has a driver problem and not the wireless card you
procedure to install the native drivers?
↧

Re: Temporary Fix for solving problems with ALFA devices

April 17, 2013, 11:28 pm
$
0
0
I don't believe, that the native drivers (via ndiswrapper) are able to run in AP mode.
↧
Search

rpi and piratebox

April 19, 2013, 9:49 am
$
0
0
Greetings,

I installed this file and booted my rpi today 19apr2013 -- all good

[downloads.piratebox.de]

I have modified /opt/piratebox/piratebox.conf

to use 10.10.0.1 and changed the netmask to 255.255.0.0 for class b subnet

rebooted and I can connect. I would like dhcpd to restrict assigned addresses
to this range 10.10.0.70 to 10.10.0.80.
but havent figured out what file to edit.

This is a great project. I am using an alpha aws037aha on a usb hub

I came across your project while testing pilfs which I plan to use once
I understand all the details of setting up hostapd, dhcpd, etc.
↧

Re: rpi and piratebox

April 21, 2013, 9:54 pm
$
0
0
Hi,
So the problem is the not existing wifi network?
or is it the not working dhcp service?

If wifi, please post the output of 
 iw list

regards Matthias
↧
↧

Re: Help with index page

April 22, 2013, 2:07 pm
$
0
0
One thing I should mention is that I am connecting to the piratebox from an internet connected
computer over wireless so I am not using [piratebox.lan] but just the
ip address. Otherwise my dns cannot find piratebox.lan and dont want to edit hosts.

I have tried a few things to correct an error when I connect to the AP the
message text is cut and pasted below this note.

The only thing that seems to work for me consistently is to hardcode
the ip address in this file /opt/piratebox/www/index.html
change piratebox.lan to whatever ip address for the ap on line 124


Also added the AP's ip address to both /etc/hosts and /opt/piratebox/conf/hosts
as I noticed I could not ping piratebox.lan by name from a shell.

Error - [piratebox.lan]

The page 'http://piratebox.lan:8080/' couldn't be loaded.

Cannot resolve hostname (piratebox.lan)

Try again
↧

Re: rpi and piratebox

April 22, 2013, 3:16 pm
$
0
0
okay I had a chance again to test the awus036nhr

iw list just says nl80211 not found


[store.rokland.com]

has this link to a driver which I tried to run the install.sh program but died at the end

[www.rokland.com]


rtl8192_8188CU_linux_v3.0.2164.20110715/wlan0dhcp
rtl8192_8188CU_linux_v3.0.2164.20110715
Authentication requested [root] for make driver:
make ARCH=armv6l CROSS_COMPILE= -C /lib/modules/3.6.11+/build M=/usr/local/src/RTL8192CU_8188CUS_8188CE-VAU_linux_v3.0.2164.20110715/driver/rtl8192_8188CU_linux_v3.0.2164.20110715 modules
make: *** /lib/modules/3.6.11+/build: No such file or directory. Stop.
make: *** [modules] Error 2
Compile make driver error: 2, Please check error Mesg


The rokland.com web page says that kernel headers are required
I have mostly used fedora in the past including the raspberry pi
but debian is still new to me.
↧

Re: rpi and piratebox

April 23, 2013, 11:44 pm
$
0
0
There should be a package containing the header files.

You should try

# sudo aptitude

This is a nice gui, which should make it easier for you searching for the correct packages.

Matthias
↧
Viewing all 1863 articles
Browse latest View live
Search