From: Clemens John <clemens-john@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Problems connecting VPN and WLAN with Batman-adv
Date: Sun, 4 Apr 2010 17:41:52 +0200 [thread overview]
Message-ID: <201004041741.56665.clemens-john@gmx.de> (raw)
In-Reply-To: <201004031254.02506.lindner_marek@yahoo.de>
[-- Attachment #1: Type: Text/Plain, Size: 6076 bytes --]
On Saturday 03 April 2010 06:54:02 Marek Lindner wrote:
> Ok, since your setup is rather small I would suggest going with the easiest
> solution possible. I'm always a big fan of making little steps that work
> well instead of aiming for the big goal which you never reach because you
> die in the process of getting there.
>
> In a classical batman-adv setup the router(s) with the internet connection
> run a DHCP server and provide IPs/default route/etc for all the nodes &
> wifi- clients in range.
>
> To connect the VPNs I see 2 feasible approaches:
> * You run batman-adv over the VPN which will bring some overhead since the
> routing messages will be relayed over the VPN. Depending on the number of
> nodes this may or may not be an issue. To keep things simple all nodes run
> in the same IP address space.
We decided to keep it simple for testing. We changed the netmasks of all ip
adresses (VPN and Wifi) from /24 to /16 but it doesnt work.
I can see all Nodes with
# batctl o
but not with ping.
-------------
root@OpenWrt:~# cat /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 'proto' 'dhcp'
option 'ifname' 'eth0'
config 'interface' 'mesh'
option 'type' 'bridge'
option 'ifname' 'ath0 bat0'
option 'proto' 'static'
option 'ipaddr' '10.18.1.1'
option 'netmask' '255.255.0.0'
-------------
root@OpenWrt:~# ifconfig
ath0 Link encap:Ethernet HWaddr 00:24:01:17:B7:55
inet6 addr: fe80::224:1ff:fe17:b755/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:2324 (2.2 KiB)
ath1 Link encap:Ethernet HWaddr 06:24:01:17:B7:55
inet6 addr: fe80::424:1ff:fe17:b755/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:580 errors:0 dropped:18 overruns:0 frame:0
TX packets:337 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18512 (18.0 KiB) TX bytes:17574 (17.1 KiB)
bat0 Link encap:Ethernet HWaddr 9A:14:E1:3B:F4:88
inet6 addr: fe80::9814:e1ff:fe3b:f488/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1476 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:16 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:944 (944.0 B)
br-mesh Link encap:Ethernet HWaddr 00:24:01:17:B7:55
inet addr:10.18.1.101 Bcast:10.18.255.255 Mask:255.255.0.0
inet6 addr: fe80::ec23:2fff:fe06:37f3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:2034 (1.9 KiB)
eth0 Link encap:Ethernet HWaddr 00:24:01:17:B7:56
inet addr:192.168.178.59 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::224:1ff:fe17:b756/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3782 errors:0 dropped:0 overruns:0 frame:0
TX packets:791 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:533232 (520.7 KiB) TX bytes:93762 (91.5 KiB)
Interrupt:4 Base address:0x1000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1958 (1.9 KiB) TX bytes:1958 (1.9 KiB)
tap0 Link encap:Ethernet HWaddr 42:49:50:CF:69:3E
inet addr:10.18.0.8 Bcast:10.18.255.255 Mask:255.255.0.0
inet6 addr: fe80::4049:50ff:fecf:693e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:402 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:31752 (31.0 KiB) TX bytes:368 (368.0 B)
wifi0 Link encap:UNSPEC HWaddr 00-24-01-17-
B7-55-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5172 errors:0 dropped:0 overruns:0 frame:424
TX packets:374 errors:1 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:195
RX bytes:716632 (699.8 KiB) TX bytes:29035 (28.3 KiB)
Interrupt:3 Memory:b0000000-b000ffff
-------------
root@OpenWrt:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.178.0 * 255.255.255.0 U 0 0 0 eth0
10.18.0.0 * 255.255.0.0 U 0 0 0 br-mesh
10.18.0.0 * 255.255.0.0 U 0 0 0 tap0
default 192.168.178.1 0.0.0.0 UG 0 0 0 eth0
-------------
root@OpenWrt:~# traceroute 10.18.0.3
traceroute to 10.18.0.3 (10.18.0.3), 30 hops max, 38 byte packets
1 10.18.1.101 (10.18.1.101) 3002.434 ms !H 3010.472 ms !H 3009.891 ms !H
10.18.0.3 is a vpn node (tap0) and running batman-adv but traceroute thinks,
that it can be connected on the mesh-bridge???
I can´t figure out his problem. Hopefully someone of you can help me.
Greetings
Floh1111
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-04 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 22:54 [B.A.T.M.A.N.] Problems connecting VPN and WLAN with Batman-adv Clemens John
2010-04-02 6:52 ` Linus Lüssing
2010-04-02 10:17 ` Clemens John
2010-04-02 11:50 ` Linus Lüssing
2010-04-02 12:27 ` Clemens John
2010-04-02 16:00 ` Marek Lindner
2010-04-02 16:25 ` Bjoern Franke
2010-04-03 4:54 ` Marek Lindner
2010-04-04 15:41 ` Clemens John [this message]
2010-04-04 15:54 ` Marek Lindner
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=201004041741.56665.clemens-john@gmx.de \
--to=clemens-john@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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