The Internet Protocol (IP) system designates how networked devices can address one another across the internet. The first major version of IP, IPv4, was deployed to the public ARPANET in 1983. IPv4 uses 4 one byte segments to designate a devices address, this 32-bit address space allows for 232 addresses to be used in total. The next major iteration of IP is called IPv6 and it uses a 128-bit address space allowing for significantly more IP addresses to be assigned. Continue reading “Difference Between ipv4 and ipv6”
localhost is a networking term; it’s the hostname for the loopback network interface of whichever server it’s said in reference to (meaning every server has a ‘localhost‘). The loopback interface bypasses any local network interface hardware, and serves as a method to connect back to the server itself. The term localhost is used often in both networking and in server administration.
The IPv4 address for localhost, or the loopback network interface, is 127.0.0.1.
The IPv6 address for localhost, or the loopback network interface, is ::1.
- These instructions are intended specifically for solving the error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
- I’ll be working from both Liquid Web Core Managed Ubuntu 12.04 LTS and 14.04 LTS servers, and I’ll be logged in as root.
- These instructions are intended specifically for solving the error: /usr/sbin/ifconfig: No such file or directory
- I’ll be working from a Liquid Web Self Managed CentOS 7 server, and I’ll be logged in as root.
Have you ever wanted to check up on the details of your server’s bandwidth usage? Liquid Web’s manage interface provides graphs that give you such information. Here’s how to read them.
Featured Freeware highlights some of the Liquid Web staff’s favorite free software. This week we are covering a treasured favorite, MTR.
MTR (originally Matt’s Traceroute, now My Traceroute) functions like traceroute insofar as it displays the network hops from your local machine (or server, depending on where you run the command) to the target IP address or hostname.
But MTR differs from traceroute by constantly observing and displaying the network hops and related statistics instead of displaying a single set of results. Put simply, if you traceroute to google.com you will get a report for a single connection from your computer to Google’s servers. If you MTR to google.com you will see a continuously updated display of each hop and its performance over time until you tell it to stop. Response times can be evaluated just like traceroute or ping results: Higher numbers are bad, lower numbers are good. If a particular hop is showing much higher response times than the others, even without packet loss, you can see that it might be having a problem.
MTR can be installed on almost any Linux machine by using a local package manager such as yum or apt. Windows and Mac OS X users can install MTR using the links in the Additional Resources section at the bottom of this post.
Basic MTR Usage
Example MTR command from a Liquid Web server to google.com:
|My traceroute [v0.85]|
|host.example.com (0.0.0.0)||Wed Mar 23 14:58:34 2016|
|Keys: Help Display mode Restart statistics Order of fields quit|
Breaking the results down from left to right:
- Host: The name or IP address of the network hop.
- Loss%: The percentage of packets that are being lost during the trace. In most cases, this is the first result you want to watch.
- Snt: The number of packets sent to the hop.
- Last: The response time of the last packet sent to the hop.
- Avg: The average response time during the entire span of the test.
- Best: The best response time during the entire span of the test.
- Wrst: The worst response time during the entire span of the test.
- StDev: Is the Standard Deviation of latencies to the host, and can help you better evaluate the average latency measurement. A high StDev indicates an inconsistency in the latency measurements on that hop, such as when a wide gap is recorded between the best and worst latencies on that hop.
Evaluating MTR Results
Almost immediately you will want to pay attention to the Loss% column in MTR’s display. As the tests progress, the percentage will get more accurate at telling you where there may be a problem. Generally speaking, you will see packet loss at every hop past the point of trouble if a network issue is in play, and the point in the route at which the packet loss occurs will narrow down the nature of the specific issue.
- Depending on your home or office network setup, the first hops likely will be your local firewall and/or router or wireless access point. If the packet loss is occurring in one of these first couple of hops, it could be an indicator of trouble within your local network. You may want to try temporarily disabling the firewall or antivirus suite on your computer and checking the route (and the site) again.
- The next hop likely will be your Internet Service Provider’s network, and you may recognize your ISP’s name in the host column. If the packet loss is here, then you have a strong indicator that your ISP is having problems on their end. Do other websites load properly, or is everything slow?
- Packet loss in the middle of the route can be an indication of a problem with a major Internet route. In this case, you can notify your ISP and they can potentially contact their upstream provider to get the matter resolved. It is important to note, however, that some packet loss at this stage is normal: You can almost always expect to see minor packet loss when the server is physically located in a different geographic region or across a large body of water, such as an ocean. The amount of packet loss typically will increase with distance. If the route continues past this point and ultimately connects to the server, there may be not be a network issue. To confirm, you can test the route to the site from a server in the same geographic region as your server using a free tool such as Traceroute Tools Online or through a free VPN service. If there are no issues, you may want to consider using a Content Delivery Network to ensure that the bulk of your site’s resources are served from the locations closest to your site visitors.
- Finally, the route will pass through your hosting provider’s router and firewall to reach their internal network, and then through your server’s firewall (which may be a cloud firewall, a hardware firewall, a software firewall, or a combination of the three). If you’re a Liquid Web customer, follow the instructions in our article at Unblocking an IP Address in the Firewall or use our semi-automated IP address unblock tool in Manage to ensure that your IP address is not being blocked in your server’s firewall.
- WinMTR – MTR for Windows Users: https://sourceforge.net/projects/winmtr/files/WinMTR-v092.zip
- MTR can be installed on Mac OS X using Fink, or Homebrew.
- MTR (software) – Wikipedia
CSF is generally considered a more advanced firewall as there are more configuration options compared to other firewalls, while still being simple enough to install and configure that even novice administrators can use it. This article will give you a simple overview about how to install and configure CSF and its security plugin LFD (Login Failure Daemon).
Starting with Mac OS X 10.6 it is now possible to connect to a Cisco IPSec VPN without having to download any extra software.
Are you unable to connect to your server to send and receive email, log into cPanel or WHM, or make an FTP or SSH connection?
If you can’t connect to your website there are a few things you can do to help us better diagnose the source of the problem. The more quickly this information is collected, the more quickly we can fix whatever is causing almost any issue. Help us help you!
Continue reading ““The website is down! Now what?” Help Us Help You!”
One of the most common e-mail issues we encounter in our support department is customers who are traveling and are encountering problems trying to send e-mail.