> 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/internet-services/troubleshooting-wan/advanced-troubleshooting/nbn-tc4-connectivity/wireless.md).

# Wireless

Check Weather and Power

Check Power Supply of WNTD IDU if connected on a stable power supply

Check ODU and IDU connection

Check and note down the status lights of the NCD

* Power
* IDU LED
* ODU LED
* Signal Strength

Note: Include if blinking or solid

{% tabs %}
{% tab title="Service Outage/Offline, Service Degradation, Dropouts" %}
**Pre-checks/Troubleshooting**

* Check IDU, ODU and CPE Cabling
* Has another Ethernet Cable and CPE tested? (Test the ethernet cable)
* Reboot WNTD IDU

**Perform nbn diagnostics check via the Partner Portal NBN Self-Diagnostics Tool**

* Perform a loopback test. If the test fails, raise a fault. If passed, please perform internal troubleshooting.
  {% endtab %}
  {% endtabs %}

#### Raising a fault to Hosted Network Support Team

* Provide Troubleshooting performed
* Provide WNTD Light status details, can be a photo (preferred) or written via email
* Provide Site Contact Details and availability for nbn tech visit
* Log a fault on the affected service via the Partner Portal or send an email to <support@hostednetwork.com.au>. Once completed, it will log a ticket with our Engineers, and will review the information and confirm the next steps.

You may always reach out to our support team to request assistance on troubleshooting the issues.

<br>


---

# 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/internet-services/troubleshooting-wan/advanced-troubleshooting/nbn-tc4-connectivity/wireless.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.