Skip to content

Subscriber IP broadcast #1727

Open

Description

@ggsnpdsn

I'm working on a project where all UEs need to be in the same broadcast domain, so that when any UE sends a broadcast, all other UEs can receive it — but the traffic shouldn't go out through the N6/Gi interface. I tried intercepting packets with a destination IP of 255.255.255.255 in XDP and then replicating and sending a unicast or broadcast copy to each UE, but the instruction count was too high and it simply wasn't feasible. The tests didn't succeed. Any ideas?

Activity

  1. added theissue type on Sep 16, 2026
  2. changed the title [-]How can I make IP broadcast packets sent by the UE reach other terminals?[/-] [+]Subscriber IP broadcast[/+] on Sep 16, 2026
  3. gruyaume commented on Sep 16, 2026

    @gruyaume
    Member

    Hello @ggsnpdsn ,

    Thanks for reaching out.

    We don't support L3 broadcast.

    If you want us to consider it for a future release, tell us more about your use case and whether this is needed for a production deployment or for testing. If it's for production, tell us more about your actual scenario.

    Have a good day,

    Guillaume

  4. ggsnpdsn commented on Sep 16, 2026

    @ggsnpdsn
    Author

    Currently, it's mainly for testing purposes. The use case is broadcasting among users carrying the same APN. For broadcast traffic coming in from the N6 interface, it needs to be broadcast to all users across all APNs. This is part of a research project on emergency communication for providing emergency alerts.
    The scenarios we want to address are:
    Users at the same site, sharing the same APN, sending mutual alerts — for example, in the case of a landslide.
    Broadcast traffic coming from N6 would indicate a larger-scale disaster, such as an earthquake.

  5. gruyaume commented on Sep 16, 2026

    @gruyaume
    Member

    Feel free to share your implementation and we can try and help you with best effort. Note that we would wait for production demand before including the feature in Ella Core itself.

    On a related note, 3GPP mentions Public Warning System (PWS) where the core sends a message to each gNB and it goes out over cell broadcast. We don't support this either but it wouldn't require datapath or IP broadcast support.

  6. ggsnpdsn commented on Sep 17, 2026

    @ggsnpdsn
    Author

    Could you give me a rough implementation approach on Ella? I'll look into how to modify and test it on my own to see if the service works end-to-end. Ideally, I'd like to only modify the XDP part.

  7. ggsnpdsn commented on Sep 26, 2026

    @ggsnpdsn
    Author

    Feel free to share your implementation and we can try and help you with best effort. Note that we would wait for production demand before including the feature in Ella Core itself.

    On a related note, 3GPP mentions Public Warning System (PWS) where the core sends a message to each gNB and it goes out over cell broadcast. We don't support this either but it wouldn't require datapath or IP broadcast support.

    If I set up a tail call like this:
    CTX_DP_SEC("tcx_broadcast_func") int tcx_broadcast_func(struct __ctx_buff *ctx) { // Function body to clone packets and send them to all terminals in the same subnet (actually the same APN) }Would invoking this tail call after upf_local_switch achieve the functionality I'm looking for? Also, is this achievable only with TCX, or can both XDP-native and TCX handle it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions