Tsume
join:2004-02-23
Johnson City, TN | reply to Tsume
Re: 2.53 on DLINK CANADA?
Just curious, but I removed the router from the loop, and my download speeds on most torrent files have doubled or even tripled. Is this coincidence, or caused by the limited number of connections the router can take? |
|
Bwuutje
join:2005-01-10
| Did anyone else notice too that the link for fw 2.53 for the 624 is gone on the .tw site ? (Well, actually the fw is still there but not in the menu.)
Bwuutje.
(No, I do not need a link, I have the fw. Yes, I know it's still on other sites, etc. It is just an observation.) |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| reply to Tsume
said by Tsume  :Just curious, but I removed the router from the loop, and my download speeds on most torrent files have doubled or even tripled. Is this coincidence, or caused by the limited number of connections the router can take? It's not a coincidence, I'd bet.
The router isn't imposing a limit, so I'm thinking it's just maxed out on the processor.
--
Robb Topolski
http://www.funchords.com/
Hillsboro, Oregon USA
Kindness is treating someone better than they deserve. |
|
elreservado
@com.ar | reply to Tsume
What exactly is to remove the router from the loop?? |
|
Tsume
join:2004-02-23
Johnson City, TN | Means connecting my PC straight to the modem, without the router between them.
--
Verizon's CEO is the business equivilant to Germany's Adolf Hitler. |
|
yukycg
@mindspring.com
| reply to Tsume
I using the C3 model, upgraded it from 2.50 to this 2.53, I just manual reenter all the information, then restart my computer, everything seem fine except I still have slow download speed in BT.(15-60K max)
It did in fact fixed the UPnP bug but not the wireless uPnp, no reboot on neither wired or wireless, (1 hr passed without any drop, but only about 35K dl speed at this point, and zero on wireless :-( ) |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC | said by yukycg:
It did in fact fixed the UPnP bug but not the wireless uPnp, What does that mean? |
|
yukycg
@mindspring.com
| I am back to 2.50 since 2.55 keeps reboot my router.(I was using 2.53, but not sure if it is stable since I only use it for few hrs and later flashed to 2.55)
What I mean is while I am using bitcomet(desktop, wired) with ICF & UPNP turn on, the firewall in the router will automatic open the port for me,
ex Allow BitComet (192.168.2.2:11122) 11 WAN,* LAN,192.168.2.2 TCP,11122
however, using my laptop (wireless), the router won't open the port, as a result a very slow download, so I have to manually enter port forwarding under virtual server. |
|
Jackass19
join:2005-06-18 | The latest DI-624 routers shipping in Australia are version C3 and are shipping with firmware 2.53 |
|
Kiddion
@193.173.x.x
| reply to yukycg
I am back to 2.50 since 2.55 keeps reboot my router.(I was using 2.53, but not sure if it is stable since I only use it for few hrs and later flashed to 2.55) 2.53 seems pretty stable, 2.55 didn't work for me either, after a while (few days without reboot) my wireless connection was totally gone. 
A day later, I couldn't even connect to the router itself! Still I could ping every host on the wired network... 
Haven't had any issues with 2.53 before, haven't had them now! |
|
peter_m
Premium
join:2005-07-13
Canada, QC
| DI-624 with fw 2.55????
yukycg@mindspring.com
&
kiddion@someip
Where can I get the 2.55 firmware? What are the changes fom 2.53b69? I know, doesnt look very promissing from your posts, but I'm very curious. Trying to find a fix for a problem with Broadcom chipsets not getting an IP through DHCP when using WPA2 on the DI-624.
Peter m. |
|
Anonymous Coward
@rr.com
| peter_m: I am afraid none of these firmwares can help you fixing the DHCP problem. The only resolution is to go back to 2.42 or 2.50.
I noticed that the newest driver from Dell shows a little bit of improvement. While aquiring a DHCP address during the boot sequence of the computer does not, restarting the interface (or selecting "repair" if you use WinXP) does work. |
|
Kiddion
@193.173.x.x
| reply to peter_m
see
»new FW ver 2.55 for DI-624
All I can say is I don't have DHCP problems, since I'm not using it.  DHCP is IMHO a luxury you could do without.
"If it ain't broken, don't fix it", so if you need WPA2 for security, don't use DHCP either (for security!). If you need DHCP (for comfort), use the 2.42 or 2.50 firmware.
But then again, I really need security where I live. I'm using a non-obvious ip range, as narrow as 16 IPs, combined with MAC filtering and of course WPA2-PSK encryption. So I have every reason to use the 2.53 firmware. |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| said by Kiddion:
But then again, I really need security where I live. I'm using a non-obvious ip range, as narrow as 16 IPs, combined with MAC filtering and of course WPA2-PSK encryption. So I have every reason to use the 2.53 firmware.
You must surf some really, really good porn.  :D:o:p
--
Robb Topolski http://www.funchords.com/  Hillsboro, Oregon USA
They who would give up an essential liberty for temporary security, deserve neither liberty or security |
|
Kiddion
@193.173.x.x
| No, surrounded by some really bad Campus IT junks like me If there is a smart way to crack WPA2, it will probably be invented here first
They probably already have all the porn they could wish for... (Not that they would agree on that) |
|
Kiddion
@193.173.x.x
| Not that this is likely to happen anywhere in the future (WPA2 cracked at a smart way).
It's more likely they'll "find" my PSK, I would still be save for a few hours/days with MAC and ip-filtering. It's just the challenge, we don't harm each other. We still drink beer together. |
|
Anonymous Coward
@rr.com
| If you want real security you WANT DHCP to work. Because without that, you cannot properly implement 802.1x authentication which is definitely better than any pre-shared key.
Using pre-shared keys is a risk and always will be, even with the current level of encryption in WPA2.
That aside... MAC filtering is of no use at all, because MAC addresses are transmitted unencrypted and really easy to sniff out. |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
·Verizon Online DSL
·Skype
| said by Anonymous Coward:
If you want real security you WANT DHCP to work. Because without that, you cannot properly implement 802.1x authentication which is definitely better than any pre-shared key. Hey Coward, can you say more about this? I don't understand the necessary relationship between DHCP and 802.1X ...
--
Robb Topolski http://www.funchords.com/ Hillsboro, Oregon USA
They who would give up an essential liberty for temporary security, deserve neither liberty or security |
|
peter_m
Premium
join:2005-07-13
Canada, QC
| reply to Tsume
Re: 2.53 on DLINK CANADA?
Ok, so I have to live without DHCP, witch I am doing right now. I now have a new problem, Constant rebooting. Any ideas out there other then cooling the router? Tried going back to WEP but the reboots still happen. Very random but they subside in the evening and pick up again in the daytime.... Can it simply be cordless phone usage in my area??? I tried my own 2.4ghz cordless within a few fee of the router and no apparent reactions... What about that new 2.55 firmware?
Peter M |
|
Anonymous Coward
@rr.com
| reply to funchords
Re: DI-624 with fw 2.55????
Funchords:
I was getting ahead of myself there. It's not required by the standard, it's a deployment requirement.
802.1X is, as you certainly know, a security standard meant for larger networks. A network administrator should not be required to set static IP addresses on all the client machines to be able to use this router in a production environment.
Many companies have several access points and several subnets. Roaming between these subnets is impossible with static IP addresses. Additionally, DHCP lets admins transmit far more parameters than just an IP address, DNS server and default router to a client. Setting these things even for a small office (>15 machines) is a pain in the ass.
What just gets me with D-Link is that they keep missing the warning on their boxes: "Our products do not work properly with Broadcom and Intel wireless network devices. Be prepared to hack in a lot static IP addresses should you not choose to buy network equipment with our prefered chipset". The DI-624 is not their first device with DHCP problems. |
|
