From: John Harris <JHarris@web.de>
To: b.a.t.m.a.n@open-mesh.net, dondavis@reglue.org
Subject: Re: [B.A.T.M.A.N.] Some questions to BATMAN
Date: Mon, 29 Dec 2008 21:39:27 +0100 [thread overview]
Message-ID: <1398907753@web.de> (raw)
Hiii Don,
thank you very much for your reply, for your help...
>
>> 1)
>> I will build a mesh network.. One of my router is connected to my server
>> with the IP 129.211.186.12. I can't make
>> a traceroute through my router to this server. If I try to make
>> "traceroute 129.211.186.12" from an another router I get the message:
>> "PING 129.211.186.12 (129.211.186.12): 56 data bytes
>> ping: sendto: Network is unreachable
>
>
> router Server (129.211.186.12)
> (batman eth0) <------------------> (batman some wireless device)
>
> On the router, which firmware are you running with Batman?
>
>
> When you type batmand -c -d 1 on the router /server what do you see?
>
> What does batmand -v show on the router / server?
>
>
I have some problems with my server at the moment, I will write the output of the other commands as soon as possible...
my freifunk firmware is v1.6.29 and the batmand version is :B.A.T.M.A.N. 0.2 rv502 (compability version 3)
>> I can send ping requests from my server to the router and from the
>> router to the server, but as I said, I can't make a traceroute to the
>> server
>> from an another router. My question is, how can I do this ?
>>
>> In OLSR it was not a problem to trace the server through the router.
>> Should I change something in HNA messages ?
>>
>> 2)
>> I read the HowTO from Freifunk Leipzig about the configuration of
>> BATMAN, look here http://wiki.leipzig.freifunk.net/BATMAN. How is the
>> configuration
>> If I want to run BATMAN in Ubuntu Intrepid? How can I configure the
>> IPTABLES ?
>>
>
> For newer batman and experimental you'll want to open up ports 4305-4307:
>
> iptables -t filter -I INPUT 2 -p udp --dport 4305 --sport 4305 -j ACCEPT
> iptables -t filter -I INPUT 2 -p udp --dport 4306 --sport 4306 -j ACCEPT
> iptables -t filter -I INPUT 2 -p udp --dport 4307 --sport 4307 -j ACCEPT
> iptables -t filter -I OUTPUT 2 -p udp --dport 4305 --sport 4305 -j ACCEPT
> iptables -t filter -I OUTPUT 2 -p udp --dport 4306 --sport 4306 -j ACCEPT
> iptables -t filter -I OUTPUT 2 -p udp --dport 4307 --sport 4307 -j ACCEPT
You helped me a lot so far,thank you,
I will write the output of the commands as soon as possible...
greetings,
John
>
>
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
_______________________________________________________________________
Sensationsangebot verlängert: WEB.DE FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.web.de/?ac=OM.AD.AD008K15039B7069a
next reply other threads:[~2008-12-29 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 20:39 John Harris [this message]
2008-12-30 2:14 ` [B.A.T.M.A.N.] Some questions to BATMAN Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2008-12-31 14:23 John Harris
2008-12-31 12:20 John Harris
2008-12-29 8:36 John Harris
2008-12-28 11:14 John Harris
2008-12-29 12:56 ` Don Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1398907753@web.de \
--to=jharris@web.de \
--cc=b.a.t.m.a.n@open-mesh.net \
--cc=dondavis@reglue.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox