HHLONIX
EN

New Zealand · Skinny

Can I use my own router with Skinny Fibre?

Yes. Skinny's current BYO Fibre instructions use PPPoE and explicitly say VLAN tagging should be off/disabled. IP address and DNS are obtained automatically.

Network equipment and server rack
Illustrative photograph; equipment and compatibility may differ.Shixart1985 · CC BY 2.0 · Wikimedia Commons
Page reviewed 6 November 2026Dataset snapshot 23 September 2026Cited sources 1How Hlonix verifies →

Quick reference

Own-router settings at a glance

From official provider sources cited below. Pick your router for a full verdict with topology and caveats.

Skinny Fibre — BYO router

Own-router path
Own router connects directly
Physical handoff
Fibre ONT → Ethernet WAN
WAN connection
PPPoE
VLAN
None — untagged
ISP phone / voice
Check with your provider
ISP TV
No dependency documented
Evidence confidence
High — official provider source

Settings to enter on your router

  1. Use PPPoE.
  2. Use a non-empty PPP username/password; Skinny documents user@skinny.co.nz / password as examples.
  3. Leave VLAN tagging off/disabled.
  4. Obtain IP address and DNS automatically.

Copy-paste router configuration

Generated from the settings above. Generic values published by the provider — any non-empty value is accepted where the provider says so. Menu names vary by firmware version.

OpenWrt
# OpenWrt 23.05+ (DSA). WAN port is usually 'wan' (older targets: 'eth1').
uci set network.wan.device='wan'
uci set network.wan.proto='pppoe'
uci set network.wan.username='user@skinny.co.nz'
uci set network.wan.password='password'
# Provider lists MTU 1500: only set mtu 1500 if your hardware supports RFC 4638 baby jumbo frames.
uci set network.wan6.device='@wan'
uci commit network
/etc/init.d/network restart
MikroTik
# RouterOS 7, default config (ether1 = WAN, interface list WAN exists)
/interface pppoe-client add name=pppoe-out1 interface=ether1 user="user@skinny.co.nz" password="password" add-default-route=yes use-peer-dns=yes disabled=no
/interface list member add list=WAN interface=pppoe-out1
UniFi
  1. Settings → Internet → select the WAN (Primary) → Advanced: Manual.
  2. VLAN ID: off.
  3. IPv4 connection: PPPoE — username user@skinny.co.nz, password password.
  4. Apply, then power-cycle the ONT/modem.
pfSense / OPNsense
  1. Use the physical WAN NIC as WAN.
  2. WAN → IPv4 configuration type: PPPoE, username user@skinny.co.nz, password password.
  3. Save, apply, then power-cycle the ONT/modem.
ASUS
  1. WAN → Internet Connection → WAN Connection Type: PPPoE; enter username user@skinny.co.nz and password password.
  2. LAN → IPTV: leave ISP Profile on None.
  3. Apply and reboot the ONT/modem.
TP-Link
  1. Advanced → Network → Internet: connection type PPPoE (username user@skinny.co.nz, password password).
  2. IPTV/VLAN: leave disabled.
  3. Deco app: More → Advanced → IPTV/VLAN and Internet connection use the same values.
  4. Save and restart the ONT/modem.
FRITZ!Box
  1. Internet → Account Information → Internet service provider: Other Internet service provider.
  2. Connection: external modem or router (LAN 1 as WAN).
  3. Account information required: Yes — username user@skinny.co.nz, password password.
  4. Use VLAN for internet access: off.
  5. Apply and restart the ONT/modem.
eero / Nest
  1. eero app → Settings → Network settings → ISP settings: PPPoE (username user@skinny.co.nz, password password).
  2. Google Home app (Nest Wifi Pro) → Wi-Fi → Network settings → Advanced networking → WAN: PPPoE.
WAN authPPPoE
VLANOff / disabled
IP / DNSAutomatic
Physical handoffFibre ONT → Ethernet WAN

This is a useful NZ counterexample

Spark and One NZ both use VLAN 10 in their cited Fibre profiles, but Skinny's current instructions say no VLAN tagging. Hlonix keeps the ISP-specific settings separate.

Credentials still need values

Skinny provides example PPPoE values and notes that the fields cannot be left blank.

Router support boundary

If the router cannot expose the required WAN mode cleanly, provider support will normally refer you to the router manufacturer.

Next step

Evidence

Page reviewed 6 November 2026 · compatibility dataset snapshot 23 September 2026.