public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH] ndp: Don't send unsolicited router advertisement if we can't, yet
Date: Fri, 15 Nov 2024 15:17:31 +0100	[thread overview]
Message-ID: <20241115141731.51359-1-sbrivio@redhat.com> (raw)

ndp_timer() is called right away on the first epoll_wait() cycle,
when the communication channel to the guest isn't ready yet:

  1.0038: NDP: sending unsolicited RA, next in 264s
  1.0038: tap: failed to send 1 frames of 1

check that it's up before sending it. This effectively delays the
first gratuitous router advertisement, which is probably a good idea
given that we expect the guest to send a router solicitation right
away.

Fixes: 6e1e44293ef9 ("ndp: Send unsolicited Router Advertisements")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
---
 ndp.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/ndp.c b/ndp.c
index 7ee44b2..b458785 100644
--- a/ndp.c
+++ b/ndp.c
@@ -420,9 +420,12 @@ void ndp_timer(const struct ctx *c, const struct timespec *now)
 	interval = min_rtr_adv_interval +
 		random() % (max_rtr_adv_interval - min_rtr_adv_interval);
 
-	info("NDP: sending unsolicited RA, next in %llds", (long long)interval);
+	if (next_ra) {
+		info("NDP: sending unsolicited RA, next in %llds",
+		     (long long)interval);
 
-	ndp_ra(c, &in6addr_ll_all_nodes);
+		ndp_ra(c, &in6addr_ll_all_nodes);
+	}
 
 	next_ra = now->tv_sec + interval;
 }
-- 
@@ -420,9 +420,12 @@ void ndp_timer(const struct ctx *c, const struct timespec *now)
 	interval = min_rtr_adv_interval +
 		random() % (max_rtr_adv_interval - min_rtr_adv_interval);
 
-	info("NDP: sending unsolicited RA, next in %llds", (long long)interval);
+	if (next_ra) {
+		info("NDP: sending unsolicited RA, next in %llds",
+		     (long long)interval);
 
-	ndp_ra(c, &in6addr_ll_all_nodes);
+		ndp_ra(c, &in6addr_ll_all_nodes);
+	}
 
 	next_ra = now->tv_sec + interval;
 }
-- 
2.43.0


                 reply	other threads:[~2024-11-15 14:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20241115141731.51359-1-sbrivio@redhat.com \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).