All of lore.kernel.org
 help / color / mirror / Atom feed
From: elektra <onelektra@gmx.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] b.a.t.m.a.n. + wrt54gl + OpenWrt Kamikaze +   X-wrt]
Date: Tue, 11 Mar 2008 08:17:45 +0100	[thread overview]
Message-ID: <47D63219.3020603@gmx.net> (raw)
In-Reply-To: <52469.70.253.200.118.1205190931.squirrel@webmail.reglue.org>

I wrote: Use individual IPs for each interface! If you want to use 
batman on all interfaces, assign IPs out of the mesh IP subnet range for 
each interface.

I don't see that here:

ifconfig eth0.0 *103.0.0.3* netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig eth0.1 *103.0.0.3* netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig eth0 *103.0.0.3* netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig wl0 *103.0.0.3* netmask 255.0.0.0 broadcast 103.255.255.255

And: Ports 4305-4307 are for the new versions of batman - which one are 
you using?





> I got batmand working with this startup script:
> (but I lost internet connectivity, even setting the gateway to 103.0.0.3)
>
>
> killall batmand
> iwconfig wl0 channel 10 essid project mode Ad-Hoc
> ifconfig eth0.0 103.0.0.3 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig eth0.1 103.0.0.3 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig eth0 103.0.0.3 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig wl0 103.0.0.3 netmask 255.0.0.0 broadcast 103.255.255.255
> 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
> batmand eth0.0 eth0.1 wl0 eth0 br-lan &
>
>
> _______________________________________________
> 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
>
>   


  reply	other threads:[~2008-03-11  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 23:15 [B.A.T.M.A.N.] b.a.t.m.a.n. + wrt54gl + OpenWrt Kamikaze + X-wrt] dondavis
2008-03-11  7:17 ` elektra [this message]
2008-03-11 12:00   ` Donald Davis
2008-03-11 13:56     ` dondavis
2008-03-11 14:07       ` side note " dondavis
  -- strict thread matches above, loose matches on Subject: below --
2008-03-10 17:02 Donald Davis
2008-03-10  5:18 dondavis
2008-03-10  9:57 ` elektra
2008-03-10 11:17   ` Donald Davis
2008-03-10 11:47     ` elektra
2008-03-10 11:51       ` elektra

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=47D63219.3020603@gmx.net \
    --to=onelektra@gmx.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.