Home/ Questions/Q 499163
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T05:57:27+00:00

I have an application bound to eth0, sending UDP packets on port A to

  • 0

I have an application bound to eth0, sending UDP packets on port A to 255.255.255.255. At the same time, I have a UDP server bound to eth0, 0.0.0.0 and port A.

What I want to do is to make sure that the server won’t receive messages generated by the application (handled purely in software by the kernel) but it will receive messages generated by other hosts in the network.

I can’t change the payload of UDP packets nor add any headers to it.

I’ve already implemented a solution using RTNETLINK to fetch all IP addresses of the machine I’m sitting on (and filter basing on address from recvfrom()), but I’m wondering if there might be a simpler and cleaner solution.

EDIT: I thought about something like tagging the skb – the tag would disappear after leaving a physical interface, but wouldn’t if it’s just routed in the software.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you can patch your Linux kernel, you could use a setsockopt() option for choosing if you want to loopback the broadcast packets you’re sending or not.

    This patch reuse the IP_MULTICAST_LOOP option exactly for this purpose.

    Also, instead of “messing” with the IP_MULTICAST_LOOP option, you could easily add your own setsockopt() option, maybe called IP_BROADCAST_NO_LOOP. This would guarantee that you’re not changing the behavior for any other application.

    • 0