Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
docs:user-guide:wifi:wide.area.wifi [2018/02/20 21:13] – ↷ Page moved from docs:user-guide:advanced:wide.area.wifi to docs:user-guide:wifi:wide.area.wifi bobafetthotmaildocs:guide-user:network:wifi:wide.area.wifi [2021/07/24 05:44] (current) – [Wide area Wi-Fi coverage] someothertime
Line 1: Line 1:
 ====== Wide area Wi-Fi coverage ====== ====== Wide area Wi-Fi coverage ======
 +
 +{{section>meta:infobox:howto_links#config-network-device&noheader&nofooter&noeditbutton}}
  
 ===== Introduction ===== ===== Introduction =====
-This HOWTO requires proficienciy in an [[wp>OpenVPN]]-based [[wp>Virtual private network]] (cf. [[docs:user-guide:services:vpn.server.openvpn.tap]]/[[docs:user-guide:services:vpn.client.openvpn.tun]] and [[docs:user-guide:services:vpn.server.openvpn.tap]]/[[docs:user-guide:services:vpn.client.openvpn.tap]]), Networking configuration on [[wp>Red Hat Enterprise Linux|RHEL]]/[[wp>CentOS]], [[wp>Shorewall]] (cf. [[docs:user-guide:services:shorewall-on-openwrt]]).+This HOWTO requires proficienciy in an [[wp>OpenVPN]]-based [[wp>Virtual private network]] (cf. [[docs:guide-user:services:vpn:openvpn:server.tap]]/[[docs:guide-user:services:vpn:openvpn:client.tun]] and [[docs:guide-user:services:vpn:openvpn:server.tap]]/[[docs:guide-user:services:vpn:openvpn:client.tap]]), Networking configuration on [[wp>Red Hat Enterprise Linux|RHEL]]/[[wp>CentOS]], [[wp>Shorewall]] (cf. [[docs:guide-user:firewall:shorewall:shorewall-on-openwrt]]).
  
 In the proposed scenario a big area must be covered with Wi-Fi access and no Access Point alone can provide that kind of reachability. Three different Wi-Fi networks are configured for different access levels. Traffic from these networks will be isolated and controlled by a central Linux box running Shorewall. A wired Ethernet backbone will carry traffic from the Access Points (three in our example). The encapsulation protocol for different network traffic will be OpenVPN with no cypher(encryption can be enabled  with one liner 'cypher' statement if required). The author has successfully done a similar setup using 802.1q (VLAN) encapsulation. L2tp is a another reasonable alternative for traffic encapsulation (cf. [[docs:guide-developer:networking:network.interfaces]]). In the proposed scenario a big area must be covered with Wi-Fi access and no Access Point alone can provide that kind of reachability. Three different Wi-Fi networks are configured for different access levels. Traffic from these networks will be isolated and controlled by a central Linux box running Shorewall. A wired Ethernet backbone will carry traffic from the Access Points (three in our example). The encapsulation protocol for different network traffic will be OpenVPN with no cypher(encryption can be enabled  with one liner 'cypher' statement if required). The author has successfully done a similar setup using 802.1q (VLAN) encapsulation. L2tp is a another reasonable alternative for traffic encapsulation (cf. [[docs:guide-developer:networking:network.interfaces]]).
Line 67: Line 69:
         option type 'mac80211'         option type 'mac80211'
         option macaddr '54:e6:fc:fb:a7:10'         option macaddr '54:e6:fc:fb:a7:10'
-        option hwmode '11ng'+        option hwmode '11g'
         option htmode 'HT20'         option htmode 'HT20'
         list ht_capab 'SHORT-GI-40'         list ht_capab 'SHORT-GI-40'
  • Last modified: 2021/07/24 05:44
  • by someothertime