Giz, that doesn't help. Infact, it's completey counter-productive and most likely a complete waste of time. Allow me to explain why...
I use an SMC barricade as my inet boundary router, and I have a Linksys WRT54G (what the GL replaces) running Sveasoft connected via LAN ports to the SMC. An Identical setup to what Ghosty here has. At first, it didn't work worth shit.
For some reason the damn Linksys won't forward DHCP requests (All broadcasts???) out its LAN ports to the SMC that is the DHCPD. So while I can get associated via the WiFi, and plug directly into a LAN port, the whole thing is useless.
So much for your advice eh? :p
However, I have no way of knowning if this is the same issue affecting ghost because when he asked me in IRC it went somethign like this:
23:39 <@Ghost> well, uh
23:40 <@Ghost> i'm about 800 miles away from said router :x
23:40 so what's the questin here then?
23:40 wpa or somethign else?
23:41 <@Ghost> i have two
23:41 <@Ghost> one, why doing what I did with the D-link to make it so only the
ISDN router is doing NAT
23:41 <@Ghost> doesn't work with the belkin
23:41 what kind of cable?
23:41 better be a cross running from the cisco to the belkin...
23:42 <@Ghost> yes
23:42 can the belkin ping the cisco?
23:42 <@Ghost> heh, no clue
23:43 <@Ghost> i suppose that doesn't help
That's not complete, but you get the idea.
Anyways, Ghost, if this turns out to be your issue I put a workaround in place of dividing the available addresses up in half and creating two DHCP pools with half in each. One DHCPD on the SMC, and one on the Linksys.