Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Offers
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

★ VirMach ★ Black Friday & Cyber Week 2018 ★ RAID 10 SSD ★ OpenVZ & KVM ★ Check inside for offers!

1…323324326328329…548

Comments

  • toumi111toumi111 Member
    edited December 2019

    Thanked by 2uptime FrankZ
  • ben47955ben47955 Member

    Weird but ok

    Thanked by 1toumi111
  • FAT32FAT32 Administrator, Deal Compiler Extraordinaire

    At this pace we can reach page 200 in 36 hours lol

  • ben47955ben47955 Member

    Maybe

  • imokimok Member

    Maybe not

  • ZA_capetownZA_capetown Member

    Worth a try

  • ben47955ben47955 Member

    Yeah

  • donlidonli Member

  • uptimeuptime Member

    Magic 8-ball says ...

    Thanked by 1FrankZ
  • pullangcubopullangcubo Member

    Hey, any more bench from your Cyber Week stash?

    Didn't know that Atlanta nodes had nice network, otherwise I would have grabbed some for me.

  • FrankZFrankZ Barred

    pullangcubo said: Didn't know that Atlanta nodes had nice network, otherwise I would have grabbed some for me.

    It took me by surprise as well. Since having a poor experience in 2016, I had stayed away from that VirMach location. Things have definitely changed for the better. Almost wish I had another one. :)

    Thanked by 1pullangcubo
  • donlidonli Member
    edited December 2019

    For those people at provider locations that only support IPv4 here is a short tutorial I've written to show how to use Hurricane Electric's free tunnelbroker to give a VPS running debian linux at somewhere like ColoCrossing IPv6 connectivity.

    For this example we assume the following:

    1 - The IP address of your IPv4-only VPS is 1.2.3.4
    (wherever you see this 1.2.3.4 address in this tutorial, replace it with the actual IPv4 address of your IPv4-only VPS)

    2 - You have installed the Debian 9 operating system (or similar operating system that uses the same format for the /etc/network/interfaces file).

    3 - The IPv4 address of your IPv4-only VPS is pingable (if you have some firewall preventing this or have otherwise removed the ability of your IPv4 VPS to be pinged you must fix this or else Hurricane Electric won't make a tunnel to it).

    Let's set up a IPv4 to IPv6 tunnel:

    Register to create a free account at tunnelbroker.net :
    https://tunnelbroker.net/register.php

    Once registered log in to your tunnelbroker.net account

    Under [User Functions]
    Click: Create Regular Tunnel

    IPv4 Endpoint (Your side) [ 1.2.3 4 ] <- (the actual IPv4 address of your IPv4-only VPS goes there).

    Available Tunnel Servers: < (choose the one that is closest geographically to your IPv4-only VPS)
    (my IPv4-only VPS was in Chicago, so I chose Chicago).
    (*) Chicago, IL US xxx.xxx.xxx.xx

    Now click:
    [ Create Tunnel ]

    And wait (and wait a little more). If tunnel creation succeeded you'll get something like:

    Tunnel ID:  12345
Creation Date:Dec 10, 2019
Description:
IPv6 Tunnel Endpoints
Server IPv4 Address:128.1.2.3                                        < (the IPv4 address of the HE tunnel endpoint)
Server IPv6 Address:5555:6666:7777:1111::1/64           < (the IPv6 address of the HE tunnel endpoint)
Client IPv4 Address:1.2.3.4                                             < (that'll be the actual IPv4 address of your IPv4-only VPS)
Client IPv6 Address:5555:6666:7777:1111::2/64            < (that'll be the new IPv6 address of your IPv4-only VPS)
Routed IPv6 Prefixes
Routed /64:5555:6666:7777:1111::/64
Routed /48:Assign /48
DNS Resolvers
Anycast IPv6 Caching Nameserver:5555:6666:20::2
Anycast IPv4 Caching Nameserver:74.82.42.42
rDNS DelegationsEdit
rDNS Delegated NS1:
rDNS Delegated NS2:
rDNS Delegated NS3:
rDNS Delegated NS4:
rDNS Delegated NS5:

    Now click on the [Example Configurations] tab

    And select the [Debian/Ubuntu] dropbox:

    You'll see something like:

    auto he-ipv6
iface he-ipv6 inet6 v4tunnel
        address 5555:6666:7777:1111::2
        netmask 64
        endpoint 128.1.2.3 
        local 1.2.3.4
        ttl 255
        gateway 5555:6666:7777:1111::1

    The system generates an example based on your specific tunnel.
    You need to paste EXACTLY what is shown to you in that tab into the file /etc/network/interfaces on your debian linux VPS.

    # cd /etc/network

    (make a copy of the original interfaces file just in case you need it)

    # cp interfaces interfaces.orig

    (Edit "interfaces" to add at the botton the exact info cut from the [Example Configurations] page:

    # edit interfaces

    (add to the bottom exactly what you copied from the Examples Configuration tab)
    (replace this one with the values specifically generated for your information)

    auto he-ipv6
iface he-ipv6 inet6 v4tunnel
        address 5555:6666:7777:1111::2
        netmask 64
        endpoint 128.1.2.3
        local 1.2.3.4
        ttl 255
        gateway 5555:6666:7777:1111::1

    (start the Ipv4 to IPv6 tunnel)

    # ifup he-ipv6

    Now test IPv6 connectivity from your formerly IPv4-only VPS:

    # ping6  -c 4 ipv6.google.com

    PING ipv6.google.com(ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e)) 56 data bytes
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=1 ttl=57 time=1.67 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=2 ttl=57 time=1.75 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=3 ttl=57 time=1.81 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=4 ttl=57 time=9.40 ms

    --- ipv6.google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 1.674/3.661/9.406/3.317 ms

    #

    You should now be able to reach an IPv6-only VPS from your formerly IPv4-only VPS.

    Assume you have an IPv6 only VPS with IP address 1111:2222:3333:4444:0000:0000:0000:0001

    With your new IPv4 to IPv6 tunnel you can now ping it from your formerly IPv4-only VPS:

    #  ping6 -c 4  1111:2222:3333:4444:0000:0000:0000:0001

    PING 1111:2222:3333:4444:0000:0000:0000:0001 (1111:2222:3333:4444::::0001) 56 data bytes
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=1 ttl=56 time=19.6 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=2 ttl=56 time=19.3 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=3 ttl=56 time=19.2 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=4 ttl=56 time=21.6 ms

    --- 1111:2222:3333:4444:0000:0000:0000:0001 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3014ms
    rtt min/avg/max/mdev = 19.244/19.967/21.686/1.013 ms
    #

    You can ssh from your previously IPv4-only VPS to your IPv6-only one:

    $ ssh  yourusername@1111:2222:3333:4444:0000:0000:0000:0001

    or sftp to it:

    $ sftp  yourusername@[ 1111:2222:3333:4444:0000:0000:0000:0001]    < (note brackets needed around IPv6 address for sftp)

    Anytime you want to temporarily disable the tunnel, just do:

    # ifdown he-ipv6

    And to bring it back up:

    # ifup he-ipv6

    To delete the tunnel:

    https://tunnelbroker.net

    Select the tunnel to delete

    Then click on [Delete Tunnel]

    (That's all).

    Thanked by 11uptime FrankZ saibal plumberg randomq dTQzBen8 KernelPanic pullangcubo ZA_capetown alilet RecD
  • uptimeuptime Member

  • plumbergplumberg Veteran, Megathread Squad

    @donli said:
    For those people at provider locations that only support IPv4 here is a short tutorial I've written to show how to use Hurricane Electric's free tunnelbroker to give a VPS running debian linux at somewhere like ColoCrossing IPv6 connectivity.

    For this example we assume the following:

    1 - The IP address of your IPv4-only VPS is 1.2.3.4
    (wherever you see this 1.2.3.4 address in this tutorial, replace it with the actual IPv4 address of your IPv4-only VPS)

    2 - You have installed the Debian 9 operating system (or similar operating system that uses the same format for the /etc/network/interfaces file).

    3 - The IPv4 address of your IPv4-only VPS is pingable (if you have some firewall preventing this or have otherwise removed the ability of your IPv4 VPS to be pinged you must fix this or else Hurricane Electric won't make a tunnel to it).

    Let's set up a IPv4 to IPv6 tunnel:

    Register to create a free account at tunnelbroker.net :
    https://tunnelbroker.net/register.php

    Once registered log in to your tunnelbroker.net account

    Under [User Functions]
    Click: Create Regular Tunnel

    IPv4 Endpoint (Your side) [ 1.2.3 4 ] <- (the actual IPv4 address of your IPv4-only VPS goes there).

    Available Tunnel Servers: < (choose the one that is closest geographically to your IPv4-only VPS)
    (my IPv4-only VPS was in Chicago, so I chose Chicago).
    (*) Chicago, IL US xxx.xxx.xxx.xx

    Now click:
    [ Create Tunnel ]

    And wait (and wait a little more). If tunnel creation succeeded you'll get something like:

    Tunnel ID:  12345
Creation Date:Dec 10, 2019
Description:
IPv6 Tunnel Endpoints
Server IPv4 Address:128.1.2.3                                        < (the IPv4 address of the HE tunnel endpoint)
Server IPv6 Address:5555:6666:7777:1111::1/64           < (the IPv6 address of the HE tunnel endpoint)
Client IPv4 Address:1.2.3.4                                             < (that'll be the actual IPv4 address of your IPv4-only VPS)
Client IPv6 Address:5555:6666:7777:1111::2/64            < (that'll be the new IPv6 address of your IPv4-only VPS)
Routed IPv6 Prefixes
Routed /64:5555:6666:7777:1111::/64
Routed /48:Assign /48
DNS Resolvers
Anycast IPv6 Caching Nameserver:5555:6666:20::2
Anycast IPv4 Caching Nameserver:74.82.42.42
rDNS DelegationsEdit
rDNS Delegated NS1:
rDNS Delegated NS2:
rDNS Delegated NS3:
rDNS Delegated NS4:
rDNS Delegated NS5:

    Now click on the [Example Configurations] tab

    And select the [Debian/Ubuntu] dropbox:

    You'll see something like:

    auto he-ipv6
iface he-ipv6 inet6 v4tunnel
        address 5555:6666:7777:1111::2
        netmask 64
        endpoint 128.1.2.3 
        local 1.2.3.4
        ttl 255
        gateway 5555:6666:7777:1111::1

    The system generates an example based on your specific tunnel.
    You need to paste EXACTLY what is shown to you in that tab into the file /etc/network/interfaces on your debian linux VPS.

    # cd /etc/network

    (make a copy of the original interfaces file just in case you need it)

    # cp interfaces interfaces.orig

    (Edit "interfaces" to add at the botton the exact info cut from the [Example Configurations] page:

    # edit interfaces

    (add to the bottom exactly what you copied from the Examples Configuration tab)
    (replace this one with the values specifically generated for your information)

    auto he-ipv6
iface he-ipv6 inet6 v4tunnel
        address 5555:6666:7777:1111::2
        netmask 64
        endpoint 128.1.2.3
        local 1.2.3.4
        ttl 255
        gateway 5555:6666:7777:1111::1

    (start the Ipv4 to IPv6 tunnel)

    # ifup he-ipv6

    Now test IPv6 connectivity from your formerly IPv4-only VPS:

    # ping6  -c 4 ipv6.google.com

    PING ipv6.google.com(ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e)) 56 data bytes
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=1 ttl=57 time=1.67 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=2 ttl=57 time=1.75 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=3 ttl=57 time=1.81 ms
    64 bytes from ord37s18-in-x0e.1e100.net (2607:f8b0:4009:805::200e): icmp_seq=4 ttl=57 time=9.40 ms

    --- ipv6.google.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 1.674/3.661/9.406/3.317 ms

    #

    You should now be able to reach an IPv6-only VPS from your formerly IPv4-only VPS.

    Assume you have an IPv6 only VPS with IP address 1111:2222:3333:4444:0000:0000:0000:0001

    With your new IPv4 to IPv6 tunnel you can now ping it from your formerly IPv4-only VPS:

    #  ping6 -c 4  1111:2222:3333:4444:0000:0000:0000:0001

    PING 1111:2222:3333:4444:0000:0000:0000:0001 (1111:2222:3333:4444::::0001) 56 data bytes
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=1 ttl=56 time=19.6 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=2 ttl=56 time=19.3 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=3 ttl=56 time=19.2 ms
    64 bytes from 1111:2222:3333:4444:0000:0000:0000:0001: icmp_seq=4 ttl=56 time=21.6 ms

    --- 1111:2222:3333:4444:0000:0000:0000:0001 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3014ms
    rtt min/avg/max/mdev = 19.244/19.967/21.686/1.013 ms
    #

    You can ssh from your previously IPv4-only VPS to your IPv6-only one:

    $ ssh  yourusername@1111:2222:3333:4444:0000:0000:0000:0001

    or sftp to it:

    $ sftp  yourusername@[ 1111:2222:3333:4444:0000:0000:0000:0001]    < (note brackets needed around IPv6 address for sftp)

    Anytime you want to temporarily disable the tunnel, just do:

    # ifdown he-ipv6

    And to bring it back up:

    # ifup he-ipv6

    To delete the tunnel:

    https://tunnelbroker.net

    Select the tunnel to delete

    Then click on [Delete Tunnel]

    (That's all).

    Awesome. Any help to get this working on Windows server or win 10 please?

  • donlidonli Member

    @plumberg said:

    Awesome. Any help to get this working on Windows server or win 10 please?

    Instead of seeing the dropbox for the values for [Debian/Ubuntu] you can choose the to see the commands to start your tunnel for:

    [Windows 10]

    or

    [Windows 2000/XP]

    or

    [Windows Vista/2008/7/8]

  • imokimok Member

    @donli said:
    tunnel

    Thanked by 1uptime
  • uptimeuptime Member

    what a magnificent creature, in its natural habitat

    Thanked by 1FrankZ
  • imokimok Member
    edited December 2019

    It's time to sleep.

    New week is coming.

    Thanked by 1uptime
  • imokimok Member

    uptime said: natural habitat

    Earth

    Thanked by 2uptime FrankZ
  • job0121job0121 Member

    Checking in

    Thanked by 1uptime
  • imokimok Member

    Good morning

    Thanked by 1uptime
  • imokimok Member

    5 hours and you haven't posted anything.

    5 hours!

    You dissapoint me.

  • FAT32FAT32 Administrator, Deal Compiler Extraordinaire

    @imok Sorry.

    Thanked by 1imok
  • imokimok Member

    It's time to go to work again.

    Monday. What is weird is that I haven't woken up reneging in my mind (until I visited this thread of course).

    Maybe good times are coming faster than I thought.

  • plumbergplumberg Veteran, Megathread Squad

    @donli said:

    @plumberg said:

    Awesome. Any help to get this working on Windows server or win 10 please?

    Instead of seeing the dropbox for the values for [Debian/Ubuntu] you can choose the to see the commands to start your tunnel for:

    [Windows 10]

    or

    [Windows 2000/XP]

    or

    [Windows Vista/2008/7/8]

    I tried that. No luck. Not sure if there is anything I need to do to activate the tunnel config on win 10. Thnx

  • imokimok Member

    I remember last time I saw my great grandmother.

    Alive. She was really sick with throat cancer. She was lying in bed, too skinny. She was suffering really bad. Most of my memories about her are not from the happy days.

    And then dead. Lying in her coffin with purple clothes. I was so curious and touched her chest. It was solid as a rock. I had never touched a dead body before. Instant regret.

    Of course that was around 20 years ago.

    Thanked by 4uptime FrankZ randomq saibal
  • ben47955ben47955 Member

    Where is page 197 ?

  • imokimok Member
    edited December 2019

    Next to the 196.

    But not yet.

  • ben47955ben47955 Member

    Thanks for the info

  • uptimeuptime Member

    Thanked by 3FAT32 alilet FrankZ
This discussion has been closed.