Reply
Ubiquiti Employee
Posts: 221
Registered: ‎08-11-2016
Kudos: 39
Solutions: 4

Known Issues of EdgeMax Series

[ Edited ]

We record the known issues of Edge Roter in  this post. 

Please also add other known issue (confirmed by UBNT employees) in the reply. Please also add the link of the issue.

I will also add into this post.

 

1 LoadBalance

a) Need one transation script to change default route distance. 

(Issue happens on R1.8, R1.8.5, R1.9.0, R1.9.1;  Fixed in next Release.)

Issue and workaround:

https://community.ubnt.com/t5/EdgeMAX/Routing-locally-originated-traffic-after-failover-in-1-9-0/m-p...

 

 

2 IPSec

a)IPSec tunnels with main site prefix overlapping remote site networks no long works in v1.8  

(Issue happens on R1.8, R1.8.5, R1.9.0, R1.9.1; Pending Fix )

Issue and workaround:

https://community.ubnt.com/t5/EdgeMAX/IPSec-tunnels-with-main-site-prefix-overlapping-remote-site/m-...

 

b) auto-firewall-nat-exclude lacks a rule, and to disable it , a reboot is required. 

https://community.ubnt.com/t5/EdgeMAX/GUI-IPSec-Site-to-Site-not-going-up-ERL-to-ERX/m-p/1775225#M14...

(Status under investigation) 

 

c) IPSEC only works with a single FQDN peer entry. 

VPN with FQDN issues

https://community.ubnt.com/t5/EdgeMAX-Beta/BUG-1-8-0-FQDN-peer-for-IPSEC-site-to-site/m-p/1748166#M1...

 (Status under investigation) 

 

3 DHCP, DNS 

a) EdgeOS 1.9.1 dhcp-server using domain-search rather than domain-name 

(Issue happens on R1.9.1; Fixed)

Issue and workaround:

https://community.ubnt.com/t5/EdgeMAX/EdgeOS-1-9-1-dhcp-server-using-domain-search-rather-than-domai...

 

b) DNSMasq dhcpserver script has errors which cause DNSMasq to fail silently if certain DHCP options are set.

Issue, with fix, acknowledged by UBNT here: https://community.ubnt.com/t5/EdgeMAX-Beta/DNSMASQ-stops-running-after-a-few-seconds/m-p/1768651#U17...

(Status: under investigation) 

 

c) Bug DNSMASQ dies when adding static-lease

...acknowledged as bug here https://community.ubnt.com/t5/EdgeMAX-Beta/Bug-DNSMASQ-dies-when-adding-static-lease/m-p/1808625#M19...

(Status: under investigation) 

 

4 GUI

a) EdgeRouter Lite "failed to apply the configuration" when updating port forwarding rules

Issue and workaround:

https://community.ubnt.com/t5/EdgeMAX/EdgeRouter-Lite-quot-failed-to-apply-the-configuration-quot-wh...

 (Status: under investigation) 

 

5 Offload

a) 1V1.9.1B1 still crashes ERXs w/ HW offload and bi-directional iperf3

 (Status: under investigation) 

 

6 L2TP

a) L2TP - Client stays connected but can only load limited parts of internal sites

(Status: under investigation)  

 

7 RADVD

a) radvd dies when pppoe drops

 (Status: under investigation) 

 

8 VPLS

a) EdgeOS VPLS PE will not forward PPPoE frames:
https://community.ubnt.com/t5/EdgeMAX/EdgeOS-1-9-0-VPLS-does-not-forward-PADI-packets-for-PPPoE/td-p...

(Status: under investigation) 

 

9 Packets Loss

There's also the issue with UDP packet transmission reordering on the ERLite: 

https://community.ubnt.com/t5/EdgeMAX/UDP-packet-loss-with-EdgeRouter-Lite/td-p/1343012

 (Status: under investigation) 

 

10 SWITCH VLAN

EdgeRouter X Inter-VLAN routing issues

When using switch in vlan-aware mode, routing between switch0 and other vif interface isn't possible.

current workaround:  put switch0 config under switch0.1  (=vif1)

