Ok - thanks @michaelmurphy I have given it a crack.

I 'copy pasted' those rules in, but it fails to commit (yes after the first failure I did run the configure command :))

set interfaces ethernet eth0 vif 10 pppoe 0 ipv6 enable
edit interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0
set prefix-length /56
set interface eth1 host-address ::1
set interface eth1 prefix-id :0
set interface eth1 service slaac
top
set interfaces ethernet eth0 pppoe 0 dhcpv6-pd prefix-only
commit
save

Should I be using eth.0.10 instead of vif 10? 

Then can I use switch0 as an interface instead of doing eth2,3,4?

My interfaces are here:

@CokemonZ You've already got some configuration in there by the looks of that error message. Look at your configuration first and amend from there.

Hello All, 

While this isn't an edge router question specifically I am wondering if anyone here has experienced my issue with my Ubiquiti USG.

I've been humming along nicely and had no problems for the last year or so but in the last few days I cannot connect to 2 Degrees.

I have no issues with my fritzbox but I just cannot get connected using my USG. 

Some key things ive noticed:

• The connection authenticates
• I get allocated my public ip
• I see LCP Terminated by peer
• I then see Connection terminated: no multilink.

I have attempted to get help from the 2degrees team but as im not using a supported router they cant help out (fair enough), but I suspect somethings happening at their end given the messages im seeing in the logs.

Any one seen this kind of thing?

Connected to XX:XX:XX:XX:XX:XX via interface eth0.10
using channel 16
Using interface ppp0
Connect: ppp0 <--> eth0.10
sent [LCP ConfReq id=0x10 <mru 1492> <magic 0xb4f97866>]
rcvd [LCP ConfReq id=0xca <mru 1492> <auth pap> <magic 0x27a7bc38>]
lcp_reqci: returning CONFACK.
sent [LCP ConfAck id=0xca <mru 1492> <auth pap> <magic 0x27a7bc38>]
rcvd [LCP ConfAck id=0x10 <mru 1492> <magic 0xb4f97866>]
sent [LCP EchoReq id=0x0 magic=0xb4f97866]
sent [PAP AuthReq id=0x10 user="XXX@snap.net.nz" password=<hidden>]
rcvd [LCP EchoRep id=0x0 magic=0x27a7bc38]
rcvd [PAP AuthAck id=0x10 ""]
PAP authentication succeeded
peer from calling number XX:XX:XX:XX:XX:XX authorized
sent [IPCP ConfReq id=0x1f <addr 0.0.0.0>]
rcvd [IPCP ConfReq id=0x34 <addr 111.69.7.XX>]
ipcp: returning Configure-ACK
sent [IPCP ConfAck id=0x34 <addr 111.69.7.XX>]
rcvd [IPCP ConfNak id=0x1f <addr 202.124.96.XX>]
sent [IPCP ConfReq id=0x20 <addr 202.124.96.XX>]
rcvd [IPCP TermReq id=0x35]
sent [IPCP TermAck id=0x35]
rcvd [LCP TermReq id=0xcb]
LCP terminated by peer
sent [LCP TermAck id=0xcb]
Connection terminated: no multilink.
Modem hangup

Jun 12 05:35:56 Gateway pppd[6139]: Connected to XX:XX:XX:XX:XX:XX via interface eth0.10
Jun 12 05:35:56 Gateway zebra[758]: interface ppp0 index 39 <POINTOPOINT,NOARP,MULTICAST> added.
Jun 12 05:35:56 Gateway pppd[6139]: Connect: ppp0 <--> eth0.10
Jun 12 05:35:56 Gateway zebra[758]: interface ppp0 mtu changed from 1500 to 1492
Jun 12 05:35:56 Gateway pppd[6139]: PAP authentication succeeded
Jun 12 05:35:56 Gateway pppd[6139]: peer from calling number XX:XX:XX:XX:XX:XX authorized
Jun 12 05:35:56 Gateway zebra[758]: interface ppp0 mtu changed from 1492 to 1500
Jun 12 05:35:59 Gateway pppd[6139]: Connection terminated: no multilink.
Jun 12 05:35:59 Gateway zebra[758]: interface ppp0 index 39 deleted.
Jun 12 05:35:59 Gateway pppd[6139]: Modem hangup

New EdgeRouter firmware 2.0.4 has been release Options

New release v2.0.4 is available here:

• ER-X, ER-X-SFP and EP-R6: https://dl.ubnt.com/firmwares/edgemax/v2.0.x/ER-e50.v2.0.4.5199165.tar
  (SHA256:a84c43f791ec06dc51dde9fb0fc354f730f2bffed49c03ba5b6fa57ee7aa7607)
