27 May
2016
27 May
'16
10:25 p.m.
I've followed the quick start guide, but apparently I'm missing
something when it comes to non-batman clients.
I've set all this up using vagrant and VirtualBox. The mesh seems to
work perfectly, however when I put in non-batman clients they cannot
communicate one with another. I would expect that they would be able to
ping one another.
I've given IP addresses to the bridge adapters on the 192.168.1.0/24
subnet. The clients I've given IP addresses on that same subnet
(192.168.1.121 and 192.168.1.142). When I tried pinging, I don't get
anything back. Sniffing packets in tcpdump shows that it is never
getting anything back, though I did get an ARP back once with the
correct MAC address, but still couldn't ping. Never got an ARP back
again...
I can ping from each client to the IP address of the bridge they are
connecting to, but cannot ping anything else on the network.
Any thoughts? Hopefully someone has seen this before and can point me
in the right direction!
Also, is there a separate list for alfred, or should I use this list for
alfred questions?
Thanks!
Jon
Here are the commands I used to setup:
batctl if add eth0 (eth0 already up)
ip link add name br0 type bridge
ip link set dev eth1 master br0
ip link set dev bat0 master br0
ip link set up dev eth1
ip link set up dev bat0
ip addr replace dev br0 192.168.1.102/24 (and 104 on the other node)
Here is what batadv-vis shows for my setup (I changed the labels "TT"
for the two clients to "CLI<IP>").
digraph {
subgraph "cluster_08:00:27:2c:10:05" {
"08:00:27:2c:10:05"
}
"08:00:27:2c:10:05" -> "08:00:27:6b:86:2e"
[label="1.016"]
"08:00:27:2c:10:05" -> "0a:00:27:00:00:06" [label="TT"]
"08:00:27:2c:10:05" -> "1e:8d:d3:23:ab:d4" [label="TT"]
"08:00:27:2c:10:05" -> "08:00:27:b1:38:03"
[label="CLI142"]
"08:00:27:2c:10:05" -> "1e:8d:d3:23:ab:d4" [label="TT"]
"08:00:27:2c:10:05" -> "08:00:27:1c:9b:14" [label="TT"]
subgraph "cluster_08:00:27:a2:8c:62" {
"08:00:27:a2:8c:62"
}
"08:00:27:a2:8c:62" -> "08:00:27:83:dd:41"
[label="1.000"]
"08:00:27:a2:8c:62" -> "08:00:27:38:31:55"
[label="1.000"]
"08:00:27:a2:8c:62" -> "08:00:27:f6:78:1a" [label="TT"]
"08:00:27:a2:8c:62" -> "d6:f4:e6:bd:22:fb" [label="TT"]
"08:00:27:a2:8c:62" -> "d6:f4:e6:bd:22:fb" [label="TT"]
"08:00:27:a2:8c:62" -> "0a:00:27:00:00:05" [label="TT"]
subgraph "cluster_08:00:27:38:31:55" {
"08:00:27:38:31:55"
}
"08:00:27:38:31:55" -> "08:00:27:83:dd:41"
[label="1.000"]
"08:00:27:38:31:55" -> "08:00:27:a2:8c:62"
[label="1.000"]
"08:00:27:38:31:55" -> "52:98:12:67:6b:06" [label="TT"]
"08:00:27:38:31:55" -> "0a:00:27:00:00:04" [label="TT"]
"08:00:27:38:31:55" -> "08:00:27:08:ee:90"
[label="CLI121"]
"08:00:27:38:31:55" -> "52:98:12:67:6b:06" [label="TT"]
"08:00:27:38:31:55" -> "08:00:27:17:21:9d" [label="TT"]
subgraph "cluster_08:00:27:6b:86:2e" {
"08:00:27:6b:86:2e"
"08:00:27:83:dd:41" [peripheries=2]
}
"08:00:27:6b:86:2e" -> "08:00:27:2c:10:05"
[label="1.000"]
"08:00:27:83:dd:41" -> "08:00:27:38:31:55"
[label="1.000"]
"08:00:27:83:dd:41" -> "08:00:27:a2:8c:62"
[label="1.016"]
"08:00:27:6b:86:2e" -> "a6:f4:5c:fa:06:cd" [label="TT"]
"08:00:27:6b:86:2e" -> "0a:00:27:00:00:03" [label="TT"]
"08:00:27:6b:86:2e" -> "08:00:27:9c:bb:a3" [label="TT"]
"08:00:27:6b:86:2e" -> "a6:f4:5c:fa:06:cd" [label="TT"]
}
1 Jun
1 Jun
5:47 a.m.
I've followed the quick start guide, but
apparently I'm missing
something when it comes to non-batman clients.
I've set all this up using vagrant and VirtualBox. The mesh seems to
work perfectly, however when I put in non-batman clients they cannot
communicate one with another. I would expect that they would be able to
ping one another.
I've given IP addresses to the bridge adapters on the 192.168.1.0/24
subnet. The clients I've given IP addresses on that same subnet
(192.168.1.121 and 192.168.1.142). When I tried pinging, I don't get
anything back. Sniffing packets in tcpdump shows that it is never
getting anything back, though I did get an ARP back once with the
correct MAC address, but still couldn't ping. Never got an ARP back
again...
I can ping from each client to the IP address of the bridge they are
connecting to, but cannot ping anything else on the network.
Any thoughts? Hopefully someone has seen this before and can point me
in the right direction!
Bump...has anyone run into this before? Am I just missing something simple?
Thanks!
8:54 a.m.
Hi Jonathan,
On Friday 27 May 2016 22:25:46 Jonathan Haws wrote:
I've followed the quick start guide, but
apparently I'm missing
something when it comes to non-batman clients.
I've set all this up using vagrant and VirtualBox. The mesh seems to
work perfectly, however when I put in non-batman clients they cannot
communicate one with another. I would expect that they would be able to
ping one another.
I've given IP addresses to the bridge adapters on the 192.168.1.0/24
subnet. The clients I've given IP addresses on that same subnet
(192.168.1.121 and 192.168.1.142). When I tried pinging, I don't get
anything back. Sniffing packets in tcpdump shows that it is never
getting anything back, though I did get an ARP back once with the
correct MAC address, but still couldn't ping. Never got an ARP back
again...
I can ping from each client to the IP address of the bridge they are
connecting to, but cannot ping anything else on the network.
Any thoughts? Hopefully someone has seen this before and can point me
in the right direction!
Also, is there a separate list for alfred, or should I use this list for
alfred questions?
You can use this list for alfred stuff, there is no other list.
Thanks!
Jon
Here are the commands I used to setup:
batctl if add eth0 (eth0 already up)
ip link add name br0 type bridge
ip link set dev eth1 master br0
ip link set dev bat0 master br0
ip link set up dev eth1
ip link set up dev bat0
ip addr replace dev br0 192.168.1.102/24 (and 104 on the other node)
This looks good as far as I can tell.
Do you happen to use the 192.168.1.0/24 somewhere else? Do you have some IPs
configured on eth0 or eth1 by any chance (best to remove them).
I guess, the best way to debug is to check with tcpdump on each interface
(eth0, eth1, bat0, etc) and on each machine where you see your data is lost.
Cheers,
Simon
2 Jun
2 Jun
12:39 a.m.
On Friday, May 27, 2016 22:25:46 Jonathan Haws wrote:
I've given IP addresses to the bridge adapters on
the 192.168.1.0/24
subnet. The clients I've given IP addresses on that same subnet
(192.168.1.121 and 192.168.1.142). When I tried pinging, I don't get
anything back. Sniffing packets in tcpdump shows that it is never
getting anything back, though I did get an ARP back once with the
correct MAC address, but still couldn't ping. Never got an ARP back
again...
I can ping from each client to the IP address of the bridge they are
connecting to, but cannot ping anything else on the network.
Can you ping from the nodes running batman-adv to other nodes running batman-
adv ? In other words: Is your mesh working ?
Can you provide specifics about what you saw when running tcpdump ? What does
'never getting anything back' mean ? The ping goes one way without any pong
showing up ? Have you checked on the ping destination (via tcpdump) that the
ping ever made it there ?
Cheers,
Marek
8 Jun
8 Jun
3:09 p.m.
Can you ping from the nodes running batman-adv to
other nodes running batman-
adv ? In other words: Is your mesh working ?
Yes, I can use the standard ping command to ping any batman node on the
mesh from any other batman node. It is the non-batman clients that are
not communicating with anything. They can only ping the node they are
directly connected to.
Can you provide specifics about what you saw when
running tcpdump ? What does
'never getting anything back' mean ? The ping goes one way without any pong
showing up ? Have you checked on the ping destination (via tcpdump) that the
ping ever made it there ?
I had two non-batman clients on the mesh, connected to two different
nodes separated by a third node (i.e. for the client on node 1 to
communicate to the client on node 3, the data has to go through node 2).
Each client can ping the node they are connected to (the br0
interface, which has the IP address), but when they try and ping another
node or the other client I see the ping requests go out in tcpdump, but
nothing received at the other end (again in tcpdump). I do see a lot of
ARP requests without replies on the originator if that helps.
Thanks!
6:08 p.m.
Can you ping
from the nodes running batman-adv to other nodes running batman-
adv ? In other words: Is your mesh working ?
Yes, I can use the standard ping command to ping any batman node on the
mesh from any other batman node. It is the non-batman clients that are
not communicating with anything. They can only ping the node they are
directly connected to. Can you
provide specifics about what you saw when running tcpdump ? What does
'never getting anything back' mean ? The ping goes one way without any pong
showing up ? Have you checked on the ping destination (via tcpdump) that the
ping ever made it there ?
I had two non-batman clients on the mesh, connected to two different
nodes separated by a third node (i.e. for the client on node 1 to
communicate to the client on node 3, the data has to go through node 2).
Each client can ping the node they are connected to (the br0
interface, which has the IP address), but when they try and ping another
node or the other client I see the ping requests go out in tcpdump, but
nothing received at the other end (again in tcpdump). I do see a lot of
ARP requests without replies on the originator if that helps.
7:29 p.m.
Can you provide specifics about what you saw when
running tcpdump ? What does
'never getting anything back' mean ? The ping goes one way without any pong
showing up ? Have you checked on the ping destination (via tcpdump) that the
ping ever made it there ?
I had two non-batman clients on the mesh, connected to two different
nodes separated by a third node (i.e. for the client on node 1 to
communicate to the client on node 3, the data has to go through node 2).
Each client can ping the node they are connected to (the br0
interface, which has the IP address), but when they try and ping another
node or the other client I see the ping requests go out in tcpdump, but
nothing received at the other end (again in tcpdump). I do see a lot of
ARP requests without replies on the originator if that helps.
9 Jun
9 Jun
1:21 a.m.
On Wednesday, June 08, 2016 19:29:12 Jonathan Haws wrote:
So it seems to be that there is something up with
unicasting from a
non-batman client. Thoughts?
Do you client isolation enabled ?
https://www.open-mesh.org/projects/batman-adv/wiki/Ap-isolation
That would achieve the desired effect.
Cheers,
Marek
20 Jun
20 Jun
9:16 p.m.
So it seems to be that there is something up with
unicasting from a
non-batman client. Thoughts?
I believe I got to the bottom of the issue - a non-issue really. It was
my virtual machine network configuration. I still don't have things
working in the virtual world, but I was able to track down a few
machines to setup a quick little network and tested my configuration -
works perfectly.
Thanks for the help everyone!
2468
days inactive
2492
days old
b.a.t.m.a.n@lists.open-mesh.org
8 comments
3 participants
participants (3)
-
Jonathan Haws -
Marek Lindner -
Simon Wunderlich