| Now.WAP Radius Configuration |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hello, I am testing the Now.WAP, I have a cisco 2600 as Access Server. Mi problem is that I don't know how the Now.WAP assign IP Address to incoming connections. Thanks a lot. | |||
| Kent Williams Moderator Username: Kent Post Number: 54 Registered: 10-2003 |
Normally, the access server has the ability to assign its own IP addresses, even if the RADIUS server does not allocate one. However, if your access server requires that the RADIUS server assign IP addresses (and I am not sure if the Cisco 2600 requires this), there is a way to configure Now.WAP to do this. You need to manually edit WAPGW.INI, and define the IP address of each of your access servers. Then for each access server, define the pool of IP addresses that can be assigned through that access server. Each access server gets its own section in WAPGW.INI, like this: [RadiusNASIP-192.168.1.1] AddressPool1=192.168.1.2-200 AddressPool2=192.168.2.1-5 The above defines the available IP addresses to be allocated to clients that connect via the NAS at 192.168.1.1. Now.WAP will allocate IP addresses from the two pools of 192.168.1.2 thru 192.168.1.200 (e.g., 192.168.1.2, 192.168.1.3, 192.168.1.4, etc.) and 192.168.2.1 thru 192.168.2.5. RADIUS configurations can be difficult to initially setup. I would advise enabling the debug log for this setup. Under the [WAPGW] section header in WAPGW.INI, add Debug=Yes. In that log, you'll be able to verify that Now.WAP is parsing the address pools for the NAS correctly ... and you can see the RADIUS requests and responses. If you have any questions, just post the relevant entries from the WAPDEBUG.LOG file. -- Kent Williams Now Wireless Support | |||
