D-Link Forums
The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Beta Code! => Topic started by: EddieZ on September 22, 2008, 02:54:26 PM
-
Before flashing, are there any comments on the new beta?
-
I'm running it at home, so far so good.
-
Lycan, can you please post a download link for the SharePort Network Utility software? We need it for using the new NAS function on the 1.21 firmware.
-
NAS functionality...great to hear. Is it USB based (guess not looking at the forumposts about more USB functionality)?
Any news on LAN/WAN/wireless speed?
-
I don't have access to the software yet guys. Sorry. Even if I did I've yet to test it and I'm not about to post code I haven't tested personally. Ru-Fi-Oh and I will be sharing the load as primary testers for this code push.
-
Yes, it is USB based. Now the DIR-655's USB port can work as Network USB and 3G USB Adapter, as well as the WCN function.
This firmware is working great as of now. I noticed a stronger wireless signal with my MacBook, although when I was testing it with VoIP, it sometimes dropped the connection for a second or two.
I would like to try the NAS function, but I can't find the necessary software for accessing the network devices. It seems to be included in the DIR-825's software CD only, as I couldn't find it anywhere else. Looking at Lycan's reply as I was writing this post, I guess we will have to wait a few days for the software to be released. Anyway, thank you for your support Lycan.
-
Thanks, we'll be awaiting Holy Beta Release patiently ;)
-
Before flashing, are there any comments on the new beta?
The printing is much better... Still not perfect (slower than 1.11) but usable!
Erik.
-
New features are appreciated but can we fix the issues caused by the new firmware? Callers still cannot hear my wife when she uses her Altigen phone for telecommuting.
-
Well here we are with yet more releases that when you turn UPnP off, the device still responds to and is browseable via UPnP. Please make sure the developers are aware of this problem. OFF = the service/port is off not just disabled modifications.
Regards,
BSPvette
-
Upgraded to 1.21 05 earlier this afternoon, all is well so far. Seems a bit better than the 1.21 that was pulled yesterday and replaced with 04 and 05 last night.
As far as the new internet security feature, there is an option and I simply disabled it.
I've seen additions of DynamicDNS, Guest Zone, and USB, which are all nice additions.
-
I don't have access to the software yet guys. Sorry. Even if I did I've yet to test it and I'm not about to post code I haven't tested personally. Ru-Fi-Oh and I will be sharing the load as primary testers for this code push.
I couldnt care less about the software ;D however, can you tell us what protocol does this thing uses for communication.. ? trying to acess it from a non-windows system... 8)
-
I couldnt care less about the software ;D however, can you tell us what protocol does this thing uses for communication.. ? trying to acess it from a non-windows system... 8)
NFS, SMB/CIFS (probably not, does not need a seperate app), NDAS, AFP, rsync (try tcp port 873)/Unison seem to be the most logical options. Although they might come up with their own protocol (non-tcpip like NDAS)...
And unless plugging in a device opens a port, there are no open TCP ports besides the standard ports.
Let's make it a guessing game ;D
Update: do not publish if you find out please. :-X
-
Nope.
Its under lock and key, and if someone manages to find out keep it to yourself. I will remove posts about reverse engineering of the Shareport.
-
Lycan, will this network usb utility have future releases which include Mac OS and Linux compatibility? I also have computers with this OS's running on my network, aside from the Windows PC's.
-
Currently I don't know. I'll ask.
-
Currently I don't know. I'll ask.
Thanks, if d-link is using undocumented, proprietary protocols in order to lock-in customers, at the very least I expect to have working software for multiple OS's.
While I'm certainly able to try reverse engineer this stuff 8) I have neither the time nor the patience to do so :'( .. it is cheaper to buy a device from a vendor that uses documented,reliable,standard protocols instead.. man-hours are expensive ya know ;)
-
While I'm certainly able to try reverse engineer this stuff 8) I have neither the time nor the patience to do so :'(
Same here :)
The name 'SharePort' got me thinking... perhaps the utility uses port 80 or any of the other three open ports on the router. This is possible, i've seen it with joint SSH and https use of port 443, which are internally redirected to other ports (which are closed to the outside world). Reference: http://old.homeip.net/martin/ssh-https.html.
Lycan, just guessing here but PM if this is the right mindset ;)
-
Again guys the Shareport at least our version of it is under lock and key currently. When I get the green light to divulge information, TRUST ME. I will. I promise. I want you guys to enjoy the product. I'm not trying to keep things from you, I'm simply doing what I've been asked to do for the time being.
It's temporary I'm sure and once I have a beta verison of the client we can work on this together.
-
Again guys the Shareport at least our version of it is under lock and key currently. When I get the green light to divulge information, TRUST ME. I will. I promise. I want you guys to enjoy the product. I'm not trying to keep things from you, I'm simply doing what I've been asked to do for the time being.
It's temporary I'm sure and once I have a beta verison of the client we can work on this together.
Don't sweat it, Lycan. Just teasing you a bit ;D
I am conviced everyone here is just impatient to get their hands on the new toys. At least I am.
-
The printing is much better... Still not perfect (slower than 1.11) but usable!
Erik.
But for use a printer or Network USB option, users will need to install the Network USB Utility into their computers to share the USB device through the router..... ??? But where is this software
Thank
-
If you look at the post for the Beta firmware, it clearly states that the Client Software is unavailable currently.
As soon as I get the green light to release it I will.
-
Hi, after updated to 1.21; I have several computers linked on the LAN, faster ones are OK (wired and wireless); a slower win2K machine (wireless connection) has problem opening web page. ("page not found" error)
If I go back to 1.11 then everything is good. Tried 1.20, same problem.
Best,
Steve
-
Hi, after updated to 1.21; I have several computers linked on the LAN, faster ones are OK (wired and wireless); a slower win2K machine (wireless connection) has problem opening web page. ("page not found" error)
If I go back to 1.11 then everything is good. Tried 1.20, same problem.
Best,
Steve
Did you import and check the router settings for the Win2000 wireless interface (or DNS settings on the PC)? It seems kind of odd that this particular machine suffers from the router firmware and others don't...
-
Whats the make of the WiFi adapter in the win2k machine?
-
Hi, all: Thanks for the reply.
The card is made by airlink101, 54g.
In fact I have two wlans in my house. This pc linked to an AP (also airlink made), then connect the AP to DIR-655 via ethernet. Other PCs I have is one gbit connected directly to DIR655 and one laptop wireless connect to DIR-655; both PCs are running WinXP
The win2K machine, when it failed I can see IP/DNS address already assigned; but pinging DNS server failed.
LAN access is OK. Currently I have already flashed back to 1.11; tonight I may try to flash again to get more info.
A side note, I moved the WinXP machine to the airlink WLAN it still OK; so it's not AP. I also have a wii
connect to airlink WLAN and it's fine, too. Tried a smart phone (windows mobile) on airlink WLAN, failed similar to win2k machine. If I use 1.11, all these tests are good.
Cheers
Steve
-
Query: Does this work on EU routers or does the router blow up :P
Query2: Any problems with save/load configuration on a transfer from 1.11 (i really have a lot of rules set, wouldn't want to loose them)
Thanks
-
I have had no issues restoring a config file after an upgrade and I have been using all the betas that have come out over the past year.
-
Query: Does this work on EU routers or does the router blow up :P
Query2: Any problems with save/load configuration on a transfer from 1.11 (i really have a lot of rules set, wouldn't want to loose them)
Thanks
+1
-
DMZ still broken for my VoIP :(
1.21b05
as in the router blocks packets to my VoIP that is in the DMZ zone
-
Not that I doubt you, but are you sure a. the modem behind the router (or your local firewall) isn't blocking VOIP or b. does it work when you configure the needed ports manually (portforwarding or virtual server)?
-
ok, took the plunge
problem,saved firmware on 1.11eu, tried to load it with 1.21, invalid config :-\ $#@#$@#@$ (curses...). ow well, guess it's time to rebuild....
problem 2, these devices
ssid 001DE064B587 192.168.0.103 802.11n (2.4GHz) 130 86
ssid 00195B109E46 192.168.0.100 802.11n (2.4GHz) 54 76
basically the 192.168.0.103 is a laptop on a table with a n card (ok 130 is normal, and perfect), .100 is a dwa 142 in a pc, and it's on the table as well - so same distance, (it's ina pc), with it i'm getting very low rates, 13,27,54... (the device itself, in windows says 270-300), problem is this one:
ssid 001B11705EF7 192.168.0.101 802.11n (2.4GHz) 65 56
an identical 142, placed at maybe 15 meters away,through a concrete wall (between the first two and the outer, there's like 5 meters and no walls)
wlan to wlan speed transfer speed (for those) is about half of what i usually see
also, i can't see the gateway connection in network connections under xp anymore :(
i reflashed 1.11, speed is back now, but the gateway connection is still missing ???
-
One thing I noticed about 1.21b05 is that every second it sends a UDP broadcast to 239.255.0.1. Each broadcast increments it source ports by one. I've watched it increment its source port from port 4100 thru 4120 before stopping the sniffer trace. After I saw this behavior, I reloaded 1.20. 1.20 does not send these broadcasts. I don't have any multicast or uPNP options enabled. This is odd behavior. Does anyone know why it is doing these UPD broadcasts to 239.255.0.1?
--
Xavier
-
OK, last night I was able to flash back 1.21 to test my DNS saga... :)
I found this option "Enable DNS Relay" under (set up-->network setting) makes a difference in my case.
It is default to enable in my case. For some reason, with DNS Relay is enabled the routing is not stable. It started with the win2K PC trying to access web and failed; after that other PC's access to same address will get incorrect routing. I disable this option; so far so good.
I did a trace route for both pass and fail case: note the IP address is resolved correctly for the website (70.42.142.20); but routing has some issue after 3rd hop.
(ok)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
1 10 ms 9 ms 10 ms bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
2 8 ms 8 ms 8 ms 64.164.107.1
3 8 ms 8 ms 8 ms 69.220.8.95
4 10 ms 9 ms 10 ms 69.220.8.31
5 17 ms 11 ms 12 ms ve318.fr4.sjc.llnw.net [208.111.152.117]
6 13 ms 12 ms 12 ms linkedin.ge3-4.fr4.sjc.llnw.net [208.111.152.102]
7 13 ms 14 ms 15 ms www.linkedin.com [70.42.142.20]
(fail)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
1 11 ms 11 ms 11 ms bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
2 10 ms 9 ms 10 ms 64.164.107.2
3 8 ms 9 ms 8 ms 151.164.93.239
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
....
My hardware version is A3; when DNS Relay is enabled, all PCs' DNS server point to 192.168.0.1; when disabled, DNS server point back to ISP.
Best,
Steve
-
OK, last night I was able to flash back 1.21 to test my DNS saga... :)
I found this option "Enable DNS Relay" under (set up-->network setting) makes a difference in my case.
It is default to enable in my case. For some reason, with DNS Relay is enabled the routing is not stable. It started with the win2K PC trying to access web and failed; after that other PC's access to same address will get incorrect routing. I disable this option; so far so good.
I did a trace route for both pass and fail case: note the IP address is resolved correctly for the website (70.42.142.20); but routing has some issue after 3rd hop.
(ok)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
1 10 ms 9 ms 10 ms bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
2 8 ms 8 ms 8 ms 64.164.107.1
3 8 ms 8 ms 8 ms 69.220.8.95
4 10 ms 9 ms 10 ms 69.220.8.31
5 17 ms 11 ms 12 ms ve318.fr4.sjc.llnw.net [208.111.152.117]
6 13 ms 12 ms 12 ms linkedin.ge3-4.fr4.sjc.llnw.net [208.111.152.102]
7 13 ms 14 ms 15 ms www.linkedin.com [70.42.142.20]
(fail)
Tracing route to www.linkedin.com [70.42.142.20]
over a maximum of 30 hops:
1 11 ms 11 ms 11 ms bras24-l0.pltnca.sbcglobal.net [151.164.184.91]
2 10 ms 9 ms 10 ms 64.164.107.2
3 8 ms 9 ms 8 ms 151.164.93.239
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
....
My hardware version is A3; when DNS Relay is enabled, all PCs' DNS server point to 192.168.0.1; when disabled, DNS server point back to ISP.
Best,
Steve
To my knowledge, when DNS Relay is disabled, the DNS does notpoint back to the provider... In that case you need a visible DNS server on the LAN to do DNS queries. At least that's what the Help item says...
-
One thing I noticed about 1.21b05 is that every second it sends a UDP broadcast to 239.255.0.1. Each broadcast increments it source ports by one. I've watched it increment its source port from port 4100 thru 4120 before stopping the sniffer trace. After I saw this behavior, I reloaded 1.20. 1.20 does not send these broadcasts. I don't have any multicast or uPNP options enabled. This is odd behavior. Does anyone know why it is doing these UPD broadcasts to 239.255.0.1?
--
Xavier
Probably you may want to check this out:
http://www.faqs.org/rfcs/rfc2365.html
Multicast...Hmmm.
-
Probably you may want to check this out:
http://www.faqs.org/rfcs/rfc2365.html
Multicast...Hmmm.
Okay, I just read the document you referenced entitled RFC2365 - Administratively Scoped IP Multicast. Now what? You didn't and it doesn't answer my question. And yes, it is a multicast. What was your point? My point is that it wasn't doing this in v1.20 and I wanted to know why it was implemented and what exactly is it doing.
-
you might want to try OpenDNS instead of your ISPs
http://www.opendns.com/
-
Well, i'm glad that dlink is listening to it's customers and make better use of the usb port.
there are a couple other features I'd like to see which i've emailed them about, one really useful thing would be to remove the SSID name in the wireless connection status page and replace it with the computetr name so it would be easier to determin which computer is having rate/signal issues, rather than having the inconvenience to navigate away from the page to try and find which computer it is.
As for the securespot addition, it's a welcomed feature, though I most likely won't have any use for it other than the anti-virus feature. One question does come to mind though is where that 30 dollars a year is going and what is it being used for. The only updates I can see to come from the software is the definition updates. However, i suppose 30.00 a year is adequate, and i'm sure there are a lot of people that would use all the features.
The transfer rate does seem to be slower than the norm for the storage feature, which could be attributed to one or both of the following: USB port is 1.1 and the router or the shareport software could be limiting the bandwidth through some throttling or QOS method. I tested several large files, rar, zip, exe, iso, mkv, ts, avi etc, and performace was all the same. A couple instances, I did see a huge increase in performance at about 58MB per second using a maxtor onetouch usb drive, but furthar testing made me suspect that the speed was due to windows write caching, thinking that the entire file had already been transfered, when in fact it wasn't. This could potentially cause a problem if the usb drive isn't unmounted after the transfer has really completed, leading to data curruption, if one were to remove the drive or if another user took over the session.
For those wondering how it interfaces, it indead would need to be using a TCP method since wireless devices would need to access the device as well.
After the upgrade, I did have to hard reset the router to successfully apply the saved configuration settings. (hard resets are always recommended) and had to reboot the gateway because for some reason the PPOE connection wasn't being established.
Noticed that after making a change, for example, to port forwarding, the router would seem like it reboots, but when it returns to the screen my PPOE connection doesnt connect anymore. I press reboot router on system screen and it still doesnt connect. I Have to manually pull the power cord our of the router.
Minor set backs, but overall thumbs up for dlinks move to push this routers use to a new level.
-
btw, the software uses port 20005 to communicate as determined by
netstat -b
TCP 192.168.0.3:21176 192.168.0.1:20005 ESTABLISHED
attempts at ftp, tftp, ssh etc, disconnects the session, disconnects the drive, disables the software, then it re-enables.
I imagine it's using some proprietary connection.
-
Shared printing is still broken. It was broken in 1.20 as well, but not in 1.11 or 1.11_MSBETA.
Symptoms: Attempting to print or open printer properties takes a long time (several minutes or more). Word will freeze on launch for a period of time if the default printer is experiencing this problem.
Operating system: Vista x64 for sure, may affect other OSs
Steps to reproduce: Have a shared printer on a computer running Windows Vista. Install this printer as a network printer, either using the add printer wizard or by typing the UNC path of the computer (i.e. \\COMPUTER) into Explorer and double-clicking on the printer on another computer running Windows Vista. Attempt to print, or view the printer properties. Either dialog box will take several minutes to appear. Several minutes pass before printing begins once the "print" button in the dialog box is clicked. File sharing with the same computers works fine. Reverting to firmwares older than 1.20 work fine.
Please fix this! I like the new features that are being added, but I can't use them, becaues I have to use older firmware merely to be able to print.
-
Shared printing is still broken. It was broken in 1.20 as well, but not in 1.11 or 1.11_MSBETA.
Symptoms: Attempting to print or open printer properties takes a long time (several minutes or more). Word will freeze on launch for a period of time if the default printer is experiencing this problem.
Operating system: Vista x64 for sure, may affect other OSs
Steps to reproduce: Have a shared printer on a computer running Windows Vista. Install this printer as a network printer, either using the add printer wizard or by typing the UNC path of the computer (i.e. \\COMPUTER) into Explorer and double-clicking on the printer on another computer running Windows Vista. Attempt to print, or view the printer properties. Either dialog box will take several minutes to appear. Several minutes pass before printing begins once the "print" button in the dialog box is clicked. File sharing with the same computers works fine. Reverting to firmwares older than 1.20 work fine.
Please fix this! I like the new features that are being added, but I can't use them, becaues I have to use older firmware merely to be able to print.
I have no problems printing (1.20, 1.21). Just can't reproduce...No delays or whatever...I use Vista x86, maybe that's the issue?
-
Nope-serious issues here with shared printing also-running 2 machines with Vista Ultimate x86. Have an HP 8180 all-in-one connected to the desktop x86 Vista machine via usb and cat5'ed to the router. When I try and print any Office docs from my laptop running x86, I get the same thing as the above poster. Hangs Office-not acceptable performance at all. Back to 1.11. Lycan, you guys need to look into this as this issue is present in 1.20 and now continues in the beta 1.21B05 :'(
-
Perhaps you can give a list of all your settings so the Dlink guys can reproduce the issue (use the .gws).
-
Hi
I still have an issue with creating schedule. Weird but I cannot create schedule when it goes through the 2 AM and end time is less then 10 AM.
For example,
cannot create schedules
1:0 AM - 8 : 0 AM
2:0 AM - 4 : 0 AM
but I can create
1:0 AM - 2:AM
3:0AM - any time
Most interesting that I can create schedule 1 AM - 2:46AM but cannot create 1 AM - (any time after 2:46 AM)
Weird that 2:46 AM - 2:47 AM is a point of error
Thanks
-
I've never had a problem with shared printing and everything works just as it should. And now with the new features of the usb port, I don't need to have, or turn on a computer just to print.
So far, using the utility to print with the printer hooked up to the dir655, everything still works like a charm. Now, I have not tried printing out large files, but standard documents print out fine without any delay that other people have been reporting. I'm using an HP 3100 series all in one printer.
A really nice feature as well that i've noticed is that I don't have to connect the printer using the utility as one would have to when sharing a usb drive. I just hit print in whatever program, and it prints automatically as if it where already connected. great stuff. :)
One thing I would like to see, if at all possible is that the utility will automatically release the printer once the print job is done so that other computers which may have jobs queued can automatically start the print job
-
Perhaps you can give a list of all your settings so the Dlink guys can reproduce the issue (use the .gws).
Settings are pretty much standard, out of the box stuff. Dir-655 Rev A2 with all defaults except named my own sid, use a pretty long TKIP/AES WPA2 only key, mixed g/n and channel width set to 20 because of an Intel 4965. Something is awry in the code if I can use 1.11 with no problems but not 1.20 and newer.
BTW, what program would you use to open a proprietary DLink gateway settings file (.gws)? :o
-
BTW, what program would you use to open a proprietary DLink gateway settings file (.gws)? :o
Haven't got a clue. But would like to find out... :-\
-
there is no program to open the file. It's to be loaded back to the router.
-
Lycan,
Any ideas why some of us are seeing unacceptable lan printing performance with the newest code? Would love to use it but can't :(
-
Lycan,
Any ideas why some of us are seeing unacceptable lan printing performance with the newest code? Would love to use it but can't :(
My name's not Lycan, but the issues seems very random. My two Vista stations don't suffer from it, tried with two brands of printers. The might achieve to replicate the issue in their lab, otherwise they might need more input on the configs or NIC's used?
-
FYI.... LYCAN is our DLink provided Moderator and tie-in to their tech support team..... This forum would be useless without his intervention in-house !!!
SD1
-
Is he? Wow...
How stupid do you think I am? :'(
-
simply because you responded to Alemaker's post to Lycan by saying you weren't Lycan....
whatever
-
My thoughts:
Status->Statistics:
menus seems somehow...misaligned (IE, labels aren't clearly related to any of the numbers floating around below them)
Tools->System Check:
It'd seem more logical to name that menu "ping test" since that what it calls itself when you select it. But that's probably just me...
Advanced->Port Forwarding (and other menus like it)
Seems to enjoy asking me if I want to save settings, even though I haven't even selected any particular box/changed anything at all. (the other menus with lots of input boxes/menus do the same...sometimes)
Advanced->Guest Zone
Menu isn't grayed out when wireless is completely disabled (it should be, because if wireless radio is off, how can I setup a guest zone?!) Though I'm sure that's not a priority, since most people probably bought the router FOR the wireless...not because it worked out to be the cheapest with a gigabit switch. :S
As far as actual functionality goes, DNS relay seems to work but the router *STILL* seems to confuse mdns broadcast clients in some way I haven't quite been able to track down. But ~mostly~ usable now, only when a client "fails" to get detected by the other mdns machines does it become problematic (in that it itself will be unable to resolve any *.local names for a few hours, and others can't see it, though sometimes other machines can resolve the troubled one's name, but not the other way around.
Its a little weird, and really hard to trigger the situation intentionally. BUT I can say that if I put my old DI-604 back in as my gateway, it works without a problem, so, either the DIR-655 is "right" and breaks stuff, or the DI-604 is broken and lets everything work when it shouldn't.
On a note related to the DI-604, its DHCP server (as screwed up as it was) would give the same address to my macs weather they were on wireless (I use a WRT54G for wireless not the 655 due to placement) or wired, this allowed them (somehow) to switch media types without interrupting any open connections, it was REALLY nice. But I'm sure that it was actually the DI-604's brokenness (or something in the verizon firmware).
-
My thoughts:
Status->Statistics:
menus seems somehow...misaligned (IE, labels aren't clearly related to any of the numbers floating around below them)
Thta's an IE issue you have...not the router
Tools->System Check:
It'd seem more logical to name that menu "ping test" since that what it calls itself when you select it. But that's probably just me...
Semantics...
Advanced->Port Forwarding (and other menus like it)
Seems to enjoy asking me if I want to save settings, even though I haven't even selected any particular box/changed anything at all. (the other menus with lots of input boxes/menus do the same...sometimes)
Advanced->Guest Zone
Menu isn't grayed out when wireless is completely disabled (it should be, because if wireless radio is off, how can I setup a guest zone?!) Though I'm sure that's not a priority, since most people probably bought the router FOR the wireless...not because it worked out to be the cheapest with a gigabit switch. :S
Greyed out? It gives you the opportunity to configure while wireless is not yet active. Could be a useful situation. Most of the time the limitation of this is considered a nuisance...
As far as actual functionality goes, DNS relay seems to work but the router *STILL* seems to confuse mdns broadcast clients in some way I haven't quite been able to track down. But ~mostly~ usable now, only when a client "fails" to get detected by the other mdns machines does it become problematic (in that it itself will be unable to resolve any *.local names for a few hours, and others can't see it, though sometimes other machines can resolve the troubled one's name, but not the other way around.
Could you elaborate some more about this mdns issue? Trying to establish whether it is a DIR655- or 'just' your local Mac issue....
Its a little weird, and really hard to trigger the situation intentionally. BUT I can say that if I put my old DI-604 back in as my gateway, it works without a problem, so, either the DIR-655 is "right" and breaks stuff, or the DI-604 is broken and lets everything work when it shouldn't.
Try the new 1.21 beta...
On a note related to the DI-604, its DHCP server (as screwed up as it was) would give the same address to my macs weather they were on wireless (I use a WRT54G for wireless not the 655 due to placement) or wired, this allowed them (somehow) to switch media types without interrupting any open connections, it was REALLY nice. But I'm sure that it was actually the DI-604's brokenness (or something in the verizon firmware).
[/quote]
-
Greyed out? It gives you the opportunity to configure while wireless is not yet active. Could be a useful situation. Most of the time the limitation of this is considered a nuisance...
'Cept the other wireless menus are grayed out, Guest zone being the only one that's not, so it seems like its more of an oversight, not a feature.
Try the new 1.21 beta...
Unless there's been a second beta release since I posted, I already am running the latest.
As far as the mdns goes, its not easy to predict the failures, or intentionally reproduce them, but a typcal solution (that seems SOMEWHAT reliable) is to pull the network cable from the mac with troubles, and reconnect it (this forces OSX to re-fresh its DNS caches, and rebroadcast all mdns stuff), then usually it works again. The same trick is less effective on the linux machines running avahi (usually they just get confused more).
I'm fairly confident it isn't the macs or linux machines configurations, since if I swap out the DIR-655 as the DHCP server/gateway for ANY other router I have (DI-604,BEFSR41,WRT54G), mdns works as it should.
There's two possibilities I can come up with based on the behavior of the failures (and what I've managed to put together about how mdns works). The first is that the DIR-655's handling of DNS requests is still not quite right, since it seems that mdns does DNS lookups on the name its trying to resolve before doing the multicast part (or looking in its multicast cache, I'm not sure which). But I suspect that sometimes the router just doesn't respond to the requests, and then OSX times out and everything breaks (I suspect it then poisons the mdns cache, since it caches that its a bad value, and since the machine doesn't re announce itself until mdns gets restarted, the computer doesn't rebroadcast for a significant amount of time). The other possibility is that the router is doing something horrible to multicast traffic, since mdns doesn't work AT ALL unless 'Enable Multicast Streams' is enabled. But I don't know enough about the internal functionality of avahi/apple mdns stuff to really tack down the source of the problem, And I haven't been able to find a tool to tell me where in the lookup process the failure occurred. I should also note, that the problems are only really bad with OSX 10.4/10.5, 10.3 seems to be somehow immune to the problems entirely (possibly because 10.3 has a much more primitive broadcast-oriented implementation of mdns but again, I can't really be sure).