My home Internet access is critical not only to me, but to my whole family. Over the course of many years, I have gone through a variety of Internet configurations. Recently, I moved to the UniFi AP AC PRO from the ASUS RT-AC3200 for WiFi. I would like to discuss my requirements as I looked for a new WiFi solution and my thoughts so far. Read on to learn more!
About a year ago, I covered my home lab v3.0 configuration. While I am happy with the configuration, I have been having issues with my ASUS RT-AC3200. In this post, I would like to cover those issues. Read on to learn more!
By default, Log Insight is configured listen on the following ports:
The question becomes, how do you change these default ports?
I have been noticing more and more frequently then when I switch between WiFi connections or switch between wired and WiFi connections that sometimes my WiFi connection would show that it was online, but I was unable to access anything on the LAN or WAN. I have experienced similar issues when DNS is not working properly, so my first test is to validate DNS is working. With this recent issue my test always returned:
$ > nslookup cnn.com /SourceCache/bind9/bind9-45.101/bind9/lib/isc/unix/socket.c:1890: internal_send: 192.168.1.1#53: Cannot allocate memory
So what is going on and how can you fix the issue?
Recently my laptop decided it no longer wanted to start. While it was in the Genius Bar, I dug up an old Macbook Pro (called MBP throughout the rest of this post) and began to configure it so I could use it for work. Configuring a different laptop gave me the opportunity to try out some new/updated applications and see if I could find more ways to be productive (I will cover this in a future post). In addition, it brought up some old issues I had experienced and gave me a chance to fix them and document them. In this post, I would like to talk about the problems I experienced attempting to connect to a Juniper Network Connect (called JNC throughout the rest of this post) VPN and how I was able to get it resolved.
In my last post, I talked about two routing modes used on load balancers: NAT and transparent. As you may recall, I recommended against using transparent mode unless it is a common practice to use a load balancer as the default gateway in your environment. In this blog post, I would like to provide another workaround that would enable transparent mode without having to point the default gateway of your Log Insight nodes to the load balancer!
In my posts about load balancer configuration for Log Insight, I have talked about configuring Network Address Translation (NAT). I would like to dive a little deeper on the differences between NAT mode and another mode available on load balancers called transparency.
In Log Insight 2.0 a scale-out feature was introduced. The best practice when using scale-out is to configure an external load balancer in front of the cluster and send all ingestion traffic (i.e. syslog and ingestion API) to the load balancer instead of directly to a node. The reason for this best practice is to assist with balancing data across nodes and also to provide ingestion high availability. In this post, I would like to discuss why data may not be balanced across a Log Insight cluster whether a load balancer is used or not.
I have heard many requests from people looking for how to configure an external load balancer (LB) to balance the traffic for a Log Insight cluster. This post provides directions for some popular LBs.
How do you collect NetFlow events over the syslog protocol so you can analysis them with a tool like Log Insight? That is the question I would like to answer in this post!