Reply
Senior Member
Posts: 4,851
Registered: ‎01-04-2017
Kudos: 662
Solutions: 232
Established Member
Posts: 2,524
Registered: ‎08-06-2015
Kudos: 1034
Solutions: 151

Re: Known Issues of EdgeMax Series

Not able to use NETv4_xxx groups in EdgeOS NAT rules.

 

Reference thread:  https://community.ubnt.com/t5/EdgeMAX/Using-NETv4-xxx-in-nat-rules-leads-to-commit-error/td-p/188632...

Veteran Member
Posts: 6,264
Registered: ‎03-24-2016
Kudos: 1640
Solutions: 712

Re: Known Issues of EdgeMax Series

As https://community.ubnt.com/t5/EdgeMAX/Known-Issues-of-EdgeMax-Series/m-p/1859460#M153239 hasn't been confirmed as bug yet

 

=>>ER-X : don't use firewall rules or QoS on eth ports under switch0 !   They apply fine....but on reboot, all eth ports will be dropped from the switch (really all) , making ER-X inaccessible from LAN

 

https://community.ubnt.com/t5/EdgeMAX/Edgerouter-X-SFP-issues-after-power-failure/m-p/1895030#M15746...

 

Member
Posts: 157
Registered: ‎10-25-2013
Kudos: 65
Solutions: 6

Re: Known Issues of EdgeMax Series

Suggesting you add MAC address leakage on WAN port to this list:

MAC address leakage

New Member
Posts: 27
Registered: ‎03-25-2017
Kudos: 1

Re: Known Issues of EdgeMax Series

The following two threads set out the same issue.

 

https://community.ubnt.com/t5/EdgeMAX/EdgeMAX-EdgeRouter-X-L2TP-issue-firmware-1-9-1/m-p/1907660#M15...

 

https://community.ubnt.com/t5/EdgeMAX/L2TP-VPN-Multiple-connections-from-same-NAT-d-location/m-p/512...

 

This issue is a show stopper for us. Will revert all sites back to Zyxel USG50 (they do not exhibit this behaviour). Will check back here for progress.

 

Ted Quade

Emerging Member
Posts: 43
Registered: ‎08-20-2016
Kudos: 6

Re: Known Issues of EdgeMax Series

This has been confirmed by UBNT: https://community.ubnt.com/t5/EdgeMAX/VPN-L2TP-IPSEC-not-connecting-to-one-WAN-link/m-p/1900960#M158...

 

If you have two PPPoE based WAN connections the VPN will only connect to one, even when the interface is not specified.

 

 

Member
Posts: 268
Registered: ‎07-30-2013
Kudos: 52
Solutions: 14

Re: Known Issues of EdgeMax Series

See this post

Senior Member
Posts: 3,730
Registered: ‎05-15-2014
Kudos: 1331
Solutions: 259

Re: Known Issues of EdgeMax Series

@UBNT-Fenng lb-local not working correctly, discussion and evidence HERE.

New Member
Posts: 6
Registered: ‎05-23-2017
Solutions: 1

Re: Known Issues of EdgeMax Series

When configuring a GRE-Bridge as discribed in this configuration guide you need to reboot both devices to get the GRE tunnel up and working. The same applies to a GRE configuration change. Without a reboot it is not working and a packet captures shows:

 

00:51:25.786513 IP 82.xxx.xxx.xxx > 92.xxx.xxx.xxx: GREv0, length 96: IP 192.168.1.3.50842 > 192.168.31.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
00:51:25.806767 IP 82.xxx.xxx.xxx > 92.xxx.xxx.xxx: ICMP 92.xxx.xxx.xxx protocol 47 port 25944 unreachable, length 124

I've had this issue with versions: 1.8.0, 1.9.1 and 1.9.1.1. Haven't tested it with other versions.

New Member
Posts: 31
Registered: ‎05-25-2017
Kudos: 2

Re: Known Issues of EdgeMax Series

IPsec performance issue (on 1.9.1.1 and most probably versions after 1.3.0):

 

- iperf-connection test without IPSec tunnel (direct WAN-WAN): line speed
- iperf-connection test on IPSec tunnel (WAN-WAN): +/- 10Mbit/s
 
I've read everyhting on this forums and i've tested changing MTU, MSS clamping, disabling offloading, but unfortunately nothing helps. Looking at the forum posts there are many more Ubiquiti customers with the same issue.
 
I hope Ubiquiti can find and fix this issue...

 

(Please also look at this thread for more info, this might (?) also help, especially robfoehls latest post)

