Print

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

[Demonized]

I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?

PS: using FF3.6 Preview, in case you were wondering...

[Clancy]

So you saying fw 1.31na-1.32na beta works? But your shareport dose not? I'm confused.

LOL! Nothing like making yourself look stupid (and I'm referring to Moi). I was taking into consideration all of the other complaints I've been hearing after upgrading to the latest Betas. Shareport's reliability issues have become something that is now only in the back of my mind. I'm just watching and waiting and spending way too much time in these dang threads. I didn't buy my DIR-655 to host a NAS. If they ever get it to work, (for me, that is, because there are users that have NO problems with it) then I will consider it icing on the cake. D-Link does have a problem in that I think they put the cart well before the horse. This feature is advertised big time. Unfortunately, if every customer out there (besides us that frequent these boards) who bought it for this purpose and has NO problems with it, we will never know. Why would they ever visit here? So, Shareport to many people could be an unqualified success and we who visit these boards are but the inmates of the assylum who think the rest of the world is just as crazy as us.

After backtracking and reading YOUR posts, I see that you have only dealt with Shareport issues alone. So, I hope that I have un-confused you. If only someone would do the same for me.

[ceed]

I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?

PS: using FF3.6 Preview, in case you were wondering...

I have rebooted several times. Entered the settings manually instead of restoring a back-up. I've disabled and enabled stuff I do not use to see if something else affects port forwarding, and I've done both a sw and hw restet to factory defaults. I've bascally done what I would expect D-Link to do before they ship a fw update: Check that everything works!

I've compared two identical routers since I have two of them. The 1.2x one works flawlessly, the 1.3x one doesn't. I do not use Shareport or Secure Spot or anything fancy, just basic router functionality, so I can't tell if these new features work or not. I simply want 1.3x to work like 1.2x for basic router operation.

[jason1722x]

The 'problem' is not that simple. There are multiple situations where everything works fine. But there are also some situations in which one thing causes an issue, the other works, there are situations that have it vice versa and situations that have both issues. Still following me? 

So...it's very hard to distinguish here where one can speak of a hardware error or firmware issue or where there is some local config issue that has nothing to do with either hardware or firmware. That's the beauty of these forum 

Demonized it is that simple and I do follow you! Either it works or it dose not period.
So it's acceptable to have a flaky Router or Firmware which ever you choose to blame @ the time to work hafe the time?

[ceed]

I run 1.31 and port forwarding saves OK....honestly, I'm not joking here. You did do a reboot after filling in the data?

PS: using FF3.6 Preview, in case you were wondering...

Just a clarification: You say that port forwarding is working. Yes it is working. The problem is not that it isn't working but rather than the settings aren't stored so the router "forgets" it's port forwarding rules after a reboot.

[jason1722x]

LOL! Nothing like making yourself look stupid (and I'm referring to Moi). I was taking into consideration all of the other complaints I've been hearing after upgrading to the latest Betas. Shareport's reliability issues have become something that is now only in the back of my mind. I'm just watching and waiting and spending way too much time in these dang threads. I didn't buy my DIR-655 to host a NAS. If they ever get it to work, (for me, that is, because there are users that have NO problems with it) then I will consider it icing on the cake. D-Link does have a problem in that I think they put the cart well before the horse. This feature is advertised big time. Unfortunately, if every customer out there (besides us that frequent these boards) who bought it for this purpose and has NO problems with it, we will never know. Why would they ever visit here? So, Shareport to many people could be an unqualified success and we who visit these boards are but the inmates of the assylum who think the rest of the world is just as crazy as us.

After backtracking and reading YOUR posts, I see that you have only dealt with Shareport issues alone. So, I hope that I have un-confused you. If only someone would do the same for me.

lol...some of these threads and posts are weeks deep and old, they are all overlapping.
It's like that movie "Ground Hog Day".

[cs120]

Port forwarding is working for me on A2 FW 1.32NA, it wouldn't save if I used firefox to configure it tried it in IE and it saved went back to firefox and settings were saved go figure..

[Demonized]

Demonized it is that simple and I do follow you! Either it works or it dose not period.
So it's acceptable to have a flaky Router or Firmware which ever you choose to blame @ the time to work hafe the time?

Don't understand what you're trying to say here...

[jason1722x]

Demonized it is that simple and I do follow you! Either it works or it dose not period.

If the chipset of the router was designed to only do certain things and accept configurations that made sense in the programming of the firmware there would not be an issue no matter how complex the config was.

@ issue: Shareport, DNS Relay, portforwarding

[Demonized]

My best guess it is in the hardware (=>kernel SDK). Running A2 here and all three work like they should here (and i don't run a minimalist config).

[ceed]

My best guess it is in the hardware (=>kernel SDK). Running A2 here and all three work like they should here (and i don't run a minimalist config).

I'm not sure I understand. Are you saying that some hw worked with hw 1.2x, but not with 1.3x, while some hw works with both 1.2x and 1.3x? If so, is there a way to see what hw version I have?

[Demonized]

That's what it looks like, yes.
The hardware version is displayed in the router setup GUI. Top right. And on the bottom of the router itself.

There are different components used in A1/A2 <=> A3 (switch) and A1/A2/A3 <=> wireless radio
The kernel for each version is the same and needs to work with all hardware. That can cause issues for one revision while not causing the issue on the other revision. And D-Link has a third party doing the coding (from Ubicom source to Dlink use), and if they do a c****y job....