31 May 2017

IPv4 and IPv6

Theory
Here are some pages on which you can get information about IPv6:

  • http://en.wikipedia.org/wiki/IPv6
  • http://www.olympus-zone.net/page_1033_en_Blue.html
  • IPv6 at Xoftmade

    For our facilities, we have the following /32 Netz: 2001:41D0::/32

    For the routing we use Cisco routers 6k (6509 SUP720 card with the native IPv6 packets to route).

    Every customer with a dedicated server at Xoftmade has a fixed IPv4, one or more IpFailover and 18,446,744,073,709,551,616 IPv6 addresses (ie a /64) are attached to the IPv4 server.

    So you can with a dedicated server:

    • Use multiple SSL certificates
    • Several anonymous FTP operations
    • Web-hosting service run (IP-based)
    • A public VPN set up based on the dedicated server
    • Etc. ..

    Preparation

    • The server must be running with a IPv6 kernel. This kernel is available by netboot Netboot
    • Find your own IPv6 address in manager v3 Manager

    An IPv6 example
    An IPv4:

    213.186.35.9/24

    IPv6 will be the following:

    2001:41d0:1:209::/64

    Here are examples from which you can configure IPv6 on your dedicated server:

    2001:41d0:1:209::1/64
    2001:41d0:1:209:FF:FF:FF:FF/64
    2001:41d0:1:209:A::1:1/64
    2001:41d0:1:209::1:B:F/64
    2001:41d0:1:209:1:1:1:1/64

    The following notations are the same:

    2001:41d0:1:209::1:B:F/64
    2001:41d0:1:209:0:1:B:F/64
    2001:41D0:0001:0209:0000:0001:000B:0000F/64

    But you can :: place only once.

    An example ifconfig
    Once you’ve switched the server to IPv6 kernel, after the reboot ifconfig already has IPv6 info:

    adr inet6: fe80::2e0:4cff:fe99:88d0/64 Scope:Lien

    This shows that IPv6 works on the network.Route: IPv6 Gateway

    The router (default gateway) for each IPv6 is always on IP: v:6:FF:FF:FF:FF:FF

    For example:

    The IPv6 server: 2001:41D0:1:46e::/64 to 2001:41D0:1:4 + 5x FF.
    IPv6 Gateway: 2001:41D0:1:4FF:FF:FF:FF:FF

    The IPv6 server: 2001:41d0:1:209::/64 to 2001:41d0:1:2 + 5x FF.
    IPv6 Gateway: 2001:41d0:1:2FF:FF:FF:FF:FF

    IPv6 Installation

    To be used for all Linux distributions in the examples below, the server has IPv6, the IPv6 kernel and it is has the address from the manager. A uname-a indicates that an IPv6 kernel, and the command shows us that ifconfig The Router IPv6 already have a local link.

    Redhat, CentOS, Fedora

    The dedicated server we are running configure with the IPv4: 213.186.35.9/24, this will lead to the following IPv6: 2001:41d0:1:209::/64.
    The following examples are identical for Redhat 7.2, Fedora and CentOS. You can therefore also use it for Xoftmade Release Plesk, (based on CentOS).

    ifconfig
    eth0 Lien encap:Ethernet HWaddr 00:E0:4C:99:88:D0
    inet adr:213.186.35.9 Bcast:213.186.35.255 Masque:255.255.255.0
    adr inet6: fe80::2e0:4cff:fe99:88d0/64 Scope:Lien

    We do 2001:41D0:1:209::1/64 and 2001:41D0:1:209::5/64 Add to eth0 :

    /sbin/ifconfig eth0 inet6 add 2001:41D0:1:209::1/64
    /sbin/ifconfig eth0 inet6 add 2001:41D0:1:209::5/64

    So IPv6 does not disappear at the next reboot it must be added in the configuration file of the eth0 interface. We will create a copy of the file and then edit it:

    cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth.backup
    pico /etc/sysconfig/network-scripts/ifcfg-eth0

    Here are the contents of the file after the change. The red options were added:

    DEVICE=eth0
    BOOTPROTO=static
    IPADDR=213.186.35.9
    NETMASK=255.255.255.0
    ONBOOT=yes
    GATEWAY=213.186.35.254
    IPV6INIT=yes
    IPV6ADDR=”2001:41D0:1:209::5/64″
    IPV6ADDR_SECONDARIES=”2001:41D0:1:209::5/64″

    All of the following IPv6 must be located in the line IPV6ADDR_SECONDARIES
    It has the file /etc/sysconfig/network edited this line and add NETWORKING_IPV6=yes

    # This line commented out by System Configuration
    NETWORKING=yes
    HOSTNAME=ghost.Xoftmade.net
    GATEWAY=0.0.0.0
    NETWORKING_IPV6=yes

    It must be restarted with /etc/init.d/network restart
    Note: It is possible that Redhat displays an error: “modprobe: Can not open dependencies file …” You can ignore this, it does not affect the result.

    ifconfig ?

    ifconfig
    eth0 Lien encap:Ethernet HWaddr 00:E0:4C:99:88:D0
    inet adr:213.186.35.9 Bcast:213.186.35.255 Masque:255.255.255.0
    adr inet6: 2001:41d0:1:209::1/64 Scope:Global
    adr inet6: 2001:41d0:1:209::5/64 Scope:Global
    adr inet6: fe80::2e0:4cff:fe99:88d0/64 Scope:Lien

    You may be able to ping the gateway but can not use your ipv6, in this case add a default route:

    route -A inet6 add default gw votre.gateway.ipv6 dev eth0

    For example:

    route -A inet6 add default gw 2001:41d0:1:2FF:FF:FF:FF:FF dev eth0

    Verification

    Ping6 Test

    We ping6 to the router:

    ping6 -c 4 2001:41d0:1:2FF:FF:FF:FF:FF
    PING 2001:41d0:1:2FF:FF:FF:FF:FF(2001:41d0:1:2ff:ff:ff:ff:ff) from 2001:41d0:1:209::5 : 56 data bytes
    64 bytes from 2001:41d0:1:2ff:ff:ff:ff:ff: icmp_seq=0 hops=64 time=127.977 msec
    64 bytes from 2001:41d0:1:2ff:ff:ff:ff:ff: icmp_seq=1 hops=64 time=24.242 msec
    64 bytes from 2001:41d0:1:2ff:ff:ff:ff:ff: icmp_seq=2 hops=64 time=205.934 msec
    64 bytes from 2001:41d0:1:2ff:ff:ff:ff:ff: icmp_seq=3 hops=64 time=129.853 msec

    4 packets transmitted, 4 packets received, 0% packet loss
    round-trip min/avg/max/mdev = 24.242/122.001/205.934/64.613 ms

    Traceroute6 Test

    Do traceroute6 to IPv6 DNS Servers by Afnic:

    traceroute6 2001:660:3006:1::1:1
    traceroute to 2001:660:3006:1

    1:1 (2001:660:3006:1

    1:1) from 2001:41d0:1:209::5, 30 hops max, 16 byte packets
    1 2001:41d0:1:2ff:ff:ff:ff:ff (2001:41d0:1:2ff:ff:ff:ff:ff) 0.726 ms 0.508 ms *
    2 * * *
    3 renater.sfinx.tm.fr (2001:660:a100:2::1) 0.879 ms 0.787 ms 0.721 ms
    4 afnic.sfinx.tm.fr (2001:660:a100:2::101) 1.13 ms 1.131 ms 1.099 ms
    5 ns3.nic.fr (2001:660:3006:1::1:1) 0.933 ms 0.954 ms 0.922 ms

    It is working.
    There are websites that can offer a traceroute6 ping6 or tests online. You can use these function to check with the added IPs.

    Share this
    15 Aug 2016

    Ways To Speed Up WordPress Websites

    This article is about Ways To Speed Up WordPress Websites, as wordpress is a great and famous platform so people are making tons of websites on it. But this CMS has a weak point too which is its slow speed, without taking proper steps while making your website on wordpress it will end up in a mess and ultimately you will loose your precious traffic due to this issue. So there are several ways to improve and speed up your wordpress websites such as:

    1. Choose a Good Theme:
    Always choose good themes for your website and never use nulled themes for your website as it has many loopholes in it. There are several tools available where you can test the theme speed before choosing it for your website. Such as google developer speed testing or (https://tools.pingdom.com) read more

    Share this
    17 Jun 2016

    Payoneer withdrawal to Local Bank in Pakistan is now free!

    Payoneer withdraw to Local Bank in Pakistan is now supported and free too. You can withdraw minimum $200 to maximum $1000 anytime. And the good news is that there is no transaction fee involved.

    How to add local Pakistani Bank account in your Payoneer account:

    1. Login to Payoneer Account
    2. Click on Withdraw->To Bank Account
    3. Add a Bank Account
    4. Provide all details and submit application.
    5. Payoneer will approve your account within 5 minutes.

    Share this
    04 Jun 2016

    How to stop hacking attempts on xmlrpc.php in WordPress Blogs?

    While Monitoring my server i noticed bulk traffic to xmlrpc.php files in my hosted websites. As this is a shared server, so there are over 40 wordpress installations in it. And that day i have noticed a continuous attack on 8 websites, a single request on xmlrpc.php took average 200MB to 250MB of memory and these requests were continuous 10 to 20 per second on each website. Which results in system instability and caused my server out of memory then eventually crashed.

    Now a days hackers started using xmlrpc.php instead of wp-login.php to execute their brute force attacks and the problem is, since wordpress version 3.5 we can’t disable the use of xmlrpc.php at least not from wordpress settings. But there are few ways, lets discuss them one by one.

    1. Deleting xmlrpc.php
    This is not recommended as after every wordpress update this file will be replaced so its not the smartest way to deal with.

    read more

    Share this

    © 2008-17 XOFTMADE Web Solutions. All rights reserved.

    Click Me