https://community.ubnt.com/t5/EdgeMAX/EdgeRouter-X-Inter-VLAN-routing-issues-How-I-solved-it/m-p/181...

 (Status: under investigation) 

 

Established Member
Posts: 1,785
Registered: ‎04-26-2014
Kudos: 687
Solutions: 20

Re: Known Issues of EdgeMax Series

Can you add this to the sticky list?
When you receive a solution to your question/issue, don't forget to mark your thread as solved and to give kudos to the people who have helped you out!
Senior Member
Posts: 3,934
Registered: ‎05-15-2014
Kudos: 1414
Solutions: 269

Re: Known Issues of EdgeMax Series

[ Edited ]

Some additional issues already acknowledged by UBNT, please add to your list:

 

 

  • L2TP - Client stays connected but can only load limited parts of internal sites
  • Summary - packets originating from L2TP client get randomly corrupted/reordered when ipsec-offload is enabled on ER-X. Corruption begins after processing 100K+ bytes via L2TP connection.

     

    Workaround - disable ipsec-offload and reboot:

    set system offload ipsec disable
    commit
    save
    reboot

    Additional info:

    1. This issue first appeared when ipsec-offload was introduced on ER-X platform in 1.9.0;
    2. PPTP VPN is not affected by this issue;
    3. IPSec site-to-site VPN is not affecged by this issue;
    4. Cavium-based ER platforms (ER, ER-pro, ER-poe, ER-lite, EP-R8) are not affected by this issue.
    5. Only Mediatek-based ER platforms (ER-X, ER-X-SFP, EP-R6) are affected by this issue.
New Member
Posts: 6
Registered: ‎01-12-2017
Kudos: 3

Re: Known Issues of EdgeMax Series

Hello, this is an issue that would also benefit from being addressed. Pixelated VOD when any other activity is being performed (p2p downloads, VPN incoming traffic, etc). It has been reported to happen on ER Lite and ERPOE-5, in versions 1.7.0, 1.8 and 1.9. 

 

https://community.ubnt.com/t5/EdgeMAX/Pixelated-VOD-IPTV/m-p/1722027#U1722027

 

Thanks!

Senior Member
Posts: 3,934
Registered: ‎05-15-2014
Kudos: 1414
Solutions: 269

Re: Known Issues of EdgeMax Series

One more already acknowledged

 

Established Member
Posts: 1,072
Registered: ‎04-07-2013
Kudos: 490
Solutions: 39

Re: Known Issues of EdgeMax Series

There is a bug with multi-homed / multi-interfaced EdgeRouter with DHCP Relay.

Ubiquiti Employee
Posts: 221
Registered: ‎08-11-2016
Kudos: 39
Solutions: 4

Re: Known Issues of EdgeMax Series

@vbman213 Can you help us find out the link of the issue?

Regular Member
Posts: 336
Registered: ‎08-06-2013
Kudos: 221
Solutions: 5

Re: Known Issues of EdgeMax Series

Senior Member
Posts: 3,078
Registered: ‎08-06-2015
Kudos: 1304
Solutions: 175

Re: Known Issues of EdgeMax Series

As noted in https://community.ubnt.com/t5/EdgeMAX/multi-homed-multi-interface-DHCP-Relay-bug/m-p/1805154 the issue is actually known and many have just accepted the need to enable the DHCP relay to listen on interface where the responses should originate (IE: the interface through which the DHCP server is reached).

 

I had posted a question about this one some time ago in these forums, as have some others.  Many *nix-based solutions have similar bug reports dating back years.

 

It looks like the Debian implementation "fixed" this in a development release about a year ago but I haven't found if it actually made it to a GA release from ISC.

 

It is/was tracked as Debian Bug #648401 That may provide a reference for a potential update/fix for EdgeOS.

 

 

 

Established Member
Posts: 1,072
Registered: ‎04-07-2013
Kudos: 490
Solutions: 39

Re: Known Issues of EdgeMax Series

@waterside: I applied every possible interface to the dhcp relay (including parent interfaces and sub interfaces) and was still unable to work around this.

