The Graveyard - Products No Longer Supported > Beta Code!

Beta v2.08NAB01 Available

(1/5) > >>

FurryNutz:
Seems to only fix Shareport that got broke in v2.07NA:

ftp://ftp.dlink.com/Gateway/dir655_revB/Beta/DIR655B1_FW208NAB01Beta.zip


Let us know what your experiences are.

Again this is only Beta. Not guaranteed or supported officially.

FurryNutz:
I loaded this on my Rev B last night.

1. Seems to fix the Shareport issue as I was able to connect to my printer and print to it from my Mac Book OSX 10.6.

2. The IPv6 Route window still has the typographical errors.

3. I'm also noticing the following: After loading code and setting up the router for reservations, Wifi, NAT, turning off WPS and enabling multicast and setting a manual 1000Mb WAN port speed. I'm seeing constant activity on my network switch and device LAN LED indicators after saving all the settings and rebooting. I noticed this a few times while using v2.03 as well. Anyone else notice this? I don't see this behavior on my other routers. Seem to have some sort of impact on network performance too. This throwing an ARP scan for some reason or getting into some sort of odd state? Doing a Factory reset of the router clears this condition and normal network activity resumes. Only seems when I go to configure, save and reboot does this condition occur. I didn't get a chance to test with wireshark. I'll do another setup tonight and see how it goes.

4. Also noticed that the router would not clear previous settings after selecting Restore Factory Defaults using Safari on OSX 10.6 after coming back from the reboot.  :-\

Any feedback appreciated for this build.

nicknml:
I'm seeing constant activity on my network switch and device LAN LED indicators after saving all the settings and rebooting. I noticed this a few times while using v2.03 as well. Anyone else notice this?

Are you talking about the LEDs of connected lan ports flashing?  I've had this happen at times.  I decided to investigate it with tcpdump (a packet sniffer).  I found out that the router likes to send out ARP requests for all ip addresses in it's range even though most of the IP addresses aren't even leased out to client devices.


My DHCP rage is 192.168.18.100-192.168.18.199
Here is some output I've captured showing this:
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.199 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.198 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.197 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.196 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.195 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.194 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.193 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.192 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.191 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.190 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.189 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.188 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.187 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.186 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.185 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.184 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.183 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.182 tell 192.168.18.1, length 46
14:d6:4d:31:ff:82 > ff:ff:ff:ff:ff:ff, ARP, length 60: Request who-has 192.168.18.181 tell 192.168.18.1, length 46

FurryNutz:
Great feedback Nick,
Yes, after doing a factory reset, I don't get constant LED activity however after going in and doing some configuration and settings and rebooting and the router comes to ready, ALL LEDs with anything connected on wired connection starts to constantly blink. I did a syslog and saw the following repeatedly after the router connected to the ISP modem: mroute: pending queue full, dropping entries..

I also saw this a few times on v2.03. I was able to clear this behavior on v2.03 by doing a power cycle most of the time or I reloaded a good saved config file.

v2.08 seems to not want to work correctly. Internet and connectivity is ok however I presume this impacts performance.

I would go back to v2.03 for now.

I've made DLink aware of this.

nicknml:
I've also noticed when accessing the web interface by it's ipv6 link-local address, sometimes a page will fail to load, but I'm still trying to figure out if it's the router itself or my pc.

Navigation

[0] Message Index

[#] Next page

Go to full version