Xwrt-Vortex Firmware 380.67 per Linksys EA6900
Tipo di file: Firmware.
Sistema Operativo: AnyOS.
Nome del file: EA6900_380.67_0.zip.
Bit: 32/64 Bit.
Licenza: Gratis.
Descrizione
Xwrt-Vortex is a port of Asuswrt-Merlin for different routers developed by Vortex. Xwrt-Vortex retains all the features of the original stock Asus firmware.
Installation:
Simply flash it like any regular update. Non è necessario ripristinare le impostazioni di fabbrica. You can revert back to an original Asus firmware at any time just by flashing a firmware downloaded from Asus’s website.
NOTA:
resetting to factory default after flashing is strongly recommended for the following cases:
– Updating from a firmware version that is more than 3 releases older
– Switching from a Tomato/DD-WRT/OpenWRT firmware
If upgrading from anything older and you experience issues, then consider doing a factory default reset then as well. Always read the changelog, as mandatory resets will be mentioned there when they are necessary.
In all of these cases, do NOT load a saved copy of your settings! This would be the same thing as NOT resetting at all, as you will simply re-enter any invalid setting you wanted to get rid of. Make sure to create a new backup of your settings after reconfiguring.
I cambiamenti:
– NEW: – Merged with GPL 380_7743 code, with binary blobs from 7378 for N66U
– NEW: Custom config support for quagga/ripd.
– NEW: Webui SSL certificate can now be saved so it gets reused instead of a new one being constantly generated. It will be stored under /jffs/ssl/, you can also easily provide your own by storing cert.pem and .pem in that location. Settings to control this can be found under Administration -> System.
– NEW: TLS support in vsftpd. Key and certs are automatically generated, and can also be replaced by your own, as ftp.key and ftp.crt under /jffs/ssl/
– NEW: fq_codel and configurable overhead support in Adaptive QoS.
– NEW: PEAP/MSCHAPv2 support via 802.1x on WAN interface, in addition to existing MD5 support (patch by Rafi Khardalian)
– CHANGED: Remember chosen sort method on DHCP static reservations page.
– CHANGED: Updated minidlna to 1.2.0.
– CHANGED: Updated nano to 2.8.5.
– CHANGED: Updated openssl to 1.0.2l.
– CHANGED: Updated ipset (ARM) to 6.32.
– CHANGED: Upgraded from vsftpd 2.0.4 to 3.0.3. You might need to revise any custom configuration you have done (if any).
– CHANGED: Moved SMB2 support switch to the main samba page.
– CHANGED: Optimized all webui images for size
– CHANGED: Tor now runs as a limited user instead of as root
– CHANGED: Limited number of supported OpenVPN clients to 2 on the RT-AC3200, to save on nvram.
– CHANGED: Removed tweak that allowed to disable/enable bridge multicast snooping, as Asus now disables it upstream at the kernel level.
– FIXED: OpenVPN client would be shown as having failed to connect if a reconnect attempt initially failed to authenticate, but succesfully connected afterward.
– FIXED: Quagga’s log could fill up RAM, reduced the amount of logging generated by it.
– FIXED: NFS sometimes failing to start properly (patch by john9527)
– FIXED: Layout issue of the status bar under Chrome when window is larger than 1800px (patch by Cyrus Dargahi)
– FIXED: UPNP and SNMP issues in Dual WAN mode.
– FIXED: NAT Loopback (merlin mode) in Dual WAN mode wasn’t supported.
– FIXED: Internal and external port specifications were swapped in miniupnpd’s config file (Asus/Tomato bug)
– FIXED: Enabling policy-based routing for a client connecting to a server that doesn’t push a redirect-gateway would fail to properly route traffic (for instance with StrongVPN)
– FIXED: Invalid port trigger rules when specifying a port range (patch by John Bacho)
– FIXED: OpenVPN client with a password containing an “&” could get corrupted when re-editing that client’s config.
– FIXED: Some remote syslogd would choke on syslog entries sent by the router if there were spaces in the tag parameter. Removed spaces where this was the case.
Note di installazione:
– Questo firmware personalizzato può essere applicato come qualsiasi normale aggiornamento.
– Non è necessario ripristinare le impostazioni di fabbrica.
– È possibile ripristinare il firmware ASUS originale in qualsiasi momento.
– Non caricare una copia salvata delle impostazioni.
Download