Search results

Remember that with bonds/LAG/LACP 1+1 != 2. Similarly 1+1+1+1 != 4. It chooses a link through an algorithm and uses the same link for a hash of same Src/Dst IP and ports.

Unless theres a workaround why not run it as a VM?

Just incase anyone else comes along: RHEL: yum -y install qemu-guest-agent Deb/Ubuntu: apt-get install qemu-guest-agent

Im saying the LV that I converted was empty to start with. I've since stopped being lazy and read up :). So you modify an existing LV to be an LVM-Thin or create a new LV as a thin-pool, you then create a disk "within" that thin-pool. Thanks for the added info though, much appreciated and good...

Well in that case you'd need to look at your DHCP server and look at the leases. Look at the MAC that Proxmox has generated for it and tally it up to the lease for that MAC on your DHCP server.

auto lo iface lo inet loopback auto eth0 iface eth0 inet manual iface eth1 inet manual auto eth0.255 iface eth0.255 inet manual vlan_raw_device eth0 auto vmbr0 iface vmbr0 inet static address 192.168.58.241 netmask 255.255.255.0 gateway 192.168.58.254 bridge_ports eth0...

That is pretty much what STP does, loop prevention. I suppose as long as you're using the same vendor on your switches and they support the same protocol it should be ok. Spanning tree is only Layer2, a router only has one connection to a VLAN so doesnt have a need for STP. It sounds like...

Can I bump this as I want to know. I converted my LVM storage to LVM-thin but it was empty, Im trying to understand how it works. Does it add a Volume Group or does it add a thin provisioned Logical Volume and use disks on that?

LACP/Bonding is also called LAG among a myriad of other terms so D-Link may have called it something else. Don't call it trunking as that relates to a trunk port (which you will most probably actualy want) which carries multiple VLANs. If the 8 port does not support STP then I'd probably not...

Unless Proxmox is working as a firewall (but I'd seriously consider setting up a Proper firewall VM for this) then I would NOT give Proxmox a Public IP address! Bridge the internet physical interface to your vmbr0 and attach the VMs to that. Or what I would do is setup a Firewall VM and setup...

login to shell of container and type: ip addr

Why do you give Proxmox a public IP? Also have you set the VM bridge as vmbr0?

What distro is your NFS server on? I had a problem on CentOS where SElinux was blocking, I had to restore the SElinux context to be able to share the directory

Looks odd that you have dropped Rx packets on eth0 and dropped TX packets on your VM100 interface0. Also surely you are missing eth0 interface on your interface file

This is my config, VMs attached to vmbr255 I can see on the switch (MAC addresses) but the Proxmox is incorrectly dropping onto the untagged VLAN

I've been thinking and I think the correct method is to have an interface for VMs tagged as VLAN 255 and passed to the LAN bridge (vmbr0). This works fine. But then I dont know how to give the Proxmox box an interface address on this VLAN? I suppose I need to add a VLAN interface but dont know how

I have 2 Proxmox hosts. One is at my network edge with a pfSense VM doing VLAN routing. Another sits on a couple of VLANs, I have a VLAN for Client to Server connection, a VLAN for Storage (NFS) and a VLAN for the Clustering (advised in the cluster wiki). I have tried a few different config but...

For future reference there are 3 ways you can do it: Setup a bridge for a specific VLAN and add interfaces to that bridge Setup one bridge and make sure its "VLAN Aware" tickbox is checked. Then add an interface to your VM and tag the interface with the VLAN. Similar to 2, setup one bridge but...

Id probably try leaving your config and unplugging one of the cables. If everything works fine then Id suggest specifically looking at your LAG config and make sure the Proxmox and Switch have a similar config for the ports that are connect.

Just for some confidence, this is almost exactly how I have mine setup. I have one interface that my cable modem plugs into that goes to one bridge, and another bridge that connects to a trunk on my VLAN switch. pfSense is the L3 device that routes between (and Firewalls and NATs) them. I've...