Skip to content

Opening your ISP box for Jumo

Your Jumo home router sits behind the box supplied by your internet provider (ISP). Your travel router has to reach it from the internet on:

  • UDP 51820 (WireGuard, the main tunnel), and if possible
  • TCP 443 (fallback, for networks that block UDP).

Jumo tries to set this up for you in this order:

  1. IPv6: it asks the box to open a firewall "pinhole" using UPnP IGDv2 or PCP.
  2. IPv4: it asks the box for a port mapping using UPnP IGD, NAT-PMP or PCP.

If the Jumo app reports that automatic setup failed, follow the guide for your box below.

How to read this page

These steps come from the ISP's own help pages where possible, and from community forums otherwise. Each section lists its sources. Anything we could not confirm from a source is marked unverified. Box menus change with firmware updates, so a label may differ slightly on your screen. Research date: October 2026.

Before you start (all boxes)

  1. Find your Jumo home router's local IP address. It is shown in the Jumo app. Most boxes also list it among connected devices.
  2. Give your Jumo router a fixed address on the box. Most boxes call this a DHCP reservation or static lease. Without it, the box may give Jumo a different address later and your rule stops working.
  3. Create one rule per protocol. You need UDP 51820 → Jumo, UDP 51820, plus TCP 443 → Jumo, TCP 443 if you want the fallback.
  4. Test from outside your home. Use mobile data, not your home Wi-Fi. Several boxes cannot reach their own public address from inside (no "NAT loopback").
  5. Do not use the DMZ unless a guide tells you to. A DMZ sends all incoming traffic to one device. Jumo is a firewall router and can handle it, but a targeted rule is safer and easier to undo.

Shared IPv4 (CGNAT)

More and more fibre lines in Europe share one public IPv4 address between several customers. On a shared IPv4 you either get only a slice of the ports (Free) or no port forwarding at all (SFR, Bouygues, Swisscom). If that is your case, you can still use IPv6, or ask your ISP for a full/dedicated IPv4 address. Free and Bouygues offer this at no charge. Each section below explains how.

Summary

ISP / box UPnP IGD on by default NAT-PMP / PCP IPv6 by default IPv6 firewall default Full IPv4 by default
Free: Freebox Revolution, Delta, Pop, Ultra Unverified (IGD v1 and v2 available) Unverified Yes (unverified, no official page found) Off when it was introduced in 2019. Current default unverified No on many FTTH lines (shared IPv4, port range). Free full-stack IPv4 on request
Orange: Livebox 5, 6, 7 Very likely yes (Orange TV depends on it). Not stated explicitly Unverified Yes (unverified) On. Firewall level "Moyen" is the default Yes (unverified)
SFR: SFR Box 8, 8X Unverified Unverified Yes (unverified) Unverified No on many fibre lines (CGNAT). Full-stack IPv4 on request to support
Bouygues: Bbox (Miami, Fibre WiFi 6/6E/7) Yes Unverified Yes On ("Normal" blocks incoming IPv6) No on some lines (shared IPv4 / MAP-T). Free "Adresse IP dédiée" option
Proximus (BE): Internet Box Yes on BBox 2/3 (community table). Internet Box unverified Unverified Unverified Unverified Unverified. Some TCP ports blocked at network level
Swisscom (CH): Internet-Box Unverified. Can be enabled ("IGD") Unverified Unverified Unverified No on some lines (CGNAT). Hotline can switch it off
Deutsche Telekom (DE): Speedport Not supported (only UPnP AV) Unverified Yes (unverified) Unverified Unverified
Xfinity (US): xFi Gateway On for some gateways (Xfinity: "on by default on some gateways") Unverified Yes Unverified (Typical/Custom options for IPv6) Yes (dynamic public IPv4, unverified)
AT&T Fiber (US): BGW210 / BGW320 Conflicting reports (AT&T staff: not supported) Unverified Yes on IPv6-capable gateways Unverified Yes (unverified)
Verizon Fios (US): CR1000A/B, G3100 Unverified (setting exists) Unverified Unverified Blocks inbound (forum report). IPv6 pinhole page exists Yes (dynamic, unverified)
Spectrum (US): Spectrum router (Advanced WiFi) Yes (Spectrum) Unverified Unverified Unverified Unverified
T-Mobile 5G Home (US) No: gateway has no UPnP or port forwarding (T-Mobile) No (same) Yes Inbound blocked, no per-device option (community) No (CGNAT)
Verizon 5G / LTE Home (US) Unverified (UPnP in gateway guide) Unverified Unverified Unverified No in most reports (CGNAT, community)
Google Fiber (US): GFiber router / Network Box Off on Network Box (Google). GFiber router unverified Unverified Yes (unverified) Inbound IPv6 opened via UPnP (GFiber) Yes (unverified)
Frontier Fiber (US): eero Yes (eero) Unverified Unverified eero has "IPv6 Firewall Rules" (default unverified) Unverified
Bell (CA): Giga Hub, Home Hub 4000/3000 Unverified (toggle exists) Unverified No on residential (Bell community) Not applicable (no IPv6) Yes on fibre (unverified). No on Wireless Home Internet (CGNAT)
Rogers (CA): Xfinity Gateway (Ignite XB7/XB8, ex-Shaw) Unverified Unverified Yes (cannot be disabled, community) Unverified Yes (unverified)
Telus (CA): Wi-Fi Hub, Network Access Hub, Boost Unverified Unverified Yes (/56 PD, community) Unverified Yes (unverified)
Videotron (CA): Helix Fi Unverified Unverified Unverified Unverified Unverified
Starlink (note) Starlink router has no port forwarding or firewall rules No Yes (all plans) Inbound blocked on Starlink router (community) No (CGNAT). Public IPv4 option on Priority plans

