D-Link Forums
The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Beta Code! => Topic started by: anthonynishat on October 01, 2009, 09:07:35 AM
-
Can someone share the changelist for this beta01 for the newly released firmware?
-
DIR-655 Firmware Release Notes
==========================================
Firmware: 1.32b04NA Beta01
Date: 09/30/09
1. This code can be used with all hardware revisions of the DIR-655.
2. This code only addresses the shareport issue
3. The attached Shareport utility will only work with this firmware version.
-
This is just a copy of a post I made in the DIR-655 forum:
And we have... failure! Woo hoo!
I have the same behavior as before the beta firmware. I just now tried to print something, about 22 hours after flashing the router to the new firmware, and the new shareport client is stuck in it's never ending attempts to connect to the printer. I can't reboot the router right now, since I am VPN'd into work, but I am confident that if I reboot the router, the printing will start.
This is with A1/A2 hardware and an HP 1510 PSC printer. With firmware 1.21, this setup worked, all the time.
-
So as alway they do what is not important.
Next release :
new font in setup :)
-
Well, the shareport functionality is important to me, but if you don't have a printer hooked up to the router, then yeah, it would be irrelavent.
-
DNS relay still has yet to be fixed :(
And well removing SecureSpot would be good too, since I prefer not having it enabled just so that my port forwarding settings will save.
As some of the others, I don't use SharePort and have no intentions on doing so. I've always bought network-capable printers, and it seems to still be the best way to go.
-
In this beta - release fixes problems with multicast addresses from udp: / / @ 239.0.1 .*: 1234 to udp: / / @ 239.0.2 .*: 1234 or not?
-
No reason to update.
Reboot after 1day:17h.
and mess in system config. Some config settings are set to default, include time.
Oct 3 18:15:43 192.168.0.2 Sat Oct 03 19:15:51 2009 AWARE-AP System Log: Web filter rejected packet from 192.168.0.28:63243 to 213.180.130.200:80
Oct 3 18:18:45 192.168.0.2 Sat Oct 03 19:18:53 2009 AWARE-AP System Log: Web filter rejected packet from 192.168.0.28:63257 to 209.85.129.100:80
Oct 3 18:20:54 192.168.0.2 Tue Sep 15 22:25:45 2009 AWARE-AP System Log: Wireless schedule init
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:45 2009 AWARE-AP System Log: Device initialized
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:46 2009 AWARE-AP System Log: LAN Ethernet Carrier Detected
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:46 2009 AWARE-AP System Log: LAN interface is up
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:47 2009 AWARE-AP System Log: WAN interface cable has been connected
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:47 2009 AWARE-AP System Log: Bringing up WAN using DHCP
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:48 2009 AWARE-AP System Log: Obtained IP Address using DHCP. IP address is X
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:49 2009 AWARE-AP System Log: Estimating speed of WAN interface
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:49 2009 AWARE-AP System Log: Gateway remote administration enabled on port: X
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:53 2009 AWARE-AP System Log: Time server time-a.nist.gov is at IP address 129.6.15.28
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:53 2009 AWARE-AP System Log: Requesting time from 129.6.15.28
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:20:59 2009 AWARE-AP System Log: Time synchronized
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:20:59 2009 AWARE-AP System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:00 2009 AWARE-AP System Log: Starting DHCP server
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:03 2009 AWARE-AP System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:05 2009 AWARE-AP System Log: Wireless link is up
-
No reason to update.
Reboot after 1day:17h.
and mess in system config. Some config settings are set to default, include time.
Oct 3 18:15:43 192.168.0.2 Sat Oct 03 19:15:51 2009 AWARE-AP System Log: Web filter rejected packet from 192.168.0.28:63243 to 213.180.130.200:80
Oct 3 18:18:45 192.168.0.2 Sat Oct 03 19:18:53 2009 AWARE-AP System Log: Web filter rejected packet from 192.168.0.28:63257 to 209.85.129.100:80
Oct 3 18:20:54 192.168.0.2 Tue Sep 15 22:25:45 2009 AWARE-AP System Log: Wireless schedule init
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:45 2009 AWARE-AP System Log: Device initialized
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:46 2009 AWARE-AP System Log: LAN Ethernet Carrier Detected
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:46 2009 AWARE-AP System Log: LAN interface is up
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:47 2009 AWARE-AP System Log: WAN interface cable has been connected
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:47 2009 AWARE-AP System Log: Bringing up WAN using DHCP
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:48 2009 AWARE-AP System Log: Obtained IP Address using DHCP. IP address is X
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:49 2009 AWARE-AP System Log: Estimating speed of WAN interface
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:49 2009 AWARE-AP System Log: Gateway remote administration enabled on port: X
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:53 2009 AWARE-AP System Log: Time server time-a.nist.gov is at IP address 129.6.15.28
Oct 3 18:21:05 192.168.0.2 Tue Sep 15 22:25:53 2009 AWARE-AP System Log: Requesting time from 129.6.15.28
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:20:59 2009 AWARE-AP System Log: Time synchronized
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:20:59 2009 AWARE-AP System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:00 2009 AWARE-AP System Log: Starting DHCP server
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:03 2009 AWARE-AP System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Oct 3 18:21:05 192.168.0.2 Sat Oct 03 19:21:05 2009 AWARE-AP System Log: Wireless link is up
Information related to '213.180.128.0 - 213.180.131.255'
inetnum: 213.180.128.0 - 213.180.131.255
netname: ONET-PL
descr: Onet.pl SA
country: PL
admin-c: ONET1-RIPE
tech-c: ONET1-RIPE
status: ASSIGNED PA
mnt-by: PL-ONET1-MNT
remarks: PLEASE ask for client support *ONLY* at: mailto:bok@onet.pl
remarks: PLEASE report any ABUSE *ONLY* to: mailto:abuse@onet.pl
source: RIPE # Filtered
role: ONET-PL NETWORK TEAM
address: Onet.pl SA
address: ITOperations
address: ul. Zapolskiej 44
address: 30-126 Krakow
address: Poland
phone: +48 12 2774630
fax-no: +48 12 2774002
remarks: In case any abuse or spam, please write to: mailto:abuse@onet.pl
remarks: In case any mail related problems, write to: mailto:bok@onet.pl
remarks: In case any client asking, write to: mailto:bok@onet.pl
remarks: This contact is valid only for network related problems, as BGP routing/peering.
abuse-mailbox: mailto:abuse@onet.pl
admin-c: ZZ18-RIPE
admin-c: TXF1-RIPE
admin-c: PP5885-RIPE
admin-c: TC1904-RIPE
tech-c: ZZ18-RIPE
tech-c: TXF1-RIPE
tech-c: PP5885-RIPE
tech-c: TC1904-RIPE
nic-hdl: ONET1-RIPE
mnt-by: PL-ONET1-MNT
source: RIPE # Filtered
% Information related to '213.180.128.0/19AS12990'
route: 213.180.128.0/19
descr: ONET-PL Onet.pl SA
origin: AS12990
mnt-by: AS12990-MNT
source: RIPE # Filtered
% Information related to '213.180.128.0/20AS12990'
route: 213.180.128.0/20
descr: ONET-PL Onet.pl SA
descr: primary services
origin: AS12990
mnt-by: AS12990-MNT
source: RIPE # Filtered
% Information related to '213.180.128.0/21AS12990'
route: 213.180.128.0/21
descr: ONET-PL Onet.pl SA
descr: services
origin: AS12990
mnt-by: AS12990-MNT
source: RIPE # Filtered
=========================================================================
Registrant:
Dns Admin
Google Inc.
Please contact mailto:contact-admin@google.com 1600 Amphitheatre Parkway
Mountain View CA 94043
US
mailto:dns-admin@google.com +1.6502530000 Fax: +1.6506188571
Domain Name: google.com
Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com
Administrative Contact:
DNS Admin
Google Inc.
1600 Amphitheatre Parkway
Mountain View CA 94043
US
mailto:dns-admin@google.com +1.6506234000 Fax: +1.6506188571
Technical Contact, Zone Contact:
DNS Admin
Google Inc.
2400 E. Bayshore Pkwy
Mountain View CA 94043
US
mailto:dns-admin@google.com +1.6503300100 Fax: +1.6506181499
Created on..............: 1997-09-15.
Expires on..............: 2011-09-13.
Record last updated on..: 2009-06-21.
Domain servers in listed order:
ns3.google.com
ns1.google.com
ns4.google.com
ns2.google.com
MarkMonitor is the Global Leader in Enterprise Brand Protection.
Domain Management
MarkMonitor Brand Protection™
AntiFraud Solutions
Corporate Consulting Services
Visit MarkMonitor at www.markmonitor.com
Contact us at 1 800 745 9229
In Europe, at +44 (0) 20 7840 1300
--
Querying whois.arin.net for 209.85.129.100...
OrgName: Google Inc.
OrgID: GOGL
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
NetRange: 209.85.128.0 - 209.85.255.255
CIDR: 209.85.128.0/17
NetName: GOOGLE
NetHandle: NET-209-85-128-0-1
Parent: NET-209-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.GOOGLE.COM
NameServer: NS2.GOOGLE.COM
NameServer: NS3.GOOGLE.COM
NameServer: NS4.GOOGLE.COM
Comment:
RegDate: 2006-01-13
Updated: 2006-06-01
-
As 1.32b04 only has changes in shareport services, perhaps still interisting.
A test report of 1.32b03 version:
http://pmdap.dlink.com.tw/PMD/GetAgileFile?itemNumber=FIR0900306&fileName=DIR-655_A4_FW_V1.32NAb03_TestReport_20090806.pdf&fileSize=1572864.0;430895.0;
Btw.: besides the known http://192.169.0.1/chklst.txt there is also a http://192.168.0.1/fw_version site.
This was new to me.. But it has less info.
-
kthaddock can you tell me the reason why you check this IPs from my log? I really know what I am blocking (ads,google spy,bad word).It is you hobby?What is conclusion of it? ???
-
A test report of 1.32b03 version:
http://pmdap.dlink.com.tw/PMD/GetAgileFile?itemNumber=FIR0900306&fileName=DIR-655_A4_FW_V1.32NAb03_TestReport_20090806.pdf&fileSize=1572864.0;430895.0;
Nice to see that documents within a password protected environment can be retrieved this easily. ;D
-
It's an official link from the tech support download site:
http://tsd.dlink.com.tw/
Just choose the DIR-655 and then the firmware 1.32NA link.
-
It's an official link from the tech support download site:
http://tsd.dlink.com.tw/
Just choose the DIR-655 and then the firmware 1.32NA link.
The source site (pmdap) is password protected
-
I find it faster to just ftp to the DIR 655 section.
DIR 655 (ftp://ftp.dlink.com/Gateway/dir655/)
-
Nice to see that documents within a password protected environment can be retrieved this easily. ;D
That was exactly my thought too. :D I tried my luck to find more reports, but sadly it seem to be the only one.
http://www.google.com/search?hl=en&q=site%3Apmdap.dlink.com.tw%2F&meta=
I find it faster to just ftp to the DIR 655 section.
DIR 655 (ftp://ftp.dlink.com/Gateway/dir655/)
Hmm, either I need new spectacles or this test report is simply not there. :P
-
That was exactly my thought too. :D I tried my luck to find more reports, but sadly it seem to be the only one.
http://www.google.com/search?hl=en&q=site%3Apmdap.dlink.com.tw%2F&meta=
Hmm, either I need new spectacles or this test report is simply not there. :P
The files not the report which I could care less about as my DIR 655 works perfectly.
-
The files not the report which I could care less about as my DIR 655 works perfectly.
;D so does mine. But saying that's like cursing in a church it seems.
-
Eddie,
Does this fix the 802.11b mixed mode compatibility issue?
Thanks,
F.
-
Eddie,
Does this fix the 802.11b mixed mode compatibility issue?
Thanks,
F.
I haven't had any compatibility issues with b devices (I found one here at home, a PocketPC 2003). So hard to say. Which issue are you referring to?
-
I can't get any of my silver or gold Orinoco Wavelan 802.11b PCMCIA cards to connect to this 655 router. I have have four PCMCIA cards, 2 silver, 2 gold, and used them with older hardware like windows CE units, etc...
F.
-
I can't get any of my silver or gold Orinoco Wavelan 802.11b PCMCIA cards to connect to this 655 router. I have have four PCMCIA cards, 2 silver, 2 gold, and used them with older hardware like windows CE units, etc...
F.
Aha, that issue ;)
It should work properly, but as I already replied these Wavelan b products have caused more issues due to OS configuration. So are you 100% sure this is not the case here?
-
Correct, if all I do is plug in my other two older routers [two older G/B and B only netgear routers].. and then do a re-request for DHCP via any of the wavelan cards, it works. No encryption BTW...
As soon as I connect the 655, I cannot get a DHCP response and cannot connect using these cards at all. I have tried running B/G/N and B/G with no luck.
Someone said to try B only mode on the 655, I think that even if this works, that is not a solution.
Also, somone recoemmended I bridge my old router to my 655 for B-only use. This is possible, but I guess I will only do this if I have too...
F.
-
I just got off the phone with e DLINK tech level 2 technician about this B compatibility issue.
This appears to be a known issue on the 655 with some B cards [not all and I could not get a list], and is resolved for now by selecting B-only mode on the 655 [not something I plan on doing].
Dlink said they are working on a fix this mix-mode issue but there is no timeline for this now.
F.