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 › General
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/Soyoustart/OVH Rise New Price

1…232233235237238…662

Comments

  • tfgp99tfgp99 Member

    @aryanraj said:

    @darkimmortal said:

    @fredo1664 said:
    I have written about this a while ago in this thread. It only works with Java8 32 bits.

    Any 32 bit jre is fine, I use 11 x86 from https://adoptium.net/en-GB/temurin/archive/?version=11 plus icedtea web

    any alternative options? like do i need to have 32bit windows installed?

    https://nicolas.busseneau.fr/en/blog/2021/07/ovh-soyoustart-install-iso-image
    I've used this before, works properly.

    Thanked by 2ChillBird ariq01
  • JerryHouJerryHou Member

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    This is very handy, I will bookmark this and try it in my next setup. :)

    Thanked by 1emgh
  • ariq01ariq01 Member

    @yopp said:
    And the winner is @ariq01!
    Drop me your nic handle in dm and server is yours!

    Thank you, server received...

    Thanked by 2yopp maverick
  • yoppyopp Member

    @ariq01 said: Thank you, server received...

    Enjoy!

    Thanked by 1ariq01
  • yoppyopp Member

    If anyone interested, there are RISE-LE-1 & RISE-LE-3 in stock:

    KS-A
------
64g    1× 480  SSD              🤷‍♀️

KS-LE-A
------
16g    3× 2000 SATA             🤷‍♀️

KS-LE-B
------
32g    ECC 2× 2000 SATA         🤷‍♀️
32g    ECC 2× 450 NVMe          🤷‍♀️

KS-LE-C
------
32g    ECC 2× 2000 SATA         🤷‍♀️
32g    ECC 2× 480  SSD          🤷‍♀️

KS-LE-D
------
16g    1× 240  SSD              🤷‍♀️
32g    1× 240  SSD              🤷‍♀️

KS-LE-E
------
64g    ECC 2× 480  SSD          🤷‍♀️
64g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-1
------
16g    2× 480  SSD              🤷‍♀️
16g    2× 960  SSD              🤷‍♀️
16g    3× 2000 SATA             🤷‍♀️
16g    3× 480  SSD              🤷‍♀️
32g    2× 480  SSD              🤷‍♀️
32g    2× 960  SSD              🤷‍♀️
32g    3× 2000 SATA             🤷‍♀️
32g    3× 480  SSD              🤷‍♀️

KS-LE-2
------
32g    ECC 2× 1920  SSD         🤷‍♀️
32g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-3
------
64g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-4
------
32g    2× 450 NVMe              BHS: 1H | FRA: 1H
64g    2× 450 NVMe              BHS: 1H | GRA: 1H

KS-LE-5
------
32g    ECC 2× 4000 SATA         BHS: 1H | GRA: 1H | RBX: 1H | WAW: 1H

KS-LE-6
------
128g   ECC 2× 450 NVMe          BHS: 1H | FRA: 1H (LOW) | GRA: 1H | RBX: 1H | SBG: 1H (LOW) | WAW: 1H
64g    ECC 2× 450 NVMe          BHS: 1H | FRA: 1H | GRA: 1H | RBX: 1H | SBG: 1H | WAW: 1H (LOW)

SYS-LE-1
------
32g    ECC 2× 4000 SATA         BHS: 1H (LOW)
32g    ECC 2× 512 NVMe          BHS: 1H | GRA: 1H | SBG: 1H (LOW)
32g    ECC 2× 960 NVMe          FRA: 1H | GRA: 1H | WAW: 1H

SYS-LE-2
------
32g    ECC 2× 1920 NVMe         BHS: 1H
32g    ECC 2× 960 NVMe          BHS: 1H | FRA: 1H | LON: 1H (LOW) | RBX: 1H
64g    ECC 2× 1920 NVMe         🤷‍♀️
64g    ECC 2× 960 NVMe          BHS: 1H | FRA: 1H | LON: 1H | RBX: 1H

SYS-LE-3
------
32g    ECC 4× 12000 SATA                🤷‍♀️

RISE-LE-1
------
64g    ECC 2× 1920 NVMe         FRA: 1H (LOW)
64g    ECC 2× 3840 NVMe         🤷‍♀️

