Howdy, Stranger!

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


Kimsufi.... 4.99 euro dedicated server - Page 29
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.

Kimsufi.... 4.99 euro dedicated server

1262729313289

Comments

  • They don't use barebones. They just assemble motherboard, CPU, RAM, HDD on a singular open blade and they stick more of those servers into an 1U. This way they power up more servers on one line. They're water cooled and all that stuff. :)

  • zhuanyizhuanyi Member

    @ACaton said:
    An Atom in BHS would be fabulous. Much like rm_ I didn't think they were available, mostly due to costs here in Canada compared to France.

    Got one with them in the last sale, the BHS one has some decent network as well.

  • nimdynimdy Member

    @Maounique said:
    I see you have no IPv6 on the container, I suggest you use bridged (veth) configuration for the container as opposed to routed (venet) one which will give you an interface seen as eth0 inside the container. Then you can control it from inside and has other advantages for advanced networking. Also, you have a lot of stuff you dont need there.

    It doesn't want to work for me. If I set up a new container with bridged networking I get no interfaces in the container other than lo.

  • MaouniqueMaounique Host Rep, Veteran
    edited May 2014

    @nimdy said:
    It doesn't want to work for me. If I set up a new container with bridged networking I get no interfaces in the container other than lo.

    Yes, you need to add it manually for example, in debian:

    auto eth0
    iface eth0 inet static
    address xx.xx.xx.xx
    netmask 255.255.255.0
    gateway xx.xx.xx.yy
    
    auto eth0
    iface eth0 inet6 static
    address 2001:f00d:2001:000a:0000:0000:0000:0002
    netmask 64
    gateway 2001:f00d:2001:000a:0000:0000:0000:0001
    

    Save, exit, ifup eth0. It will autostart at boot.

  • earlearl Member

    @nimdy

    Not sure what you've done so far but probably best to just reinstall Promox. then

    nano /etc/sysctl.conf

    Add the following lines, save and exit..

     net.ipv6.conf.all.forwarding=1
     net.ipv6.conf.all.proxy_ndp=1
     net.ipv6.bindv6only=1
    

    In putty issue command

    sysctl -p

    Under the following file

    nano /etc/modules

    add the line, to enable ipv6 on reboot.. save and exit.

    ipv6

    From Proxmox ver 3.2 you can input ipv6 addresses directly in the network tab when creating your CT. No need to vzctl or use a private ip.

    Once Proxmox completes creating your CT, just select it and under the DNS tab remove the v4 DNS if you have a IPv6 only VPS and replace with Google's public DNS

    2001:4860:4860::8888

    You need to manually change the DNS for each new CT you create since the Global DNS setting for proxmox still does not recognize v6 address..

    The IP "2001:41D0:8:XXXX::1" is already used for the host node so when you create a CT I would start with something like..

    2001:41D0:8:XXXX::5

    This setting works for all 4 of my kimsufi servers.. anyways good luck.

    Thanked by 2linuxthefish berkay
  • nimdynimdy Member
    edited May 2014

    @earl
    Here's the weird thing. Out of annoyance I have reinstalled Proxmox from the Kimsufi control panel. The first thing I do when its finished reinstalling is SSH into the server and ping6 google.com. I still get the same

    root@abigail:~# ping6 google.com
    PING google.com(lhr14s21-in-x09.1e100.net) 56 data bytes

    I don't understand. It can obviously resolve the address as it shows "lhr14s21-in-x09.1e100.net", but there are no response lines. If I ping6 my own IPv6 address I get responses.

    The same goes for traceroute ipv6.google.com. It times out after the 30th line.

    If I do apt-get update it reloads most of the sources but gets stuck on one of the OVH mirrored ones as I can see this line:

    71% [Connecting to debian.mirrors.ovh.net (2001:41d0:b:9ca::1)] [Connecting to security.debian.org (2001:a78:5:0:216:35ff:fe7f:be4f)]

    This is fresh out of the box installation, so nothing I've done. I then followed your instructions and still get the same results. I'm stumped :(

  • MaouniqueMaounique Host Rep, Veteran

    Try install another os see if IPv6 works

  • earlearl Member
    edited May 2014

    @nimdy

    So you are doing this from the host node not a CT you created?

    if so I noticed your host name is different did you change any of the following?

    /etc/hosts

    /etc/hostname

    If so the host name you choose needs to resolve.. so eg. htpps://abigail.com:8006 should take you to proxmox.

    Also if you don't have a subscription to proxmox you need to change to the "Proxmox VE No-Subscription Repository"

    https://pve.proxmox.com/wiki/Package_repositories

    and it's tracetroute6 not traceroute.

  • nimdynimdy Member
    edited May 2014

    @earl

    Yes this is on the host node. I want to make sure that is working before creating CTs.

    The hostname is abigail, but the domain name is abigail.example.com.

    /etc/hosts shows:

    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1       localhost.localdomain localhost
    5.39.91.152     abigail.example.com   abigail
    # The following lines are desirable for IPv6 capable hosts
    #(added automatically by netbase upgrade)
    ::1     ip6-localhost ip6-loopback
    feo0::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    ff02::3 ip6-allhosts

    and

    /etc/hostname shows

    abigail.example.com

    I use Cloudflare for my domain DNS and both the A and AAAA records for abigail.example.com point to the Kimsufi box.

    I'm sure I have been able to ping 6 addresses on this box before. I may follow @Maounique's suggestion and install another distro to see if it is the Proxmox install that is borked for me. Hoping my HDD doesn't die on me - this will be the 4th time reinstalling in the last month. I don't think these boxes are as resilliant as VPS :0

    [edit]
    Oh sorry didn't realise there was a traceroute6 (makes sense I suppose). I have the same problems with traceroute6 :(

  • earlearl Member
    edited May 2014

    @nimdy

    I would try first without changing the host name cause the one that was assigned from OVH actually resolves..

    If not maybe you can ask in the kimsufi forum.. sure someone would know

  • MaouniqueMaounique Host Rep, Veteran
    edited May 2014

    Best way to install proxmox is to setup wheezy and go from there:
    http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy
    It might not have the OVH monitoring tools in case proxmox has them, but I use this setup now on my main computer as a desktop with Proxmox :) Sure, it is not recommended in production, but I hope the KS is not for production anyway...

    Thanked by 1marrco
  • earlearl Member

    @Maounique

    I do that on my KVM VPS.. Does work great.

    Thanked by 1Maounique
  • nimdynimdy Member
    edited May 2014

    @earl @Maounique

    I've got the same behaviour in Debian 7 installation too as well as a default Proxmox installation without me changing the hostname.

    I decided to boot into rescue mode and try ping6 / traceroute6 from there. I get different responses:

    root@rescue:~# ping google.com
    PING google.com (173.194.34.130) 56(84) bytes of data.
    64 bytes from lhr14s21-in-f2.1e100.net (173.194.34.130): icmp_req=1 ttl=54 time=12.7 ms
    64 bytes from lhr14s21-in-f2.1e100.net (173.194.34.130): icmp_req=2 ttl=54 time=12.7 ms
    64 bytes from lhr14s21-in-f2.1e100.net (173.194.34.130): icmp_req=3 ttl=54 time=12.8 ms
    traceroute to google.com (173.194.34.132), 30 hops max, 60 byte packets
     1  * * *
     2  rbx-g2-a9.fr.eu (178.33.100.75)  1.924 ms  1.911 ms  1.881 ms
     3  gsw-g1-a9.fr.eu (91.121.215.150)  4.760 ms gsw-g1-a9.fr.eu (91.121.131.214)  4.732 ms  4.662 ms
     4  * * *
     5  google.as15169.fr.eu (91.121.131.2)  5.523 ms  5.462 ms  5.462 ms
     6  72.14.238.228 (72.14.238.228)  18.822 ms 72.14.238.234 (72.14.238.234)  4.667 ms 72.14.238.228 (72.14.238.228)  4.966 ms
     7  209.85.245.83 (209.85.245.83)  5.260 ms  5.163 ms 209.85.245.72 (209.85.245.72)  9.750 ms
     8  209.85.242.78 (209.85.242.78)  40.733 ms  39.817 ms  39.744 ms
     9  209.85.253.197 (209.85.253.197)  13.787 ms 209.85.244.241 (209.85.244.241)  24.459 ms 209.85.253.197 (209.85.253.197)  24.151 ms
    10  209.85.253.115 (209.85.253.115)  14.194 ms  14.035 ms  13.981 ms
    11  lhr14s21-in-f4.1e100.net (173.194.34.132)  11.916 ms  12.859 ms  11.944 ms
    root@rescue:~# ping6 google.com
    PING google.com(lhr14s21-in-x09.1e100.net) 56 data bytes
    From fe80::da24:bdff:fe90:b0c0 icmp_seq=1 Destination unreachable: Beyond scope of source address
    From fe80::da24:bdff:fe90:b0c0 icmp_seq=2 Destination unreachable: Beyond scope of source address
    From fe80::da24:bdff:fe90:b0c0 icmp_seq=3 Destination unreachable: Beyond scope of source address
    root@rescue:~# traceroute6 google.com
    traceroute to google.com (2a00:1450:4009:804::1009), 30 hops max, 80 byte packets
     1  fe80::da24:bdff:fe90:b0c0%eth0 (fe80::da24:bdff:fe90:b0c0%eth0)  0.591 ms !H  0.849 ms !H  0.824 ms !H

    I would say that says that something outside of my server configuration is at fault, would you agree?

    Now to write a message to the Kimsufi forums and wait a few weeks for a response! :p

  • earlearl Member

    @nimdy I don't think IPv6 is enabled in rescue mode.. so looks normal.

  • earlearl Member
    edited May 2014

    @nimdy

    If you want to test it in rescue mode then..

    /etc/resolv.conf

    nameserver 2001:4860:4860::8888

    /etc/network/interfaces

    auto eth0
    iface eth0 inet6 static
            address 2001:41d0:8:XXXX::1
            netmask 64
            post-up /sbin/ip -f inet6 route add 2001:41d0:8:XXff:ff:ff:ff:ff dev eth0
            post-up /sbin/ip -f inet6 route add default via 2001:41d0:8:XXff:ff:ff:ff:ff
            pre-down /sbin/ip -f inet6 route del default via 2001:41d0:8:XXff:ff:ff:ff:ff
            pre-down /sbin/ip -f inet6 route del 2001:41d0:8:XXff:ff:ff:ff:ff dev eth0
    
    

    Then

    service networking restart


    you should be able to ping6 google.com

    Thanked by 1marrco
  • GunterGunter Member
    edited May 2014

    rm_ said: Well this is interesting. Earlier they said the 5 EUR ones are not available in BHS.

    I imagine this was early on.

  • nexmarknexmark Member

    Are they out of stock? How many IPV4 is available? I assume only 1.

  • It tells you on their site if they are out of stock or not. :)
    All Kimsufi servers get 1x IPv4 and 1x IPv6.

  • MaouniqueMaounique Host Rep, Veteran

    nexmark said: Are they out of stock?

    Most of the time.

    nexmark said: How many IPV4 is available? I assume only 1.

    Correct.

  • nexmarknexmark Member

    @Maounique said:
    Correct.

    Looks like a good secondary backup node for cPanel/WHM!
    Thanks

  • nimdynimdy Member
    edited May 2014

    @earl

    Thanks for that.

    Interesting, it works there...

    root@rescue:~# ping6 google.com
    PING google.com(lhr14s22-in-x0e.1e100.net) 56 data bytes
    64 bytes from lhr14s22-in-x0e.1e100.net: icmp_seq=1 ttl=54 time=573 ms
    64 bytes from lhr14s22-in-x0e.1e100.net: icmp_seq=2 ttl=54 time=12.8 ms
    64 bytes from lhr14s22-in-x0e.1e100.net: icmp_seq=3 ttl=54 time=12.8 ms
    64 bytes from lhr14s22-in-x0e.1e100.net: icmp_seq=4 ttl=54 time=12.8 ms
    64 bytes from lhr14s22-in-x0e.1e100.net: icmp_seq=5 ttl=54 time=12.7 ms

    Guess I'll add that to the Kimsufi board thread.

  • andrewnandrewn Member

    Whats the phone number for kimsufi? I heard that account validation can take weeks…..

  • wychwych Member

    @andrewn said:
    Whats the phone number for kimsufi? I heard that account validation can take weeks…..

    You dont get phone support.

  • Any type of support is via forum for KS.

  • earlearl Member

    @nimdy said:
    earl

    If that works then technically there is nothing wrong on OVH side..

    As I mentioned, reload with the proxmox image, change to the no subscription repo and follow the guide I posted.. don't change any other settings and v6 should work.

  • nimdynimdy Member

    @earl said:
    As I mentioned, reload with the proxmox image, change to the no subscription repo and follow the guide I posted.. don't change any other settings and v6 should work.

    I'll try again. Fourth time lucky? :p

  • nimdynimdy Member

    @earl

    Nope, still no luck from a standard install using your steps. I really cant understand it. The people on the Kimsufi boards are saying my v6 IP isn't pingable - 2001:41d0:8:9d98::1 and asking if I have made any firewall changes. I have simply installed the Proxmox template and SSH'd in, no config changes, other than your steps. I'm baffled. I'm sure I had IPv6 working on my first install a couple of weeks ago. Wish I hadn't wiped it :(

  • J1021J1021 Member

    I tried using UptimeRobot to monitor my IPv6 and it kept reporting as down. Could be the monitor node though I guess.

    Though sometimes I am able to connect to ftp.debian.org via IPv6.

  • MaouniqueMaounique Host Rep, Veteran

    @nimdy said:
    earl

    Nope, still no luck from a standard install using your steps. I really cant understand it. The people on the Kimsufi boards are saying my v6 IP isn't pingable - 2001:41d0:8:9d98::1 and asking if I have made any firewall changes. I have simply installed the Proxmox template and SSH'd in, no config changes, other than your steps. I'm baffled. I'm sure I had IPv6 working on my first install a couple of weeks ago. Wish I hadn't wiped it :(

    Try the other way, put up wheezy, test IPv6, add proxmox over it, test ipv6, then make a vm, test ipv6 see where it breaks.

  • earlearl Member

    @nimdy said:

    Hmm.. what I find odd is that I can't ping your gateway.. regardless of your IP I would think you should be able to ping your gateway.

    You can try @Maounique suggest and try a different OS, other than that I suppose you would have to wait for support to get back to you on it..

Sign In or Register to comment.