<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Network on shocksolution.com</title><link>https://shocksolution.com/tags/network/</link><description>Recent content in Network on shocksolution.com</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Jan 2020 18:05:28 +0000</lastBuildDate><atom:link href="https://shocksolution.com/tags/network/index.xml" rel="self" type="application/rss+xml"/><item><title>2020 Ubiquiti Wireless Access Point (WAP) Roundup</title><link>https://shocksolution.com/posts/2020-ubiquiti-wireless-access-point-wap-roundup/</link><pubDate>Tue, 21 Jan 2020 18:05:28 +0000</pubDate><guid>https://shocksolution.com/posts/2020-ubiquiti-wireless-access-point-wap-roundup/</guid><description>&lt;p&gt;Ubiquiti publishes detailed data sheets for all of their products, but it&amp;rsquo;s hard to find all the information you need in one place for comparison purposes. That&amp;rsquo;s the purpose of this article.&lt;/p&gt;&#10;&lt;h2 id="first-generation-access-points"&gt;First Generation Access Points&lt;/h2&gt;&#10;&lt;p&gt;It can be confusing to distinguish between the &lt;a href="https://help.ubnt.com/hc/en-us/articles/360012192813#3"&gt;generations of UniFi access points&lt;/a&gt;; you have to look at the access point label, or access it via the UniFi software to see the version. The performance difference between generations are significant. The &lt;a href="https://dl.ubnt.com/datasheets/unifi/UniFi_AP_DS.pdf"&gt;datasheet for first generation Ubiquiti UAP wireless access points&lt;/a&gt; is still available.&lt;/p&gt;</description></item><item><title>Monitoring a switch or router port via SNMP</title><link>https://shocksolution.com/posts/monitoring-a-switch-or-router-port-via-snmp/</link><pubDate>Mon, 16 Dec 2019 20:19:52 +0000</pubDate><guid>https://shocksolution.com/posts/monitoring-a-switch-or-router-port-via-snmp/</guid><description>&lt;p&gt;Most business-class switches and routers support monitoring via SNMP. The main barrier to implementing SNMP monitoring is that so many parameters can be monitored, and it can be very hard to isolate the most important parameters. This example shows how to monitor the status of a specific port. Note that the term &amp;ldquo;port&amp;rdquo; includes link aggregation groups (LAGs) or other logical groups of ports like VLANs.&lt;/p&gt;&#10;&lt;h2 id="use-case"&gt;Use Case&lt;/h2&gt;&#10;&lt;p&gt;A top-of-rack switch has several important link aggregation groups (LAGs). For example, one LAG has connections to two identical routers in a VRRP cluster. Other LAGs provide redundant network paths to independent NICs on the same server. I want to be alerted if the port status changes on any critical LAG. The ISP delivers Internet to a single port on the switch, which I also want to monitor.&lt;/p&gt;</description></item><item><title>Secure, Automated Network Device Backups</title><link>https://shocksolution.com/posts/secure-automated-network-device-backups/</link><pubDate>Tue, 03 Sep 2019 16:38:30 +0000</pubDate><guid>https://shocksolution.com/posts/secure-automated-network-device-backups/</guid><description>&lt;p&gt;You probably have at least a few business-class switches and routers silently do their job, year after year. Network devices can be so reliable that we configure them once, and then forget that they exist. However, forgetting them is a really bad idea, since they require regular OS or firmware updates to patch vulnerabilities, and at some point, they will become unreliable and fail. If your device fails, do you have the configuration available to apply to its replacement? Are you sure the configuration that&amp;rsquo;s in your archive or documentation is up to date? This post deals with automating backups from Netgear switches and Ubiquiti EdgeRouters (and possibly switches, if they run EdgeOS). Please check out the accompanying repo at &lt;a href="https://github.com/craigafinch/network-backup-scripts"&gt;&lt;a href="https://github.com/craigafinch/network-backup-scripts"&gt;https://github.com/craigafinch/network-backup-scripts&lt;/a&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Another Reason to Enable Private IP Addresses on Google Cloud SQL</title><link>https://shocksolution.com/posts/another-reason-to-enable-private-ip-addresses-on-google-cloud-sql/</link><pubDate>Wed, 26 Jun 2019 18:16:22 +0000</pubDate><guid>https://shocksolution.com/posts/another-reason-to-enable-private-ip-addresses-on-google-cloud-sql/</guid><description>&lt;p&gt;Google Cloud SQL recently introduced the capability for an instance to have an IP address within the private address space of your VPC network. Previously, all Cloud SQL instances had IP addresses within the address space of the public Internet. Obviously, the public IP was a security and privacy concern, as well as a potential violation of some compliance and governance frameworks. Now, each instance may have a public IP, private IP, or both. There&amp;rsquo;s another potential benefit to using a private IP address: performance!&lt;/p&gt;</description></item></channel></rss>