cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1999
Views
5
Helpful
3
Replies

P2P Printing While P2P Blocking Using Flexconnect

proddy1
Visitor

I am working on a WLAN solution on a Flexconnect 7510 WLC using local switching. This WLAN has the P2P Blocking action set to "Drop" due to company policy. There is a need to allow printing between two devices on the same WLAN. With the current P2P configuration, printing is failing as expected. The company will not allow P2P; therefore, I am looking for an ACL solution that would allow printing to occur without allowing P2P on the WLAN.

The WLC User Guide notes:

"Cisco controller with central switching clients supports peer-to-peer blocking for clients associated with
different APs. However, this solution targets only clients connected to the same AP. FlexConnect ACLs
can be used as a workaround for this limitation."

So my question: Is it possible to continue having the policy configured to "drop", and exclude the two devices so that only the two devices can print? If so, will you provide a useful link that I can reference, or an example of what the ACL would look like? There are other devices on the WLAN.

1 Accepted Solution

Accepted Solutions

Rich R
VIP
VIP

Central switching - WLC blocks all p2p even between clients on different APs
Flex local switching - AP only blocks p2p between clients on the same AP.  It cannot block p2p between clients on different APs so that must be done with ACL or on the switch network.  That's literally the opposite of what you're wanting to do.  So the limitation is inability to block between APs, the workaround is to use an ACL instead to do the blocking.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/wlan_security.html#peer-to-peer-blocking
If you connect the printer to the LAN then the wireless clients won't be blocked from talking to the printer at all - they can still talk to the printer because that is not wireless p2p.

 

------------------------------
Please click Helpful if this post helped you and Accept as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390

View solution in original post

3 Replies 3

Rich R
VIP
VIP

Central switching - WLC blocks all p2p even between clients on different APs
Flex local switching - AP only blocks p2p between clients on the same AP.  It cannot block p2p between clients on different APs so that must be done with ACL or on the switch network.  That's literally the opposite of what you're wanting to do.  So the limitation is inability to block between APs, the workaround is to use an ACL instead to do the blocking.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/wlan_security.html#peer-to-peer-blocking
If you connect the printer to the LAN then the wireless clients won't be blocked from talking to the printer at all - they can still talk to the printer because that is not wireless p2p.

 

------------------------------
Please click Helpful if this post helped you and Accept as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390

Thank you for the response. The feedback has been helpful. After considering the available options, we decided to move the wireless printer to a separate SSID, which I thought might create the same effect as placing it on the LAN, however, that didn't work and after viewing the document, I understood why.

As a follow up to my original question, can I create a specific VLAN and/or SSID that allows peer-to-peer connectivity and ensure it won't change other SSID/VLAN security controls?

Review Cisco Networking for a $25 gift card