PermaLINK Firmware Release Notes
Version V3119 / V6119
Aug. 10th, 2006
Enhancement – Under prolonged failure of the WAN line, Healthy Check retries will timedout. This is an extraordinary situation! Now, Healthy Check will retries 3 times to see whether
the WAN connection is reconnected. If not, it will wait for 3 hours, and then tries again…
23 2006-08-02 23:05 WAN1 DHCP client try to restart
24 2006-08-02 23:05 WAN1 cable on, DHCP client start.
25 2006-08-02 23:06 Gateway 1 exist (192.168.0.1)
26 2006-08-02 23:06 WAN1 UP IP = 192.168.1.64
27 2006-08-02 23:06 No wan port for NTP Update
28 2006-08-02 23:06 [HCk] WAN1 is Back to normal !!
29 2006-08-02 23:07 WAN1 is NO response, [HCk] Disable it !!
30 2006-08-02 23:07 WAN1 cable off
31 2006-08-02 23:07 DHCP client stop.
32 2006-08-02 23:07 WAN1 Down.
33 2006-08-02 23:07 WAN1 HC(3) push to connect ...
34 2006-08-02 23:07 WAN1 cable on, DHCP client start.
35 2006-08-02 23:07 Gateway 1 exist (192.168.0.1)
36 2006-08-02 23:07 WAN1 UP IP = 192.168.1.64
37 2006-08-02 23:07 No wan port for NTP Update
38 2006-08-02 23:08 [HCk] WAN1 is Back to normal !!
39 2006-08-02 23:08 WAN1 is NO response, [HCk] Disable it !!
40 2006-08-02 23:08 WAN1 cable off
41 2006-08-02 23:08 DHCP client stop.
42 2006-08-02 23:08 WAN1 Down.
43 2006-08-02 23:09 WAN1 HC(2) push to connect ...
44 2006-08-02 23:09 WAN1 cable on, DHCP client start.
45 2006-08-02 23:09 Gateway 1 exist (192.168.0.1)
46 2006-08-02 23:09 WAN1 UP IP = 192.168.1.64
47 2006-08-02 23:09 No wan port for NTP Update
48 2006-08-02 23:09 [HCk] WAN1 is Back to normal !!
49 2006-08-02 23:10 WAN1 is NO response, [HCk] Disable it !!
50 2006-08-02 23:10 WAN1 cable off
51 2006-08-02 23:10 DHCP client stop.
52 2006-08-02 23:10 WAN1 Down.
53 2006-08-02 23:11 WAN1 HC(1) push to connect ...
54 2006-08-02 23:11 WAN1 cable on, DHCP client start.
55 2006-08-02 23:11 Gateway 1 exist (192.168.0.1)
56 2006-08-02 23:11 WAN1 UP IP = 192.168.1.64
57 2006-08-02 23:11 No wan port for NTP Update
58 2006-08-02 23:11 [HCk] WAN1 is Back to normal !!
59 2006-08-02 23:12 WAN1 is NO response, [HCk] Disable it !!
60 2006-08-02 23:12 WAN1 cable off
61 2006-08-02 23:12 DHCP client stop.
62 2006-08-02 23:12 WAN1 Down.
63 2006-08-02 23:12 WAN1 HC(0) push to connect ...
64 2006-08-02 23:12 WAN1 DHCP connect (0) in waiting
65 2006-08-02 23:12 Fail to start WAN1 (4) DHCP client
66 2006-08-02 23:12 Retry it after 180 mins
Enhancement – Increase NAT & DMZ table entries. NAT is from 10 to 20 and DMZ is from 20
to 40.
Version V3118 / V6118
Version V3117A / V6117A
Not released.
Apr. 26th, 2006
Enhancement – UltraSmartSharing™ (Default is ON): This is a new and exclusive PermaLINK
feature! You access it via:
Main Page > Load Balance
It provides you with automatic assignment of each LAN PC represented by an IP to a particular
connected WAN line, and it will continue to use that WAN line, until time-out. Fault-tolerance and
fail-over is automatically maintained. This is an exclusive mode that permits a group of PCs
automatically to work well for games, VOIP, HTTPS, etc. We’ve developed this as a continuous
innovation to support Internet Café, Schools, VOIP provider, Wireless ISP…etc
Please note: If you are using PermaLINK for a few users like under 5, we recommend that you
disable UltraSmartSharing.
Version V61156 (PRI-885) Version V31156 (PRI-785) Mar. 22nd, 2006
Enhancement – DNS Relay: Some ISP only allows DNS queries from their own lines. i.e. DNS
query packets from WAN1 is only allowed to the DNS Server of WAN1’s ISP.
If you have such a requirement, please enter your PermaLINK router’s LAN IP into the DHCP
Server’s Primary and Secondary DNS fields. Assuming you have the default 192.168.1.254:
Then after you reset the PermaLINK router, and assuming your are a DHCP Client, at the
command window please run:
ipconfig/release
ipconfig/renew
And finally
ipconfig/all
You will get the following:
You will have the DNS Servers as 192.168.1.254. Please note: if your LAN PC uses static
IP,then please configure your Primary and Secondary DNS Servers as: 192.168.1.254
Version V61146 (PRI-885) Version V31146 (PRI-785)
not released
Version V61136 (PRI-885) Version V31136 (PRI-785) Jan. 24th,, 2006
BUG fix – 2 Dynamic WAN lines fail-over – When one line dropped, it caused SMTP to fail.
Enhancement – Mail Alert – added additional Mail Alert System Error Logs
Version V61126 (PRI-885) Version V31126 (PRI-785) Jan. 10th, 2006
BUG fix – HEALTHY CHECK – when enabled, it caused NTP (Network Time Protocol) to fail.
Version V61116 (PRI-885) Version V31116 (PRI-785) Dec. 23rd, 2005
BUG fix – HEALTHY CHECK
There are 2 types of disconnections:
1. physical Ethernet LINK at the WAN port
2. some kind of data stoppage upstream from the WAN port
Healthy check is a process for type 2 disconnection and for the hopefully subsequent
reconnection. When it operates properly, it does fail-over and auto-reconnect when the data
stream gets going again. From examining the SYSLOG, I have determined that
Healthy check is invoked approximately every minute.
For the type 2 disconnection, we have previously fixed the PPPoE WAN configuration. The
current fix is for Static and Dynamic IP WAN configurations.
There are instances when the WAN port has a physical Ethernet LINK and also a valid IP
address, i.e. a Dynamic WAN configuration where the ADSL line connects using PPPoE at the
ADSL modem. Here we have a physical Ethernet LINK to the ADSL modem and also a DHCP
Client getting its IP from the DHCP Server in the ADSL modem.
In cases where either the ISP or the Telephone company’s routers are DOWN, an enabled
Healthy Check will correctly detect the disconnection and will bring the WAN connection DOWN.
After one minute’s time, Healthy Check will see if the line is coming back UP again. If the
connection processor sees a WAN Port with a valid IP, it assumes that the WAN line came back
UP.
25 1970-01-01 00:02 [HCk] WAN2 push to connect ...
26 1970-01-01 00:02 WAN2 cable on.
27 1970-01-01 00:02 WAN2 DHCP client start.
28 1970-01-01 00:02 Gateway 2 exist (71.131.244.139)
29 1970-01-01 00:02 WAN2 UP IP = 71.131.244.140
30 1970-01-01 00:02 Request NTP Updated Time fail
31 1970-01-01 00:03 [HCk] WAN2 is Back to normal !!
32 1970-01-01 00:03 WAN2 is NO response, [HCk] Disable it
33 1970-01-01 00:03 WAN2 cable off, WAN2 DHCP client stop.
34 1970-01-01 00:03 WAN2 Down.
35 1970-01-01 00:04 [HCk] WAN2 push to connect ...
36 1970-01-01 00:04 WAN2 cable on.
37 1970-01-01 00:04 WAN2 DHCP client start.
38 1970-01-01 00:04 Gateway 2 exist (192.168.0.1)
39 1970-01-01 00:04 WAN2 UP IP = 192.168.1.64
40 1970-01-01 00:04 Request NTP Updated Time fail
41 1970-01-01 00:04 [HCk] WAN2 is Back to normal !!
42 1970-01-01 00:05 DHCP Client renewing Fail.
43 1970-01-01 00:05 WAN2 DHCP client stop.
44 1970-01-01 00:05 WAN2 Down.
This cycle is approximately 90 seconds; continuous and on-going as shown in the SYSLOG.
Previously, during the time period when the WAN line is assumed to be UP, the load balancer is
assigning Sessions to that WAN line. But, in reality, that WAN line is actually DOWN, but Healthy
Check hasn’t detected it yet. (an approximately 45 seconds time period.) So, assigned Sessions
will not respond within this 45 seconds window.
This new version fixes the false assignment of Sessions to a WAN line that does NOT pass the
enabled Healthy Check. With this bug fix, Healthy Check is highly recommended for fail-safe
Internet.
Enhancement – Virtual Server table length is 100 entries; Group Virtual Server table length is 30.
Version V61116 (PRI-885) Version V31116 (PRI-785) Not released
Version V61106 (PRI-885) Version V31106 (PRI-785) Not released
Version V61096 (PRI-885) Version V31096 (PRI-785) Not released
Version V61086 (PRI-885) Version V31086 (PRI-785) Nov 18th, 2005
Bugfix – Bidirectional DMZ – For LAN PC accessing DMZ via WAN IP addresses
-
MultiWAN mapped to a single DMZ host
Enhancement – Virtual Server Table – Number of table entries increased from 20 to 100.
Version V61076 (PRI-885) Version V31076 (PRI-785) Not released
Version V61066 (PRI-885) Version V31066 (PRI-785) Not released
Version V61056 (PRI-885) Version V31056 (PRI-785) Not released
Version V61046 (PRI-885) Version V31046 (PRI-785) Sep 20th, 2005
Bugfix – Added support Linux DHCP Clients
Version V61036 (PRI-885) Version V31036 (PRI-785) Not released
Version V60026 (PRI-885) Version V30026 (PRI-785) Aug 31st, 2005
Enhancement – Provide, once again, the WAN5/DMZ switch. You access it via: Main Page >
WAN Configure
You may select WAN5 for load balancing or select a completely separated DMZ
port.
-
Virtual Server Table entry fields has been increased from 20 to 100 entries
-
Group Virtual Server entry fields has been increase from 5 to 30 entries
Version V60016 (PRI-885) Version V30016 (PRI-785) Aug 7st, 2005
Not released
Enhancement - DHCP Server now provides 2 DNS Server fields, so that for DHCP Client, there
is a primary and secondary DNS Server. If they are from different ISP, then it will provide faulttolerant, redundant, DNS resolutions.
Version V6000B6 (PRI-885) Version V3000B6 (PRI-785) Aug 1st, 2005
Initial Production Version