What this means for Jumo:

  • UPnP is off or missing by default on Speedport (no UPnP IGD at all). For Free, SFR, Proximus and Swisscom the default could not be confirmed. Expect to enable it by hand.
  • Shared IPv4 is common on Free FTTH, SFR fibre, Bouygues fibre and some Swisscom lines. Automatic IPv4 mapping fails or gets a limited port range there. Use IPv6, or request a full IPv4.
  • Opening IPv6 for one device is hard or unclear on several boxes. The Freebox firewall is all-or-nothing. Livebox rules are tied to an address that may change. Bbox rules are reported to work only when set up a certain way.

Free: Freebox (Revolution, Delta, Pop, Ultra)

Admin interface: Freebox OS at http://mafreebox.freebox.fr, or the Freebox Connect app.

a) UPnP / NAT-PMP / PCP

  • Freebox OS has a UPnP IGD service that can be switched on and off. It supports protocol version 1 or 2 (Free developer API documentation).
  • Default state: unverified. The API documentation example shows it disabled, but that is only an example, not the factory setting.
  • IPv6 pinholes over UPnP: not supported according to a user report on Free's bug tracker ("the service only works on IPv4"). Unverified by Free.
  • NAT-PMP / PCP: unverified (no source found).
  • Menu path for UPnP IGD in Freebox OS: unverified. Look under Paramètres de la Freebox in Mode avancé.

b) IPv6

  • IPv6 is generally active on Free lines. Unverified: no official page found.
  • IPv6 firewall: added in Freebox Server firmware 4.0.6 (2019) and off by default at that time. Free said it might later be switched on by default for customers who had not changed their settings. Current default: unverified.
  • Turn it on or off:
    1. Open http://mafreebox.freebox.fr and log in.
    2. Click Paramètres de la Freebox.
    3. Switch to Mode avancé, then open Configuration IPv6.
    4. In Général, tick or untick the firewall box, then click Appliquer.
  • No per-device IPv6 rules. Users report that when the IPv6 firewall is on, all incoming ports are closed and cannot be opened for a single device. Free has not provided a simple fix. To reach Jumo over IPv6 you have two options:
    • leave the Freebox IPv6 firewall off (Jumo has its own firewall), or
    • delegate an IPv6 /64 to Jumo using a next-hop (advanced). In the same Configuration IPv6 page, set a next-hop for a /64 to Jumo's link-local address. Unverified as a step-by-step.

c) Manual IPv4 port forward

In Freebox OS:

  1. Open http://mafreebox.freebox.fr and log in.
  2. Click Paramètres de la Freebox, then the Mode avancé tab.
  3. Open Gestion des ports (shown as "Redirections de ports" in some guides), then Ajouter une redirection.
  4. Fill in:
    • IP Destination: your Jumo router
    • Redirection active: ticked
    • IP source: all
    • Protocole: UDP
    • Port de début / Port de fin: 51820
    • Port de destination: 51820
  5. Click Appliquer.
  6. Repeat with protocol TCP and port 443 for the fallback.

In the Freebox Connect app: Réseau → ⋯ (top right) → Paramètres réseau avancés → port redirection.

d) Shared vs full IPv4

  • On many FTTH lines, Free shares one IPv4 address between several customers. Each customer gets a port range, for example 49152–65535. The range assigned to your box is shown in Freebox OS. With a shared IPv4 you cannot use ports outside your range, so 51820 and 443 may be impossible.
  • Request a full-stack IPv4 (free of charge):
    1. Log in to your Espace Abonné Freebox.
    2. Open Ma Freebox.
    3. Choose Demander une adresse IP V4 fixe full-stack.
    4. Read the conditions and click Valider.
    5. Wait about 30 minutes, then restart your Freebox Server.
  • Caveats: your public IPv4 address changes. The request must be redone if you move house. Community sources describe it as irreversible.

e) DMZ

  • Freebox OS has a DMZ option. It opens all ports to the IP address you enter. Free says to disable it by entering an address ending in .0.
  • Community guides place it at the bottom of Paramètres de la Freebox → Gestion des ports. Unverified on Pop/Ultra.
  • The Freebox Server also has a bridge mode (mentioned in Free firmware news for Pop/Delta/Ultra). Jumo would then get the public IPv4 directly. Menu path and side effects are unverified, and we have not tested it with Jumo.

f) Caveats

  • On a shared IPv4, rules are only possible inside your port range. With UPnP on, Jumo asks the box for any free port and the box picks one inside your range; nothing to do by hand. For a manual rule, pick an external port inside the range. Full-stack remains the simplest.
  • Freebox Delta/Ultra with 4G aggregation: port redirections only apply to the fixed line's IP, not the 4G IP (Free bug tracker).
  • Users report occasional IPv6 slowdowns tied to the IPv6 firewall. Toggling it off and on fixed it temporarily.

