ip version 6 (ipv6) Configuration on Linux

Auto configuration  is completely independent. Getting the mac address of the card and giving a random ipv6 address.

Static ipv6 configuration
# ——————————————————————————-
auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

iface eth0 inet6 static
address 2001:db8::xxxx:yyyy
netmask 64
gateway 2001:db8::xxxx:yy:zzzz
# —————————————————————————–
Your /etc/hosts file should read localhost serverubuntu//change this to serverubuntu//add your static IP

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

#— Network Fail logs
#systemctl status network.service
network.service – LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed since Thu, 09 Feb 2012 00:11:18 -0500; 8min ago
CGroup: name=systemd:/system/network.service
├ 3850 /bin/bash ./ifup 59173567_autom tica boot
├ 3859 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 25236 /bin/bash ./ifup 59173567_autom tica boot
├ 25245 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 25507 /bin/bash ./ifup 59173567_autom tica boot
├ 25516 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 25903 /bin/bash ./ifup 59173567_autom tica boot
├ 25912 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 26168 /bin/bash ./ifup 59173567_autom tica boot
├ 26177 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 26427 /bin/bash ./ifup 59173567_autom tica boot
├ 26436 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 26686 /bin/bash ./ifup 59173567_autom tica boot
├ 26695 nmcli con up uuid 32aea3d4-ce65-42d1-a3ed-6a42c17a2111
├ 27471 /bin/bash ./ifup ALEJANDRO_autom tica boot
├ 27480 nmcli con up uuid f8a46744-7098-4eb6-8902-34df1bd351f5
├ 28228 /bin/bash ./ifup Auto_58915877 boot
├ 28234 nmcli con up uuid 80a61972-1616-431e-bcf3-d4660386ec35
├ 29174 /bin/bash ./ifup Auto_58915877 boot
└ 29180 nmcli con up uuid 80a61972-1616-431e-bcf3-d4660386ec35
Route Commands


Centos Configuration  or  RedHat


cat /etc/sysctl.conf





Apache enable Htaccess for directory


Php GD (GD Extension for php)

# apt-get install php5-gd

Proof that ;

$ php5 -m | grep -i gd


Xserver on Windows (Installing/Configuring PuTTy and Xming)

X-windows system, forwarding the display from the server to the PC.

Software must be installed on the PC to make this link work and the best software (so far) for this task is the PuTTy terminal emulator and the Xming X-window client.

PuTTy can be downloaded from http://www.chiark.greenend.org.uk/~sgtatham/putty/
Xming can be downloaded from http://sourceforge.net/project/downloading.php?group_id=156984&filename=Xming-6-9-0-31-setup.exe


Configuring Xming

Once Xming is installed, run the application called ‘XLaunch’ and verify that the settings are as shown:


Save the configuration and close XLaunch

Configuring PuTTy

After installing PuTTy, double-click on the PuTTy icon on the desktop and configure as shown:


The most important setting is the X11 Forwarding.

Without that set, the X-window system cannot find your PC for display



ref; www.geo.mtu.edu (pictures token)

Docker Shared Mount ( Mount directory from one container to another )



Ant Deployment – (Ant for building and deployment)

Cmd :  Ant Get Task

Cmd:  Apache Ant can do a lot of tasks automatically

Cmd : FTP –  TAR – Other



Ant Documentation(Reference) : http://ant.apache.org/manual/





Docker : Use host networking

Using host networking

If you use the host network driver for a container,

that container’s network stack is not isolated from the Docker host.

For instance, if you run a container which binds to port 80 and you use host networking,

the container’s application will be available on port 80 on the host’s IP address.

The host networking driver only works on Linux hosts,

and is not supported on Docker for Mac, Docker for Windows, or Docker EE for Windows Server.


Command Line :

--network host to the docker container create command.

In this case,

if a service container binds to port 80, only one service container can run on a given swarm node.

If your container or service publishes no ports, host networking has no effect.