[B.A.T.M.A.N.] Gateway routing / finding

[B.A.T.M.A.N.] Gateway routing / finding

[dondavis]

Yesterday, I thought I had a basic understanding of what was going on and
how to do it.

So this morning I woke up and decided to improve it with the individual
ip's for each interface.
killall batmand
iwconfig wl0 channel 10 essid project mode Ad-Hoc
ifconfig eth0 103.0.0.81 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig eth0.0 103.0.0.82 netmask 255.0.0.0 broadcast 103.255.255.255
#ifconfig eth0.1 103.0.0.83 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig wl0 103.0.0.84 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig br-lan 103.0.0.85 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 eth0.0 wl0 br-lan &


Yesterday I had all the batmannodes with internet connectivity.  I did
notice though that if changed gateways they weren't picking up on it; so I
was going to try out batman III once I clarified for myself what was going
on.  So I tried the aforementioned script.  It didn't work.  So I thought
"ah ha, it might help the interfaces to share ip addresses because some
piece is not being found."  So I went back to what I thought was a working
script.

killall batmand
iwconfig wl0 channel 10 essid project mode Ad-Hoc
ifconfig eth0 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig eth0.0 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
# ifconfig eth0.1 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig wl0 103.0.0.8 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 br-lan &

that didn't work so I killalled batmand and then
 batmand -d 3 -r 3 -p 103.0.0.3 wl0 br-lan

I was wrong.

Even though I see:
Using interface wl0 with address 103.0.0.8 and broadcast address
103.255.255.255
Using interface br-lan with address 103.0.0.8 and broadcast address
103.0.0.255
debug level: 3
routing class: 3
preferred gateway: 103.0.0.3
Adding route to 103.0.0.3 via 0.0.0.0 (br-lan)
Adding route to 10.0.2.122/32 via 103.0.0.3 (br-lan)

It has found the internet gateway 10.0.2.122; it can't reach the internet.

now, I'm going to:
remove the x-wrt webif-batman stuff (just in case)
look for batman config files
reread the openmesh.net stuff
reinstall batman with the pkg's from openmesh.net
possible try out batman III

thoughts? suggestions?

cheers,

D Davis

Re: [B.A.T.M.A.N.] Gateway routing / finding

[elektra]

I wrote that newer versions of Batman (Experimental and Beta) use ports 
4305-4307, but you are using the stable version. So if you didn't 
upgrade you have to open ports 1966-1967, not 4305.

> Yesterday, I thought I had a basic understanding of what was going on and
> how to do it.
>
> So this morning I woke up and decided to improve it with the individual
> ip's for each interface.
> killall batmand
> iwconfig wl0 channel 10 essid project mode Ad-Hoc
> ifconfig eth0 103.0.0.81 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig eth0.0 103.0.0.82 netmask 255.0.0.0 broadcast 103.255.255.255
> #ifconfig eth0.1 103.0.0.83 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig wl0 103.0.0.84 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig br-lan 103.0.0.85 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 eth0.0 wl0 br-lan &
>
>
> Yesterday I had all the batmannodes with internet connectivity.  I did
> notice though that if changed gateways they weren't picking up on it; so I
> was going to try out batman III once I clarified for myself what was going
> on.  So I tried the aforementioned script.  It didn't work.  So I thought
> "ah ha, it might help the interfaces to share ip addresses because some
> piece is not being found."  So I went back to what I thought was a working
> script.
>
> killall batmand
> iwconfig wl0 channel 10 essid project mode Ad-Hoc
> ifconfig eth0 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig eth0.0 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
> # ifconfig eth0.1 103.0.0.8 netmask 255.0.0.0 broadcast 103.255.255.255
> ifconfig wl0 103.0.0.8 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 br-lan &
>
> that didn't work so I killalled batmand and then
>  batmand -d 3 -r 3 -p 103.0.0.3 wl0 br-lan
>
> I was wrong.
>
> Even though I see:
> Using interface wl0 with address 103.0.0.8 and broadcast address
> 103.255.255.255
> Using interface br-lan with address 103.0.0.8 and broadcast address
> 103.0.0.255
> debug level: 3
> routing class: 3
> preferred gateway: 103.0.0.3
> Adding route to 103.0.0.3 via 0.0.0.0 (br-lan)
> Adding route to 10.0.2.122/32 via 103.0.0.3 (br-lan)
>
> It has found the internet gateway 10.0.2.122; it can't reach the internet.
>
> now, I'm going to:
> remove the x-wrt webif-batman stuff (just in case)
> look for batman config files
> reread the openmesh.net stuff
> reinstall batman with the pkg's from openmesh.net
> possible try out batman III
>
> thoughts? suggestions?
>
> cheers,
>
> D Davis
>
>
>
> _______________________________________________
> 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
>
>   

