From: "gary" <guohuizou2000@sina.com>
To: 'Jonathan Haws' <jhaws@sdl.usu.edu>, sven@narfation.org
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] alfred and batadv-vis issue
Date: Tue, 30 Oct 2018 13:24:23 +0800 [thread overview]
Message-ID: <001901d47010$d20e57d0$762b0770$@sina.com> (raw)
In-Reply-To: <98bb1f935c1da5ecdb978b7c95e243ec5c81f04a.camel@sdl.usu.edu>
In my test setup, both BBN1/2 and MP1/2 are in one subnet.
ipv4_arp_request ret = -1 interface =0x120020070 sipaddr = 0x50505f7 (the first try, sipaddr is right)
ipv4_arp_request ret = 0 interface =0x120020070 sipaddr = 0x50505f7 (the second try with latest patch)
the cause should be there is no arp entry for the source ip address at the first try.
-----Original Message-----
From: Jonathan Haws <jhaws@sdl.usu.edu>
Sent: 2018年10月30日 0:07
To: guohuizou2000@sina.com; sven@narfation.org
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] alfred and batadv-vis issue
> The patch does NOT work for me.
>
> I review the code again and find the issue. The following code may
> make my testbed work.
Gary - can you describe to me some more details of your test setup?
How are BBN1 and BBN2 configured? Are they machines with two different Ethernet interfaces (i.e. each having one connected to the downstream node and one connected to the switch)? Are they more or less acting as routers (i.e. doing IP forwarding)?
The testing I have been doing is just connecting MP1 and MP2 to the same switch and having them on the same subnet. Is that not the case in your setup?
The other thing I am interested in is what is the result of the first
ioctl() call? I'm guessing it has to be failing, or else the patch would have worked for you. Can you add a print statement before the return that would give the error string as well as the interface and IP (i.e. interface->interface and addr->ipv4.s_addr)? That would be helpful in helping me find the root issue.
One thing to note (and Sven, maybe you can tell me if this is
expected): in my testing I found that alfred is getting into this ipv4_arp_request call for the local node as well, thus the very first
ioctl() will fail with "No such device or address". Should there be a check for this being the local node and just discard it before making the check or is making the check all the time then discarding okay?
next prev parent reply other threads:[~2018-10-30 5:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 5:53 [B.A.T.M.A.N.] alfred and batadv-vis issue gary
2018-10-18 6:22 ` Sven Eckelmann
2018-10-22 17:36 ` Jonathan Haws
2018-10-23 3:02 ` gary
2018-10-23 4:04 ` Jonathan Haws
2018-10-23 6:29 ` Sven Eckelmann
2018-10-23 9:52 ` gary
2018-10-23 10:25 ` Sven Eckelmann
2018-10-23 13:50 ` Jonathan Haws
2018-10-23 14:06 ` Sven Eckelmann
2018-10-23 14:11 ` Jonathan Haws
2018-10-23 14:16 ` Sven Eckelmann
2018-10-24 18:39 ` Jonathan Haws
2018-10-25 6:15 ` Sven Eckelmann
2018-10-25 9:06 ` gary
2018-10-29 16:07 ` Jonathan Haws
2018-10-29 16:48 ` Sven Eckelmann
2018-10-29 17:25 ` Jonathan Haws
2018-10-29 17:34 ` Sven Eckelmann
2018-10-30 5:24 ` gary [this message]
2018-10-30 14:20 ` Jonathan Haws
2018-10-30 14:27 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2018-10-25 13:40 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='001901d47010$d20e57d0$762b0770$@sina.com' \
--to=guohuizou2000@sina.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=jhaws@sdl.usu.edu \
--cc=sven@narfation.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