Whats your expirence using the 8.32.xxxx software release?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-27-2014 12:42 PM
I have started using the latest EWC software release (8.32.xxxx) in production environments to use the new 3715 access points. In two projects i have some issue using it:
The biggest problem is a complete freeze of some processes (C25 controller), including the internal dhcp server und resulting in an inaccessible web interface (timeout/hang after login screen). Just opened a case for GTAC.
Interested in other user expirence.
Regards
Hartmut
The biggest problem is a complete freeze of some processes (C25 controller), including the internal dhcp server und resulting in an inaccessible web interface (timeout/hang after login screen). Just opened a case for GTAC.
Interested in other user expirence.
Regards
Hartmut
12 REPLIES 12
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-12-2014 04:03 PM
Do you have any legacy access points (26xx or 4102) in your configuration or any access points that have not been updated to the 8.32.x image??
General rule...
Default action is the last rule on the rules list. All your traffic will hit the filter rules before hitting the default action. Couple of things to point out...
Access - In Policy Rules List ( Most Common)
Allow = Puts the traffic in the default topology defined in the WLAN service else apply the default topology defined in the Global Default Policy (most cases B@AP Untagged)
Contain to VLAN = Traffic goes in the VLAN ID selected
Deny = Traffic is dropped if you match this rule
If you do not have an end rule that says deny all traffic then the default action is hit. The same access rules above apply.
Ap's with older code or ap's that do not support these advance access methods in the Filter Rules List will default to supporting contain to VLAN as the default action. If the access is set to allow on the individual rule line then the traffic will be placed in the default actions contain to VLAN ID.
General rule...
Default action is the last rule on the rules list. All your traffic will hit the filter rules before hitting the default action. Couple of things to point out...
Access - In Policy Rules List ( Most Common)
Allow = Puts the traffic in the default topology defined in the WLAN service else apply the default topology defined in the Global Default Policy (most cases B@AP Untagged)
Contain to VLAN = Traffic goes in the VLAN ID selected
Deny = Traffic is dropped if you match this rule
If you do not have an end rule that says deny all traffic then the default action is hit. The same access rules above apply.
Ap's with older code or ap's that do not support these advance access methods in the Filter Rules List will default to supporting contain to VLAN as the default action. If the access is set to allow on the individual rule line then the traffic will be placed in the default actions contain to VLAN ID.
Doug Hyde
Director, Technical Support / Extreme Networks
Director, Technical Support / Extreme Networks
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-12-2014 04:03 PM
Might be useful so below a example that works for access control=deny, running 8.32.04.
In that case I'll allow only DHCP/DNS for the clients and also http/https traffic.
The last rule is important to allow the return/downlink traffic.
And also please make sure that you set the default topology in the WLAN service.
In that case I'll allow only DHCP/DNS for the clients and also http/https traffic.
The last rule is important to allow the return/downlink traffic.
And also please make sure that you set the default topology in the WLAN service.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-12-2014 04:03 PM
No. Open network. No captive portal.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-12-2014 04:03 PM
was that for a captive portal WLAN service?
what AP type did you use, legacy or only new ones?
what AP type did you use, legacy or only new ones?
