New EdgeMAX software version v1.9.0 for EdgeRouter products has been released and is available here:
Some notable features/enhancements in the 1.9.0 release include:
More details can be found in the release notes below. I would like to thank everyone for their participation in the community, as always helping with testing, reporting issues, providing feedback, suggestions, even patches! We certainly could not have done it without you Thank you very much!
[Release Notes v1.9.0]
Changes since v1.8.5
In the above screen, the first "queue" specifies that the host 192.168.100.101 has "upload" rate limit of 2 Mbps (megabits per second) and "download" rate limit of 10 Mbps (using SFQ in both directions). In this context "upload" means "source" (192.168.100.101) to "destination" (not specified so "any"), and download means destination to source. The second queue specifies a rate limit of 20 Mbps for traffic going from 192.168.1.0/24 to 192.168.2.0/24, and 15 Mbps for the reverse direction (192.168.2.0/24 to 192.168.1.0/24), using simple FIFO in both directions.
Here is another example that includes some more settings:
First, note that "Show burst settings" is enabled and so the Basic Queue page now shows the burst rate/size settings for each direction. The first queue specifies "P2P" traffic (as identified by the DPI feature) for host 192.168.100.101 has 2 Mbps upload rate limit, allowing bursting up to 3 Mbps for 1 MB (megabytes) of data, and 10 Mbps download rate limit (bursting up to 15 Mbps for 5 MB), using FQ-CoDel in both directions.
The second queue specifies an upload rate limit of 30 Mbps (with FQ CoDel) for the 192.168.1.0/24 network. For the download (reverse) direction, the rate limit is 60 Mbps and the queue type is HFQ (host fairness queueing), which further specifies that each client in the 192.168.1.0/24 subnet has download rate limit of 1 Mbps, bursting up to 1.5 Mbps for 500 KB.
One important thing to note is that the Basic Queue Web UI actually generates "Advanced Queue" configuration "under the hood". If the configuration is changed "outside" the Basic Queue page (e.g., through the CLI or Advanced Queue Web UI), the Basic Queue Web UI will no longer be able to show the config. Therefore, for now if the Basic Queue Web UI is used, it would probably be best to stay with the Basic Queue Web UI for making config changes.
Issues related to basic and simplified QoS configuration have been discussed with many community members before, including @Magician @Paetur @wispwest @esseph @SPITwSPOTS @WisTech @Kevo @SpecialK @doush @rzirzi @takumix @MCT @zsc100 @ElbowWilham @jdk59404 @rps @bcdouglas @mackintire @amishgenius @danutz49 @lumaform @remikk @leeandy @broken @rebelwireless @mrhone @jacobturner @wyopno @CWescott @gaetancambier @redfive @skoenman @turtles2 for example in these threads: 1 2 3 4 5 6 7 8.
set system offload ipsec enableand then "commit" and "save", and then a router reboot is currently required for the setting to take effect.
set service dhcp-server use-dnsmasq enableA few things to note:
Enhancements and bug fixes
set load-balance group x lb-local disable(Default is enable which is the same as previous behavior.)
set interfaces ipv6-tunnel v6tun0 encapsulation ip6gre set interfaces ipv6-tunnel v6tun0 local-ip '2a02:f00d:::1' set interfaces ipv6-tunnel v6tun0 remote-ip '2a01:cafe::1' set interfaces ipv6-tunnel v6tun0 address 10.6.6.1/32 set protocols static interface-route 10.6.6.2/32 next-hop-interface v6tun0Discussed with Corny tommie matthardeman jwilko Kazyini here.
set protocols bgp 111 neighbor 2001::1 no-activate set protocols bgp 111 neighbor 2001::1 address-family ipv6-unicastReported by and discussed with NVX matthardeman wdeman here.
Updated software components