Recent content by carlosho17

  1. C

    iptables FORWARD chain shows no traffic in 5.1-38

    I just found the difference between both versions that impacts the FORWARD chain, it is net.bridge.bridge-nf-call-iptables So the solution seems to be to include net.bridge.bridge-nf-call-iptables=1 in /etc/sysctl.conf, and same for ip6tables.
  2. C

    iptables FORWARD chain shows no traffic in 5.1-38

    Hi there I've noticed a change between two proxmox versions. In newer ones , no traffic is passing through the FORWARD chain (.e.g iptables -L FORWARD -vxn shows 0 packets 0 bytes) proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve) pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)...
  3. C

    Network interfaces of other VMs listed on LXC

    Hi yes obviously! but how can one identify which guest-id is the container's own ? Is there any other place under /proc or /sys/fs where to find the container's own ID ?
  4. C

    Network interfaces of other VMs listed on LXC

    Hello Fabian, yes, no means of changing anything, though not good for multitenancy as you can just "see" which are your neighbours' net devices. Is there a way to know from within the LXC container which one is its own primary network device, and which is not his ? e.g. to identify his own...
  5. C

    Network interfaces of other VMs listed on LXC

    Hi there, I have a security related question, maybe related to privileged/unprivileged containers. On a privileged LXC container on Proxmox 5.1 , you can list other containers' and KVM VMs' interfaces by issuing cat /sys/fs/cgroup/net_cls/net_prio.ifpriomap In my case, it shows lo 0 eno1 0...
  6. C

    iptables: no traffic in FORWARD chain for VMs

    Found a thread with the solution: in /etc/sysctl.d/pve.conf set net.bridge.bridge-nf-call-iptables = 1 sysctl -p /etc/sysctl.d/pve.conf and it works!
  7. C

    iptables: no traffic in FORWARD chain for VMs

    Hi i upgraded to newest version, and traffic accounting stopped working for VMs, though still works for CTs VM network interfaces are RTL8139 in bridged mode over vmbr0 pveversion: pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46) running kernel: 2.6.32-14-pve proxmox-ve-2.6.32: 2.1-74...
  8. C

    cannot access /etc/pve: Transport endpoint not connected

    /etc/init.d/pve-cluster restart restored /etc/pve
  9. C

    cannot access /etc/pve: Transport endpoint not connected

    Hi I'm getting this error when running vzlist or anything related to access /etc/pve: Unable to open /etc/pve/openvz/200.conf: Transport endpoint is not connected Unable to open /etc/pve/openvz/201.conf: Transport endpoint is not connected Unable to open /etc/pve/openvz/202.conf: Transport...
  10. C

    KVM Traffic Accounting

    Hi I'm currently reading tx_bytes and rx_bytes from /sys/devices/virtual/net/tapNNNi0d0/statistics/ to perform traffic accounting by VM interface in Proxmox 1.9, is this the suggested way to do it , even in 2.0 ? Regards
  11. C

    Change NFS mount options

    Hi how can I change NFS mount options ? I just have these lines in /etc/pve/storage.cfg nfs: storagexxx path /mnt/pve/storagexxx server xxx.xxx.xxx.xxx export /storage/nfs content images But I would like to have the equivalent to this in /etc/fstab...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!