3 weeks ago - last edited 3 weeks ago
Not looking to be argumentative here but why doesn't Ubiquiti just test it in the same we do? Our current test bed is simple, WAN 1 broadband cable, WAN 2 verizon 4G LTE modem. We have static IP's for both but we test both static and DHCP. We have continuoulsy tested every version since 1.5.0 which means in almost 5 YEARS they have not gotten this right! VERY FRUSTRATING!
2 weeks ago - last edited 2 weeks ago
@laurin1 Please open a new post and upload your sanitised configuration. And send me the link. Or you can wait one or two weeks. We will try to release a new FW. We have completely rewrite the load-balance feature. And I am testing it. It will be very stable.
2 weeks ago
2 weeks ago - last edited Monday
@laurin1 The old images does not support multiple-groups. Please try this new firmware.
Please make sure you have a backup ER image installed, before you test this image.
Please backup your configuration before you test this new firmware.
a week ago
@laurin1 Have you tested the new version? How is the result? If you still meet some issue, please simplify your configuration and send to me. I will try to reproduce it.
Monday - last edited Monday
@voiproute Thank you!
(This is an image for testing. Please backup your important configurations.)
Please use the test image from this post:
@voiproute These are the major changes:
* Increase max supported load-balance interface number to 55. (Sum of all groups interfaces.)
* Support multiple Load-balance groups.
* Fix the random crash issue, when delete load-balance interfaces.
* Add configuration 'lb-local-dns' to control local DNS packets
* Add configuration 'flush-on-active' to control conntrack-flush
* Support more than 1 failover interfaces.
* Add command 'show load-balance config' to show the detail configuration of load-balance group.
* Add command 'clear load-balance counters.'
Monday - last edited Friday
Here is the test images with new Load-Balance implementation.
Updated in 2019-02-13
Fixed 1 When delete load-balance interface, some rule still in iptables.
Fixed 2 Improve performance.
Updated in 2019-02-14
Please get the new image from this link: