Emby Emby Emby Learn
  • Emby Home
  • Video
  • Audio
  • Media Files
    • Subtitles and captions
    • Photos and images
    • Metadata and discovery
    • Libraries and media collections
    • Playback and streaming
    • Media hardware acceleration
    • Displays and AV connections
    • Live TV and recording
  1. Emby Learn
  2. Networking and remote access
  3. Network boundaries
Search Results for

    Show / Hide Table of Contents

    Overview: Network boundaries

    Network boundaries constrain routes, visibility and forwarding across interfaces or execution environments.

    A guest network, VLAN, container namespace or second interface can change the path an application sees. Multicast adds its own forwarding and listener relationships. This area identifies the boundary involved so a successful connection on one side is not treated as evidence of the same access on another.

    • Guest network isolation
      Guest isolation applies a network’s chosen policy to guest clients and destinations, allowing internet access without necessarily permitting local media-server or discovery paths.

    • VLANs
      A VLAN identifies a bridged network context through port and tag handling, with routing and policy required for communication between separately defined realms.

    • Multicast routing
      Multicast delivery uses receiver membership and forwarding context to copy group traffic onto selected paths, with link-local discovery retaining its own scope rules.

    • Container network modes
      A container’s network mode selects the namespace and forwarding relationship that owns its service listener, with published ports and discovery behavior depending on the actual implementation.

    • Multiple network interfaces
      Multiple network interfaces add address, listener, route and advertisement choices whose independent selection determines the server path seen by each client.

    References

    • Emby: Client connection paths
    • RFC 4632: Prefixes and route specificity
    • RFC 9776: IGMPv3, replacing RFC 3376
    • Docker: Bridge network driver
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top