Virtual LANs (VLANs) By design, Network Hosts connected to the same Local Network topology, whether by means of an Access Point or Switch, can pass traffic back-and-forth transparently. Often, a flat, transparent network topology can be undesirable, especially if Users with Different Access Privileges, such as Guests & Admins, send and receive data on the same LAN. By contrast, Virtual LANs, or VLANs for short, logically divide a local network topology in order to isolate traffic to separate broadcast domains. Conceptually, deploying two different LANs is the same as configuring two different VLANs on the same hardware. However, VLANs consolidate hardware, like in “Router-on-a-stick” topologies. In this example, three Hosts connected to the same Switch can reach each other via Broadcast. However, once assigned a VLAN, Hosts can only broadcast to other Hosts in the same VLAN. InterVLAN traffic therefore, requires a Router or Layer-3 Switch. --- According to 802.1Q, the industry standard for Virtual LANs, Network Traffic receives VLAN Assignment through “tagging”. More specifically, the Header of a Layer-2 Frame receives a specific “tag” or VLAN ID, representing the VLAN to which the “tagged” traffic belongs. In general, most vendors, including Ubiquiti, use VLAN1 as the Default VLAN so Network Devices and Protocols communicate and work ‘out-of-the-box’. However, today’s Network Layer-2 Network Devices all support 802.1Q for traffic “tagging”, where Host packets receive VLAN assignment. Because Host traffic in VLAN 10, 20, and 30 is tagged with their respective VLAN ID’s, they can only broadcast to other Hosts within their Virtual LANs, and not to Hosts in other VLANs. ---- In order to work with “tagged” traffic, Interfaces and Ports receive Port VLAN Assignments, or PVID for short, and classify as one of two Port Types: Access Ports, and Trunk Ports. Access Ports connect to Host Devices, and therefore have a single Port VLAN ID. On the other hand, Trunk Ports connect to other Trunk Ports of VLAN-Ready Devices, and can receive as many Port VLAN IDs as are required per the Network Topology. --- To help illustrate how “VLAN tagging” works with traffic, consider the following: A Host sends traffic upstream without “tags”. The “untagged” traffic reaches the Access Port, at which point, the Access Port inserts the VLAN ID, or, the “tag”, to the Frame Header. With the VLAN “tag” now in the Frame Header, Trunk Ports recognize which areas of the Layer-2 Network to carry the VLAN Traffic going upstream. As “tagged” traffic moves downstream, the Access Port removes the VLAN “tag” from the Layer-2 Header, so the Host receives the traffic “untagged”. Trunk Ports can also carry “untagged” traffic if desired, but only one VLAN ID can and should be assigned to the “untagged” traffic. ---- Like all traffic destined to non-local networks, inter-VLAN traffic, must be routed through a Local Gateway. To clarify, interVLAN traffic must be routed for two reasons: At Layer-2, each Virtual LAN represents a separate broadcast domain, while At Layer-3, each VLAN receives a unique Network IP Range. Similar to how Switch Ports and Access Point SSIDs receive PVIDs, a Router can be configured with Virtual Interfaces to participate in a Virtual LAN.
Views: 209168 Ubiquiti Networks
The UVC Micro is part of the UniFi Video surveillance management system. It records 720p HD video, day or night, indoors. It's about the size of a golf ball and mounts anywhere with its versatile 3-axis magnetic base. The Micro streams video via Wi-Fi and also features a microphone and speaker for audio. UVC Micro is $99 MSRP. Go to http://www.ubnt.com/unifi-video/unifi-video-camera-micro to learn more.
Views: 34770 Ubiquiti Networks
Short video tutorial explaining the concept and use for airMagic, Ubiquiti's cutting-edge, RF tool freely available on airMAX-ac products running airOS version 8 and later. In summary, airMagic collects & analyzes the individual airView data of each radio in the PtMP network, allowing operators to plan & build networks for maximum possible performance. To download the latest airOS-8 firmware, visit the airMAX Blogs section of our Community: http://community.ubnt.com/t5/airMAX-Beta-Blog/bg-p/blog_airMAX_Beta
Views: 25782 Ubiquiti Networks
UniFi Layer-3 Device Adoption Methods In order for the UniFi Controller to discover and adopt UniFi Devices over Layer-3 Network boundaries, each device must be configured with updated INFORM URL settings. To review, the INFORM URL represents the Network Address of the UniFi Controller, and can therefore, point to any reachable network address belonging to the Controller, including: IP address, Hostname, or even, a Fully-Qualified Domain Name. --- There are four Methods for updating a UniFi Device’s INFORM URL for the purpose of remote management, including: UniFi Discovery Tool SSH Client DHCP Option 43, and, DNS Resolution The UniFi Discovery Tool comes freely bundled with the UniFi Controller software, and runs on the PC to discover UniFi Devices on the Local Area Network. Subsequently, the tool can be used to manually update a UniFi Device’s INFORM URL to reach the Layer-3 IP of the UniFi Controller. Alternatively, any SSH Client like Terminal or PuTTY can be used to connect to a UniFi Device, then update its INFORM URL to the Layer-3 IP of the UniFi Controller via the set-inform command. In addition to offering an IP Address, Gateway, and DNS settings, a DHCP Server can also share the IP address of the UniFi Controller to UniFi Devices, through DHCP Option 43 configuration, whereupon, the DHCP Server listens for Vendor-Class Identifier, ‘ubnt’, in the DHCP Lease Request. Conveniently, Ubiquiti DHCP Server Devices, such as EdgeRouter & UniFi Gateway can be configured with Option 43 to include the Layer-3 IP of the UniFi Controller in the DHCP lease. Finally, because the default INFORM URL includes the hostname, ‘unifi’, the network DNS server can also be configured to resolve ‘unifi’ to the Layer-3 IP of the UniFi Controller. UniFi Security Gateways automatically listen and resolve 'unifi' for any hosts on the network that point to the USG as their DNS server. --- Among the four Methods for updating a UniFi Device’s INFORM URL, DHCP Option 43 and DNS Resolution trigger Auto-Discovery for Adoption ‘en-masse’, and are therefore very useful for Large-Scale Deployments.
Views: 14212 Ubiquiti Networks
Network Switches and Access Points connect Hosts on the same Local Network and move traffic according to information stored in their MAC Table. Also known as the Content Addressable Memory, or CAM table, the MAC Table keeps track of the interfaces or Ports on which a given MAC Addresses can be reached. For example, a Frame arrives on Switch Port 1 with the Source MAC of Host A. After UPDATING the MAC Table with Host A’s MAC on Port 1, the Switch will take one of three actions regarding the Frame. If the Destination MAC is already mapped to a certain Port, then the Switch will FORWARD the Frame to that particular Port, and only that Port. If however, no entry exists in the MAC Table for the Destination MAC, then the Switch will FLOOD the Frame out all Local Ports, except the Port on which the Frame was received (so as to avoid loops in the Network). A Switch will also FLOOD should the Layer-2 Broadcast Address be used as the Destination MAC Address. As source traffic begins to populate on the network, the Switch continues to update its MAC tables in order to forward traffic, rather than flood. Lastly, a Switch may also FILTER the Frame according to its Destination and/or Source MAC Address, when the Switch is configured with a MAC Access Control List, or ACL, for short. The Forward Information Base, or FIB for short, allows a Router to look up the interface on which it forwards a Packet received on a different Interface. The source & destination MAC addresses in the Layer-2 Frame are rewritten in order to enable traffic to pass across each Local Segment, when moving data across networks. In this way, the MAC table only fills with Layer-2 addresses, that is, addresses belonging to Hosts and interfaces inside the LAN. 44:33:4A:7D:FD:84 A1:8E:09:3A:DC:2C 12:E6:95:77:E8:B6 BF:C9:BB:3B:9C:7B 70:1D:89:7C:FE:3D 38:FD:E1:0D:D2:29 Whenever a Host needs to reach another Host on a different network, it sends the Frame to its Local Gateway. At Layer-2, the Destination MAC is the Gateway, but at Layer-3, the At Layer-2 destined to a host on a different Network which it determines according to MAC entries in its FIB, and rebuilds the Layer-2 Frame Local Interface on a rebuilt Frame will be forwarded to reach the intended recipient.
Views: 11728 Ubiquiti Networks
A brief video tutorial describing backup configuration file management.
Views: 46401 Ubiquiti Networks
The airFiber®AF-5X is designed for long-range, Point-to-Point (PtP) backhaul links. It features the highest TDD throughput available and proprietary HDD for ultra-low latency. airFiber X is $399 MSRP. Go to http://www.ubnt.com/airfiber/airfiber5x to learn more.
Views: 55860 Ubiquiti Networks
A quick video demonstrating how to set up and begin managing UniFi Video Cameras on the Ubiquiti NVR-Controller appliance.
Views: 89775 Ubiquiti Networks
LANs, WLANs, WANs, the Internet & Ubiquiti Products Any device that acts as a point along which data passes on the network is called a Node. A Local Area Network or LAN for short, is a group of interconnected Nodes, typically in the same physical location. Network Administrators configure, control, and manage the LAN, most notably, through Network Address assignment. After receiving a Network Address to communicate on the Network, a Node is described as a Host. Although Local Hosts share common Address characteristics, each Host’s traffic is identified by its unique Network Addresses. In general, a Network Switch is a device that increases the size of the Local Segment, or LAN. Local Hosts connect to Switch Ports to communicate locally. The International standards group, IEEE 802, including 802.2 & 802.3, discusses LAN Technology in great detail. Nodes with wireless radio capability are called Stations. Ad-hoc describes Stations that communicate independent of LAN infrastructure. In contrast, a Wireless LAN, or WLAN for short, allows wireless clients to connect to and communicate on the Local Network through Access Points, devices which increase the size of the LAN by broadcasting, or, announcing the existence of the Wireless Segment. IEEE 802.11 describes Wireless LAN Technology standards, such as 802.11r, for fast roaming, or 802.11ac, the fifth generation of Wi-Fi. By definition, the Wide Area Network, or WAN for short, represents the greater Network beyond the boundaries of the LAN. Also known as Gateways, Routers sit on the boundary between LANs and the WAN. Compared to Switches, which move traffic within the LAN, Routers are responsible for moving Local Host traffic between the LAN and WAN, and also, between different LANs. Synonymous with the WAN, the Internet is a Global System of Routers owned and maintained by different Internet Service Providers, or ISPs, who together, enable Network Traffic to reach its intended Destination. Compared to ISPs, who use airMAX, airFiber, EdgeMAX and other Ubiquiti platforms to build Broadband Internet Networks, IT Administrators work with UniFi to manage, scale, and monitor LAN, WLAN, and WAN for Enterprise users in industries such as education, hospitality, government, and more.
Views: 10069 Ubiquiti Networks
A video tutorial explaining how to set up an L2TP over IPsec VPN server with local accounts (as opposed to RADIUS authentication) via the CLI. The conclusion of this video tutorial demonstrates how to create firewall exceptions (based on the default firewall for WAN+2LAN2 template), then configure a VPN client on an iOS device, and finally, how to monitor/track connections. For step-by-step information, you can also visit our Community Knowledge Base: http://community.ubnt.com/t5/EdgeMAX-CLI-Basics-Knowledge/EdgeMAX-VPN-on-L2TP-via-CLI/ta-p/473925
Views: 44483 Ubiquiti Networks
Troy Hunt helps you determine the perfect build out for your environment.
Views: 74997 Ubiquiti Networks
UniFI Controller Management Protocol, Device Adoption & Inform URL Ubiquiti enables administrators to centrally manage the Devices and Users on their Enterprise Networks via a Software Defined Networking Control Plane, known more simply as, the UniFi Controller. The UniFi Platform was purposefully built using an architecture that scales massively, to support maximal number of managed devices, irrespective of their location on the Global Network. The UniFi Controller therefore, uses a robust, proprietary protocol to remotely access, configure, and monitor Network Devices, despite sitting behind NAT firewalls, or any derivation thereof, However, it is UniFi’s simple web GUI that makes device management simple and straight-forward, while behind the scenes, managed UniFi Network Devices ‘heartbeat’ into the Controller to periodically inform the Controller of their reachable Network IP. In this way, the Controller can instantly reach the UniFi Device with whenever the Admin chooses to push Configuration updates. However, before provisioning, that, Device Configuration can occur, a UniFi Device must fall under Controller Management, through a process called, Device Adoption. -- UniFi Adoption is a handshake between Device & Controller, outlined in three simple steps: While in its factory default state, a UniFi Device INFORMs the Controller of its Network Presence through Beacon announcements. When located on the same Local Network, the INFORM Beacon announces via Layer-2 broadcast, resulting in immediate discovery at the Controller. Inside the GUI of the Controller, the Admin chooses to Adopt the Pending Device. Using the Network Information described in the INFORM Beacon, the Controller now connects over SSH to the UniFi Device to complete the process of adoption and manage the Device. Immediately thereafter, the UniFi Device is ‘bound’ to the Controller, and provisions with any configuration settings specified at the Controller. ----- In order to discover and adopt Devices over Layer-3 Network boundaries, a UniFi Device must be configured with updated INFORM URL settings. The INFORM URL represents the Network Address of the UniFi Controller, and can therefore, point to any reachable network address belonging to the Controller, including: IP address, Hostname, or even, a Fully-Qualified Domain Name. Supported methods of updating the Inform URL for Layer-3 adoption include, the UniFi Discovery Tool, SSH, DNS & DHCP option 43. After updating the INFORM URL, the factory default factory UniFi Device will appear in the UniFi Controller, ‘Pending Adoption’, ready to be managed. If device doesn’t appear, ensure end-to-end IP connectivity exists between Controller & Device. To successfully perform Layer-3 adoption, it may be necessary to update the INFORM URL again after the first adoption appears to fail. -- Once Adopted, a UniFi Device populates under ‘Unplaced Devices’ in the Controller, ready for naming & placement on any map under the adopted site. After provisioning, the adopted UniFi devices takes on the Site Username & Password, both of which, are required in case either SSH Access or Adoption to a new Controller, is desired. Once adopted, the UniFi devices begins reporting traffic statistics to the Controller. As a final note, all communication between UniFi Controller and Managed Devices is encrypted and untagged.
Views: 11914 Ubiquiti Networks
The Open Systems Interconnection (OSI) Model is a 7-Layer data model that very simply describes the software protocols and hardware involved in end-to-end network Communication. At the top of the OSI stack, the Application Layer represents protocols such HTTP for web browsing. End-users interface their Internet Apps at this layer, and unlike Network Admins, are generally not concerned with the lower layers. A Payload passing down the OSI stack undergoes Encapsulation, process whereby each layer adds specific information to help move the payload across the network, closer to its final destination. After passing from Layer-7, Layer-6 & Layer-5, the Payload arrives at Layer-4, the Transport Layer, where it is encapsulated with Network Protocol & Port information. The resulting envelope of encapsulated data is called, a Segment. At Layer-3, the Network Layer, the Segment becomes encapsulated with IP Address information. The resulting envelope of encapsulated data is called, a Packet. At Layer-2, the Data Link Layer, the Packet becomes encapsulated with MAC Address information. The resulting envelope of encapsulated data is called, a Frame. Finally, at Layer-1, the Physical Layer, the Frame is converted to a modulated Carrier Signal, then transmitted over a physical medium, be it wired (via copper & fiber lines), or wirelessly (via radios). Across the Network, APs, Switches, and Routers help move the Payload to its intended destination, examining info Layer-by-Layer in a process called, Decapsulation. Here, the AP listens to a Host’s Wirelessly signal to rebuild the Encapsulated Data, then determines at Layer-2, the intended local recipient is the Gateway, and forwards along a rebuilt Frame via Ethernet. Similarly, the Gateway receives the wired, transmitted signal, rebuilds the Encapsulated Data, determines at Layer-2 that it is the intended recipient, but discovers that the Layer-3 address belongs to a host on a different network segment, and forwards along a rebuilt Frame via Ethernet. The process is repeated until the Payload reaches a Network host, who at Layer-3, discovers that it is the intended recipient, and at Layer-4, that an established connection exists for the Packet, so the End-user can retrieve the Payload in the respective Application at Layer-7. At Layer-2, data moves between Nodes according to MAC addresses. This is commonly understood as Intranetwork communication, like when a Host communicates over a Ubiquiti AP and/or Switch to reach another Host, but also, when data moves across direct links, like two Peered Internet Routers linked at datacenter. At Layer-3, data moves between Network Hosts according to IP addresses. Commonly understood as Internetwork communication, this includes Ubiquiti Routers that move data between networks. At Layer-3, data moves between Network Hosts according to IP addresses. And at Layer-4, protocol and port assignment helps hosts decide how to establish the connection, if necessary, on both sides. As a final networking note—the term “Packet” broadly describes any Network Traffic, even when discussing the Layer-1 ‘Physical Signal’, Layer-2 ‘Frame’, Layer-4 ‘Datagram’, or Layer-7 ‘Data Payload’.
Views: 6435 Ubiquiti Networks
In this video, we’ll examine management of the UniFi Controller software through a quick analysis of UniFi Device behavior with and without the Controller online, as well as when, where and how to deploy the Controller. We’ll then close by discussing best practices for Controller use. Available for free download, the UniFi Controller server software supports Windows, Mac, and Linux operating systems, with Mobile app support on iOS & Android. The desktop software package comes bundled with the UniFi Discovery tool for finding & managing UniFi Devices on the Local network via layer-2 broadcast. When installed to a PC, the UniFi Server requires the latest version of Java installed, the Controller Software actually runs over top Apache Tomcat, permitting any network host to access from anywhere via web browser. Although the Controller is required for initial setup, adoption & configuration of UniFi devices, the server need not be running in order for UniFi Devices to move traffic as expected in the Enterprise Network. Specifically, this means that A UniFi Gateway will continue to Route, offer DHCP addresses, and filter according to Firewall rules, Even as Switches supply POE and keep VLAN While APs, continue broadcasting WLANs, band-steer, and apply bandwidth limits. In fact, for fast WLAN deployments, UniFi Access Points can even be configured using Easy Setup Mobile App, a standalone app for iOS and Android Devices. The decision whether to keep the UniFi Controller online & connected to UniFi Devices following initial adoption & configuration, depends primarily on whether the following features are needed: Post-adoption provisioning, that is, device configuration Real-time Device Monitoring User Traffic Statistics Network Insights, like Rogue Access Points and Guest Authorization And, perhaps most importantly, the UniFi Guest Portal & Hotspot system Assuming the UniFi Controller remains online, consider first, whether the Controller will remain in close proximity to the UniFi Devices and users it manages. If the Administrator remains on-site or the sites under management are closely concentrated within a single region, it may be a good idea to keep Local Controllers However, if the customer sites are scattered and lack proper IT personnel, it may be a good idea to keep the Controller off-site or even in the Cloud where an admin can access from anywhere, at any time. Keep in mind that an off-site controller means UniFi Management & Guest Portal Traffic must traverse the WAN, so where Internet bandwidth and uptime connectivity are concerning, Ubiquiti recommends Local Controllers. With proximity in mind, as well as traffic requirements for total number of devices and users on the sites under management, consider the type of Controller server hardware to deploy. In the case of smaller, localized sites, the UniFi-Cloud Key or even a more powerful Linux PC could serve the needs of the customers. Hosted Server Virtualization platforms like UniFi Elite reduce server maintenance requirements, and ensure high reliability & uptime for Enterprise Networks. Although the UniFi Controller itself supports a limitless number of Devices and Users, Controller performance depends on the server hardware and traffic to/from the Controller. In scenarios where the controller is hosted using a third party, and, as the Enterprise Network under management grows from Tens to Hundreds to Thousands of Users, simply locate and restore the Backup UniFi Server file to a more powerful Virtual Server instance. Regardless of Controller Setup, Ubiquiti’s Hybrid Cloud Technology allows Admins to manage multiple UniFi Controllers under a single, common Dashboard, without any license costs. The Dashboard shows the status of each managed Controller, and includes summarized data of each Controller’s Sites, Devices, and Users. Built on the WebRTC protocol, the Hybrid Cloud enables end-to-end connectivity for remote access, even in situations where the WAN IP address is dynamic or when sitting behind a double NAT Firewall. To link a UniFi Controller to the Hybrid Cloud Dashboard, enter the SSO Ubiquiti Account of the Admin under the Cloud Access tab inside the Controller settings. Among the most important, recommended practices for UniFi Controller management, consider the following: To skip server setup & maintenance altogether, opt for the UniFi Elite Cloud platform, which grants Admins additional support, extended warranties, resilient storage, auto-backup redundancy, and other important Enterprise features.
Views: 46816 Ubiquiti Networks
Learn more about how to select the right AF-11FX radio and duplexers. This video also covers basic configuration, firmware upgrade and more in firmware v4.0 or higher.
Views: 21059 Ubiquiti Networks
To learn more and download the case study, please go to www.ubnt.com/airmax.
Views: 41344 Ubiquiti Networks
Network Traffic & Interfaces Encapsulation helps prepare Host Networks, starting with the local segment, and when necessary, beyond network boundaries. At Layer-4, the Payload receives Network Protocol & Port information. At Layer-3, IPv4 and IPv6 Addresses define the Sender & Receiver Internet address. An IPv4 address is a logical, 32-bit address used in local and internetwork communication. Inside the Layer-3 Packet, a Source & Destination IP Address exist to move traffic across Networks. At Layer-2, MAC Addresses define a Network Device’s address for Link-Local communication. The MAC is a unique 48-bit hexadecimal-based hardware address. Inside the Layer-2 Frame, a Source & Destination MAC Address exist to help move traffic on the Local Network. In order for networks to behavior, it’s important that Host Network Interfaces are configured with unique Layer-2 & Layer-3 Network Addresses. Network interfaces identify the physical and logical ports on which a Host can receive or send Network traffic. In addition to physical Network interface, like a Wired or Wireless Card, or group of Switch Ports, several types of logical interfaces exist, including: Loopback, generally for testing & network administration Bridge, like when joining a wired & wireless interface on the same local segment under a common network address Virtual, which enables an interface to participate in a Virtual LAN, Tunnel, for point-to-point links across WANs, And more. Network traffic can generally be described to move in either of two directions, relative to an interface: egress or ingress. Egress describes traffic leaving an interface—think egress, or exit. Ingress describes traffic approaching an interface—think ingress, or, in. Colloquially, Network Traffic is also said to move “Downstream” or “Upstream” relative to a Network’s Topology, Devices, and/or Users. In networking today, Hosts use both Layer-2 and Layer-3 Addresses to communicate via one of three methods. Unicast traffic involves one-to-one communication, where either the intended recipient’s Layer-2 or Layer-3 Network Address is known. For example, an ICMP Ping Reply is Unicast traffic. Broadcast traffic is one-to-all communication, where all Hosts on the Layer-2 or Layer-3 Network are the intended recipients. For example, a Host needing a DHCP Address would use the Layer-2 Broadcast address FF:FF:FF:FF:FF:FF in attempt to Discovery a DHCP Server on the Local Network. All Hosts on the Local Network would receive the Broadcast message. Multicast traffic is one-to-some communication, where not all, but some Network Devices are the intended recipients. For example, Dynamic Routing protocols use Multicast addresses to communicate solely among Routers, but not with other Network Hosts.
Views: 14847 Ubiquiti Networks
Unboxing Video for the new UniFi AC product: UniFi AC Lite, UniFi AC LR, UniFi AC Pro Datasheets-https://www.ubnt.com/download/ Ubiquiti Store-https://store.ubnt.com/ Distributors-https://www.ubnt.com/distributors/
Views: 16493 Ubiquiti Networks
Troy Hunt goes in depth with the UniFi product line.
Views: 57004 Ubiquiti Networks
A short video guide explaining the revolutionary DPI engine available on Ubiquiti UniFi Security Gateways & EdgeRouter products. For more information about this technology, consult our Knowledge Base: https://ubnt.zendesk.com/hc/en-us/articles/204951104 or visit our Community: https://community.ubnt.com/t5/EdgeMAX-Updates-Blog/EdgeMAX-EdgeRouter-software-release-v1-7-0/ba-p/1287631
Views: 28844 Ubiquiti Networks
Broadcast Domains & CSMA/CA In networking, Layer-2 hardware, including switches, Access points & bridges, are programmed to forward Broadcast Message so as to reach all Hosts on the LAN. The area over which a Broadcast message reaches is known as the Broadcast Domains, which is synonymous with the size of the Local Area Network. Because the Broadcast Domain represents the interconnected topology of layer-2 equipment, more Switches, Access Points, and Bridges equates to a larger Broadcast Domain. By comparison, however, Routers do not forward Broadcast Messages, and therefore mark the boundaries of the Broadcast Domain, that is, the LAN. When the Broadcast Domain becomes too large or populous, Broadcast Messages lead to Broadcast Storms, where normal Host traffic causes LAN performance to suffer tremendously, noting increased latency and reduced throughput. A good rule of thumb is to limit the size of a LAN to no greater than a couple hundred Network Devices, before building another Network Segment and Range. Building a new LAN is as simple as adding another Router, with new LAN interfaces. However, a more cost-effective, practical way to add additional Network Segments and Ranges is to implement Virtual LANs on existing Network Devices. As more Local Networking continues to trend toward mobile computing, Wireless Design & planning for Networks becomes increasingly more important. Like Switches, Access Points expand the Broadcast Domain, but face a unique challenge, since Wireless Stations in the same proximity, by design, compete for shared access to the Wireless Channel over which they transmit. Whenever two Wireless Stations attempt to transmit over top of each other, a collision can result at nearby Receiver Radios, necessitating a retransmission. In order to reduce the chance of collisions, the 802.11 Wireless protocol relies on Carrier Sense Multiple Access / Collision Avoidance, or CSMA/CA for short, which basically requires Wireless Stations “Listen before Talk”. If the Wireless Channel is occupied, wait, then listen again before transmitting. Despite reducing collisions, CSMA/CA is an imperfect access method, as seen in scenarios involving Hidden Nodes, where a receiver hears two transmitters, but the transmitters cannot hear each other, whether due to proximity or physical obstructions. And although mechanisms like Request-to-Send, Clear-to-Send, mitigate the effect of Hidden Nodes, CSMA/CA remains an imperfect access method, with upper limits on the density and volume of stations in a wireless coverage area.
Views: 6215 Ubiquiti Networks
A visual anthem for our WISPs. Enjoy! Make sure to join the ISP Revolution. Sign up at https://www.goubiquiti.com/signup Learn more about the Ubiquiti World Network on our forums: http://community.ubnt.com/t5/Ubiquiti-Announcements-and-News/Ubiquiti-World-Network/ba-p/594555 Agency: DGWB
Views: 38621 Ubiquiti Networks
A complete video tutorial demonstrating the steps to creating a Point-to-Point (PtP) link using two airMAX-ac radios with airOS-7, Ubiquiti's newest software web interface. Written guide from Ubiquiti's community page: http://community.ubnt.com/t5/airMAX-Configuration-Examples/airMAX-Configure-a-Bridged-PtP-Link-using-airMAX-ac-radios-amp/ta-p/1117898 Here
Views: 44213 Ubiquiti Networks
Troy Hunt introduces UniFi from a "prosumer" perspective.
Views: 78220 Ubiquiti Networks
TCP/IP Model and the Internet Compared the OSI Model, the TCP/IP Model is a simplified stack comprised of 4 Layers: - The Application Layer - The Transport Layer - The Internet Layer - The Link Layer The Link Layer identifies and moves traffic across Local Segments, while the Internet Layer identifies the intended Network & Host, wherever it be on the global network. Under this model, Internet traffic moves analogous to the Postal System. Two friends write and send letters to each other, aloof to the work required to mail the letters. Not unlike the End User who, at Application Layer, types into their web browser, www.ubnt.com, unaware of the connections & data required to load the webpage. Should a friend change address, the letter may be lost, or even returned to the sender. Not unlike the Transport Layer, which regulates network connections and informs the Application if errors occur. The letter is enclosed in an envelope with Sender/Receiver address information. Not unlike Encapsulation, where the Payload is placed into an IP Packet with Source & Destination IP address. In order for addressed envelopes to reach their final mailboxes, postal employees carry the mail from Postal Office to Postal Office. Not unlike the IP Packet, transformed to Ethernet or 802.11 Frame, built & rebuilt on a hop-by-hop basis from Gateway-to-Gateway until the Packet reaches its final destination.
Views: 20494 Ubiquiti Networks
A video tutorial explaining when and how PBR should be used in a dual WAN ISP scenario where traffic is balanced 50:50 between upstream ISPs. For step-by-step information, you can also visit our Community Knowledge Base: http://community.ubnt.com/t5/EdgeMAX-Configuration-Examples/EdgeMAX-Policy-based-routing-with-WAN-load-balancing/ta-p/521957
Views: 36100 Ubiquiti Networks
UniFi User Groups, also known as Traffic Shaping or Bandwidth Controls, allow Admins to cap the speed of Wireless Users accessing the Enterprise Network. In this way, UniFi Access Points impose bandwidth limits on how quickly a Wireless Station can send or receive traffic. The UniFi User Group is configured at time of WLAN Creation, under the UniFi Settings Tab. The Default User Group allows Users to send and receive traffic as quickly as their Physical Layer rates allow them. UniFi can impose User Group limits broadly for all users joining the WLAN or, an individual basis, in case a particular User necessitates a speed override, by accessing the Station’s profile and assigning the User Group.
Views: 22608 Ubiquiti Networks
A walkthrough step-by-step guide on how to set up a Ubiquiti device to connect to a remote access point or hotspot in order to share internet with multiple local devices. Ideal for boat, RV, or other similar users who may have to search for new APs to connect to frequently.
Views: 204638 Ubiquiti Networks