<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic mesh point with WLAN on radio1 in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54455#M3457</link>
    <description>Hello all,&lt;BR /&gt;
Our regulation is not allows using of 5Ghz outdoor.&lt;BR /&gt;
Sometimes we need to deploy outdoor AP's with mesh point and WLAN on 2.4Ghz only.&lt;BR /&gt;
But as we see is working not so stable as we need - meshpoint links refreshed every several hours even if there is excellent signal and signal quality/noise level.&lt;BR /&gt;
&lt;BR /&gt;
Please recommend some special recommendations for setting up mesh point with WLAN together  on radio1.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
&lt;BR /&gt;
Aviv&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Sun, 03 Sep 2017 23:41:00 GMT</pubDate>
    <dc:creator>Aviv_Kedem</dc:creator>
    <dc:date>2017-09-03T23:41:00Z</dc:date>
    <item>
      <title>mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54455#M3457</link>
      <description>Hello all,&lt;BR /&gt;
Our regulation is not allows using of 5Ghz outdoor.&lt;BR /&gt;
Sometimes we need to deploy outdoor AP's with mesh point and WLAN on 2.4Ghz only.&lt;BR /&gt;
But as we see is working not so stable as we need - meshpoint links refreshed every several hours even if there is excellent signal and signal quality/noise level.&lt;BR /&gt;
&lt;BR /&gt;
Please recommend some special recommendations for setting up mesh point with WLAN together  on radio1.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
&lt;BR /&gt;
Aviv&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Sun, 03 Sep 2017 23:41:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54455#M3457</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2017-09-03T23:41:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54456#M3458</link>
      <description>Aviv, it's not clear what AP platform or what release you are running. And not clear what you have configured so it's hard to help you without that info.</description>
      <pubDate>Wed, 06 Sep 2017 22:40:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54456#M3458</guid>
      <dc:creator>Alona</dc:creator>
      <dc:date>2017-09-06T22:40:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54457#M3459</link>
      <description>Hello Alona,&lt;BR /&gt;
There is the root AP conf example:&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;&lt;BR /&gt;
&lt;/BLOCKQUOTE&gt;!&lt;BR /&gt;
! Configuration of AP7131 version 5.8.4.0-034R&lt;BR /&gt;
!&lt;BR /&gt;
!&lt;BR /&gt;
version 2.5&lt;BR /&gt;
!&lt;BR /&gt;
!&lt;BR /&gt;
client-identity-group default&lt;BR /&gt;
 load default-fingerprints&lt;BR /&gt;
!&lt;BR /&gt;
ip access-list BROADCAST-MULTICAST-CONTROL&lt;BR /&gt;
 permit tcp any any rule-precedence 10 rule-description "permit all TCP traffic"&lt;BR /&gt;
 permit udp any eq 67 any eq dhcpc rule-precedence 11 rule-description "permit DHCP replies"&lt;BR /&gt;
 deny udp any range 137 138 any range 137 138 rule-precedence 20 rule-description "deny windows netbios"&lt;BR /&gt;
 deny ip any 224.0.0.0/4 rule-precedence 21 rule-description "deny IP multicast"&lt;BR /&gt;
 deny ip any host 255.255.255.255 rule-precedence 22 rule-description "deny IP local broadcast"&lt;BR /&gt;
 permit ip any any rule-precedence 100 rule-description "permit all IP traffic"&lt;BR /&gt;
!&lt;BR /&gt;
mac access-list PERMIT-ARP-AND-IPv4&lt;BR /&gt;
 permit any any type ip rule-precedence 10 rule-description "permit all IPv4 traffic"&lt;BR /&gt;
 permit any any type arp rule-precedence 20 rule-description "permit all ARP traffic"&lt;BR /&gt;
!&lt;BR /&gt;
ip snmp-access-list default&lt;BR /&gt;
 permit any&lt;BR /&gt;
