Ubiquiti Bullet 2
Tyrone Miles
Is there a way to flash my bullet 2's with the mesh potato firmware,
or is there a way to used them as such? I flashed one of the with the:
http://downloads.openwrt.org/kamikaze/8.09.2/atheros/openwrt-atheros-ubnt2-squashfs.bin,
I'm not sure if what I need to do next? I also get this error from
this missing link:
wget: server returned error: HTTP/1.1 404 Not Found
Collected errors:
* opkg_download: ERROR: Command failed with return value 1: `wget --
passive-ftp -P /tmp/opkg-oDD6ES
http://downloads.afrimesh.org/stable.villagetelco/atheros/packages/Packages'
Your help is greatly appreciated.
Thank.
wayne
Hi Tyrone
I'm no expert on Afrimesh but try this.
Edit your opkg.conf
vi /etc/opkg.conf
src/gz snapshots
http://downloads.openwrt.org/kamikaze/8.09.2/brcm-2.4/packages
src packages http://downloads.afrimesh.org/stable/brcm-2.4/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /jffs
opkg update
Then try again.
Or try the scripts on this page
http://code.google.com/p/afrimesh/downloads/list
Wayne
Tyrone Miles
I was able to get pass the error, by using the repository location
from elektra (MESH-POTATO/VT-FIRMWARE-TESTING/packages/) for the
chipset of my hardware. The info your supplying is for a linksys
wrt54G series routers. My question at this point is about flashing
Ubiquiti Bullet 2's to act as the mesh potato, and if this is
possible? What are the steps?
On Feb 19, 1:33 am, wayne <plet...@gmail.com> wrote:
> Tyrone Miles wrote:
> > Hello Team,
> > Is there a way to flash my bullet 2's with the mesh potato firmware,
> > or is there a way to used them as such? I flashed one of the with the:
> > this missing link:
>
> > wget: server returned error: HTTP/1.1 404 Not Found
> > Collected errors:
> > * opkg_download: ERROR: Command failed with return value 1: `wget --
> > passive-ftp -P /tmp/opkg-oDD6ES
> > Your help is greatly appreciated.
> > Thank.
>
> Hi Tyrone
> I'm no expert on Afrimesh but try this.
>
> Edit your opkg.conf
> vi /etc/opkg.conf
>
> src/gz snapshotshttp://downloads.openwrt.org/kamikaze/8.09.2/brcm-2.4/packages
Steve Song
Sure this is possible. The Ubiquiti Bullet 2 will accept the same
image as the NS2 which means that you can follow the instructions at
to install Kamikaze, or if you would prefer something more up-to-date,
you can get the latest OpenWRT firmware from
http://downloads.openwrt.org/snapshots/trunk/atheros/openwrt-atheros-ubnt2-squashfs.bin
and follow the instructions at
http://wiki.villagetelco.org/index.php?title=Default_Configurations_for_Other_APs
Note, this is to configure the Bullet as a supernode or gateway device
for your network.
Hope that answers your question.
Cheers... Steve
P.S. Ubiquiti also have a basic guide on flashing OpenWRT on Bullets at
http://www.ubnt.com/wiki/Installing_OpenWRT_on_NanoStations/Bullets
> --
> You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
> To post to this group, send email to village-...@googlegroups.com.
> To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
>
>
--
Steve Song
Telecommunications Fellow, Shuttleworth Foundation
email: steve...@shuttleworthfoundation.org
mobile: +27 83 482 2088
skype: steve_l_song
blog: http://manypossibilities.net
next: http://villagetelco.org
twitter: stevesong
Tyrone Miles
I will report back to the post, once completed.
Thanks you.
On Feb 19, 8:10 am, Steve Song <steve.s...@shuttleworthfoundation.org>
wrote:
>
> Sure this is possible. The Ubiquiti Bullet 2 will accept the same
> image as the NS2 which means that you can follow the instructions at
>
> to install Kamikaze, or if you would prefer something more up-to-date,
> you can get the latest OpenWRT firmware from
>
> and follow the instructions at
>
> Note, this is to configure the Bullet as a supernode or gateway device
> for your network.
>
> Hope that answers your question.
>
> Cheers... Steve
>
> P.S. Ubiquiti also have a basic guide on flashing OpenWRT on Bullets at
>
> http://www.ubnt.com/wiki/Installing_OpenWRT_on_NanoStations/Bullets
>
> --
> Steve Song
> Telecommunications Fellow, Shuttleworth Foundation
>
Tyrone Miles
Can I flash the MP01 firmware to the bullet 2, or setup the bullet 2
to simulate the mesh potato?
Thanks.
>
> Sure this is possible. The Ubiquiti Bullet 2 will accept the same
> image as the NS2 which means that you can follow the instructions at
>
> to install Kamikaze, or if you would prefer something more up-to-date,
> you can get the latest OpenWRT firmware from
>
> and follow the instructions at
>
> Note, this is to configure the Bullet as a supernode or gateway device
> for your network.
>
> Hope that answers your question.
>
> Cheers... Steve
>
> P.S. Ubiquiti also have a basic guide on flashing OpenWRT on Bullets at
>
> http://www.ubnt.com/wiki/Installing_OpenWRT_on_NanoStations/Bullets
>
> --
> Steve Song
> Telecommunications Fellow, Shuttleworth Foundation
>
Steve Song
Sure. You can just use the default configuration from an MP once
batmand is installed on your bullet although it is more common to use
Ubiquiti gear as gateway or supernodes because they have such
impressive antennas. Here are the defaults settings for the Mesh
Potato's network and wireless configuration:
/etc/config/network
config 'interface' 'loopback'
option 'ifname' 'lo'
option 'proto' 'static'
option 'ipaddr' '127.0.0.1'
option 'netmask' '255.0.0.0'
config 'interface' 'lan'
option 'ifname' 'eth0'
option 'proto' 'static'
option 'netmask' '255.255.255.0'
option 'dns' '192.168.1.20'
option 'ipaddr' '192.168.1.20'
option 'gateway' '192.168.1.20'
config 'interface' 'wifi0'
option 'ifname' 'ath0'
option 'proto' 'static'
option 'netmask' '255.255.255.0'
option 'ipaddr' '10.130.1.XX' <- where XX is some number between 1
and 254 but not 20
/etc/config/wireless
config 'wifi-device' 'wifi0'
option 'type' 'atheros'
option 'channel' '1'
config 'wifi-iface'
option 'device' 'wifi0'
option 'mode' 'ahdemo'
option 'ssid' 'potato'
option 'bssid' '01:CA:FF:EE:BA:BE'
option 'swmerge' '1'
option 'bgscan' '0'
-Steve
> For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
>
>
--
Steve Song
Telecommunications Fellow, Shuttleworth Foundation
email: steve...@shuttleworthfoundation.org
Tyrone Miles
I'll be using it as super node in the future, I want see if I can get
it up and running. I want emulate what you've here http://vimeo.com/14262841
On Feb 19, 11:02 am, Steve Song
<steve.s...@shuttleworthfoundation.org> wrote:
> Hi Tyrone,
>
elektra
> Can I flash the MP01 firmware to the bullet 2,
no, don't try this, it won't work. The MP phone (FXS) port drivers will
interfere with the operation of the bullet. It would be possible to run the MP
firmware on the bullet, if the FXS port drivers are removed from the firmware
image.
However this wouldn't make much sense. The MP firmware contains Asterisk, but
it would be of limited use since the bullet has no FXS interface, and only 4
MB of flash. It would hardly fit.
So better follow the path already mentioned by Steve.
Cheers,
Elektra
Tyrone Miles
Thank you, Elektra
Tyrone Miles
Is it possible to manage multiple VT/Mesh networks(VTE's) from one
main Afrimesh server setup. If possible, what are the limitations?
Main Office - VTE (main hub station/ multiple mesh networks) -
Afrimesh - Asterisk - PSTN - Internet ->
Agent Location - VTE - Mesh - (Main Office) ->
elektra
sorry for the late reply! I am not knowledgeable enough to answer this
question. I was hoping someone more competent would pick up this question.
Antoine?
Cheers,
Elektra
Antoine van Gelder
>> Is it possible to manage multiple VT/Mesh networks(VTE's) from one
>> main Afrimesh server setup. If possible, what are the limitations?
>>
>> Main Office - VTE (main hub station/ multiple mesh networks) -
>> Afrimesh - Asterisk - PSTN - Internet ->
>> Agent Location - VTE - Mesh - (Main Office) ->
Managing multiple networks from a single server&dashboard is something quite a few people have asked for.
Although Afrimesh can only manage a single network at present it would not require any radical changes to implement this functionality.
The main limitation with such an implementation would be that the various networks would each require a distinct network address in order that they may be uniquely identified within the system.
If anyone wanted to work on extending the code I'd be more than happy to offer some direction!
- antoine
Tyrone Miles
I would offer my assistance, but I'm not a programmer. My though would
be to set it up like a VLAN with a unique id for that subnet. This
would be base on the super-node being the main focus in that network?
If I can be of assistance, I would honor the request.
Thanks.
On Feb 22, 10:05 am, Antoine van Gelder <anto...@7degrees.co.za>
wrote:
Antoine van Gelder
> Hello Antoine,
> I would offer my assistance, but I'm not a programmer. My though would
> be to set it up like a VLAN with a unique id for that subnet. This
> would be base on the super-node being the main focus in that network?
> If I can be of assistance, I would honor the request.
> Thanks.
Hi Tyrone,
VLAN's wouldn't bee too much help in this instance - essentially the limitation is that each network needs a unique network address in order to avoid the situation where you have two routers from two different mesh networks showing up on the same IP address on the dashboard
e.g. You'd need to do something along the lines of:
Mesh 1 -> 10.130.1.0/24
Mesh 2 -> 10.130.2.0/24
Mesh 3 -> 10.130.3.0/24
The main work required to extend the Afrimesh code to handle this use case would be to query the vis daemon on each mesh network and concatenate the results.
Having said that, another (probably terrible) thought has just occurred to me, and maybe you can help here Elektra?
Is it possible / a-good-idea to to run a single B.A.T.M.A.N. vis daemon on a server shared between multiple mesh networks and have nodes from all networks report to that vis daemon?
- antoine
Don Onwunumah
I was thinking about extending and diving into Afrimesh development for some of my monitoring needs (it is based around a Django web app that auto-magically gave me reports on the health of Nodes) and this seems like a good starting point. Although I am not an expert in LUA, I am pretty versed in nearly everything else and have played around with it in the past.
If you point me to the right direction I will be happy to help - FYI I am already in the process of setting up a dev environment to look at the code base.
Regards,
Don
elektra
just having one instance of the Batman VIS server running for each mesh should be the solution.
Cheers,
Elektra
Antoine van Gelder
On 23 Feb 2011, at 09:36 , Don Onwunumah wrote:
> Antoine,
>
> I was thinking about extending and diving into Afrimesh development for some of my monitoring needs (it is based around a Django web app that auto-magically gave me reports on the health of Nodes) and this seems like a good starting point. Although I am not an expert in LUA, I am pretty versed in nearly everything else and have played around with it in the past.
>
> If you point me to the right direction I will be happy to help - FYI I am already in the process of setting up a dev environment to look at the code base.
The docs on the Afrimesh wiki are (mostly) up to date but please feel free to bombard me with email if you have questions getting a dev environment running!
Just make sure you check out the _unstable_ branch:
svn checkout http://afrimesh.googlecode.com/svn/branches/unstable
:-)
re: Very brief thoughts on visualizing multiple vis servers:
So the way I'd approach it would be to add a new module called topology.lua to:
afrimesh/villagebus/lua/modules/
Within that module I would:
a) Accept a request for the mesh topology from the dashboard
b) Fire off a request to each of the B.A.T.M.A.N. vis servers I want to visualize
c) Concatenate the output from each vis server
d) Respond to the initial request with the concatenated output.
If this sounds like something you might feel like tackling please drop me an email and we can make a time to chat on IRC.
- antoine