Sources

Orange: Livebox 5, 6, 7

Admin interface: http://livebox/ or http://192.168.1.1. User name admin. The default password is the first 8 characters of the security key printed on the Livebox label.

a) UPnP / NAT-PMP / PCP

  • Default: very likely on. Orange's help says that if UPnP is disabled, Orange TV no longer works fully, and tells customers to check it is ticked. The page does not state the factory default explicitly.
  • Enable it (Livebox 7, 6, S, 5, 4):
    1. Open the Livebox interface and log in.
    2. Click the Paramètres avancés icon at the bottom of the page.
    3. Click Réseau, then the UPnP tab.
    4. Tick Activer le service UPnP IGD and save.
  • UPnP IGD version (v1/v2) and IPv6 pinhole support: unverified.
  • NAT-PMP / PCP: unverified.

b) IPv6

  • IPv6 is enabled on Orange lines. Unverified: no official page found for Livebox 6/7.
  • Firewall: Paramètres avancés → Pare-feu. Levels are faible, moyen (default, recommended by Orange), élevé and personnalisé. Orange says the IPv6 firewall is set up in the same Paramètres avancés → Pare-feu screen.
  • Allow incoming IPv6 to Jumo (procedure from community reports, exact labels unverified):
    1. Paramètres avancés → Pare-feu.
    2. Choose personnalisé and click Enregistrer. The règles de filtrage spécifiques link becomes clickable.
    3. In the IPv6 rules section, add a rule for UDP 51820 to Jumo's IPv6 address. Add a second rule for TCP 443 if wanted.
    4. Users report that the IP externes autorisées field may refuse "Toutes" with a format error.
  • Caveat: Orange states that LAN IPv6 addresses depend on the Livebox's IPv6 prefix, which can change. Users report IPv6 rules being deleted automatically when the target address changes. Jumo should use a stable IPv6 address (not a temporary/privacy address).
  • Prefix delegation: users report that the Livebox gives only one /64 to a router behind it. Unverified for Livebox 6/7.

c) Manual IPv4 port forward (NAT/PAT)

From Orange's official guide for Livebox 6 and 7 (Livebox 5 is the same):

  1. Open http://192.168.1.1 and log in as admin.
  2. Click the Paramètres avancés icon at the bottom of the page.
  3. Click Réseau, then the NAT/PAT tab.
  4. On the new-rule line, create a custom service named "Jumo". Set the internal and external port to 51820 and the protocol to UDP, and pick your Jumo router as the device.
  5. Click Créer (button label from community reports). Check the rule appears in the table at the bottom.
  6. Repeat for TCP 443.

Orange recommends giving the device a fixed IP first (static DHCP lease, under Réseau → DHCP; tab name unverified).

d) Shared vs full IPv4

  • Orange residential lines in France are understood to have a dedicated public IPv4. Unverified: no official statement found.

e) DMZ

  • Orange documents a DMZ for Livebox Pro models. On consumer Livebox 5/6/7, community guides use a DMZ tab under Paramètres avancés → Réseau. Unverified for Livebox 6/7.
  • Orange recommends removing the DMZ when you do not use it.

f) Caveats

  • A manual NAT/PAT rule can be refused if it clashes with an existing UPnP rule for the same port. Users disabled UPnP, created the rule, then re-enabled UPnP.
  • One external port can only be forwarded to one device.
  • Some users report the NAT/PAT Créer button doing nothing on Livebox 5 (firmware bug).
  • Orange warns that the élevé and personnalisé firewall levels can break some services (for example TV).

Sources

SFR: SFR Box 8, SFR Box 8X

Admin interface: http://192.168.1.1 (community sources. Unverified for the 8X).

Note

We could not reach SFR's official help site (assistance.sfr.fr) during research. Everything in this section comes from community reports and is less certain than for the other ISPs.

a) UPnP / NAT-PMP / PCP

  • Default state, menu path, NAT-PMP and PCP: unverified. A Red by SFR community post lists "UPnP activé" among working settings on SFR 7/8 boxes, which suggests a UPnP toggle exists.

b) IPv6

  • IPv6 is offered on SFR fibre. Default state: unverified.
  • IPv6 firewall: on older SFR boxes (NB6) it is under Réseau v6 → Pare-feu. On the Box 8, users mention an IPv6 firewall screen (shown as "not active" in one screenshot) and an onglet DHCP V6. Default state and exact menu: unverified.
  • IPv6 DMZ: a Red by SFR community thread describes a DMZv6 setting plus a next-hop on SFR 7/8 boxes. You give the router behind the box (Jumo) a fixed IPv6 address and enter it as the IPv6 DMZ and gateway next-hop. This is reportedly the working method behind a CGNAT line. Exact labels: unverified.

c) Manual IPv4 port forward

  • Only possible if your line has a full IPv4 (see d). Users report that on CGNAT lines there is no NAT tab at all.
  • Community reports describe the rule screen under the Sécurité tab → Accès sub-tab. Create one rule per port and protocol:
    1. Open http://192.168.1.1 and log in.
    2. Go to Sécurité → Accès (unverified, from a 2022 forum post).
    3. Add a rule: protocol UDP, external port 51820, internal port 51820, destination = Jumo's IP.
    4. Add a second rule for TCP 443.
    5. Restart the box if the rule does not take effect.

