Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Access Point 1240AG allowing multiple network traffic

Good afternoon, have a customer site that has some 1240AG Access Points throughout their facility. Each one's software version is 12.3(7)JA2. Each access point is assigned a static IP# of - I can access each via web browser using it's IP (ie ) and see it's configuration settings.

I also have a Windows server with two NICs, one has a 172.16.1.x IP# for hard wired connections and other has a IP# for wireless connections.

Each access point is wired to a standard non-cisco switch. No VLANs have been configured on APs. We are running static IP#s on all devices.

Problem is that the 1240AG(s) are allowing clients that have an IP# of 172.16.1.x access to the network resources, eventhough the access point is setup on a 10.16.0.x network without VLANs. Users were instructed to change their IP#s to the 10.16.0.x network whenever they wanted to use wireless, but most have not since they know they can jump on the 10.16.0x access points using their 172.16.1.x IP#.

I don't want any wireless clients access to AP(s) unless they are on the 10.16.0.x network. I want to force the users to use correct 10.16.0.x IP#s.

Any comments and suggestions appreciated.

Thank you.



Re: Access Point 1240AG allowing multiple network traffic

You can configure IP ACL on the access point to filter absed on ip address. Refer URL for doing it.

New Member

Re: Access Point 1240AG allowing multiple network traffic

Did you connect both server nics to the same switched network or isolate them ? The real question is how did you plan to route from 10.16.0.x to the 172.16.1.x network ? Are you routing through the server or do you have a layer 3 switch somewhere. If you put a switch or router with secondary IPs that would explain the problem. Isolate the 10.16 network and that should fix it.