RUCKUS Community Forums are now in READ-ONLY mode while we migrate to a new platform.
You will still be able to read posts and knowledge articles, but will be unable to post new content until Go Live on the new platform Monday August 17.
Lennar Smart Home customers: please contact [email protected] for assistance during the week of August 9-17.
07-07-2015 11:41 AM
07-07-2015 02:05 PM
Hi Mark,
I updated a knowledge base article, that will appear on Support after the next every 6hr update period.
https://support.ruckuswireless.com/answers/000001391
Root Cause:
The reason for this issue is that wireless printers do not do webauth. On a Guest WLAN the clients are redirected before they are allowed access, even when there is no authentication on the WLAN there is a redirect that happens. Hence printers will not be able to authenticate and connect successfully.
Workaround:
Create a WLAN with WPA-PSK or Open type authentication, and connect the printer or other non HTTP capable guest resource.
Resolution:
Use a Non-Webauth WLAN on the Guest Access VLAN for non-webauth capable guest resources.
1. Create a Standard WLAN with WPA PSK,
2. Connect the printer on this WLAN.
- Most printers will work with open and WPA enabled WLAN's.
- WPA2/AES combination is prefered if the printer/device supports it.
For the above scenario, if the Guest user's are placed on a VLAN, then we can allow them to
access the printer by creating a Standard WLAN (with/without auth), tagged with the same
VLAN as the Guest user's.
After connecting the printer to this WLAN on the same VLAN, the Guest user's will be able to
access the printer/other resource.
If a customer wants Full Client Isolation enabled on the Guest WLAN, they will have to allow
the printer's IP address under Restricted Subnets (eg: 192.168.2.25/32 - this /32 host address
allows only this single IP) to permit/allow the Guests access to the device.
10-09-2017 12:02 AM
10-11-2018 11:22 PM
09-28-2019 12:58 AM
