Search results

Downloaded, many thanks... but just a question: how did you install the system? With the normal installer or? Diaolin

Perfect: didi you produce an installer with the kernel? Or better, do you have a link for downloading it? My e-mail is diaolin AT diaolin DOT com Tx, Diaolin

Anyone resolved this question??? Diaolin

Yeah, done many times and result was always ok Diaolin

Edit the conf file directly DIaolin

My suggestion on /usr/share/pve-manager/ext4/pvemanagerlib.js In this case I could mantain the actual naming convention or use my idea: vmbr0 old method vmbr0lan my method vmbr1 -> vmbr1net vmbr2 -> vmbr2dmz and bond in the same mode I use the addition of the hint to the bridge/bond...

Perfect, tomorrow i'll write the patch and send to you. Many tx, Diaolin

Is it possible to add a hint to each node interface like vmbr0 (dmz) vmbr1 (net) vmbr2 (local) just to intercept correctly (when adding a new machine) the correct interface to join machine to??? I know that this is not in the code and i can write it myself... and send the patch, obviously...

a bridge is a simple, SIMPLE, hub if the two vm can see the bridge indipendently from the lan position right or left inside hypervisor or outside no problem: ONLY ON THE SAME BRIDGE

why????? this is simply strange Connect the two vm to the same bridge and you are ok

it cannot work, the two bridges don't speak one to another...

Yeah, of course i didn't see it! This is true. In your config vmbr1 is a mute bridge

Remove this: iptables -t nat -A POSTROUTING -s '172.16.16.1/24' -o eth0 -j MASQUERADE and add iptables -t nat -A POSTROUTING -p gre -s '172.16.16.1/24' -o vmbr0 -j MASQUERADE

Just use xinetd apt-get install xinetd touch /etc/xinetd.d/pve vi pve ######################## service https { socket_type = stream wait = no disable = no user = root redirect =...

All machine have a small Notes where i can insert informations about machine itself Is it possible to have sucha a small Notes even on each node???? Tx anyway, DIaolin

You forgot to nat and dnat even proto 47 iptables -t nat -A PREROUTING -p gre -d xx.xxx.xx.xx -j DNAT --to destination 172.16.16.2 DIaolin

You have the public addresses on eth0 (all public addresses) and create a simple vmbr0 withouth interfaces associated to it like this auto eth0 iface eth0 inet static address myplublicaddress netmask mynetmask gateway mygateway up "ip address add mysecondaddress dev eth0...

Why iptables does not work? Do you mean usign iptables on the Proxmox node itself (of course)?

Ok: then the question is: if a server fails to run a copy (and the server itself should know how to determine that the running machine is not OK) it should restore immediately from an up-to-date copy... And who says that the latest up-o-date is OK? I think that this should be made only...

Just a simple question: anyone tested openvswitch on Proxmox? Or, better, is it in the future of Proxmox or do you have any other solution for a virtual switch? I'm testing 3.x rc1 and i think it's a good solution (testing on my own lan as stable server) Tx, Diaolin