Changes

Jump to navigation Jump to search
4,910 bytes added ,  17:22, 5 December 2013
Update for Proxmox with SME at online.net
Line 81: Line 81:  
=== Proxmox ===
 
=== Proxmox ===
 
* Interesting [http://pve.proxmox.com/wiki/SMEServer_KVM article] on installing SME Server as guest on Proxmox
 
* Interesting [http://pve.proxmox.com/wiki/SMEServer_KVM article] on installing SME Server as guest on Proxmox
 +
 +
 +
== SME v8 on Proxmox at Online.net ==
 +
 +
This is based on work by Daniel here :
 +
 +
https://wikit.firewall-services.com/doku.php/tuto/virtualisation/netwok_conf_sur_dedibox
 +
 +
You need a second IP (failover) address. Assign it to your server and make sure you set the MAC for this IP before you do anything else - failure to do so may block your network !!!!!
 +
 +
The problem is that your IP is NOT on the same network range as your gateway so we have to fool the system.
 +
 +
Some assumptions :
 +
 +
Your main IP address :
 +
 +
Ip address 62.20.20.250
 +
Netmask 255.255.255.0
 +
Gateway 62.20.20.1
 +
 +
Your secondary IP address :
 +
 +
200.30.30.1
 +
10:10:00:00:20:20 - you DID set the MAC didn't you ?
 +
 +
Proxmox.
 +
 +
Make sure you set your default keyboard - it makes life much easier !
 +
 +
We will use the vmbr0 that is set up, but we need to create a dummy one so we can put SME in server/gateway mode and use Daniels scripts.
 +
 +
Create a new network interface. Call it vmbr1
 +
 +
Do NOT set IP address/subnet/bridge ports etc.
 +
 +
Next, create your KVM for SME. Make sure that you give it two network adaptors - one is vmbr0 and one is vmbr1
 +
 +
vmbr0 should have the following settings :
 +
 +
Model : virtio
 +
MAC : 10:10:00:00:20:20 (as per your mac that you set)
 +
 +
After you have created the KVM add a second adaptor :
 +
 +
vmbr1 should have the following settings :
 +
Model : virtio
 +
MAC : should be the MAC of your main IP address
 +
 +
It doesn't matter which one is 0 or 1 as long as the settings are correct.
 +
 +
 +
Now do your standard SME installation.
 +
 +
<here would be a lot easier if we could force it to have a local IP first so you could ssh from Proxmox to SME and you could then use scp to copy files or a terminal to copy and paste>
 +
 +
When you go through the setup, make sure you pick the DUMMY adaptor for the local interface, and the real adaptor for the external interface. Make sure you know your MAC addresses so you know which one is which.
 +
 +
you can use your second IP address for the external interface, but you will have to set a subnet mask and gateway IP that it likes e.g.:
 +
 +
IP : 200.30.30.1
 +
Subnet : 255.255.255.0
 +
Gateway : 200.30.30.1
 +
 +
One you have rebooted your network will not be working correctly so we need to follow Daniels guide to fix it :
 +
 +
db configuration set ExternalIP 200.30.30.1
 +
db configuration set ExternalNetmask 255.255.255.255
 +
db configuration set GatewayIP 62.20.20.1
 +
/etc/e-smith/events/actions/initialize-default-databases
 +
 +
mkdir  -p  /etc/e-smith/templates-custom/etc/sysconfig/network/
 +
 +
 +
echo  '# GATEWAYDEV disabled for dedibox network'  >  /etc/e-smith/templates-custom/etc/sysconfig/network/40GATEWAYDEV
 +
echo  ' # GATEWAY disabled for dedibox network '  >  /etc/e-smith/templates-custom/etc/sysconfig/network/50GATEWAYto pass in THIS_DEVICE MORE_DATA \ n " Unless ( defined $ THIS_DEVICE ) ;   
 +
 +
    my $ device = $ ExternalInterface { Name } ;
 +
    Unless ( $ device )
 +
    {   
 +
        warn ( "Can not determined for external network device name" ) ;
 +
        return  "# template expansion error - Can not determined for external network device name" ;
 +
    }
 +
 +
    return  "# Gateway Applies only one external interface"
 +
        Unless ( ExternalInterface $ { Name } eq $ THIS_DEVICE ) ;
 +
 +
    my $ gw = $ ExternalInterface { 'gateway' } ;
 +
 +
    $ OUT =. " $ gw dev $ THIS_DEVICE \ ​​n " ;
 +
    $ OUT =. "default via $ gw dev $ THIS_DEVICE " ;
 +
}
 +
EOF
 +
 +
If you have got it right then you should be able to run the following without error :
 +
 +
expand-template / etc / sysconfig / network-scripts / ifcfg-$ ( db configuration getProp ExternalInterface Name )
 +
expand-template / etc / sysconfig / network-scripts / route-$ ( db configuration getProp ExternalInterface Name )
 +
 +
Check all the network settings look correct and then :
 +
 +
signal-event post-upgrade;signal-event reboot
 +
 +
You should now be able to connect to your Proxmox box on your primary IP address, and your SME server on your added IP
 +
 +
 +
Your network setting should look similar to this :
 +
 +
EthernetDriver1=virtio_net
 +
EthernetDriver2=virtio_net
 +
ExternalDHCP=off
 +
ExternalIP=200.30.30.1
 +
ExternalInterface=interface
 +
    Broadcast=(whatever)
 +
    Configuration=static
 +
    Driver=virtio_net
 +
    Gateway=62.20.20.1 (gateway for your main IP address)
 +
    HWAddress=10:10:00:00:20:20 (MAC that you set for 2nd IP address)
 +
    IPAddress=200.30.30.1 (your 2nd IP address)
 +
    Name=eth1
 +
    Netmask=255.255.255.255
 +
    Network=200.30.30.1 (your 2nd IP address)
 +
ExternalNetmask=255.255.255.255
 +
GatewayIP=62.20.20.1 (gateway for your main IP address)
 +
 +
Following your 'local network' and is the range when you VPN :
 +
 +
InternalInterface=interface
 +
    Broadcast=192.168.98.255
 +
    Configuration=static
 +
    Driver=virtio_net
 +
    HWAddress=fe:aa:16:19:e8:bf (MAC for 'virtual' adaptor)
 +
    IPAddress=192.168.98.1
 +
    NICBondingOptions=miimon=200 mode=active-backup
 +
    Name=eth0
 +
    Netmask=255.255.255.0
 +
    Network=192.168.98.0
 +
LocalIP=192.168.98.1
 +
LocalNetmask=255.255.255.0
    
=== Xen ===
 
=== Xen ===

Navigation menu