• ERLite-3 and ERPoe-5: https://dl.ubnt.com/firmwares/edgemax/v2.0.x/ER-e100.v2.0.4.5199165.tar
  (SHA256:a9d274cff247f26af3b3b037b718aaa0be42a6e88463be427c382064c00914c4)

• ER-8, ERPro-8 and EP-R8: https://dl.ubnt.com/firmwares/edgemax/v2.0.x/ER-e200.v2.0.4.5199165.tar 
  (SHA256:8e1deec2d86faa5e5616548b635c4ee8505073d2429be5759f572694f268b230) 

• ER-4, ER-6P and ER-12: https://dl.ubnt.com/firmwares/edgemax/v2.0.x/ER-e300.v2.0.4.5199165.tar
  (SHA256:e088a9a9ed556c9b432c1afc1c1ff1cfe75a921f60f1468a9f64551d3cc9dd7a)

• ER-8-XG: https://dl.ubnt.com/firmwares/edgemax/v2.0.x/ER-e1000.v2.0.4.5199165.tar
  (SHA256:17a3b1a3d7ccdbd94128c51d45fa8ecb687839b572cb0048c882da9b68454afe)

Note: The ER-X/ER-X-SFP/EP-R6 has more limited storage, and in some cases, an upgrade may fail due to not enough space. If this happens, remove the old backup image first (using "delete system image" command, see here for more details) before doing an upgrade.

More details can be found in the release notes below. Please give it a try if you are interested in the new features/changes to help us test them so that we can get the release out sooner! Thanks very much!

[Release Notes v2.0.4]

Changelog

Changes since v2.0.3

New features:

• [UNMS] - Add support for UNMS v1.0!

Enhancements and bug fixes:

• [Dnsmasq] - Improve speed of dnsmasq configuration during initial boot
• [Offloading] - Fix bug that caused Qos/Netflow malfunction when offloading was enabled
• [FactoryReset] - Add eth9 LED blinking when doing factory reset on ER-10X
• [LLDP] - Fix regression in v2.0.1 when interfaces of switch ports did not transmit LLDP frames. Discussed here
• [IPv6] - Add config validation that forbids simultaneous use of dhcpv6 and dhcpv6-pd. Discussed here
• [Discovery] - Fix bug when UBNT discovery did not work if UNMS was configured.
• [TechSupport] - Add more IPSec info to tech-support file
• [UPnP] - Fix bug when UPnP rules were not properly flushed by "clear upnp2 rules" CLI command. Discussed here
• [Offloading] - Fix bug when syslog&console were filled with "protocol 0800 is buggy" error messages if gre offloading was enabled. Discussed hereand here
• [SFP] - Fix bug when SFP status sometimes disappeared when SFP module was inserted. Discussed here and here
• [Switch] - Fix regression in v2.0.0 when counters of switch0 were not incremented on ER-12/ER-12P. 
• [Switch] - Fix potential packet leaking issue after detaching interface from switch0
• [Interface] - Fix bug when interfaces counters added in switch0 didn't get updated on ER-10X
• [Security] - Fix bug when ER could be DOSed by opening unauthenticated WebGUI session that would 
  lead to resource consumption
• [Boot] - Disable interactive prompt when installing new packages from "/config/data/firstboot/install-packages". Discussed here
• [Bootloader] - Upgrade bootloader automatically for those ERs that have backup bootloader partition (ER, ERPro, ER-Infinity)

Known issues:

• [Performance] - Throughput degradation by 5-10% when comparing with v1.10.9 firmware with older kernel
• [VPN] - IPsec and VLAN offloading on ER-X/ER-X-SFP and EP-R6 does not work yet
• [VPN] - L2TP remote access VPN does not work with Android6/7 L2TP clients (but works with Android9 client)
• [LoadBalancing] - On ER-X LoadBalancing sometimes fails to recover after switching to failover interface
• [WebGUI] - Sometimes statistics in WebGUI is "freezing" and page refresh is needed in order to weke it up
• [DPI] - Sometimes DPI is reporting wrong rx/tx counters

Updated software components:

• n/a

Bootloader enhancements and fixes:

• [Bootloader] - Include updated bootloader images with TFTP recovery improvements.

This firmware will be published on main forum and UNMS in 1-2 weeks if no mjor issues/regressions will be detected.

Hey folks,

I have my new ER-X-SFP and am super excited to start using it. I have two questions for the community before I start:

 