d) Shared vs full IPv4

  • Many SFR and Red by SFR fibre lines are on CGNAT (shared IPv4) by default. Sign: the box has no port-forwarding/NAT menu, or its WAN address is not your public address.
  • Request a full-stack IPv4: contact SFR customer service (phone 1023, chat, or SFR on X). Say: "I host a server and need IPv4 full stack to manage the ports of my box." Users report it is done within 15 minutes to 48 hours. Some had to insist or escalate to the technical team because first-level agents said it required a business plan.
  • One user reports that after Red by SFR switched the line off CGNAT, IPv6 was also disabled and had to be re-enabled in the box interface.

e) DMZ

  • The Box 8 has an IPv4 DMZ that accepts only an IP address. Users reported (2021–2023) that the Box 8 DMZ did not forward traffic reliably, and that SFR acknowledged a bug. Explicit port rules worked. A fix in later firmware is unverified.
  • Users also report the box refuses a DMZ/forward target outside its own LAN subnet.

f) Caveats

  • Without full-stack IPv4, use IPv6 (DMZv6 / firewall) or request full-stack.
  • An old issue (2017) where SFR box redirections stopped after 24 h affected older boxes (LaBox, 4K), not the Box 8.

Sources

Bouygues Telecom: Bbox (Miami, Fibre WiFi 6 / 6E / 7)

Admin interface: https://mabbox.bytel.fr (also the Gérer ma box app). The local IP http://192.168.1.254 is commonly cited (unverified).

Note

We did not find official Bouygues Telecom help pages for these settings. This section relies on Bbox-Mag (an independent site) and its forum.

a) UPnP / NAT-PMP / PCP

  • UPnP is on by default on the Bbox.
  • Menu: mabbox.bytel.fr → Réseau avancé → UPnP toggle.
  • NAT-PMP / PCP, UPnP IGD version and IPv6 pinholes via UPnP: unverified.

b) IPv6

  • IPv6 is on by default (dual stack) and cannot be turned off by the customer.
  • IPv6 firewall levels: Faible (incoming IPv6 allowed), Normal (default, incoming IPv6 blocked), Élevé.
  • Allow incoming IPv6 to Jumo (from a 2026 forum thread on a Bbox WiFi 7 with WireGuard, exact menu labels unverified):
    1. Open mabbox.bytel.fr and find the IPv6 firewall (pare-feu IPv6) settings.
    2. Keep the level on Normal.
    3. Add a rule allowing UDP, destination port 51820, to Jumo's IPv6 address. Leave the source port empty. The user reports the rule only worked once the source port was removed.
    4. Add a second rule for TCP 443 if wanted.
  • Do not set the level to Faible to make it work. That opens every device in your home to incoming IPv6.

c) Manual IPv4 port forward

  1. Open https://mabbox.bytel.fr and log in.
  2. Give Jumo a fixed IP (DHCP reservation) in the Bbox network settings.
  3. Go to the advanced network settings, section Redirection de ports / NAT/PAT (label varies).
  4. Add a rule: name "Jumo", protocol UDP, external port 51820, internal port 51820, local IP = Jumo.
  5. Add a second rule for TCP 443.

d) Shared vs full IPv4

  • Bouygues first deployed shared IPv4 ("CGNAT maison") and is moving affected lines to MAP-T (shared IPv4 carried over IPv6). Which lines are affected is not published.
  • How to tell: the Bbox admin page shows a limited port range when your IP is shared. If you can create NAT rules on any port, your IP is dedicated.
  • Request a dedicated IPv4 (free option "Adresse IP dédiée"):
    1. Log in to your Espace Client Bouygues Telecom.
    2. Select your Bbox line.
    3. Ajouter une option → Internet & Maison → Adresse IP Dédiée.
    4. Activation takes about 15 minutes. The Bbox restarts on its own.
  • If the option does not appear (reported in 2023–2024), ask customer service to activate "Adresse IP dédiée". Explain you need to leave CGNAT for a VPN server.

e) DMZ

  • No DMZ is active by default. A DMZ exists but its menu path is unverified. Prefer a NAT/PAT rule.

f) Caveats

  • Users report manual NAT rules not applying while UPnP rules from devices worked. Check that Jumo uses the Bbox as its gateway and has a fixed IP.
  • Review the UPnP rule list from time to time. Any device on the network can open ports.

Sources

Proximus (Belgium): Internet Box / BBox 3

