Home 9 Sup­port and FAQ 9 Down­loads 9 Chan­ge­log

Chan­ge­log for firm­ware ver­si­on 3.0

3.0–6009

  • Exten­si­on of the hot­spot sub­net to /22 netmask
  • Youth pro­tec­tion fil­ter updated

3.0–6007

  • simi­lar to 3.0–6006, but now it is pos­si­ble to flash via TP-Link web interface

3.0–6006

  • first release for TP-Link C7v5
  • fea­tures like 3.0–6003, newer Open­Wrt base for more cur­rent hardware

3.0–6003

  • Edge­Rou­ter: file sys­tem is moun­ted with sync option
  • youth pro­tec­tion fil­ter can only be con­fi­gu­red via web interface

3.0–6002

  • policies/bandwiths for users/links are now being considered
  • Wal­led-Gar­den addres­ses are not being con­si­de­red for accounting

3.0–6001

  • nati­ve HSVPN sup­port — simi­lar to Appliances
  • chil­li bypass func­tion to incre­a­se band­with active
  • various smal­ler fixes and updates (Ker­nel, WiFi driver)

3.0–5386

  • 12 June 2018

3.0–5381

  • 4 April 2018
  • initi­al release for TP-LINK 1043v5 and TP-LINK Archer C7 v4
  • back­port from LEDE/OpenWrt trunk
  • update of WiFi drivers

3.0–537

  • 21.04.2017
  • first release for TP-LINK 1043v4
  • nati­ve sup­port for HOTSPLOTS lan­ding­pa­ge for ser­vices TV to go, Press and Tou­rist Info
  • Ker­nel update to ver­si­on 4.4.x
  • cur­rent WiFi drivers

3.0–531

  • Beta ver­si­on of 06 Janu­a­ry 2015
  • Sup­ports the TP-Link Archer C5 / C7 platforms
  • Num­ber of free MAC addres­ses incre­a­sed to 64
  • VPN rou­ting swit­ched on by default
  • Watch­dog initia­tes reboot if VPN tun­nel is off­line for more than 10 minutes
  • Bug fix in band­width control
  • RADIUS via VPN: some upstream rou­ters reject “intel­li­gent” traf­fic. This can lead to fil­te­ring RADIUS UDP packets and thus pre­vent hot­spot log­ins. As a work­around RADIUS packets can also be sent through the VPN tunnel.
  • GRO dis­ab­led on all inter­faces (may lead to poor through­put, depen­ding on the connection)
  • Pre­pa­ra­ti­on for HSVPN routing
  • Reset but­ton easier to use: if the but­ton is pres­sed and held, the sta­tus LED starts blin­king after 10 seconds. If the but­ton is released during the blin­king peri­od, the rou­ter is being reset.

3.0–524

  • 29 August 2014 — Ubi­qui­ti Uni­Fi AP Pro only
  • A newer ran­ge comes with a new flash chip. Ver­si­on 3.0–524 adds sup­port for this new hardware.

3.0–523

  • 07 August 2014 — Ubi­qui­ti Uni­Fi AP only
    Fix for the ope­ra­ting mode hot­spot router

3.0–521

  • 18 July 2014
  • Fix for WDR4900: after chan­ging the ope­ra­ting mode the MAC address was not set correctly
  • Fix for Uni­Fi AP: now usable in rou­ter and AP modes

3.0–520

  • 16 June 2014
  • Repo­si­to­ry for opkg packets adjus­ted, small bug fixes
  • Sup­port for Uni­Fi AP and Uni­Fi AP Pro in rou­ter mode

3.0–516

  • 06 Febru­a­ry 2014
  • Bug fix: after chan­ging the ope­ra­ting mode, WiFi set­tings were not main­tai­ned. Fixed.
  • Bug fix: an update from 3.0–0xx to 3.0–5xx with retai­ned set­tings cau­sed faul­ty rou­ting. Fixed.
  • DHCP server’s lea­se time reset to 10 minu­tes (from 11).
  • Opti­on “dns­pa­ra­noia” deac­ti­va­ted again by default.

3.0–515

  • 22 Janu­a­ry 2014
  • Bug fix: PPPoE dial­up cor­rec­tions of ver­si­on 3.0–514 cau­sed pro­blems in con­nec­tion with VP rou­ting. Fixed.

3.0–514

  • 22 January2014
  • Bug fix: fixed PPPoE dialup.
  • Bug fix: the hard­ware watch­dog could crash the TP-LINK WR1043ND v1. This has been fixed.

3.0–513

  • 17 Decem­ber 2013
  • Bug fix: a ker­nel error in the net­work bridge could cau­se rou­ters and APs to crash during boot when recei­ving cer­tain net­work packets. This has been fixed.
  • Com­pa­ti­bi­li­ty: Ver­si­on 3.0–5xx does by default not allow repea­ter con­nec­tions. The­se have to be acti­va­ted in the web inter­face first. In order to main­tain com­pa­ti­bi­li­ty with ver­si­on 3.0–0xx, this set­ting is set when updating the firm­ware from 3.0–0xx to 3.0–5xx.

3.0–512

  • 24 Novem­ber 2013
  • First release of an Open­Wrt trunk based back­port to sup­port new hard­ware genera­ti­ons from TP-Link and Ubiquiti.
  • 802.11n ought to run stable.
  • This build is based on a new ker­nel and new WiFi drivers.
  • Func­tions and web inter­face of firm­ware 3.0 are retained.
  • The reset but­ton only fac­to­ry resets if the but­ton is pres­sed lon­ger than 10 but no lon­ger than 14 seconds (to pre­vent an acci­den­tal reset).