1. This thread seems pretty heavily used, but the original guide is a couple of years old now. Is it still current, or do I need to read all 35 pages of the thread to get all the details?
2. It seems there are some problems with the newer firmware and the ER-X. Is it safe to use the 2.0.x firmware, or should I be going for 1.10.x?

Many thanks in advance for the help.

Christopher

chrislaing:

 

Hey folks,

 

 

 

I have my new ER-X-SFP and am super excited to start using it. I have two questions for the community before I start:

 

 

 

 

1. This thread seems pretty heavily used, but the original guide is a couple of years old now. Is it still current, or do I need to read all 35 pages of the thread to get all the details?
2. It seems there are some problems with the newer firmware and the ER-X. Is it safe to use the 2.0.x firmware, or should I be going for 1.10.x?

 

Many thanks in advance for the help.

 

 

 

Christopher

 

For an ER-X or ER-X-SFP, I would recommend you to stay on 1.10.9 / 1.10.x.

This is a discussion about firmware v2.0.3.  Looks to me many ER-X users are still having problems with the firmware.

https://community.ui.com/releases/EdgeMAX-EdgeRouter-software-version-v2-0-3-has-been-released-2-0-3/f220e257-6917-45dd-816c-7bbadc526b27

Unfortunately Ubiquiti updated the website of their community pages / forums and it is so hard to use.  And a lot of older posts disappeared.

Hey all,

Just a follow-up to let you know that I got fibre yesterday, and thus far my Edgerouter X + Unifi APs are working beautifully together.

Thanks to everyone on here for freely sharing their knowledge!

EdgeMAX EdgeRouter Beta Firmware v2.0.5 Important notes

This is urgent EdgeOS firmware release that contains only security fixes in kernel and IPSec areas.

The ER-X/ER-X-SFP/EP-R6 has more limited storage, and in some cases, an upgrade may fail due to not enough space. If this happens, remove the old backup image first (using "delete system image" CLI command, see here for more details) before doing an upgrade.

More details can be found in the release notes below. Please give it a try if you are interested in the new features/changes to help us test them so that we can get the release out sooner! Thanks very much!

This firmware will be released on stable community page and on UNMS next week.

Features

• n/a
• Improvements
• n/a

Bugfixes

• [Kernel] - Fix SACK vulnerabilities in TCP networking stack (CVE-2019-11477, CVE-2019-11478)
• [Kernel] - Fix excessive resource consumption flaw in TCP networking stack (CVE-2019-11479)
• [IPsec] - Fix potential authorization bypass vulnerabilities in strongSwan (CVE-2018-16151, CVE-2018-16152, CVE-2018-17540)

Known issues

• [Performance] - Throughput degradation by 5-10% when comparing with v1.10.9 firmware with older kernel.
• [Offloading] - IPsec and VLAN offloading on ER-X/ER-X-SFP and EP-R6 does not work yet.
• [VPN] - L2TP remote access VPN does not work with Android6/7 L2TP clients (but works with Android9 client).
• [LoadBalancing] - On ER-X LoadBalancing sometimes fails to recover after switching to failover interface.
• [WebGUI] - Sometimes statistics in WebGUI is "freezing" and page refresh is needed in order to wake it up.
• [DPI] - Sometimes DPI is reporting wrong rx/tx counters.

Instructions

EdgeRouter firmware can be installed via CLI, WebGUI or UNMS. Detailed installation instruction is available here.

Download links
ER-X, ER-10X, ER-X-SFP and EP-R6 | md5sum | sha256sum
ERLite-3 and ERPoe-5 | md5sum | sha256sum
ER-8, ERPro-8 and EP-R8 | md5sum | sha256sum
ER-4, ER-6P and ER-12 | md5sum | sha256sum
ER-8-XG | md5sum | sha256sum

I have an EdgeRouter-X with v2.0.4 firmware. I've switched over to 2degrees today and have my PPPoE configuration set up. I called in and tried to switch to a static IP, but to no avail. The internet connection instantly stops working as soon as they apply a static IP address to my account. Here's my interfaces at the moment:

It seems to get assigned an IPv4 address via PPPoE with no problem, but I cannot seem to get a static IP working. I'm not sure what I'm missing, and I feel I'm still missing some important context after some Googling. I didn't imagine that switching to a static IP through 2degrees would require any configuration change on my end.

Any ideas?

BarTender: You should never change anything on the router when any ISP enables static IP.
Leave your end as it was before and just ask 2D to enable the Static IP. Then the session will drop and come back with the static.