RISE-LE-2
------
32g    ECC 2× 1920 NVMe         🤷‍♀️

RISE-LE-3
------
64g    ECC 2× 1920 NVMe         BHS: 1H

RISE-LE-4
------
128g   ECC 2× 1920 NVMe         🤷‍♀️

RISE-LE-5
------
256g   ECC 2× 3840 NVMe         🤷‍♀️
256g   ECC 2× 3840  SSD         🤷‍♀️
    Thanked by 4JerryHou ariq01 Joao336 mycloud
  • loayloay Member

    @JerryHou said:

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    This is very handy, I will bookmark this and try it in my next setup. :)

    For eaiser nat configuration with Proxmox check this code:
    https://lowendtalk.com/discussion/197821/nat-manager-py-manage-nat-port-forwarding-for-proxmox-vms-and-containers

    Thanked by 2JerryHou tridinebandim
  • emghemgh Member, Megathread Squad
    edited December 2024

    Yesterday night I did my books finally for all BF buys etc

    I also did it for the KS-A

    Second time

    One entry for the purchase
    One for the payment
    One for the refund invoice
    One for the actual refund received

    Can’t recommend

  • wuckwuck Member

    @yopp said:
    If anyone interested, there are RISE-LE-1 & RISE-LE-3 in stock:

    KS-A
------
64g    1× 480  SSD              🤷‍♀️

KS-LE-A
------
16g    3× 2000 SATA             🤷‍♀️

KS-LE-B
------
32g    ECC 2× 2000 SATA         🤷‍♀️
32g    ECC 2× 450 NVMe          🤷‍♀️

KS-LE-C
------
32g    ECC 2× 2000 SATA         🤷‍♀️
32g    ECC 2× 480  SSD          🤷‍♀️

KS-LE-D
------
16g    1× 240  SSD              🤷‍♀️
32g    1× 240  SSD              🤷‍♀️

KS-LE-E
------
64g    ECC 2× 480  SSD          🤷‍♀️
64g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-1
------
16g    2× 480  SSD              🤷‍♀️
16g    2× 960  SSD              🤷‍♀️
16g    3× 2000 SATA             🤷‍♀️
16g    3× 480  SSD              🤷‍♀️
32g    2× 480  SSD              🤷‍♀️
32g    2× 960  SSD              🤷‍♀️
32g    3× 2000 SATA             🤷‍♀️
32g    3× 480  SSD              🤷‍♀️

KS-LE-2
------
32g    ECC 2× 1920  SSD         🤷‍♀️
32g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-3
------
64g    ECC 4× 2000 SATA         🤷‍♀️

KS-LE-4
------
32g    2× 450 NVMe              BHS: 1H | FRA: 1H
64g    2× 450 NVMe              BHS: 1H | GRA: 1H

KS-LE-5
------
32g    ECC 2× 4000 SATA         BHS: 1H | GRA: 1H | RBX: 1H | WAW: 1H

KS-LE-6
------
128g   ECC 2× 450 NVMe          BHS: 1H | FRA: 1H (LOW) | GRA: 1H | RBX: 1H | SBG: 1H (LOW) | WAW: 1H
64g    ECC 2× 450 NVMe          BHS: 1H | FRA: 1H | GRA: 1H | RBX: 1H | SBG: 1H | WAW: 1H (LOW)

SYS-LE-1
------
32g    ECC 2× 4000 SATA         BHS: 1H (LOW)
32g    ECC 2× 512 NVMe          BHS: 1H | GRA: 1H | SBG: 1H (LOW)
32g    ECC 2× 960 NVMe          FRA: 1H | GRA: 1H | WAW: 1H

SYS-LE-2
------
32g    ECC 2× 1920 NVMe         BHS: 1H
32g    ECC 2× 960 NVMe          BHS: 1H | FRA: 1H | LON: 1H (LOW) | RBX: 1H
64g    ECC 2× 1920 NVMe         🤷‍♀️
64g    ECC 2× 960 NVMe          BHS: 1H | FRA: 1H | LON: 1H | RBX: 1H

SYS-LE-3
------
32g    ECC 4× 12000 SATA                🤷‍♀️