Emerging Member
Posts: 43
Registered: ‎12-21-2016
Kudos: 3

Re: Known Issues of EdgeMax Series

[ Edited ]

Agreed, why hardcode a likely changing IP when the router manages the IP. Or fix the problem associated with using "any", which does not currently work.

 


MimCom wrote:

How about a GUI option to allow dhcp-interface eth[n] in place of local-ip.




SuperUser
Posts: 5,745
Registered: ‎08-26-2009
Kudos: 1757
Solutions: 55

Re: Known Issues of EdgeMax Series

Wait, the GUI and/or CLI saves a hardcoded IP that was obtained via DHCP?

Emerging Member
Posts: 43
Registered: ‎12-21-2016
Kudos: 3

Re: Known Issues of EdgeMax Series

[ Edited ]

twinkletoes wrote:

Wait, the GUI and/or CLI saves a hardcoded IP that was obtained via DHCP?


In the GUI:

  • Config Tree
  • VPN
  • IPSEC
  • Site-to-Site
  • Peer
  • Peer URL/Name

Then set "dhcp-interface" to your external interface, such as eth0. Delete the hardcoded IP under local-address, assuming that you had entered a fixed IP in the GUI or from the command line.  Preview and Save.

 

Your router now obtains the IP automatically from the dhcp interface. Don't forget that you manually set this because it will not appear anywhere under the dedicated VPN settings in the GUI. So yes, and I'm not sure why this isn't the default. Life saver for me because the "any" setting doesn't work.

 

Enjoy

Veteran Member
Posts: 5,192
Registered: ‎07-03-2008
Kudos: 1615
Solutions: 129

Re: Known Issues of EdgeMax Series

Really needs to be in the GUI, but not intuitive at all from the CLI --since dhcp-interface is up a level from the FQDN or IP it replaces.

New Member
Posts: 11
Registered: ‎04-19-2017
Kudos: 2
Solutions: 1

Re: Known Issues of EdgeMax Series

EdgeMax-1-9-1-1-l2tpv3-Multicast-message-not-sent-in-tunnel seems also to be an inssue on the EdgeSeries, 

I would be happy to know if there is a work around and if it has been reproduced in labs

 

I have tried to change the MTU without success to solve this issue

 

Vincent

New Member
Posts: 26
Registered: ‎05-10-2017
Kudos: 4
Solutions: 4

Re: Known Issues of EdgeMax Series

PPPoE connection drops, the folowing LCP request is shown in the logs looping indefinitely (always id=0x5):

 

 

Sent [LCP ConfReq id=0x5 <mru 1492> <magic 0x5e760a64>]

 

Issue highlighted here:

 

https://community.ubnt.com/t5/EdgeMAX/Probl%C3%A8me-ip-lease-time-withe-provider/m-p/1968804#M165256

 

and here:

 

https://community.ubnt.com/t5/EdgeMAX/Loop-in-PPPoE-log-when-PPPoE-connection-drops-daily-Log-always...

 

 

 

 

New Member
Posts: 10
Registered: ‎07-03-2017

Re: Known Issues of EdgeMax Series

I had the same problem.   I had to disable all explit interface rules for DHCP relay and then it listened on all of them and began working.

New Member
Posts: 4
Registered: ‎01-08-2016
Kudos: 1

Re: Known Issues of EdgeMax Series

QoS traffic shaper unit of measurement incorrect.

 

1 mbps => 8 mbps

1 Mbps => 8 mbps

1 mbit => 1 mbps

 

Original Post

New Member
Posts: 3
Registered: ‎07-01-2017

Re: Known Issues of EdgeMax Series

  ipv6 6rd- add tunnel "sit0" failed: No buffer space available

 

 https://community.ubnt.com/t5/EdgeMAX/ipv6-6rd-add-tunnel-quot-sit0-quot-failed-No-buffer-space/m-p/...

New Member
Posts: 1
Registered: ‎12-08-2016

Re: Known Issues of EdgeMax Series

Hello,

 

I cannot access https://community.ubnt.com/t5/EdgeMAX-Beta/DNSMASQ-stops-running-after-a-few-seconds/m-p/1768651 because of authorization failure and thus cannot verify is this about the same I found on my ERPro. My pull request to vyos which seems to incorporate the same problem in dhcpd-config.pl is here https://github.com/vyos/vyatta-cfg-dhcp-server/pull/12

 

Please be aware about that issue if not yet. I would love to see this perl script fixed in some next firmware releases so it needs not to be fixed by hand anymore. :-)

Reply