From: Sven Eckelmann <sven@narfation.org>
To: Jonathan Haws <jhaws@sdl.usu.edu>
Cc: "guohuizou2000@sina.com" <guohuizou2000@sina.com>,
"b.a.t.m.a.n@lists.open-mesh.org"
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] alfred and batadv-vis issue
Date: Mon, 29 Oct 2018 17:48:34 +0100 [thread overview]
Message-ID: <17712655.F8A4oun0WA@sven-edge> (raw)
In-Reply-To: <98bb1f935c1da5ecdb978b7c95e243ec5c81f04a.camel@sdl.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Montag, 29. Oktober 2018 17:07:26 CET Jonathan Haws wrote:
[...]
> 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?
Uhm, this sounds extremely wrong to me. Why would you receive your own UDP
packets (push_data, announce_master, status_txend) again in the first place?
See netsock_own_address for the code which drops such packets in the main recv
function - you should know it because you've tried to modify it for IPv4
support.
But your memory initialization is completely broken and have to be fixed.
Right now, you are just comparing uninitialized memory regions against each
other.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-29 16:48 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 [this message]
2018-10-29 17:25 ` Jonathan Haws
2018-10-29 17:34 ` Sven Eckelmann
2018-10-30 5:24 ` gary
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=17712655.F8A4oun0WA@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=guohuizou2000@sina.com \
--cc=jhaws@sdl.usu.edu \
/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