Search results

Hello David, shows that you have configured "bridged" now. Does connection between host and VM work? shows that also your host is probably behind a NAT router. It´s now the question: does this NAT router accept your VM? Does it provide an address to it via DHCP? If the answer for both...

Hello David Should work without any problems - but you must not forget of course to adapt the settings inside the VMs (e.g.: if there is no (external) DHCP server connected to the bridge you must assign the proper address directly in Windows). If you post more details, making grep ""...

Hello rh3 Your next step should be now to verify the configuration related to the NIC which has that MAC carefully: - is it used in a bridge? - is it used for a virtual NIC (too)? - check also the configuration inside your VMs and CTs! - occurs somewhere the address 144.76.72.235? Where...

Hello rh3, "Just set" an IP address in a container is venet0 and not veth - in that case is not bridged either, it is - seen from outside - like an additional address assigned in the host. No - but it´s question if you have bridges and veth - see above. It can be clarified if you post...

Hello N3ST If I understood it correctly you want to have the following: mirror-port-from-switch -----> Proxmox-Host-eth1 -----> OSSIM-VM-in_Proxmox-ethxy Create a new bridge vmbr1 connected with eth1. Assign a virtual NIC from the VM to it - you will see all the traffic from mirror port...

Hello soholingo You mean "openvswitch", don´t you? Which version do you use? There were problems in Version 3.2 (and maybe still in V3.3) but V3.4 should work fine. Especially with vlans I experienced that ovs works better than linux bridges. What in detail does not work ? Can you post your...

Hello dswartz Sometimes there are problems with the resolution - depends possibly on both graphic card and display monitor. How I used to managed this: press alt + <letter for continuation>, usually it´s alt+N (for Next); the first screen e.g. expects alt+G (for aGree). What it is in...

Hello Altar As far as I see your basic configuration is quite correct and it should work. But: as soon if the vm has started an additional NIC should occur in ipconfig (if not, the virtual NIC of the VM is not correctly configured). However, in order to follow the packages and discover where...

Hello tfjelde Your package versions are up to date - strange what happened (I upgraded to the same versions and did not encounter such a problem). Difficult to say if something is irregular now. Try the following /etc/init.d/pvedaemon restart If this works without any problem and does not...

Hello Fenixoid No problem to assign more IP addresses to a container - but: don´t use venet0 in this case! Define virtual NICs (one for each address) instead and route to/from them via routing tables as in case of physical machines. The details depend from your network architecture and...

Hello Nils, I have seen such a phenomenon too sometimes - when I had problems with access to NFS storage. Cannot say if it is in your case the same, but at least you can try (e.g. remove temporarily NFS storage) Kind regards Mr.Holmes

Hello Dolomike have a look here http://forum.proxmox.com/threads/18331-Migrating-to-Open-vSwitch?p=93726#post93726 Note: Since the bug when using it in containers is solved in the meantime the mentioned work around is not necessary any more. To separate different kinds of traffic is...

Hello Rudi This version is rather old - but I don´t think that is relevant here. So it seems the relevant kernel modules are available - otherwise it would look like this: # iptables -t nat -vnL FATAL: Could not load /lib/modules/2.6.32-37-pve/modules.dep: No such file or directory...

Hello Sgt To which flow do you refer? Between an external client to the host or from/to the KVM? Remarkable for me is that both bridges are membrs in the same subnet. So I suppose the bonded links are connectet to the same switch as eth0 is. However, in order to have clear conditions I...

Hello jherazob Sounds quit clear - why are there necessary more (V)LANs? Assign to each container the requested address and that´s it! The only one thing you should take care of is to make all these addresses routable from/to proxmox host. Kind regards Mr.Holmes

Hello Spookycare That works without any problems. It is true that one address (found in /etc/hosts) is seen as "Main" Proxmox address, but all features as web UI will work using the other address too. The only one: when you have a cluster with more nodes for multicast traffic only the...

Hello jonathan2493 Independently which storage you use exporting a virtual hard disk works as follows (do it rather when the machine is stopped): - move disk to a local (directory) storage - copy the created file to your target system The following I never tried, but should work in...

Hello jompsi, Didn´t you create a filesystem in /dev/local/name mount it and define it then as local storage? I the problem occurs even all this has been done correctly post /etc/pve/storage.cfg and the content of "Task Viewer:Backup" for detailed analysis. Kind regards Mr.Holmes

Hello mlanner, I think that´s it - change also /etc/resolv.conf Here a small script which is self-explaining: #change the files: sed -i 's/olddomainname.com/newdomainname.com/g' /etc/hosts sed -i 's/olddomainname.com/newdomainname.com/g' /etc/resolv.conf #activate the changes...

Hello maxim.dogonov Seems to be rather a problem of the application than container configuration. Obviously your sip application is bound to lo address 127.0.53.53 and as sip server seems to be configured 127.0.53.53 too... If you post more details about your application it can become...