!&lt;BR /&gt;
firewall-policy default&lt;BR /&gt;
 no ip dos smurf&lt;BR /&gt;
 no ip dos twinge&lt;BR /&gt;
 no ip dos invalid-protocol&lt;BR /&gt;
 no ip dos router-advt&lt;BR /&gt;
 no ip dos router-solicit&lt;BR /&gt;
 no ip dos option-route&lt;BR /&gt;
 no ip dos ascend&lt;BR /&gt;
 no ip dos chargen&lt;BR /&gt;
 no ip dos fraggle&lt;BR /&gt;
 no ip dos snork&lt;BR /&gt;
 no ip dos ftp-bounce&lt;BR /&gt;
 no ip dos tcp-intercept&lt;BR /&gt;
 no ip dos broadcast-multicast-icmp&lt;BR /&gt;
 no ip dos land&lt;BR /&gt;
 no ip dos tcp-xmas-scan&lt;BR /&gt;
 no ip dos tcp-null-scan&lt;BR /&gt;
 no ip dos winnuke&lt;BR /&gt;
 no ip dos tcp-fin-scan&lt;BR /&gt;
 no ip dos udp-short-hdr&lt;BR /&gt;
 no ip dos tcp-post-syn&lt;BR /&gt;
 no ip dos tcphdrfrag&lt;BR /&gt;
 no ip dos ip-ttl-zero&lt;BR /&gt;
 no ip dos ipspoof&lt;BR /&gt;
 no ip dos tcp-bad-sequence&lt;BR /&gt;
 no ip dos tcp-sequence-past-window&lt;BR /&gt;
 no ip-mac conflict&lt;BR /&gt;
 no ip-mac routing conflict&lt;BR /&gt;
 dhcp-offer-convert&lt;BR /&gt;
 no stateful-packet-inspection-l2&lt;BR /&gt;
!&lt;BR /&gt;
!&lt;BR /&gt;
mint-policy global-default&lt;BR /&gt;
!&lt;BR /&gt;
meshpoint-qos-policy default&lt;BR /&gt;
!&lt;BR /&gt;
wlan-qos-policy default&lt;BR /&gt;
 qos trust dscp&lt;BR /&gt;
 qos trust wmm&lt;BR /&gt;
!&lt;BR /&gt;
radio-qos-policy default&lt;BR /&gt;
!&lt;BR /&gt;
wlan TEST&lt;BR /&gt;
 ssid TEST&lt;BR /&gt;
 vlan 1&lt;BR /&gt;
 bridging-mode local&lt;BR /&gt;
 encryption-type tkip-ccmp&lt;BR /&gt;
 authentication-type none&lt;BR /&gt;
 no broadcast-ssid&lt;BR /&gt;
 no answer-broadcast-probes&lt;BR /&gt;
 wpa-wpa2 psk 0 XXXXXXXXXX&lt;BR /&gt;
 use ip-access-list out BROADCAST-MULTICAST-CONTROL&lt;BR /&gt;
 use mac-access-list out PERMIT-ARP-AND-IPv4&lt;BR /&gt;
 shutdown on-primary-port-link-loss&lt;BR /&gt;
!&lt;BR /&gt;
meshpoint mesh1&lt;BR /&gt;
 meshid mesh1&lt;BR /&gt;
 beacon-format mesh-point&lt;BR /&gt;
 control-vlan 1&lt;BR /&gt;
 allowed-vlans 1&lt;BR /&gt;
 security-mode psk&lt;BR /&gt;
 wpa2 psk 0 XXXXXXXXXX&lt;BR /&gt;
 root&lt;BR /&gt;
!&lt;BR /&gt;
!&lt;BR /&gt;
management-policy default&lt;BR /&gt;
 telnet&lt;BR /&gt;
 no http server&lt;BR /&gt;
 https server&lt;BR /&gt;
 ssh&lt;BR /&gt;
 user admin password 1 82728d2cd05b08c2855b163cb0484fed7237a89c0691557d43b5a6c77e68b4fd role superuser access all&lt;BR /&gt;
 no snmp-server manager v3&lt;BR /&gt;
 snmp-server community 0 private rw&lt;BR /&gt;
 snmp-server community 0 public ro&lt;BR /&gt;
 snmp-server user snmptrap v3 encrypted des auth md5 0 admin123&lt;BR /&gt;
 snmp-server user snmpmanager v3 encrypted des auth md5 0 admin123&lt;BR /&gt;
