From: Marek Lindner <mareklindner@neomailbox.ch>
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.] Non-batman Clients
Date: Thu, 02 Jun 2016 08:39:33 +0800 [thread overview]
Message-ID: <1486656.g3lhHQC2Ly@voltaire> (raw)
In-Reply-To: <31c117a7ea164528a8d01a730c7dd9e8@Ek.usurf.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-02 0:39 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
2016-06-02 0:39 ` Marek Lindner [this message]
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=1486656.g3lhHQC2Ly@voltaire \
--to=mareklindner@neomailbox.ch \
--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