Getting Started

• If you are just getting started with configuring your firewall.
• Most of the rules that are described here assume that your iptables is set to drop incoming traffic, through the default input policy, and you want to selectively allow traffic in.
• Use whichever subsequent sections are applicable to what you are trying to achieve. Most sections are not predicated on any other, so you can use the examples below independently.
• Use the Contents menu on the right side of this page (at wide page widths) or your browser’s find function to locate the sections you need.
• Copy and paste the command-line examples given, substituting the values in red with your own values.

Keep in mind that the order of your rules matter. All of these iptables commands use the -A option to append the new rule to the end of a chain. If you want to put it somewhere else in the chain, you can use the -I option which allows you to specify the position of the new rule (or simply place it at the beginning of the chain by not specifying a rule number).

Allow Loopback Connections

The loopback interface, also referred to as lo, is what a computer uses to for network connections to itself. For example, if you run ping localhost or ping 127.0.0.1, your server will ping itself using the loopback. The loopback interface is also used if you configure your application server to connect to a database server with a “localhost” address. As such, you will want to be sure that your firewall is allowing these connections.

Nam eu est ac metus posuere rutrum. Curabitur elementum ac velit nec scelerisque. Proin turpis purus, maximus a dolor ac, rhoncus sagittis nisi. Sed sapien lacus, elementum sit amet nisl et, bibendum volutpat eros. Aliquam tempor eros mattis felis cursus ultricies. Vivamus quis hendrerit purus, vel gravida diam. Quisque placerat posuere tortor bibendum pretium. Ut tincidunt, ipsum non pretium pellentesque, nunc nisl auctor nibh, ac molestie est ipsum a urna. Cras ac erat a urna pretium vulputate at ut sem. In velit enim, hendrerit sed sapien id, sodales luctus nisl. Nunc sagittis non augue at vestibulum. Vestibulum sit amet pretium felis, sed varius justo. Nam at mi est. Cras eu consequat dolor. Phasellus non vestibulum nibh, vitae scelerisque tortor.

Basic Configuration

Integer at lectus augue. Ut feugiat odio felis. Nullam aliquet diam vel elit tempus aliquet. Phasellus mattis nec neque eu porta. Sed purus risus, tincidunt a mauris nec, placerat dapibus ipsum. Suspendisse facilisis convallis orci nec tincidunt. Nam posuere quis ipsum in tempus.

Duis volutpat a massa eu egestas. Duis ac lectus sollicitudin, bibendum augue sit amet, sollicitudin augue. Maecenas accumsan egestas dolor, non cursus massa imperdiet et. Praesent euismod nec dolor sit amet condimentum. Fusce vulputate sed enim sed egestas. Donec porta risus vulputate, sodales massa vitae, tempor purus. Aenean mattis bibendum elit, sit amet consequat dolor vitae.

Conclusion

That should cover many of the commands that are commonly used when configuring a firewall. Of course, iptables is a very flexible tool so feel free to mix and match the commands with different options to match your specific needs if they aren’t covered. Continue reading this guide at Digital Ocean. This article has been used as an example of an Ecko WordPress theme. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

The post Essentials: Common Firewall Rules and Commands appeared first on EckoThemes.

NGINX

NGINX is a high performance, open source web application accelerator that helps over 37% of the world’s busiest websites deliver more content, faster, to its users.

Companies deploy NGINX to manage the complexities and pitfalls associated with HTTP and to make their web applications more responsive, scalable, fast and secure. NGINX is commonly installed between the network and the application to offload concurrency processing, URL switching, HTTP load balancing, SSL termination, caching, and security policies.

APACHE

The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache HTTP Server and recognize the many contributors.

VARNISH

Varnish is an HTTP accelerator designed for content-heavy dynamic web sites. In contrast to other web accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols.

The post Faster Response Time with Reverse Proxy Cache appeared first on EckoThemes.

var http = require('http');
http.createServer(function (req, res) {
    res.writeHead(200, {'Content-Type': 'text/plain'});
    res.end('Hello Worldn');
}).listen(1337, '127.0.0.1');
console.log('Server running at http://127.0.0.1:1337/');

The post Simple HTTP Server in NodeJS appeared first on EckoThemes.

Step One – Install Nginx

We can install Nginx easily because the Ubuntu team provides an Nginx package in its default repositories. Since this is our first interaction with the apt packaging system in this session, we should update our local package index before we begin so that we are using the most up-to-date information. Afterwards, we will install nginx:

sudo apt-get update
sudo apt-get install nginx

You will probably be prompted for your user’s password. Enter it to confirm that you wish to complete the installation. The appropriate software will be downloaded to your server and then automatically installed.

Step Two – Check your Web Server

You can access the default Nginx landing page to confirm that the software is running properly by visiting your server’s domain name or public IP address in your web browser.

If you do not have a spare domain name, or have no need for one, you can use your server’s public IP address. If you do not know your server’s IP address, you can get it a few different ways from the command line.

Continue reading this guide at Digital Ocean. This article has been used as an example of an Ecko WordPress theme. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

The post Installing Nginx on Ubuntu 14.04 with Server Caching appeared first on EckoThemes.