Hi, I'm setting up RADIUS server to use with Wireless network 1) RADIUS server is Debian (eth0=192.168.25.254 (support all local computer, Access point) and eth1=192.168.2.45 (to Internet) 2) Access Point is LinkSys WAP54G (192.168.25.75) 3) Client is Dell Inspiron with Intel Broadcom wireless network card. My setting RADIUS server has 2 network cards. They are I started installing, ,setting, running ./radiusd -X with default configuration. Everything seems find. Server is running. ================================================================== On Server terminal, I test with radtest test test localhost 0 testing123 Debug message shows up: Sending Access-Request of id 102 to 127.0.0.1 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 rad_recv: Access-Request packet from host *192.168.2.45 *port 36272, id=102, length=56 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 then it ends with Sending Access-Accept of id 102 to* 192.168.2.45* port 36272 Framed-MTU = 1400 NAS-IP-Address = 192.168.25.77 NAS-Port = 15 Finished request 5. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Accept packet from host 192.168.2.45 port 1812, id=102, length=38 radclient: received response to request we did not send. (id=102 socket 3) Sending Access-Request of id 102 to 127.0.0.1 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 My question is why the Access-Accept is to 192.168.2.45 (It should be 192.168.25.254??) I also try to use RTRadPing Test Utility from local computer-WinXP SP3 ( 192.168.25.142) asking Authentication Request to 192.168.25.254 RTRadPing says no response from server, timeout. Seems like my ./radiusd runs on *192.168.2.45* ?? (eth1) ================================================================== On Server terminal, I try again with radtest test test 192.168.25.254 0 testing123 Sending Access-Request of id 162 to 192.168.25.254 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 rad_recv: Access-Request packet from host 192.168.25.254 port 36275, id=162, length=56 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 then it ends with Sending Access-Accept of id 162 to 192.168.25.254 port 36275 Framed-MTU = 1400 NAS-IP-Address = 192.168.25.77 NAS-Port = 15 Finished request 6. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Accept packet from host 192.168.25.254 port 1812, id=162, length=38 Framed-MTU = 1400 NAS-IP-Address = 192.168.25.77 NAS-Port = 15 ================================================================== Then, I kill ./radiusd start with ./radiusd -i 192.168.25.254 -p 1812 -X & (I start it in background mode, fix IP+Port) It ends with... radiusd: #### Opening IP addresses and Ports #### Listening on authentication address 192.168.25.254 port 1812 Listening on accounting address 192.168.25.254 port 1813 Listening on proxy address 192.168.25.254 port 1814 Ready to process requests. Seems like RADIUS is listening on 192.168.25.254..... :D ================================================================== On Server terminal, I test with radtest test test localhost 0 testing123 Sending Access-Request of id 103 to 127.0.0.1 port 1812 User-Name = "test" User-Password = "test" NAS-IP-Address = 127.0.1.1 NAS-Port = 0 *There is no response at all....* if I try with radtest test test 192.168.25.254 0 testing123 It ends with Sending Access-Accept of id 88 to 192.168.25.254 port 36277 Framed-MTU = 1400 NAS-IP-Address = 192.168.25.77 NAS-Port = 15 Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Accept packet from host 192.168.25.254 port 1812, id=88, length=38 Framed-MTU = 1400 NAS-IP-Address = 192.168.25.77 NAS-Port = 15 It replies!! Seems like it is listening at eth0 192.168.25.254 port 1812 BUT when I use RTRadPing Test Utility from local computer-WinXP SP3 ( 192.168.25.142) asking Authentication Request to 192.168.25.254 RTRadPing says no response from server, timeout. What should I do next?? Somebody can suggest me? I think this is just the first step, then I need to install OpenSSL and test....a long way to go.. Best regards, Pongsak