Cobalt Networks and Sun Microsystems are long gone, and so are the stylish blue Cube and RaQ server appliances.Cobalt featured a highly customized RedHat Linux as it's base, and can't run without modifications in a virtual environment.Until now. Here is a ready to run VM, patched-up to make it run in VirtualBox.This VM has been created using the toolset on GitHub,see https://github.com/gpdm/cobaltos-patcher for more details.How to use this VM----Add a new NAT network:VBoxManage natnetwork add --enable --netname "vCobaltRaq" --network 10.254.0.0/29 --dhcp on --ipv6=off VBoxManage natnetwork modify --netname "vCobaltRaq" --port-forward-4="Rule 1:tcp:[]:2022:[10.254.0.3]:22" VBoxManage natnetwork modify --netname "vCobaltRaq" --port-forward-4="Rule 2:tcp:[]:80:[10.254.0.3]:80" VBoxManage natnetwork modify --netname "vCobaltRaq" --port-forward-4="Rule 3:tcp:[]:81:[10.254.0.3]:81" VBoxManage dhcpserver add --network vCobaltRaq --server-ip 10.254.0.2 --netmask 255.255.255.248 --lower-ip 10.254.0.3 --upper-ip 10.254.0.3 --enable Then download the OVA file and import it into VirtualBox.It should automatically map to the "vCobaltRaq" NAT network created before.Otherwise, double-check the network settings of the VM.Then boot-it up.The VM exposes the most crucial TCP ports via NAT.So on the host where you a running VirtualBox, you may access the VM like this:localhost:2022 to access the RaQ at TCP:22 for SSH accesslocalhost:80 to access the RaQ at TCP:80 for the standard webserverlocalhost:81 to access the RaQ at TCP:81 for the admin UIIf you rather stick your VM into another network, or connect it to a bridge-network,adaptions of the network settings inside the VM are also required.This is best done from the recovery console, as outlined here:https://github.com/gpdm/cobaltos-patcher/blob/main/README.md#i-want-to-change-the-network-settings

weiterlesen: RSS Quelle öffnen