While preparing for a recent trip to Las Vegas for a cybersecurity conference, I decided I would stop by Death Valley National Park before returning home. And by “stop by” I mean “climb a mountain.” I had seen a slickdeals.net post about the Garmin Fenix 3 GPS smartwatch a few days earlier, so I bought it and had it shipped to my hotel in Las Vegas. I was looking for a mountain in the eastern area of the park, close to Death Valley Junction if possible, as DVJ is pretty easy to get to from Las Vegas.
We are living in a time of constant digital surveillance. If you do not actively take the initiative to protect yourself, you are being monitored. You are being watched. You have no privacy. You have no expectation of privacy. Your security is not protected. You are responsible for securing your right to privacy. This year, I will be stepping up my initiative to protect myself. Our “rights” are already gone. It is now up to the individual to take action.
Okay, I feel the need to write this because I just upgraded from FortiOS 5.4.0 to FortiOS 5.4.1 on my FortiGate 90D-POE, and my FortiAP couldn’t handle it. I actually had to completely reconfigure my FortiGate from scratch, as I lost everything but console access whenever I would attempt to import my configuration. Before we begin: You have two SSID types you can configure I chose “Bridge to FortiAP’s local interface” for my main WiFi network for two reasons: A) This Fortinet doc says “Bridge mode is more efficient than Tunnel mode, as it uses the CAPWAP tunnel for authentication only” B) A post in this Reddit thread suggests that tunneled APs use more system resources than a bridged AP I chose “Tunnel to wireless controller” for my guest network because I want to apply different levels of UTM to guests than I do to my own WiFi traffic, and if I bridge both SSIDs to the FortiAP interface, I can’t apply separate UTM policies.
Goal: Replace Google Fiber Network Box with your own FortiGate router 2016/07/08 UPDATE – PLEASE READ: The following configuration will allow your FortiGate to work with Google Fiber. However, after reviewing the hit count for the three policies outlined in this guide, it appears that my DHCP and IGMP policies are not matching any traffic. Apparently, absolutely all traffic from all services, including DHCP and IGMP, is being assigned an 802.