All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Non-batman Clients
Date: Wed, 01 Jun 2016 10:54:34 +0200	[thread overview]
Message-ID: <1832776.WWitf2ljLt@prime> (raw)
In-Reply-To: <31c117a7ea164528a8d01a730c7dd9e8@Ek.usurf.usu.edu>

[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-06-01  8:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 22:25 [B.A.T.M.A.N.] Non-batman Clients Jonathan Haws
2016-06-01  5:47 ` Jonathan Haws
2016-06-01  8:54 ` Simon Wunderlich [this message]
2016-06-02  0:39 ` Marek Lindner
2016-06-08 15:09   ` Jonathan Haws
2016-06-08 18:08     ` Jonathan Haws
2016-06-08 19:29       ` Jonathan Haws
2016-06-09  1:21         ` Marek Lindner
2016-06-20 21:16         ` Jonathan Haws

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=1832776.WWitf2ljLt@prime \
    --to=sw@simonwunderlich.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 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.