[onhel]

I have DD-WRT running on a Alix 2c2 board strictly as a access point. No WAN, just a LAN wire to the Alix.

Previously I had DD-WRT running on a Buffalo WHR-HP-G54 and all connections from a wireless client showed the IP address of the wireless client, not the access point.

Now I have a router that I have assigned to only accept connections from certain LAN IP's. This worked great with the Buffalo AP, but now with the ALIX AP, all wireless connections are showing up to come from the ALIX IP and not the actual wireless client IP.

For example:
Router 192.168.1.1
ALIX Access Point w/DD-WRT 192.168.1.3
Laptop 192.168.1.7

Connecting from the laptop to the Router shows up under Syslog as coming from 192.168.1.3 instead of 192.168.1.7. With the Buffalo I had previously all connections from laptop showed up as coming from laptop so what am I doing wrong now?

How do I get DD-WRT to forward wireless clients IP to connections. Right now I think by default at installation eth0 eth1 and ath0 are bridged. Any attempt to remove bridge blocks me from connecting to DD-WRT and forces me to physdiskwrite a new CF card and start fresh. Any thoughts? Thanks in advance.

[Sash]

hmmm

do you have the latest rc 6.2 installed?
btw its goot to update the board to the latest bios. there are problems with mpci cards in older bios rev.

[onhel]

Thanks for replying Sash.

I already had the latest Alix BIOS. Upgraded to 6.2 from RC5. Now I get this in my syslogs when I try to connect

Feb 17 05:23:46 kernel: hostapd[5744]: segfault at 00000004 eip 0804fb7d esp bfa0e100 error 4<000>

I'll go back to rc5

[Sash]

hmm..did you reset to factory defaults after the update?

on my alix erverything is working afaik. im useing it as ap-only, too

[onhel]

Yes I reset to factory defaults like you recommended and still same problem. I'm using WPA2 Enterprise with an external Zeroshell RADIUS Server and DD is causing it to fail authentication.

Reverting back to RC5 solves that error problem and the RADIUS server works fine with it. Something is broken between RC5 and 6.2 in regards to RADIUS authentication.

RC5 works great although I still have my original problem of all connections from any wireless client is showing as coming from the IP of the DD-WRT access point.

[Sash]

did you start a bug report in the bugtracker for the radius problem?

for your other problem i dont see a solution jet. maybe its a bug, too.

[onhel]

Submitted both problems as separate bugs. Hopefully will be resolved soon. Thanks for help Sash, I'll keep this thread updated with any changes.

[onhel]

Both of the above issues I see as resolved now with v24 SP1.