Admin interface: the newer Internet Box has no local web interface for customers. Port forwarding is managed in the MyProximus app or website. The older BBox 3 has a local interface (address unverified).

  • UPnP: a community table lists UPnP as available and on by default for BBox 2/3. Internet Box: unverified. NAT-PMP / PCP: unverified.
  • IPv6 / IPv6 firewall: unverified.
  • Port forwarding: in MyProximus, switch the Internet Box to advanced mode, reserve a fixed IP for Jumo, then add a port forwarding rule (exact menu path unverified).
  • Network-level blocked ports: Proximus blocks some inbound TCP ports on its network by default: 23, 80, 443, 992, 8023, 8080, 8443. They must be unblocked in your MyProximus account (subscription settings), and the security level may need lowering. TCP 443 fallback will not work until you do this. UDP 51820 is not on this list.
  • Caveats: users report external and internal port had to be equal, and that after changing rules the Internet Box should be switched off for about 6 minutes and turned back on. Several users report rules not working even when configured correctly.
  • Full IPv4 / DMZ: unverified.

Sources

Swisscom (Switzerland): Internet-Box

Admin interface: http://internetbox.home or http://192.168.1.1, user admin.

  • UPnP: can be enabled. Switch to expert mode, then Network → Settings → Port forwarding → UPnP, and activate IGD. Default state: unverified. NAT-PMP / PCP: unverified.
  • Port forwarding: all ports are closed by default.
    1. Log in to http://internetbox.home as admin.
    2. Switch to expert mode.
    3. Go to Network → Settings → Port forwarding.
    4. Choose Add new rule. Set UDP 51820 → Jumo, then add TCP 443.
  • Shared IPv4 (CGNAT): some Swisscom lines are behind CGNAT. Check the external IP under Diagnose: an address in the 100.x.x.x range means CGNAT. Ask the Swisscom hotline (the community page lists 0800 800 073) to switch off CGNAT on your line. Port forwarding does not work until they do.
  • IPv6 / IPv6 firewall default / DMZ: unverified.

Sources

Deutsche Telekom (Germany): Speedport

Admin interface: http://speedport.ip or http://192.168.2.1.

  • UPnP IGD: not supported. Telekom staff state that Speedport routers do not support normal UPnP, only UPnP AV (media sharing on the home network). Jumo's automatic IPv4 mapping will therefore fail. Set the rule by hand. NAT-PMP / PCP: unverified.
  • Port forwarding (IPv4):
    1. Open http://speedport.ip and log in.
    2. If needed, switch to the Expertenansicht (expert view) in the settings.
    3. Go to Internet → Portfreischaltung → Port-Umleitungen und Port-Weiterleitungen.
    4. Add UDP 51820 → Jumo, then TCP 443 → Jumo.
  • IPv6: on IPv6, the Speedport opens a port for a device's address ("Portfreischaltung") instead of forwarding. This comes from a community comment, so the exact menu and the IPv6 firewall default are unverified.
  • Caveats: a port can be forwarded to only one internal device. No NAT loopback, so test from mobile data.
  • Full IPv4 / DMZ: unverified.

Sources

North America overview

North America at a glance

  • CGNAT by default, so no IPv4 port forwarding at all: T-Mobile 5G Home Internet, Verizon 5G/LTE Home (most reports), Starlink (residential and Roam plans), and Bell Wireless Home Internet. On these lines, Jumo works only over IPv6 if the ISP lets inbound IPv6 through. On T-Mobile and the Starlink router it does not.
  • App-only management: Xfinity, Rogers (Xfinity platform), Spectrum and the GFiber router manage port forwarding in a mobile app. Xfinity and Rogers port forwards work only for IPv4 devices.
  • No residential IPv6: Bell (Canada).

Comcast Xfinity (USA): xFi Gateway

Where to configure: the Xfinity app (port forwarding). The Admin Tool at http://10.0.0.1 handles firewall, UPnP and bridge mode. On newer gateways you may need to turn on Admin Tool access from the app first.

a) UPnP / NAT-PMP / PCP

  • Xfinity says UPnP is on by default on some gateways. It is toggled in the Admin Tool under Advanced → Device Discovery.
  • Users report UPnP switching itself off after a few days (unverified cause).
  • NAT-PMP / PCP: unverified.

b) IPv6

  • Comcast provides native dual-stack IPv4 + IPv6 (community guide; a /60 is delegated to a customer router in bridge mode).
  • IPv6 firewall: Admin Tool → Gateway → Firewall, then choose IPv6. Xfinity describes the levels Maximum, Typical, Minimum and Custom. On an XB7, a moderator says IPv6 only offers Typical Security and Custom Security. Whether Typical blocks unsolicited inbound IPv6 is unverified.
  • Port forwarding in the app does not apply to IPv6. Xfinity says it works only for IPv4 devices using DHCP. There is no documented per-device IPv6 allow rule.

c) Manual IPv4 port forward (Xfinity app)

  1. Open the Xfinity app and sign in.
  2. Tap WiFi → View WiFi equipment → Advanced Settings → Port forwarding.
  3. Add a rule, pick your Jumo router from the device list, and enter the ports manually: UDP 51820.
  4. Add a second rule for TCP 443.
  5. If Jumo is not in the list, it may be using IPv6 or a static IP. Xfinity requires an IPv4 DHCP device.

d) Shared vs public IPv4

  • Residential lines get a dynamic public IPv4 (community, unverified). A static IPv4 is reported as a Business-only product (unverified).

e) Bridge mode / DMZ

  • Bridge mode: Admin Tool → Gateway → At a Glance → Bridge Mode → enable. Bridge mode turns off the gateway's routing and Wi-Fi, and limits you to one device on the Ethernet ports. Forum replies say the app cannot turn it off; use the Admin Tool. With bridge mode on, Jumo gets the public IP and handles the ports itself. This is the most reliable option.
  • A DMZ setting also exists (Xfinity support article).

