Print

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

[jdrom]

It's odd that so many of you guys are seeing this, we're not able to replicate the error. Has any of you tried reflashing the firmware?

I'll give that a shot today and manually configure everything again. I won't reload my current configuration.

I don't really use UPnP so I can't comment there, I just cannot keep any of my port forwarding and virtual server settings after the router reboots, but every single other setting stays.

UPDATE:
Well I opened up IE8 (Windows 7 RC), loaded the defaults on the router, then enabled Compatibility Mode in IE8. Then I logged back in and flashed the firmware again. Once it was done rebooting, logged in and restored defaults yet again. After it rebooted, then I went ahead and configured all my settings (didn't load them). Now all seems to be working fine.

Previously I had updated the firmware using Firefox 3.5 Beta 4, no idea if using IE8 in compatibility mode helped or not but might as well detail what I did precisely.

EDIT: Spoke too soon I guess. Just logged in and everything was gone...

[jason1722x]

try "Use Unicasting", Ive noticed a drop in blocked ports.

[jdrom]

It's odd that so many of you guys are seeing this, we're not able to replicate the error. Has any of you tried reflashing the firmware?
Also that 30-30-30 "reset" you're doing will not have an effect on the 655, Ubicom products do not have a crash reset.

No other recommendations Lycan?

[jason1722x]

bump:

After taking a closer look @ my setup I have same issues as others with port forwarding. Torrent client and some web pages loading into right ports which explains the 404's for some web sites. I thought maybe DNS Relay was the issue but was wrong. Not sure if dropped packets on the wireless side can be blamed on this as well, just a thought.
 The other posts on this topic explain it all, port forwarding dose not work with 1.31NA. 1.21 had no problem.

[EddieZ]

Did you have a good look at your internet gateway device? Some need a restart to reconnect properly with an updated router.

[Xinot]

Here is log for my port forwarding setup attempt..

Mon 1.6.2009 20:42:31   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:42:33 2009 D-Link Systems DIR-655 System Log: Allowed configuration authentication by IP address 192.168.0.100
Mon 1.6.2009 20:43:12   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:14 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:12   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:14 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:13   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:15 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:21   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: Disconnect all stations
Mon 1.6.2009 20:43:21   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: The DHCP address xx.xxx.xxx.xxx is released by the user
Mon 1.6.2009 20:43:21   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:21   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:22 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:22   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:22   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Mon 1.6.2009 20:43:22   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:23 2009 D-Link Systems DIR-655 System Log: Requesting time from 207.232.83.70
Mon 1.6.2009 20:43:22   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:24 2009 D-Link Systems DIR-655 System Log: Time synchronized
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Warning<<<108>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: Wireless schedule init
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:27 2009 D-Link Systems DIR-655 System Log: Device initialized
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:28 2009 D-Link Systems DIR-655 System Log: LAN Ethernet Carrier Detected
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:28 2009 D-Link Systems DIR-655 System Log: LAN interface is up
Mon 1.6.2009 20:43:28   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:29 2009 D-Link Systems DIR-655 System Log: WAN interface cable has been connected
Mon 1.6.2009 20:43:29   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:29 2009 D-Link Systems DIR-655 System Log: Bringing up WAN using DHCP
Mon 1.6.2009 20:43:30   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:30 2009 D-Link Systems DIR-655 System Log: Obtained IP Address using DHCP. IP address is xx.xxx.xxx.xxx
Mon 1.6.2009 20:43:31   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:31 2009 D-Link Systems DIR-655 System Log: Estimating speed of WAN interface
Mon 1.6.2009 20:43:36   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:36 2009 D-Link Systems DIR-655 System Log: Starting DHCP server
Mon 1.6.2009 20:43:40   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:40 2009 D-Link Systems DIR-655 System Log: Wireless link is up
Mon 1.6.2009 20:43:48   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:49 2009 D-Link Systems DIR-655 System Log: WAN interface speed measurement completed.  Upstream speed is 2909 kbps
Mon 1.6.2009 20:43:52   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:53 2009 D-Link Systems DIR-655 System Log: Time server ntp1.dlink.com is at IP address 207.232.83.70
Mon 1.6.2009 20:43:52   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:53 2009 D-Link Systems DIR-655 System Log: Requesting time from 207.232.83.70
Mon 1.6.2009 20:43:52   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:54 2009 D-Link Systems DIR-655 System Log: Time synchronized
Mon 1.6.2009 20:43:53   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:54 2009 D-Link Systems DIR-655 System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Mon 1.6.2009 20:43:55   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:57 2009 D-Link Systems DIR-655 System Log: primary: Unlock AP setup
Mon 1.6.2009 20:43:55   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:57 2009 D-Link Systems DIR-655 System Log: guest: Unlock AP setup
Mon 1.6.2009 20:43:56   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:43:58 2009 D-Link Systems DIR-655 System Log: Stored configuration to non-volatile memory
Mon 1.6.2009 20:43:58   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:00 2009 D-Link Systems DIR-655 System Log: Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
Mon 1.6.2009 20:44:10   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:12 2009 D-Link Systems DIR-655 System Log: Allowed configuration authentication by IP address 192.168.0.100
Mon 1.6.2009 20:44:13   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 20:44:14 2009 D-Link Systems DIR-655 System Log: Log viewed by IP address 192.168.0.100

All log from router login, port forward rule make, save, boot and new router login. Port forwarding page is all empty again.

Re-flash done, and no go.

[Xinot]

Oh CMON D-link!
Enabled Securespot and BAM port forwarding works ok... My securespot test period has expired allready but i did get this annoying "last change to buy" window and didnt get to net before i choose to abandon this great promotion...

So, enabled securespot, save & boot, make port forward rule, save & reboot and there it is. Working and saved settings..

This is BS... 

edit: Can not add OR remove any port forwarding rules if securespot is not enabled...
When i make or remove rule with securespot theres this in log:

Mon 1.6.2009 21:41:42   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 21:41:44 2009 D-Link Systems DIR-655 System Log: Establishing connection w/ auth server: 165.193.49.40:443.
Mon 1.6.2009 21:41:43   : 192.168.0.1 >>LOGAUDIT.Info<<<110>Mon Jun 01 21:41:44 2009 D-Link Systems DIR-655 System Log: Local firewall edits sent successfully.

Hope this help

[Lycan]

Your unit needs to be replaced and the replacement needs to be tested.

Let me see what I can set up.

[Xinot]

Your unit needs to be replaced and the replacement needs to be tested.

Let me see what I can set up.

Easy to say, but not so easy to do...
So everyone who have this problem have broken router because of 1.3x f/w? I think we should wait if someone else try this out and then see what next. It seems to me that this router and securespot are little too married with each other... How can this be hardware problem?
btw. If i change this router, i should update new one to 1.3x too to see if theres everything ok?! Have to take securespot trial to use too and let it expire etc...
So maybe this "new router" is not nr1 solution for now?

[Lycan]

It has nothing to do with shareport. I want your unit so I can see it happen for myself.
Please understand that if this was a failure of the firmware as a whole then the entire community would be suffering.

Rather I beleive there is a factor thats causing select units to behave improperly and I need a failing unit to prove it.

I offer you an RMA with a replacement unit that I've tested myself.

[Xinot]

It has nothing to do with shareport. I want your unit so I can see it happen for myself.
Please understand that if this was a failure of the firmware as a whole then the entire community would be suffering.

Rather I beleive there is a factor thats causing select units to behave improperly and I need a failing unit to prove it.

I offer you an RMA with a replacement unit that I've tested myself.

Sure i can do that. Send you PM.

[Xinot]

I did some more testing and found that if i reset router to factory defaults, and do port forward rule with securespot enabled (default), and restore factory defaults after this again, it wont reset port forwarding at all. So this rules are saved to somewhere in securespot service, not in router? Securespot is have to use feature?

edit: disabled securespot and restored factory default after this but still didn't wipe out port forward rule...

[mgw]

You can add me to the list of people have trouble with Windows Home Server port forwarding and firmware 1.31 on the DIR-655. I will try disabling the upnp and manually setting the ports. I have tried to set the ports without disabling the upnp and the settings only hold for a few minutes. I too am glad I am not the only one with this problem.

[cmrivera]

Add me to that same list with WHS,firmware 1.31 and port forwarding not working. How long are we going to have to complain about this before something is done?

[stogs]

It seems as though we have not even passed the first step.....acknowledging that there is a problem.  All I have seen is that they (D-link), cannot recreate.  Have they tried with Windows Home Server?