loading
I am currently looking for someone to help out with this blog. I didn't realize the scope that this blog would effect. Hits from countries in political strife and the like, people looking for a way to communicate outside of government control. If you would like to help please send me an email George dot Endrulat at Gmail dot Com.

Monday, April 11, 2011

Re: [Wing] Wing on Atheros platforms with openwrt

the ubiquity units I was using do not have wan ports, so I had to use
the script.

On 11 April 2011 22:13, Roberto Riggio <roberto.riggio@create-net.org> wrote:
> Il 11/04/2011 11:55, Ross Wakelin ha scritto:
>>
>> Hi Roberto
>
> Hi
>>
>> At the end of this message I have put the steps I used to get wing
>> going on the ubiquity
>> rocket/bullet modules.
>>
>> I will go quiet on this list now, as the application I am aiming for
>> needs the higher 802.11n data rates, so
>> I will probably go back to 802.11s, and try to use classifies for QOS.
>>  When the mac drivers catch up
>> with 802.11n, I might just come back to wing.
>
> I'm also testing 11s from time to time. To this point the biggest
> disappointment was not being able to get high rate in 11n mode.
> Basically even for a simple STA-AP configuration i get higher application
> rates in 11g mode then in 11n mode.
>
>> Wing on Atheros SOC systems with OpenWrt
>>
>> Checkout the core OpenWrt repository
>>
>> svn co svn://svn.openwrt.org/openwrt/trunk/ openwrt
>>
>> Download the radiotap patch from here and move it into
>> openwrt/package/mac80211/patches,
>> as file 811-radiotap.patch
>> This patch is needed in order to enable support for injecting raw
>> frames at arbitrary
>> rates over an interface operating in monitor mode.
>>
>> Switch to the OpenWRT directory:
>>
>> cd openwrt
>> Update the external packages feed and install the wing package:
>>
>> ./scripts/feeds update packages
>> ./scripts/feeds install wing
>> ./scripts/feeds install wing-extra
>>
>> make menuconfig
>>
>>
>> Select the wing package and wing-extra that can be found into the
>> Network section.
>> Then leave the configuration interface selecting Yes when prompted if
>> you want to save the configuration.
>>
>> Finally run:
>>
>> make defconfig&&  make
>>
>> When the build process is finished, the resulting firmware and packages
>> will be
>> available in the openwrt/bin directory.
>>
>> Move the firmware to the target
>> [for Ubiquity Bullet/Rocket systems:
>>        press and hold down the reset switch whilst connecting the
>>                ethernet cable with the POE connected
>>        keep the reset switch pressed until the four top LEDS begin
>>                to flash in alternate twos
>>        set your workstation to an address in the 192.168.1.x/24 subnet
>>                but not address 192.168.1.20, because that is the address
>>                of the wireless unit
>>        use tftp to upload the image
>>                tftp 192.168.1.20
>>                        bin
>>                        trace
>>                        put
>> openwrt-ar71xx-generic-ubnt-bullet-m-jffs2-factory.bin
>>                        quit
>>                leave the radio unit to reboot (about 60 seconds), its new
>> IP
>> address will be 192.168.1.1
>> ]
>>
>> Once running the new firmware, login using telnet and change a few files:
>> /etc/config/wireless    (this is for a bullet 5m,  for a 2.4Ghz
>> system, change the channels etc.)
>>
>>        config 'wifi-device' 'phy0'
>>                option 'phy' 'phy0'
>>                option 'type' 'mac80211'
>>                option 'channel' '40'
>>                option 'country' 'US'
>>                option 'hwmode' '11na'
>>
>>
>>        config 'wifi-iface'
>>                option 'device' 'phy0'
>>                option 'mode' 'monitor'
>>
>>
>> I also created a file called /etc/meshup and made it executable:
>>
>> iwconfig wlan0 channel 40
>> route add default dev wing-mesh
>> write_handler wr/gw.han_add 10.1.2.0/255.255.255.0
>>
>> chmod +x /etc/meshup
>>
>> and then added this line to /etc/rc.d
>> /etc/meshup
>> just before the "exit 0" line
>
> Thanks. BTW, if you installed also the wing_extra package, you should
> also have a new daemon in /etc/init.d/ called wing. This daemon checks
> if Internet connectivity is available over the wan interface and basically
> execute automatically the commands that you put in meshup.
>
> I have checked this only on alix and cambria boards.
>
> R.
>
>
>
>
>

_______________________________________________
Wing mailing list
Wing@create-net-ml.org
http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing

No comments:

Post a Comment