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. Home network fundamentals
  4. IP addressing
Search Results for

    Show / Hide Table of Contents

    Overview: IP addressing

    IP addressing identifies interfaces and network relationships under particular address scopes and configuration rules.

    An address can belong to a local subnet, a public route or a loopback context. IPv4, IPv6, CIDR notation and DHCP reservations describe different properties of that arrangement. These pages help interpret the address the server or app is actually using rather than treating every visible address as equally reachable.

    • IP addresses
      An IP address identifies an addressable interface or endpoint within a particular address family and scope, with routing and service selection determining whether Emby can be reached there.

    • IPv4
      IPv4 carries packets between 32-bit source and destination addresses, with routing, packet lifetime and fragmentation separate from the transport service carried inside.

    • IPv6
      IPv6 uses 128-bit addresses with explicit scope and interface context, allowing several addresses and routes that a client must interpret when reaching a server.

    • Private and public addresses
      Private, shared, local and special-purpose address ranges have different routing roles, and a globally assigned address still needs a permitted service path to be reachable.

    • Subnets and CIDR notation
      CIDR notation specifies how many leading address bits form a prefix, defining address membership and the specificity used to choose matching routes.

    • DHCP reservations
      A DHCP reservation binds a chosen server-side client identity to a stable address allocation while the client continues obtaining its network configuration through DHCP.

    • Loopback addresses
      Loopback addresses reach the requesting host’s own network stack, making localhost useful for same-host access while proving little about another device’s server path.

    References

    • RFC 791: Internet Protocol
    • RFC 8200: IPv6 specification
    • RFC 1918: Private IPv4 address allocation
    • RFC 4632: CIDR addressing and aggregation
    • RFC 2131: DHCP leases and client binding
    • RFC 1122: Internet host communication requirements
    2026 © EMBY LLC. Please see our terms of use and privacy policy.
    Back to Top