Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FurryNutz]

Probably due to the fact that NA and EU and WW have different people and projects managing them and there are differences between them all and testing the code, so there is probably going to be differences in release times and schedule. Many things factor in to releasing code. It realistically can't be all done at once. Maybe in a perfect universe. 

[BengtB]

In my universe when you make a hardware product you have different teams:
Hardware
Software onboard (firmware)
Software on computer
Sales
Support

To have different teams that does the same thing, but in different ways sounds totaly wrong in every aspect (except for sales, that want to segment the market in different ways).

The DIR-655 B1 has not been working properly since it release 1 1/2 year ago.

If the business I'm working in would have behaved in the same way, our products would be dead.
Because our customers have more relation to each other, and if something is not working as expected the rumor is around.

But D-Link is in another situation. Maybe 80% of their customers haven't done any research about the product before they buy it.
I owned a DI-624+ that lasted for seven years I think. And it worked from day one. Thats pretty good for a consumer product.
Thats why I bought another product from D-Link.

It does not feel so nice to be a testpilot for over a year (so far).

/Bengt

[FurryNutz]

Well, since we are in the D-Link universe then I guess we have to deal with there ways and there business practices. Were all beta testers in some form. We can only help each other out as best we can and gain a good experience as much as possible.

My B1 has been working great for me.

[Mark_KF8RV]

Any response from the D-Link firmware guys and gals?

[FurryNutz]

They are aware of it.

[Mark_KF8RV]

Do any of the latest firmware releases (after 2.00NA) have changes in the PPPoE IPv4 performance?  I don't know if that protocol changes or if it's set in stone.  I use PPPoE and DSL Bridge.  Performance sometimes stinks but then that's DSL in a lot ways since it's not cable.  I'm just thinking that perhaps I should give 2.03NA a whirl.     

[TomatoKetchup]

After switching back and forth between 2.03 and 2.07 I noticed Dynamic Fragmentation (QoS) is on by default in 2.07.  I've also noticed there are some spelling errors present in both firmwares.  






I've also noticed the log is a bit different in 2.07.  It seems to show less than it previously did even though I have all the check boxes checked.  My main reason for posting though is this, I get this constantly from my macbook when using 2.07.  Doesn't happen when I use 2.03, at least it's not showing in the logs.  Same settings.

Mar 19 16:13:26     info     [  852.390000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3
Mar 19 16:13:26     info     [  852.390000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3
Mar 19 16:13:10     info     [  836.410000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3

EDIT: Also 2.07 allows you to save your changes without rebooting.   Which is a huge plus if you're changing a lot of settings.  

[nicknml]

After switching back and forth between 2.03 and 2.07 I noticed Dynamic Fragmentation (QoS) is on by default in 2.07.  I've also noticed there are some spelling errors present in both firmwares.  





I've also noticed the log is a bit different in 2.07.  It seems to show less than it previously did even though I have all the check boxes checked.  My main reason for posting though is this, I get this constantly from my macbook when using 2.07.  Doesn't happen when I use 2.03, at least it's not showing in the logs.  Same settings.

Mar 19 16:13:26     info     [  852.390000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3
Mar 19 16:13:26     info     [  852.390000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3
Mar 19 16:13:10     info     [  836.410000] '[DROPPED-PACKET]:'IN= OUT=br0 SRC=192.168.0.1 DST=192.168.0.100 PROTO=ICMP TYPE=3 CODE=3

EDIT: Also 2.07 allows you to save your changes without rebooting.   Which is a huge plus if you're changing a lot of settings.  

Why is there IPv4 routes in your IPv6 routing table?  I have the same firmware loaded 2.07NA, and that isn't happening to me.

[FurryNutz]

Possibly those are separate screen captures?

[TomatoKetchup]

Possibly those are separate screen captures?

This is correct, sorry, I should have separated them better.

[nicknml]

This is correct, sorry, I should have separated them better.

Gotcha.

[Mark_KF8RV]

I'm anxious for a stable fireware release (tried, true, and tested firmware) for my DIR-655.

I'm using 2.00NA.  I thought of trying the DIR-825 but at present I don't need for it in any way.  I'd like to always continue the use of my existing DIR-655.  It's an outstanding single-band router with a lot of potential provided its onboard resources can continue to handle the load of any updated firmware without bogging down the performance of the router.  The DIR-655's signal is strong and reliable.  The 5GHz band is intriguing but not practical for me because of what the signal has to traverse through between the router and my computer.  The DIR-655 is ideal, in other words; therefore, I'll continue to use it and I will be o' so pleased if it continues to be supported by D-Link. 

Mark KF8RV.


 

[FurryNutz]

V2.03 is a good and stable version. If your not using IPv6 then v2.00 is good aswell.

[Mark_KF8RV]

For the time being, I'll stick with 2.00NA.

I'm not sure whether Charter supports IPv6.  I'm not even sure if my Motorola SB6121 supports it.  I don't know what to think of IPv6 at this time.

Mark.

[FurryNutz]

All SB 6 Series modems support IPv6.
If your ISP doesn't support IPv6 in your area then theres nothing to worry about. Enjoy what you have man.