f) Caveats

  • Advanced Security (xFi) can block all traffic on a forwarded, DMZ or UPnP port if it detects a threat. Users report it blocking VPN and remote access. It can be switched off in the app (community).
  • If a device uses MAC randomization, rules can break. Delete and recreate the rule.
  • Users report inbound TCP 80 and 443 blocked on residential service (community, unverified; Xfinity publishes a blocked-ports list). The TCP 443 fallback may not work. UDP 51820 is not reported blocked.

Sources

AT&T Fiber (USA): BGW210, BGW320

Admin interface: http://192.168.1.254. Protected pages ask for the Device Access Code printed on the gateway label.

a) UPnP / NAT-PMP / PCP

  • Conflicting reports. An AT&T community specialist says AT&T gateways do not support UPnP. A Roon community post says the BGW320 does support it but hides it, and that AT&T may disable it. Treat UPnP as unavailable and set rules by hand.
  • NAT-PMP / PCP: unverified.

b) IPv6

  • AT&T lists the BGW320 and BGW210 as IPv6-capable and says most users need no setup. A LAN-side IPv6 toggle is under Home Network → IPv6 (community).
  • IPv6 inbound firewall default and per-device allow rule: unverified. Users report needing to turn off Packet Filter and Firewall Advanced for IPv6 to flow to a router in passthrough.

c) Manual IPv4 port forward (NAT/Gaming)

From AT&T's official steps:

  1. Open http://192.168.1.254 and select the Firewall tab.
  2. Enter the Device Access Code.
  3. Select NAT/Gaming. If you see a warning, port forwarding must first be enabled on your account.
  4. In Service, choose Custom Services. Enter a service name ("Jumo"), port 51820 (AT&T recommends one entry per port, not a range) and protocol UDP. Select Add.
  5. Select Return to NAT/Gaming.
  6. In Needed by Device, choose your Jumo router and select Add.
  7. Check the entry under Hosted Applications and select Save.
  8. Repeat for TCP 443.

d) Shared vs public IPv4

  • Residential fiber is understood to get a public IPv4. Unverified: no source found.
  • IP Passthrough gives the gateway's public IPv4 to one device (Jumo), which then does its own NAT and firewall. AT&T says passthrough removes the gateway's firewall protection for that device.
  • AT&T's official article covers older gateways (Firewall → IP Passthrough, Allocation Mode = Passthrough, Passthrough Mode = DHCPS-fixed, enter Jumo's MAC address, then Save and restart). On BGW210/BGW320 the same labels are reported by users. Menu location on the BGW: unverified.
  • After enabling it, restart Jumo so it picks up the public address.

f) Caveats

  • Creating a custom service does nothing until it is assigned under Needed by Device.

Sources

Verizon Fios (USA): CR1000A / CR1000B, G3100

Admin interface: the router web UI (address commonly http://192.168.1.1, unverified for these models).

a) UPnP / NAT-PMP / PCP

  • A Universal Plug & Play setting exists. Users place it under Advanced → Network Settings → Universal Plug & Play (CR1000A user guide, per community) or Devices → Universal Plug and Play (G3100/CR1000A/B). One user reports it missing from the menu on a newer unit. Default state: unverified.
  • Users report UPnP rules can override manual rules. If a manual rule fails, turn UPnP off, create the rule, then turn it back on.
  • NAT-PMP / PCP: unverified.

b) IPv6

  • IPv6 default: unverified.
  • IPv6 pinholes: on the G3100, a user locates them at Advanced → Security & Firewall → IPv6 Pinhole, and says the default firewall blocks all inbound IPv4 and IPv6. This is the place to allow UDP 51820 to Jumo's IPv6 address. Exact fields and CR1000A location: unverified.

c) Manual IPv4 port forward

  1. Log in to the router web UI.
  2. Open the port forwarding page (Verizon redesigned it in firmware 3.2.0.x; community guides place it under Firewall → Port Forwarding, unverified on current firmware).
  3. Forward UDP 51820 to Jumo's IP, then TCP 443.

d) Shared vs public IPv4

  • Fios gives a public IPv4 that is not static and can change (community). Use dynamic DNS.

e) Bridge / own router

  • Unverified: no source found.

f) Caveats

  • Users report an "invalid IP address" error in the Fwd to field on firmware 3.2.0.7. Others report rules wiped after firmware updates or DHCP renewals.

Sources

Spectrum (USA): Spectrum router with Advanced WiFi

Where to configure: the My Spectrum app only, on Spectrum-managed routers. A router you own uses its own interface.

a) UPnP / NAT-PMP / PCP

  • Spectrum says UPnP is enabled by default. It can be turned off in the app's advanced settings.
  • NAT-PMP / PCP: unverified.

b) IPv6

  • IPv6 default, inbound firewall and per-device allow: unverified. No IPv6 rule option is documented in the app.

