From: David Ahern <dsahern@kernel.org>
To: Ben Greear <greearb@candelatech.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>
Subject: Re: VRF and UDP broadcast frames
Date: Mon, 25 Aug 2025 08:16:38 -0600 [thread overview]
Message-ID: <511a143b-183d-40aa-926c-25931e03b2f4@kernel.org> (raw)
In-Reply-To: <39bf5755-254b-e7b8-cc15-500be99d0a6b@candelatech.com>
[ cc'ed Ido ]
On 8/22/25 1:16 PM, Ben Greear wrote:
> Hello,
>
> Assume I have a network interface assigned to a VRF (wifi AP interface
> is what I'm testing now).
> I would like to have it be able to send and receive UDP broadcast
> frames. I am binding the socket
> to the AP netdev with SO_BINDTODEVICE. From what I can tell, the socket
> at least cannot receive
> UDP broadcasts sent to it. I do see the broadcast arriving on the AP
> interface if I run tshark.
>
> Is there any particular issue with UDP broadcast sockets in VRF? Do I
> have to instead
> bind to the vrf netdev instead of the ap netdev?
I am not aware of any issues with VRF and broadcast, but the fcnal-test
suite (covers permutations across the uapi) is lacking broadcast tests.
As I recall you tend to run relatively new kernels, so either device
should work.
I use the fib:* tracepoints as a start point for debugging cases like this.
>
> And always possible I doing something wrong in my socket code, my
> current test setup
> is quite complicated.
>
> Thanks,
> Ben
>
next prev parent reply other threads:[~2025-08-25 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 19:16 VRF and UDP broadcast frames Ben Greear
2025-08-25 14:16 ` David Ahern [this message]
2025-08-25 15:20 ` Ben Greear
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=511a143b-183d-40aa-926c-25931e03b2f4@kernel.org \
--to=dsahern@kernel.org \
--cc=greearb@candelatech.com \
--cc=idosch@nvidia.com \
--cc=linux-wireless@vger.kernel.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.