!&lt;BR /&gt;
l2tpv3 policy default&lt;BR /&gt;
!&lt;BR /&gt;
profile ap71xx default-ap71xx&lt;BR /&gt;
 autoinstall configuration&lt;BR /&gt;
 autoinstall firmware&lt;BR /&gt;
 crypto ikev1 policy ikev1-default&lt;BR /&gt;
  isakmp-proposal default encryption aes-256 group 2 hash sha&lt;BR /&gt;
 crypto ikev2 policy ikev2-default&lt;BR /&gt;
  isakmp-proposal default encryption aes-256 group 2 hash sha&lt;BR /&gt;
 crypto ipsec transform-set default esp-aes-256 esp-sha-hmac&lt;BR /&gt;
 crypto ikev1 remote-vpn&lt;BR /&gt;
 crypto ikev2 remote-vpn&lt;BR /&gt;
 crypto auto-ipsec-secure&lt;BR /&gt;
 crypto remote-vpn-client&lt;BR /&gt;
 interface radio1&lt;BR /&gt;
 interface radio2&lt;BR /&gt;
 interface radio3&lt;BR /&gt;
 interface ge1&lt;BR /&gt;
 interface ge2&lt;BR /&gt;
 interface vlan1&lt;BR /&gt;
  ip address dhcp&lt;BR /&gt;
  ip address zeroconf secondary&lt;BR /&gt;
  ip dhcp client request options all&lt;BR /&gt;
 interface wwan1&lt;BR /&gt;
 interface pppoe1&lt;BR /&gt;
 use firewall-policy default&lt;BR /&gt;
 use client-identity-group default&lt;BR /&gt;
 logging on&lt;BR /&gt;
 service pm sys-restart&lt;BR /&gt;
!&lt;BR /&gt;
rf-domain default&lt;BR /&gt;
 timezone Etc/GMT+2&lt;BR /&gt;
 country-code il&lt;BR /&gt;
!&lt;BR /&gt;
ap71xx XX-XX-XX-XX-XX-XX&lt;BR /&gt;
 radio-count 2&lt;BR /&gt;
 use profile default-ap71xx&lt;BR /&gt;
 use rf-domain default&lt;BR /&gt;
 hostname AP2-root&lt;BR /&gt;
 license AP VIRTUAL_CONTROLLER_DEFAULT_AP_LICENSE&lt;BR /&gt;
 no adoption-site&lt;BR /&gt;
 ip default-gateway 172.XX.XX.254&lt;BR /&gt;
 interface radio1&lt;BR /&gt;
  wlan TEST bss 1 primary&lt;BR /&gt;
  meshpoint mesh1 bss 2&lt;BR /&gt;
 interface radio2&lt;BR /&gt;
 interface vlan1&lt;BR /&gt;
  ip address 172.XX.XX.202/24&lt;BR /&gt;
  ip address zeroconf secondary&lt;BR /&gt;
 no logging console&lt;BR /&gt;
 meshpoint-device mesh1&lt;BR /&gt;
  monitor primary-port-link action no-root&lt;BR /&gt;
 service meshpoint loop-prevention-port ge1&lt;BR /&gt;
!&lt;BR /&gt;
!&lt;BR /&gt;
end&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
On the other side is the non root AP.&lt;BR /&gt;
Can you point me what may improve the stability of the mint links?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
&lt;BR /&gt;
Aviv&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Sep 2017 19:30:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54457#M3459</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2017-09-07T19:30:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54458#M3460</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
Any suggestions?&lt;BR /&gt;
&lt;BR /&gt;
Thanks&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Oct 2017 11:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54458#M3460</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2017-10-02T11:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54459#M3461</link>
      <description>Add following under radio 1:&lt;BR /&gt;
