ASUS WL-500bv2 Oleg Custom Firmware 1.9.2.7-8 Download

Posted at November 21, 2024 by PCI-DB Team

ASUS WL-500bv2 Oleg Custom Firmware 1.9.2.7-8 Description

Changes: 

- Patched to WL-500W 1.9.8.5 firmware base code (New drivers for wl and et: 4.108.9.0)
- Added support for WL500W
- Added support for WL320gE/gP, additional lights are not supported (use WL550gE firmware)
- Added a handling for DHCP supplied routes (Use Route page to enable/disable)
- Multicast/IPTV: no longer need routes to be specified, cleaned up igmp logs
- It's now possible to specify DNS server IP address in the AP mode (added to IP Config page)
- Added new flashfs option: try 'flashfs enabled' to enable flashfs loading forever
- Added new http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable repository: use 'ipkg.sh install ipkg-opt' during initial ipkg installation
- Fixed PPPoE clamping code (set Maximum Segment Size to actual MTU)
- L2TP: server name resolution, persist/reconnect fixes
- NFS: added statd for proper locking
- SMB: Server string, new r/w share mode
- /etc/fstab: swapon and post-mount called now properly
- USB storage detection should work correctly for Philips mass storage devices
- /proc/cpuinfo now reports CPU model, revision and packaging options
- Changed connection tracking TCP timeout to 6 hours vs. 5 days
- Some WL-HDD IDE fixes
- Yet more fixes for built-in flash support (WL-500gP, WL-500W)
- Some minor kernel fixes

Important changes:

To reset username/password you've to reset to defaults using a RESET/RESTORE button!
- Port numbers used for RAW printing are changed: use 9100 for USB and 9101 for LPT
- Root fs is now ext3
- All scripts should now have
#!/bin/sh
line, otherwise they will not work
- post & pre scripts are now stored in the /usr/local/sbin directory; there is no /usr/local/init anymore
- post-firewall script should be adjusted, be careful when adding rules with -A - this will no longer work correctly, due to unconditional rule. Check the iptables -L -v output
- Client mode is not supported by the WL-500bv2 units

WARNING:

DON'T TRY CUSTOM FIRMWARES UNLESS YOU KNOW WHAT YOU ARE DOING, YOU COULD DESTROY YOUR UNIT BY DOING THIS! I'M NOT RESPONSIBLE TO ANY DAMAGE CAUSED TO YOUR UNIT BY USING IT! USE ON YOUR OWN RISK!

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 Oleg Drivers