Xwrt-Vortex Firmware 380.67 for Linksys EA6900 Download

Posted at December 24, 2024 by PCI-DB Team

Install Driver Automatically

Device Name	Xwrt-Vortex Firmware 380.67 for Linksys EA6900
Category	Router Switch Access Point
Manufacturer	Linksys
File Size	28.2 MB
Supported OS	OS Independent

Xwrt-Vortex Firmware 380.67 for Linksys EA6900 Description

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. You should not need to reset to factory defaults. You can revert back to an original Asus firmware at any time just by flashing a firmware downloaded from Asus's website.

NOTE:

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.

Changes:

- 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.

Installation Notes:

- This custom firmware can be applied like any regular update.
- You should not need to reset to factory defaults.
- You can revert back to an original ASUS firmware at any time.
- Do not load a saved copy of your settings.

About Router Firmware:

Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn't either newer or matching this release.

Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.

In theory, these steps shouldn't be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don't always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.

If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.

If you're looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don't power off the router or use its buttons during the installation, if you wish avoid any malfunctions.

If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don't miss the update that will improve your device.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Linksys Drivers