TEW-652BRP Firmware Release Note
Firmware: v2.01 Build: 0013
Hardware: R1
Date: Thu, 02 Sep 2010
Firmware Version = 2.01, Build=13, Date=Thu, 02, Sep, 2010
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0032, Date: Tue, 17, Aug, 2010
2.0, Build: 1451, Date: Tue, 04, May, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0636C272
Problems Resolved:
1. FQDN support in PPTP /L2TP /RUSSIA PPTP / RUSSIA L2TP mode.
=================================================================
Firmware: v2.01 Build: 0012
Hardware: R1
Date: Fri, 27 Aug 2010
Firmware Version = 2.01, Build=12, Date=Fri, 27, Aug, 2010
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0032, Date: Tue, 17, Aug, 2010
2.0, Build: 1451, Date: Tue, 04, May, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0636573D
Problems Resolved:
2. It can not be checked as VPN server by name is not accepted.
_________________________________________________________________________
Firmware: v2.01 Build: 0011
Hardware: R1
Date: Tue, 10 Aug 2010
Firmware Version = 2.01, Build=11, Date=Tue, 10, Aug, 2010
KERNEL =
2.6.x, SDK: 2.0, Build: 0031, Date: Mon, 14, Jun, 2010
Application =
2.0, Build: 1451, Date: Tue, 04, May, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0637CAB5
WLAN Version =
CheckSum =
Problems Resolved:
3.
Router traffic (Ping test, E-mail Log, NTP…etc) do NOT go through PPTP tunnel
network. The traffics from LAN clients are OK that will go through PPP tunnel
network.
_________________________________________________________________________
Firmware: v2.01 Build: 0010
Hardware: R1
Date: Tue, 03 Aug 2010
Firmware Version = 2.01, Build=10, Date=Tue, 03, Aug, 2010
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0031, Date: Mon, 14, Jun, 2010
2.0, Build: 1451, Date: Tue, 04, May, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0638299D
Problems Resolved:
1.
2.
3.
Host allows to enter special characters and WAN DHCP will fail.
Connected PC still get IP from previous IP range after DHCP pool is changed.
Gateway is not displayed in Static Russia PPPoE/PPTP/L2TP.
4. PPPoE doesn't reconnect after WAN cable is disconnected then reconnected.
5. Some devices such as IP camera can not get IP from DUT.
_________________________________________________________________________
Firmware: v2.01 Build: 0009
Hardware: R1
Date: Thu, 15 July 2010
Firmware Version = 2.01, Build=09, Date=Thu, 15, July, 2010
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0031, Date: Mon, 14, Jun, 2010
2.0, Build: 1451, Date: Tue, 04, May, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x063875A1
Problems Resolved:
1.
2.
3.
Trendnet TEW-652BRP ECS support with Utility v1.00b01.
IGMPSNOOPING support.
Remote login has only user privilege.
4.
5.
6.
7.
8.
9.
10.
“User” becomes “Admin” privilege.
Can not get any UPnP information by "Intel Device Spy" tool.
Block LAN to WAN will also block LAN to DUT.
2 items in X-BOX test are failed.
“Manual Dial” doesn’t work in some specific PPTP environment.
Ping timed out when packets size is the same or large than MTU.
Fixed the bug that WAN port ping fail when enabling a firewall rule no matter the host
exits or not.
11. Fixed the bug that Remote Management and wan ping will not work if Firewall rule is
12.
13.
14.
15.
16.
17.
18.
configured.
Fixed the bug that IP/Protocol filter does not take effect to the PC that is in “Only
Allowed” MAC list.
LAN to LAN multicast movie is choppy.
Fixed the bug that LAN can receive WAN bootp packets.
Router with PPTP/MPPE enabled will reboot after disconnected by PPTP server
SIP phone can’t hear each other in Brekeke SIP server.
GUI lost icon when Avast (Anti-virus) is running.
Router e-mails log on every boot up regardless the configured schedule.
_______________________________________________________________________________
Firmware: v2.01 Build: 0008
Hardware: R1
Date: Fri, 12 Mar 2010
Firmware Version = 2.01, Build=08, Date=Fri, 12, Mar, 2010
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0024, Date: Fri, 26, Feb, 2010
2.0, Build: 1385, Date: Fri, 05, Mar, 2010
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x06367806
Note:
If you want to upgrade firmware from v2.00bXX to v2.01B08, please update to
v2.00b28 first. And once you upgrade to v2.01b08 successfully, you can’t downgrade
to v2.00bXX.(per new function request, modify flash check for new image)
Problems Resolved:
1. pptp/l2tp low throughput
2. Wireless client sometimes can’t ping to router but gets the ip-address. While applying the
settings from page, it works fine.
3. Client bug 01: Need to change order of DHCP options, to add 249
4. Client bug 02: WAN-LAN speed at L2TP_rus is too small
5. Client bug 03: IP TV starts not at once, only after approximately 5-10 minutes. Users consider,
that IP TV does not work, as they do not wait the display beginnings.
6. Client bug 04: In Configuration settings file there is strings
“ntp_default_server=ntp1.dlink.com,ntp.dlink.com.tw” and “lan_device_name=dlinkrouter”
7. Client bug 05: Does not connect Russia_PPPoE/PPPoE with dynamic and static IP address
8. TSD bug 01: WPA-EAP Fail issue
9. TSD bug 02: DNS query issue with PPTP / L2TP / Russia PPTP / Russia L2TP / Russia PPPoE
10. TSD bug 03: Firewall issue
11. TSD bug 04: MAC filter issue
12. TSD bug 05: MAC filter issue
13. TSD bug 06: PPTP can not link with TW100-BRV304 (VPN Router) issue
.
Known Bugs:
1. Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and service
name.
2. In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on demand mode
and the server IP is domain name but IP address, it would take long time to connect after boot.
3. Client bug 06: Does not work SYSLOG at L2TP/PPTP connection
Firmware: v2.01 Build: 0007
Hardware: R1
Date: Mon, 04 Dec 2009
Firmware Version = 2.01, Build=07, Date=Mon, 04, Nov, 2009
WLAN Version =
2.6.x, SDK: 2.0, Build: 0020, Date: Fri, 30, Oct, 2009
2.0, Build: 1291, Date: Thu, 3, Dec, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
CheckSum =
0x06379D86
KERNEL =
Application =
Problems Resolved:
1.
2.
.
SNMP bug(pre test): wan status dns fail while set by snmp
Pre-test v2.01b06 bug: WPA/WPA2 EAP is fail
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1. Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0006
Hardware: R1
Date: Mon, 30 Nov 2009
Firmware Version = 2.01, Build=06, Date=Mon, 30, Nov, 2009
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0020, Date: Fri, 30, Oct, 2009
2.0, Build: 1280, Date: Mon, 30, Nov, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0637F6A8
Problems Resolved:
1.
SNMP bug:Update table access
2.
SNMP bug:Main PPPOE setting DNS fail.
3.
SNMP bug main PPTP setting gateway fail (must set to static-ip type, see the node description)
4.
SNMP bug Wireless security WEP HEX & ASCII 128 bit 1~4 key setting fail.
5.
SNMP bug Dynamic DNS Server Address to choose NO-IP.com fails.
.
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1. Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0005
Hardware: R1
Date: Thu, 12 Nov 2009
Firmware Version = 2.01, Build=05, Date=Thu, 12, Nov, 2009
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0020, Date: Fri, 30, Oct, 2009
2.0, Build: 1259, Date: Wed, 11, Nov, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0637EA6A
Problems Resolved:
1.
Add SNMP V1 V2 (You can find it in Management page)
.
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1. Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0004
Hardware: R1
Date: Tue, 3 Nov 2009
Firmware Version = 2.01, Build=04, Date=Tue, 3, Nov, 2009
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0019, Date: Wed, 14, Oct, 2009
2.0, Build: 1243, Date: Thu, 29, Oct, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0638E4B0
Problems Resolved:
1.
Pre-test v2.01b03 bug No.1 After disconnecting Russia PPPoE, the field of Default
Gateway shows "0.0.0.0", in case the Russia PPPoE mode is static IP mode, it should
shows Russia physical gateway.
Known Bugs:
1.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
2.
3.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1. Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0003
Hardware: R1
Date: Thu, 29 Oct 2009
Firmware Version = 2.01, Build=03, Date=Thu, 29, Oct, 2009
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0019, Date: Wed, 14, Oct, 2009
2.0, Build: 1243, Date: Thu, 29, Oct, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x06389C77
Problems Resolved:
1.
Pre-test v2.01b02 bug No.1 After disconnecting Russia PPPoE, the field of Default
Gateway shows "0.0.0.0", it should shows Russia physical gateway.
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1.
Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0002
Hardware: R1
Date: Fri, 23 Oct 2009
Firmware Version = 2.01, Build=02, Date=Fri, 23, Oct, 2009
KERNEL =
2.6.x, SDK: 2.0, Build: 0019, Date: Wed, 14, Oct, 2009
Application =
2.0, Build: 1222, Date: Wed, 14, Oct, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x06386D45
WLAN Version =
CheckSum =
Problems Resolved:
1.
2.
Pre-test v2.01 b01 No.1 Setting WAN connection type from L2TP to Russia L2TP, the
connection type filed still shows L2TP.
Pre-test v2.01 b01 No. 2 There is a “MPPE Enable” filed in Russia L2TP page, this
filed isn’t need to appear in Russia L2TP page. (“MPPE Enable” filed would be
removed in this version.)
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1.
Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.
Firmware: v2.01 Build: 0001
Hardware: R1
Date: Tue, 20 Oct 2009
Firmware Version = 2.01, Build=01, Date=Tue, 20, Oct, 2009
KERNEL =
Application =
WLAN Version =
CheckSum =
2.6.x, SDK: 2.0, Build: 0019, Date: Wed, 14, Oct, 2009
2.0, Build: 1222, Date: Wed, 14, Oct, 2009
1.0, Build: 0001, Date: Thu, 15, Jan, 2009
0x0638D48D
Note:
1.
Please help to verify Russia dual access feature.
Known Bugs:
1.
2.
3.
Problem of input the "\" character in PPPoE / PPTP / L2TP password, username , and
service name.
pptp/l2tp low throughput
In Russia PPTP and Russia L2TP mode, in case the connection mode is dial on
demand mode and the server IP is domain name but IP address, it would take long time
to connect after boot.
Known issue:
1.
Wireless client sometimes can’t ping to router but gets the ip-address. While applying
the settings from page, it works fine.