I'm also using DD-WRT and Titan, no problems whatsoever.

Can those who are running without issue confirm if they are using Mixed mode or Only G mode for the AP's.

This is the cause of the problem which i am having with my DDWRT router and i think the same that everyone who is having a problem here is facing.

It simply cannot even see the router when it is set to mixed N/G mode.
The bug link is https://bugs.maemo.org/show_bug.cgi?id=10893.

Unfortunately the person who raised it simply closed it because he changed to openwrt instead of following up to close it for ddwrt.

The issue could be ddwrt's fault as to how it implements signalling for moxed mode or how N900 reads it.

The network I'm having trouble with is set to B/G/N mode (that's what I infer from "Mixed." It lists Mixed, B-Only, G-Only, BG-Mixed, NG-Mixed, and N-only.)

I doubt there's anything older than a G adapter connected though (typically a bunch of recent Blackberries and iPhones, laptops with G or newer adapters, and my N900) so it could be operating in NG mode, but the Wireless status just shows "Mixed."

Allright sounds like its the same issue.
You wont have the problem if you set it to G only mode.

I have edited my post above with the bug in maemo.org.

If you have additional info, please do raise a new one to check if maemo is the cause of the issue. If not we can bug ddwrt instead.

I have no problem connecting to the same network in the same mode when using the stock kernel, only the power kernel, so the bug is either in the power kernel or DD-WRT (although DD-WRT is looking more likely now).

My specific settings on the router:

Router: Buffalo WHR-HP-AG108
Firmware: DD-WRT v24-sp2 (10/10/09) std - build 13064

This router has 2 network interfaces (one is A, one is B/G). I will skip listing the settings for the A interface since N900 does not have 802.11a and is irrelevant here.

The second interface is the B/G antenna and here are my settings:

Regulatory Domain - UNITED_STATES
TX Power - 20 dBm
Antenna Gain - 0 dBi
Wireless Mode - AP
Wireless Network Mode - Mixed
Noise Immunity - Auto
Noise Immunity Level - 4
OFDM Weak Detection - Enable
Protection Mode - None
RTS Threshold - Disable
Transmission Minimum Rate - Auto
Transmission Maximum Rate - Auto
Short Preamble - Disable
Extended Range - Disable
Super G Fast Framing - Disable
Outdoor Band - Disable
Channel Width - Full (20 MHz)
Diversity - Disable
TX Antenna - Primary
RX Antenna - Primary
AP Isolation - Disable
WMM Support - Disable
Wireless Network Name (SSID) - whatever
Radar Detection - Disable
Wireless Channel - Auto
Wireless SSID Broadcast - Enable
ScanList - default
Sensitivity Range (ACK Timing) - 2000
Max Associated Clients - 256
MTik Compatibility - Disable
Network Configuration - Bridged



In the Wireless Security section, this interface is set up as:
Security Mode - WPA2-Personal
WPA Algorithms - AES
WPA Shared Key - secret
Key Renewal Interval (in seconds) - 3600


WDS is disabled. MAC filter is disabled.

I am using DNSMasq (enabled on Services page) and on the main Setup page I have "Use DNSMasq for DHCP", "Use DNSMasq for DNS" and "DHCP-Authoritative" all enabled.

Hope that helps.

I am having similar issue and I think it is Maemo issue as I am able to connect to the WIFI (DD-WRT, NG-MIXED, WPa2-PSK) when booted with NITDroid and not with Maemo. To fix the issue I had to set my router to G-Only for now while I find a fix for it.

Here is my setup
N900 connected when
Router : - DIR-615 C1 on DD-WRT build dt 8/12/2010 with G-Only and WPA2-PSK setting.

N900 connected when booted with NITDriod
Router : - DIR-615 C1 on DD-WRT build dt 8/12/2010 with NG-Mixed and WPA2-PSK setting.

N900 not connected when booted with Power40 Kernel and
Router : - DIR-615 C1 on DD-WRT build dt 8/12/2010 with NG-mixed and WPA2-PSK setting.

I see wl1251 down or link not ready error in dmesg. I don't know if there is any firmware realted to wl1251 chip that is used in NITdriod that can be ported into Maemo5 to fix this issue.

Thanks for doing research, please comment the corresponding bug is NOT resolved. Glad I'm not the only one.

This is more or less my stance
http://www.schneier.com/blog/archive...n_wireles.html

Hmm I was just going to reflash my home DIR-615 C1 to DD-WRT, maybe I better wait...