no dynamic-chain-selection&lt;BR /&gt;
rate-selection opportunistic&lt;BR /&gt;
non-unicast tx-rate lowest-basic&lt;BR /&gt;
&lt;BR /&gt;
You need to do this for both root and non-root. I assume this is 7131n . What antenna are you using? What gain? Distance between the APs? Why not 7161? AP 7131 went out of engineering support at this point. &lt;BR /&gt;
&lt;BR /&gt;
Alona</description>
      <pubDate>Tue, 03 Oct 2017 04:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54459#M3461</guid>
      <dc:creator>Alona</dc:creator>
      <dc:date>2017-10-03T04:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54460#M3462</link>
      <description>Hi Alona,&lt;BR /&gt;
We used AP7131int because we don't have AP7161 because of regulation problems (IL)&lt;BR /&gt;
&lt;BR /&gt;
Thank you for your support.&lt;BR /&gt;
&lt;BR /&gt;
Aviv&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Oct 2017 04:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54460#M3462</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2017-10-03T04:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54461#M3463</link>
      <description>Hi Aviv,&lt;BR /&gt;
&lt;BR /&gt;
From what I see you have channel at default (smt).  When a meshpoint is mapped to a radio with smt set, which is the default, then mesh auto channel scan is enabled (smart-rf is not used when a meshpoint is mapped to a radio).  By default, mesh auto channel will re-evaluate channel conditions every 30 minutes (channel hold time which is configured under meshpoint-device) e.g.&lt;BR /&gt;
      acs channel-hold-time 2.4GHz&lt;BR /&gt;
&lt;BR /&gt;
Set this value to zero (0) to prevent the periodic re-evaluation.&lt;BR /&gt;
&lt;BR /&gt;
When mesh auto channel is used, the channel list that is used is actually configured under the rf-domain.  If nothing is defined then all channels will be scanned.  Perhaps this is what you are seeing.  &lt;BR /&gt;
&lt;BR /&gt;
Also note, that you are using the default path method uniform which means path selection is metric based.  Signal level is only one of many components that determine a path or path change.  What do the metrics look like.  Try these useful commands:&lt;BR /&gt;
&lt;BR /&gt;
show wireless meshpoint neighbor statistics rf&lt;BR /&gt;
show wireless meshpoint neighbor detail&lt;BR /&gt;
show wireless meshpoint path detail&lt;BR /&gt;
more system:/proc/dataplane/wireless/radio/radio1-proximity &lt;BR /&gt;
&lt;BR /&gt;
To be sure you can enable debugging to see what the meshpoint is doing. With logging enabled, go to the cli and type "debug wireless meshpoint level debug".  Wait for a change to occur and send me a tech dump.&lt;BR /&gt;
&lt;BR /&gt;
Also, you do have CRM configured. I would also check the logs to see if there have been any CRM events.&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Dan</description>
      <pubDate>Tue, 03 Oct 2017 18:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54461#M3463</guid>
      <dc:creator>Daniel_DiLuzio</dc:creator>
      <dc:date>2017-10-03T18:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54462#M3464</link>
      <description>Hi Aviv,&lt;BR /&gt;
&lt;BR /&gt;
Correction, I did not mean CRM but primary-port-link.  You may want to check and see if there have been any issues with interface going up and down causing a conversion.&lt;BR /&gt;
&lt;BR /&gt;
Thank you,&lt;BR /&gt;
&lt;BR /&gt;
Dan</description>
      <pubDate>Tue, 03 Oct 2017 18:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54462#M3464</guid>
      <dc:creator>Daniel_DiLuzio</dc:creator>
      <dc:date>2017-10-03T18:21:00Z</dc:date>
    </item>
    <item>
      <title>RE: mesh point with WLAN on radio1</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54463#M3465</link>
      <description>Hi Daniel,&lt;BR /&gt;
I talking about something global and not a specific issue, but thank you.&lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
&lt;BR /&gt;
Aviv&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Oct 2017 18:21:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/mesh-point-with-wlan-on-radio1/m-p/54463#M3465</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2017-10-03T18:21:00Z</dc:date>
    </item>
  </channel>
</rss>