RISE-LE-1
------
64g    ECC 2× 1920 NVMe         FRA: 1H (LOW)
64g    ECC 2× 3840 NVMe         🤷‍♀️

RISE-LE-2
------
32g    ECC 2× 1920 NVMe         🤷‍♀️

RISE-LE-3
------
64g    ECC 2× 1920 NVMe         BHS: 1H

RISE-LE-4
------
128g   ECC 2× 1920 NVMe         🤷‍♀️

RISE-LE-5
------
256g   ECC 2× 3840 NVMe         🤷‍♀️
256g   ECC 2× 3840  SSD         🤷‍♀️

    Can only buy with API I guess link down

  • NeoonNeoon Community Contributor, Veteran

    @emgh said:
    Yesterday night I did my books finally for all BF buys etc

    I also did it for the KS-A

    Second time

    One entry for the purchase
    One for the payment
    One for the refund invoice
    One for the actual refund received

    Can’t recommend

    Thanked by 1emgh
  • wuckwuck Member
    edited December 2024

    All the Rise server went up in price somehow by around 4$, Octave tight on money

    edit: price just went back to normal, I guess he's reading

    Thanked by 1emgh
  • wii747wii747 Member

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    Just what I needed to get IPv6 to work on my VM's

  • ChillBirdChillBird Member

    stupid question but what is the best way to get a 32bit win 10 running?

  • plumbergplumberg Veteran, Megathread Squad

    @aryanraj said:
    stupid question but what is the best way to get a 32bit win 10 running?

    Whats the use case?

  • fredo1664fredo1664 Member

    @aryanraj said:
    stupid question but what is the best way to get a 32bit win 10 running?

    You dont need win 32 bit to run Java 32 bit, if thats what you want to do.

  • NeoonNeoon Community Contributor, Veteran
    edited December 2024

    wrong thread

  • icemaniceman Member
    edited December 2024

    Still looking for KS-LE-B NVMe in EU, since my guy @sk29 betrayed me for more money :(

    Thanked by 1yopp
  • IliasksIliasks Member
    edited December 2024

    Looking for KS-LE A-D,HDDs,EU
    PM m if you have.

    I ve got an OVH US/EU acc.

  • ChillBirdChillBird Member
    edited December 2024

    @fredo1664 said:

    @aryanraj said:
    stupid question but what is the best way to get a 32bit win 10 running?

    You dont need win 32 bit to run Java 32 bit, if thats what you want to do.

    got it working. thanks

  • wlambrechtswlambrechts Member

    I have a KS-LE-A in BHS (CA account).

  • RizRiz Member

    @wlambrechts said:
    I have a KS-LE-A in BHS (CA account).

    How much?

  • buddermilchbuddermilch Member
    edited December 2024

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    I just remembered something I've forgot. If you use this setup you have to disable the firewall for the VM or container and manage if through the host (for IPv4 NAT). Native IPv6 can be manged for the VM or container through the Proxmox CP firewall for each instance separately.

    Thanked by 1ariq01
  • barbarosbarbaros Member

    @emgh said:
    Yesterday night I did my books finally for all BF buys etc

    I also did it for the KS-A

    Second time

    One entry for the purchase
    One for the payment
    One for the refund invoice
    One for the actual refund received

    Can’t recommend

    boo hoo :'(

    Thanked by 1emgh
  • JerryHouJerryHou Member

    @barbarza said:
    Looking to Transfer:

    KS-LE-C with 2x4TB lottery upgrade in RBX
    KS-LE-1 with 32GB RAM lottery upgrade in BHS

    PM me if interested.

    @Iliasks said:
    Looking for KS-LE A-D,HDDs,EU
    PM m if you have.

    I ve got an OVH US/EU acc.

    both you guys can talk. :)

    Thanked by 1plumberg
  • ChillBirdChillBird Member

    me as a CA account holder can't even get a different server transferred from eu account. sad :'(

  • optisoftoptisoft Member

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    Is working on back friday kimsufi servers?

    I copy config using ndppd from SYS to one kimsufi, and not stable ipv6 on VMs

    Now have other kimsufi, and not working IPV6 on VMs.

    Proxmox 8.3.1

  • CasualCanvasCasualCanvas Member

    @barbarza said:
    Looking to Transfer:

    KS-LE-C with 2x4TB lottery upgrade in RBX
    KS-LE-1 with 32GB RAM lottery upgrade in BHS

    PM me if interested.

    Is that KS-LE-1 SSD or HDD?

  • aj6828aj6828 Member

    does any one know how to install windows on a ovh server? windows 11 if possible

  • adnsadns Member

    @aj6828 said:
    does any one know how to install windows on a ovh server? windows 11 if possible

    There are a number of solutions, one of is to boot in rescue, pass the disk(s) with QEMU and install the OS, reboot and enjoy. A tutorial shown here but I can not find it now so there might be important details, E.G. retrieving IP, opening device to remote desktop connections etc.

    Which server is it? Install method depending on boot method. Old KS server uses legacy and new ones (LE-B) use UEFI without secure boot.

  • wii747wii747 Member

    @optisoft said:

    @buddermilch said:

    @JerryHou said:

    @aryanraj said:
    as there is no more steal servers available, i am thinking to buy a normal server and setup promox for a month in hope to get deal when it get restocked, can somebody help how different is default ovh proxmox template, compare to installing via remote kvm?

    anyone have a guide to use remote kvm, video preferred. Thanks.

    @proset10 said:
    I had problem with no network on VMs from template image, but maybe it is only my poor knowledge about config proxmox.

    for PVE on OVH, need some efforts to config the newwork, I got some diffculities to setup the network for VMs... so I give up...

    I found that configuring the network is easy and straight forward. Maybe due to changes in Proxmox 8?

    IPv6 works out of the box by assaigning the VM or container an IP from your OVH control panel:

    iface eth0 inet6 static
              address x:x:x:x:2/128
              gateway "ipv6 gateway"

    IPv4 NAT you crate a bridge in Proxmox on your host and assaign a local IP for example 192.168.0.254/24 as you gateway which you need to set as "gateway" when creating a LXC container or editing network/interfaces.

    On the host you set

    auto vmbr1
iface vmbr1 inet static
        address 192.168.0.254/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -o vmbr0 -j MASQUERADE

    When creating a LXC container you set the IP to 192.168.0.1/32 and 192.168.0.254 as gateway and use vmbr1 as a bridge, Proxmox does the rest. If you want addational IPv6 you create another adpater for the LXC container through proxmox and bridge to vmbr0 not vmbr1 and assaign an IPv6 from your /64 given by ovh through Promox cp.

    If you want port forwarding you have to set it on the host for the IP assigned to the container:

        # Port-Forwarding 
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 80 -j DNAT --to 192.168.0.1:80
    post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 443 -j DNAT --to 192.168.0.1:443

    If you do it for a VM not an LXC container you have to edit network/interfaces yourself for example:

    auto eth0
iface eth0 inet static
        address 192.168.0.1/32
        gateway 192.168.0.254
        post-up ip route add 192.168.0.254 dev eth0
        post-up ip route add default via 192.168.0.254 dev eth0
        pre-down ip route del default via 192.168.0.254 dev eth0
        pre-down ip route del 192.168.0.254 dev eth0

auto eth1
iface eth1 inet6 static
        address x:x:x:x::2/128
        gateway "ipv6 gateway"
        post-up ip route add "ipv6 gateway" dev eth1
        post-up ip route add default via "ipv6 gateway"  dev eth1
        pre-down ip route del default via "ipv6 gateway"  dev eth1
        pre-down ip route del "ipv6 gateway"  dev eth1

    For a VM you also need to create a second network interface through proxmox to connect IPv6 to vmbr0 for full IPv6 connectivity. IPv4 connects to vmbr1.

    Also check if IPv6 forwarding is enable on the host:

    net.ipv6.conf.all.forwarding=1

    Is working on back friday kimsufi servers?

    I copy config using ndppd from SYS to one kimsufi, and not stable ipv6 on VMs

    Now have other kimsufi, and not working IPV6 on VMs.

    Proxmox 8.3.1

    I have got ipv6 working on the back friday kimsufi servers

  • yoppyopp Member

    KS-LE-1

    32G 3× 2000 SATA: RBX 1H LOW

    Hurry up, there some (I suppose a single one) KS-LE-1 dropped

    Thanked by 2JerryHou Quotacious
Sign In or Register to comment.