Yep... lots of problems here also... (BTW.. I'm not a novice at this... 11 years @ Cisco developing SW for routers, now developing SW for Routers at Juniper Networks..)
First upgraded to 1.65. now...
1. Unit, even in dedicated Router mode (DHCP and NAT server), FAILS to connect to my upstream Comcast cable modem... Even after the CM has been left OFF, forcing a new Comcast DHCP session, Buffalo will only 1 out of 10 times actually successfully negotiate a WAN DHCP connection.
2. Unit will not serve up DHCP addresses to clients, even AFTER the unit has successfully established a connection to the CM. Sometimes it serves up a foreign address which is NOT in the range of the DHCP configuration. And this is NOT the Windows PC APIPA or "alternate address". Of course, the unit will NOT pass traffic to the WAN side.
3. Even if manually configured with static IP address, DNS servers, and gateway, clients will not get traffic through to the WAN.
After each configuration step router was allowed to reset and in many cases, after allowing the config to be taken, I power-cycled the router for a clean boot... This did NOT help. All the problems continued.
Cmmon, Buffalo... What the heck is up with this?
I'll wait for a couple days to see if they respond with a committment to ack these issues and come up with a firmware fix. Otherwise I'll return it and give it a very negative review on my networking blog.
Otherwise, I would caution everyone to steer clear of this router.
-Andrew