When i start meshs3d i can see the ip of the access point but not the image
and on shell i got this errors:
(process:29085): LibG3D-WARNING **: no handler for file
'objs/accesspoint.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'./objs/accesspoint.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../objs/accesspoint.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../../objs/accesspoint.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'objs/accesspoint_inet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'./objs/accesspoint_inet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../objs/accesspoint_inet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../../objs/accesspoint_inet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file 'objs/internet.3ds'
found
(process:29085): LibG3D-WARNING **: no handler for file
'./objs/internet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../objs/internet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../../objs/internet.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file 'objs/btn_close.3ds'
found
(process:29085): LibG3D-WARNING **: no handler for file
'./objs/btn_close.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../objs/btn_close.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../../objs/btn_close.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'objs/s3d_berlios_de.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'./objs/s3d_berlios_de.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../objs/s3d_berlios_de.3ds' found
(process:29085): LibG3D-WARNING **: no handler for file
'../../objs/s3d_berlios_de.3ds' found
The file are present in that folder but seem that meshs3d can't find it
right?
Any help is welcome :)
Eidos
Hi guys!
I'm trying to compile B.A.T.M.A.N. for the fonera 2100 from svn
http://downloads.open-mesh.net/svn/batman/trunk/batman/ (is in this
directory the latest svn code for B.A.T.M.A.N. ?), but i don't know how
cross compile for fonera 2100 ... Can you help me?
Eidos
news from leipzig, 131 nodes with batman experimental.
-------- Original-Nachricht --------
Betreff: [FFL] B.A.T.M.A.N eXperimental Status
Datum: Fri, 13 Jun 2008 00:21:36 +0200
Von: tetzlav <tetzlav(a)leipzig.freifunk.net>
Antwort an: Freifunk Leipzig <freifunk-leipzig(a)subsignal.org>
Organisation: Freifunk Leipzig
An: freifunk-leipzig(a)subsignal.org
Newsgruppen: freifunk.de.leipzig.discuss
Ist vllt. niemandem so wirklich aufgefallen das ein alternatives
Routingprotokoll neben olsr ein Schattendasein in allen aktuellen
Firmwares führt.
Grade eben hat mich mal interessiert wieviele Freifunk-Router
mittlerweile bmx
"sprechen"...
> root@tetzlav-uplink:~# ip route list table 78 | wc -l
> 131
das heisst es existieren in der bmx-host-Routen-Tabelle 131 Einträge,
was soviel
bedeutet wie: Es existiert ein Netz aus 131 Knoten, bei welchen man olsr
ausschalten könnte ohne das der Kontakt zueinander verloren gehen
würde... ;)
Das GRÖSSTE reale B.A.T.M.A.N-Netz der Welt würde ich mal sagen. :D
Gruß
tetzlav
_______________________________________________
Freifunk Leipzig Community
http://leipzig.freifunk.net
Hi there,
Exists there any theoretical work about batman's routing properties?
For example a model explaining batman as some kind of 'ant-routing'
or statements a'la
"If the network and load balance does not change for a long enough
time, than the routing tables converge agains a nash-equilibrium."
Do you know, if anybody is working in that direction, or is 'out
there' somebody interested in this kind of work?
with kind regards,
daniel
Elektra,
Thank you for pointing out in May 08 that most embedded boards do not
have enough CPU power to saturate the capacity of single radio link. I
was experimenting Batman in a straight line, three node configuration
with the middle node having two radios so it doesn't have to switch
between node 1 and node 3. My configuration is as follows:
node 1 node 2 node 3
------ ------ ------
ath0 <--ch 1--> ath0
ath1 <--ch 11-> ath0
When I ran iperf between node 1 and 3, I did not see any throughput
improvements with either one or two radios in node 2. I even stopped
Batman and manually setup the routes and the performance remains the
same. However, when I upgrade node 2 from a 200MHz CPU board to a
500MHz CPU board, the bandwidth went up 50%. So thanks again for
pointing out my bottleneck:)
Lastly, can someone suggest some embedded boards fast enough to push
wifi radios to its limits?
Thanks,
Shane
Hi all.
I have made a new version of the patch posted by acinonyx (rv502),
for interfacing batmand with the zebra routing daemon. There are 2
versions available: One for the latest svn (rv1060) and one for the
stable 0.3 release. Take a look at:
http://www.cslab.ece.ntua.gr/~chazapis/batman/
Please consider this code experimental. Some initial tests are
promising,
but there may be bugs... :)
For now, the plug-in just supports sending routes to zebra, not the
opposite (redistributing routes from other protocols). That was also
the case with the older - rv502 - version.
What the patch does is:
- Adds a flag "-z" to the batmand executable which may be used to
enable zebra communication and accepts as an argument the
path to the corresponding zebra unix-domain socket.
- If zebra is enabled:
- No rules are added to the kernel.
- All UNICAST routes are sent to zebra.
All routes are also sent to the kernel (in linux/route.c), but the extra
routing tables are not used by linux, because of the lack of rules.
These routing tables remain, just to help with route management,
so batmand can successfully remove all added routes on shutdown.
Antony
I am seriously looking at using B.A.T.M.A.N. to drive a mesh network in
a small town in Australia. One of the hassles with typical mesh networks
is the way the performance drops off when you have many hops, due to the
radio having to keep switching between send and receive. The standard
way to get around this appears to be to use multiple radios.
How is this done with batman? Is it a case of having multiple
directional aerials - such that one radio can be receiving from one
direction and another can be sending to the next node up the chain? It
makes sense to put the local traffic (e.g. running a local AP) on a
separate radio from the "back haul".
Does anyone have any experience with sort of layout? The main driver
here is performance rather than coverage.
Damian
--
Launtel - Plugging Tassie into the world
Tel: 1800LAUNTEL (1800528683)
Mob: 0418217582
Fax: 1300784109
http://www.launtel.net.au
Hi,
I'm testing Batman-Advanced on Open WRT. I've compiled the package
release # 1074 (the last from svn) and I'm working on a X86 machine.
I've installed Batman Advanced on 2 virtual machine (using Qemu and
Vde Switch, software used to create the simulation environment) and,
after the configuration of the interface and the assignation of the IP
address on each bat0 device I've tried to test the connection between
the machine using ping command. Well, the ping crash the reciver
machine. I only have to restart becouse it doesn't answer.
Someone can help me?
Regards, Paolo