Two physical ports:
Eth0 and Eth1

4 subonterfaces:
Eth0.10, Eth0.20
Eth1.30, Eth1.40

DHCP Servers are on Eth0.10

DHCP Relay configured on:
Eth0, Eth1, Eth0.10, Eth0.20, Eth1.30, Eth1.40

Both Eth1 and Eth0 are connected to trunk ports on the same switch.

If I move all sub interfaces to Eth0, everything works. As soon as I move a few to Eth1, those subnets don't respond to dhcp requests. I can see the discover making it to the dhcp server, but the offer never makes it back to the client.
Senior Member
Posts: 3,078
Registered: ‎08-06-2015
Kudos: 1304
Solutions: 175

Re: Known Issues of EdgeMax Series

It is probably better to take this to a separate thread, but it is working for me.

New Member
Posts: 17
Registered: ‎01-30-2014
Kudos: 6

Re: Known Issues of EdgeMax Series

Firmware 1.9.1

When using dnsmasq, can't see client lease in GUI.

Veteran Member
Posts: 7,201
Registered: ‎03-24-2016
Kudos: 1855
Solutions: 816

Re: Known Issues of EdgeMax Series

Regular Member
Posts: 725
Registered: ‎01-29-2014
Kudos: 291
Solutions: 33

Re: Known Issues of EdgeMax Series

DNSMasq dhcpserver script has errors which cause DNSMasq to fail silently if certain DHCP options are set.

Issue, with fix, acknowledged by UBNT here: https://community.ubnt.com/t5/EdgeMAX-Beta/DNSMASQ-stops-running-after-a-few-seconds/m-p/1768651#U17...

 

Member
Posts: 251
Registered: ‎03-06-2016
Kudos: 119
Solutions: 8

Re: Known Issues of EdgeMax Series

There's also the issue with UDP packet transmission reordering on the ERLite:

 

https://community.ubnt.com/t5/EdgeMAX/UDP-packet-loss-with-EdgeRouter-Lite/td-p/1343012

 

Rodney

Senior Member
Posts: 3,934
Registered: ‎05-15-2014
Kudos: 1414
Solutions: 269

Re: Known Issues of EdgeMax Series

[ Edited ]

EDIT: To add. FQDN still works, the issue seems to be only when PSK is used.

As an example, I have 10 VPN site to site tunnels working just fine, all with FQDN all peers are on dynamic IP. That said, I'm using x509 and not PSK. Here's an example of working peer

 

            peer peer1.remotesite.com {
                authentication {
                    mode x509
                    remote-id CN=peer1.remotesite.com
                    x509 {
                        ca-cert-file /config/auth/ca.myca.com.crt
                        cert-file /config/auth/me.myca.com.crt
                        key {
                            file /config/ipsec.d/rsa-keys/localhost.key
                        }
                    }
                }
                connection-type initiate
                description PEER1
                ike-group FOO1
                ikev2-reauth inherit
                local-address any
                tunnel 1 {
                    allow-nat-networks disable
                    allow-public-networks disable
                    esp-group FOO1
                    local {
                        prefix 192.168.1.0/24
                    }
                    remote {
                        prefix 192.168.2.0/24
                    }
                }
            }

 

Regular Member
Posts: 745
Registered: ‎11-06-2013
Kudos: 230
Solutions: 26

Re: Known Issues of EdgeMax Series

IPSEC only works with a single FQDN peer entry.

https://community.ubnt.com/t5/EdgeMAX-Beta/BUG-1-8-0-FQDN-peer-for-IPSEC-site-to-site/m-p/1748166#M1...

 

IPSEC spews all kinda bad stuff with 'any' in multiple local address fields. Multiple threads on this for a year or more now.

Senior Member
Posts: 5,688
Registered: ‎01-04-2017
Kudos: 794
Solutions: 284

Re: Known Issues of EdgeMax Series

Ubiquiti Employee
Posts: 221
Registered: ‎08-11-2016
Kudos: 39
Solutions: 4

Re: Known Issues of EdgeMax Series

Reply