Re: [B.A.T.M.A.N.] Gateway routing / finding

[dondavis]

>
>
> I wrote that newer versions of Batman (Experimental and Beta) use ports
> 4305-4307, but you are using the stable version. So if you didn't
> upgrade you have to open ports 1966-1967, not 4305.


Sorry, I wasn't sure what constituted 'newer.'  My apologies.  I thought
the ports were okay beacuse I was getting Batman info.  I just wasn't able
to send ip packets through the gateway.  I've tried to amend the script to
reflect your advice but I get

batmand -d 3 -r 3 -p 10.0.2.115 eth0 eth0.0 wl0 br-lan
B.A.T.M.A.N. 0.2 (compability version 3)
Using interface eth0 with address 103.0.0.31 and broadcast address
103.255.255.255
Using interface eth0.0 with address 103.0.0.32 and broadcast address
103.255.255.255
Using interface wl0 with address 103.0.0.33 and broadcast address
103.255.255.255
Using interface br-lan with address 103.0.0.3 and broadcast address
103.0.0.255
debug level: 3
routing class: 3
preferred gateway: 10.0.2.115
Adding route to 103.0.0.8 via 0.0.0.0 (br-lan)
Adding route to 103.0.0.81/32 via 103.0.0.8 (br-lan)
Adding route to 10.0.2.115/32 via 103.0.0.8 (br-lan)
Adding route to 103.0.0.82/32 via 103.0.0.8 (br-lan)
Adding route to 103.0.0.83/32 via 103.0.0.8 (br-lan)

and no internet.

I can ping the gateway.

I've tried to upgrade the script:
(I know there are some extra ports...)

killall batmand
iwconfig wl0 channel 10 essid project mode Ad-Hoc
ifconfig eth0 103.0.0.31 netmask 255.0.0.0 broadcast 103.255.255.255
ifconfig eth0.0 103.0.0.32 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 wl0 103.0.0.33 netmask 255.0.0.0 broadcast 103.255.255.255
iptables -t filter -I INPUT 2 -p udp --dport 1965 --sport 1965 -j ACCEPT
iptables -t filter -I INPUT 2 -p udp --dport 1966 --sport 1966 -j ACCEPT
iptables -t filter -I INPUT 2 -p udp --dport 1967 --sport 1967 -j ACCEPT
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 1965 --sport 1965 -j ACCEPT
iptables -t filter -I OUTPUT 2 -p udp --dport 1966 --sport 1966 -j ACCEPT
iptables -t filter -I OUTPUT 2 -p udp --dport 1967 --sport 1967 -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 eth0.0 eth0.1 wl0 br-lan &

Re: [B.A.T.M.A.N.] Gateway routing / finding

[elektra]

Hi -
> Sorry, I wasn't sure what constituted 'newer.'  
<quote>

Btw.: IANA has assigned port 4305 for the newer versions of Batman. _So 
if you are going to update to_ Experimental or Beta open the firewall 
for udp ports 4305 and 4306 instead of 1966. 4305 is for protocol 
messages, 4306 is used for tunneling traffic to the gateway.  If you 
want to use the VIS server, open port 4307 also.

</quote>

Which interfaces did you (or the system that you have installed) assign 
to br-lan? You shouldn't assign a interface to batman twice (by itself 
and as part of a bridge)

Re: [B.A.T.M.A.N.] Gateway routing / finding

[dondavis]

>
> Which interfaces did you (or the system that you have installed) assign
> to br-lan? You shouldn't assign a interface to batman twice (by itself
> and as part of a bridge)

I'm a bit unsure about which interface to use.  Now, I've switched to
freifunk to try to facilitate things.  It's a new set of interfaces
(similar but different).

br0
eth0
eth1
vlan0
vlan1
lo

and on the machine with the internet connection

tun0
tun1

netstat -rn for the machine with an internet connection tells me:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.2.0        0.0.0.0         255.255.255.0   U         0 0          0
vlan1
0.0.0.0         10.0.2.1        0.0.0.0         UG        0 0          0
vlan1

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.2.0        0.0.0.0         255.255.255.0   U         0 0          0
vlan1

or most recently....
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
10.0.2.100      192.168.1.2     255.255.255.255 UGH       0 0          0 br0
192.168.1.2     0.0.0.0         255.255.255.255 UH        0 0          0 br0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 br0
10.0.2.0        0.0.0.0         255.255.255.0   U         0 0          0
vlan1

Re: [B.A.T.M.A.N.] Gateway routing / finding

[Donald Davis]

Well, I think I've got it working for now with freifunk.  I'm thinking
there were some ports that needed unblocking (besides 1966-67) in
Kamikaze.  I think disabling the  firewall in freifunk helped clear
things up.  

Thank you for your help.  Hopefully I'm close.


Cheers,

D Davis