c) Manual IPv4 port forward (My Spectrum app)

  1. Open the My Spectrum app.
  2. Go to Services → Your Spectrum Network → Advanced WiFi Settings.
  3. Reserve an IP address for your Jumo router (IP Reservation). Spectrum requires a reservation before forwarding.
  4. Open Port Forwarding, add a rule for Jumo: external and internal port 51820, protocol UDP. Save.
  5. Add a second rule for TCP 443.

d) Shared vs public IPv4 / e) Bridge

  • Unverified: no source found.

f) Caveats

  • Spectrum says Advanced Settings are only available in certain markets. If you cannot find them, a Spectrum moderator suggests rebooting the router and reinstalling the app.

Sources

T-Mobile 5G Home Internet (USA)

Inbound connections are not possible

T-Mobile says its gateways cannot be configured for NAT/port forwarding or UPnP. Community reports say T-Mobile uses CGNAT for IPv4 and blocks unsolicited inbound IPv6 on the network, so even your own router or bridge mode does not help. Jumo cannot be reached directly on this connection.

  • UPnP / NAT-PMP / PCP: not available on the gateway (T-Mobile).
  • IPv6: devices get global IPv6 addresses, but inbound traffic is blocked, with no per-device option (community, unverified by T-Mobile). Users also report no IPv6 prefix delegation.
  • Public IPv4: not offered on residential plans (community, unverified).
  • What to do: Jumo needs a connection that accepts inbound traffic. Options are an outbound tunnel to a public relay/VPS, or another home connection. Whether a T-Mobile business plan offers a public IP is unverified.

Sources

Verizon 5G Home / LTE Home Internet (USA)

  • Port forwarding page exists on the 5G Internet Gateway (LVSKIHP):
    1. Sign in to the gateway's Admin WebGUI.
    2. Click System Settings → Firewall → Port Forwarding.
    3. Enter Rule Name, From Port (51820), Protocol (UDP), IP Address (Jumo) and To Port (51820), then click Add.
    4. Make sure the Port Forwarding switch is on.
    5. Repeat for TCP 443.
  • But inbound IPv4 usually does not arrive. Most community reports say 5G Home is behind CGNAT, so the rule has no effect. Check your gateway's WAN IPv4: an address in 100.64.0.0/10 means CGNAT. Unverified by Verizon.
  • UPnP: the 5G Internet Gateway user guide mentions a UPnP function for automatic port forwarding. Default: unverified.
  • IPv6: users report the gateway gets a public IPv6 but gives only a /64 with no prefix delegation to a router behind it. Inbound IPv6 behaviour: unverified.
  • LTE Home: Verizon publishes a port forwarding article. CGNAT status: unverified.
  • A factory reset deletes your rules.

Sources

Google Fiber (USA): GFiber router, Network Box

Where to configure: the GFiber app (newer GFiber routers) or the Fiber account (older Network Box).

a) UPnP / NAT-PMP / PCP

  • Network Box: Google says UPnP port forwarding is Off by default.
  • GFiber router: default unverified. Toggle: Network tab → Network settings → Advanced network settings → Ports → Universal plug and play → Save.
  • GFiber says that in most cases port forwarding (IPv4) and port opening (IPv6) are configured automatically using UPnP. This means Jumo's automatic IPv6 pinhole request should work once UPnP is on.
  • NAT-PMP / PCP: unverified.

b) IPv6

  • IPv6 default: unverified (GFiber's UPnP note implies IPv6 is in use). Manual per-device IPv6 rules: unverified. Turning on UPnP is the documented route.

c) Manual IPv4 port forward (GFiber app)

  1. Open the GFiber app and tap Network in the bottom menu.
  2. Tap Network settings → Advanced network settings → Ports.
  3. Tap Add a new rule.
  4. Device: your Jumo router. Service: Custom. Protocol: UDP. Port Range: 51820 to 51820.
  5. Tap Save, then Confirm.
  6. Repeat with protocol TCP, port 443.

GFiber recommends reserving the device's IP address first. A DMZ toggle is also available (Wi-Fi 6 Router, Multi-Gig Router, Wi-Fi 6E router, Network Box).

d) Shared vs public IPv4

  • Unverified: no source found.

Sources

Frontier Fiber (USA): eero

