> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/connectivity/router-modem-configuration-guides/netcomm-bridge-mode.md).

# Netcomm Bridge Mode

#### What's happening

We've identified a known issue affecting Netcomm routers configured in Bridge mode. In some cases, the connected device (such as a firewall or router) ends up receiving a private IP address from the Netcomm itself, instead of the intended public IP passing straight through via Bridge mode.

#### Why this happens

This occurs when DHCP is still enabled on the Netcomm's settings after the service has been switched to Bridge mode. For Bridge mode to work correctly, DHCP must be properly disabled, otherwise the router continues assigning IP addresses locally instead of passing the connection through.

#### How to resolve it

1. Update to the **latest firmware** available for your device.
2. Perform a **factory reset** after the firmware update to clear all existing settings.
3. Remove any **default Internet Profiles**.
4. Use the **Quick Setup Wizard** to configure VDSL/IPoE Bridge mode.
5. Confirm that **DHCP is Disabled** on the LAN page.
6. Disable **Wi-Fi** on both the 2.4GHz and 5GHz bands.
7. **Reboot** the router for the changes to take effect.

#### Important note

For IPoE Bridge mode to work correctly, DHCP must be turned off properly. If any other device connects to the router, whether through another LAN port or Wi-Fi, while it's in Bridge mode, it can hijack the connection, since Bridge mode passes the IPoE session through to whichever device claims it first.

#### Accessing the router for management

Once in Bridge mode, the router's management interface won't be reachable the normal way. To retain management access, connect an additional device or port to a separate port and configure it with a static IP, this gives you a way to reach the router for ongoing management without interfering with the Bridge mode connection itself.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.hostednetwork.com.au/support/services/connectivity/router-modem-configuration-guides/netcomm-bridge-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.