Direct attaching a Ubiquiti Edge Router to a fibre network – confirm blog

I’m not

a giant fan of the free-ish routers you get out of your web supplier in Switzerland. Most units are simply low cost “crap units” they usually lack of any barely superior characteristic. Therefore I’m at all times going with a Ubiquiti Edge Router!

I like Ubiquti lots, as I’ve skilled their units as rock stable (roughly no less than) and their software program is sort of good. If you’re an Ansible person, you can even automate the entire configuration with it!

Internet suppliers in Switzerland

As talked about earlier than, web suppliers in Switzerland usually present free routers or alike. And even should you resolve to go along with your personal {hardware}, they usually offer you an ONT (Optical Network Terminal) to your fibre web. Thus, often you’ve to attach the supplier’s ONT to the fibre port and your pretty router by way of Ethernet to the ONT.

This works as anticipated, however there’s a disadvantage. You’ve only one extra machine, another layer of complexity, another factor that may fail or malfunction on occasion. Trust me, I’ve been there and also you don’t wish to troubleshoot a FritzBox or alike!

So, in case your router has an SFP interface, then you definately may wish to join it by way of fibre SFP on to the fibre community of your web supplier. In Switzerland, there are a few them who help you do this.


I’m a bit biased and I at all times go along with iWay, as a result of:

  • They enable me to instantly connect my fibre router formally (simply talked about “direct hooked up” in your registration)
  • Their customer support is pleasant & responsive, as they instantly reply the telephone and replying to assist tickets very quick
  • Their assist is remarkably good, by no means seen that on one other Swiss web supplier to this point

My {hardware}

This is the {hardware} I’m utilizing to direct connect my router to the fibre community:

I feel this {hardware} ought to work for many of the Swiss web suppliers / OTO fibre connectors.

My configuration

Here’s what I needed to configure to get the instantly hooked up fibre router up & operating with iWay.

Firmware replace

Update the router firmware to model 1.10.8 or later. There are two causes to replace the firmware:

  • Security enhancements (after all)
  • Proper velocity choice on the SFP port

Unfortunately, leaving the SFP port on auto negotation didn’t work for me, because the distant web site (iWay or SAK) didn’t reply very effectively to it. The hyperlink didn’t wish to come up. The outdated firmware solely allowed me to set the port to 100/full. After the firmware replace, I used to be capable of choose 1000/full and I instantly acquired a hyperlink up!

Interface configuration

On the Dashboard, configure the eth5 port as follows:

  • Enable: Check
  • Address: Use DHCP
  • MTU: 1500
  • Speed/Duplex: 1000/full (vital, Auto negotiation received’t work)


The corresponding CLI instructions are:

set interfaces ethernet eth5 handle dhcp
set interfaces ethernet eth5 description WAN
set interfaces ethernet eth5 duplex full
set interfaces ethernet eth5 velocity 1000


In the Firewall/NAT tab underneath Port Forwarding, configure the next settings to setup the right routing:

  • WAN interface: eth5
  • LAN interface: (no matter your LAN interfaces are)


Also within the Firewall/NAT tab however underneath NAT, add a brand new Source NAT Rule to masquerade your outgoing site visitors:

  • Description: AWAN masquerading
  • Enable: Check
  • Outbound Interface: eth5
  • Translation: Use Masquerade
  • Protocol: All Protocols


The corresponding CLI instructions are:

set port-forward lan-interface switch0
set port-forward wan-interface eth5

set service nat rule 5000 description 'WAN masquerading'
set service nat rule 5000 log disable
set service nat rule 5000 outbound-interface eth5
set service nat rule 5000 sort masquerade

Test connectivity

You ought to now see a public IP handle on the eth5 interface. To check the connectivty, you are able to do the next steps:

  • Run ping instance.web out of your shell
    • If that works, you’re able to go
    • If that doesn’t work, proceed to the subsequent step
  • Run ping out of your shell
    • If that works however not the above, then you definately may wish to test your DNS configuration
    • If that doesn’t work, proceed to the subsequent step
  • Ping from the Edge Router (by way of WebUI on high proper nook or by way of SSH)
    • If that works however not the above, then you definately may wish to test your NAT guidelines
    • If that doesn’t work, test the WAN port configuration, your firewall or test along with your web supplier

I’d suggest utilizing personal DNS or Cloudfare’s DNS servers ( & You can even use Google’s DNS servers, however I’m not a giant fan of Google gathering and correlating all of your information!

Source link