Frontier Fiber plans include eero routers, managed in the eero app.

  • UPnP: eero says it is on by default. Toggle: Settings → Advanced networking → UPnP. NAT-PMP / PCP: unverified.
  • IPv4 port forward:
    1. Open the eero app.
    2. Go to Settings → Advanced networking → Reservations & port forwarding.
    3. Reserve an IP for your Jumo router, then add a port forward: UDP 51820, then TCP 443.
  • IPv6: eero has an IPv6 Firewall Rules section to allow inbound IPv6 to a device (per eero's port forwarding guide). Default inbound behaviour and whether Frontier provides IPv6 on your line: unverified.
  • Public IPv4 / CGNAT: unverified. If the eero app shows a WAN address in 100.64.x.x, you are behind CGNAT.
  • Bridge mode on eero removes UPnP and port forwarding from the eero. Only use it if Jumo is the router.
  • Frontier says it only supports the routers it supplies.

Sources

Bell (Canada): Giga Hub, Home Hub 4000 / 3000

Admin interface: http://192.168.2.1 (community).

  • UPnP: toggle under Advanced Tools and Settings → Networking (Bell community reply). Default: unverified (one user believes it is off). NAT-PMP / PCP: unverified.
  • IPv6: not offered on residential service. A Bell representative said so in 2022. In June 2026 a user reported the Giga Hub 2.0 still has no IPv6 on the LAN. Jumo must use IPv4.
  • IPv4 port forward (community):
    1. Open http://192.168.2.1 and log in.
    2. Go to Advanced Tools and Settings → Port Forwarding.
    3. Add a rule: UDP 51820 → Jumo, then TCP 443 → Jumo.
    4. A Bell community reply recommends turning UPnP off before adding manual rules.
  • Public IPv4: Bell Wireless Home Internet uses CGNAT, so port forwarding is impossible there. For Fibe fibre, one user says a rep claimed CGNAT and offered a business static IP, but this is a single report. Fibre lines are generally reported to work with forwarding (unverified).
  • Bridge alternatives: the Hub has no true bridge mode. Users instead use:
    • PPPoE passthrough: connect Jumo's WAN to a Hub LAN port and set Jumo to PPPoE with your Bell b1 credentials. Jumo then gets the public IPv4. Users report it is the more reliable option.
    • Advanced DMZ: gives the public IP to one device. Users report it dropping after a while (fix: remove from DMZ, reboot, re-add).
  • Caveat: a Bell moderator calls Giga Hub port forwarding "trial and error".

Sources

Rogers (Canada): Rogers Xfinity Gateway (Ignite XB7 / XB8, former Shaw)

Rogers Ignite and former Shaw (BlueCurve) customers now use the Rogers Xfinity app, which runs on the same platform as Comcast Xfinity.

  • IPv4 port forward (Rogers official):
    1. Open the Rogers Xfinity app.
    2. Tap Wi-Fi → View Wi-Fi equipment → Advanced Settings → Port Forwarding → Add Port Forward.
    3. Choose Manual Setup, pick your Jumo router, and enter UDP 51820. Then add TCP 443.
    4. Rogers recommends a static IPv4 address for the device.
  • IPv6: port forwards work only for IPv4 devices. A dual-stack device may not appear in the list. IPv6 cannot be disabled on Ignite gateways (community). Inbound IPv6 firewall default and per-device allow: unverified.
  • UPnP / NAT-PMP / PCP: unverified.
  • Bridge mode: community reports say it is available on cable service, not fibre. Only a limited number of devices can get a public IP. Bridge mode is the most reliable option where available. Menu location: unverified.
  • Public IPv4: unverified.
  • Caveats: Rogers support agents give limited port forwarding help. A factory reset erases all rules.

Sources

Telus (Canada): Wi-Fi Hub, Network Access Hub, Boost

Note

We found no official Telus article on port forwarding. Telus support says port forwarding is not supported by their tech support team. Everything below is from the Telus community forum.

  • Which device: the Wi-Fi Boost units are only extenders. Rules are set on the router: on the Network Access Hub (white box) users find them at http://192.168.1.254 under Network → Firewall → Port Forwarding. Exact location on the Wi-Fi Hub: unverified.
  • IPv4 port forward (community):
    1. Open http://192.168.1.254 and log in.
    2. Go to Network → Firewall → Port Forwarding.
    3. Add UDP 51820 → Jumo, then TCP 443 → Jumo.
  • IPv6: Telus delegates a /56 to routers that request a prefix (community). Hub IPv6 firewall default and per-device allow: unverified.
  • UPnP / NAT-PMP / PCP: unverified.
  • Public IPv4: unverified.
  • Caveats: one user reports rules reassigning themselves to a random IP (one of their Boosts) and the port closing again after a minute. A factory reset of the Hub and Boosts fixed it.

Sources

Videotron (Canada): Helix Fi

Note

Videotron's help site could not be reached during research, and we found no reliable community guide. Everything in this section is unverified.

  • A user reports running a Helix gateway in bridge mode with their own router. Bridge mode is the likely route for Jumo, but steps are unverified.
  • The Helix Fi app manages the Wi-Fi network and connected devices. Whether it offers port forwarding, UPnP or IPv6 rules is unverified.
  • Contact Videotron support and ask: (1) how to forward UDP 51820 and TCP 443 to one device, (2) whether UPnP is on, (3) whether the line has a public IPv4 and IPv6, and (4) how to enable bridge mode.

Sources

  • IPv4: Starlink's default IPv4 policy is CGNAT, which does not allow inbound traffic. A public IPv4 option exists for Local and Global Priority customers (paid plans). It is not truly static, but a reservation keeps it across power cycles.
  • Starlink routers do not support port forwarding or firewall rules for IPv4 or IPv6 (Starlink support article, via search excerpt).
  • IPv6: native IPv6 on all routers, kits and plans. Community reports say the Starlink router blocks inbound IPv6 with no option to open it. Behind your own router in bypass mode, you get a delegated prefix (reported /56, sometimes smaller), which changes over time.
  • For Jumo: put the Starlink router in bypass mode, connect Jumo directly, and use IPv6 with dynamic DNS. Or choose a Priority plan with the public IPv4 option. Users report needing workarounds for short IPv6 prefix lifetimes on OpenWrt (unverified for Jumo).

Sources