Recent content by Idar Lund

  1. I

    pveproxy LISTEN address

    I don't know if that'll be added or not. However; you can just use a reverse proxy for that. Listen on loopback (127.0.0.1) device and put a reverse proxy on the interfaces you want to listen on the network.
  2. I

    pveproxy LISTEN address

    The feature request is now in production. Add LISTEN_IP=<your_IP> to /etc/default/pveproxy and restart pveproxy. ie: echo 'LISTEN_IP=127.0.0.1' > /etc/default/pveproxy systemctl restart pveproxy To check if it worked: netstat -lntp|grep 8006
  3. I

    pveproxy LISTEN address

    Created https://bugzilla.proxmox.com/show_bug.cgi?id=2997
  4. I

    pveproxy LISTEN address

    With the implementation today we are totally dependable on that the application will withstand attempted attacks. If the pveproxy application some time in the future suffers from a vulnerability that can buypass this application security layer, we are at risk. It's good practice to have several...
  5. I

    pveproxy LISTEN address

    Hi, I have several ethernet interfaces. To secure Proxmox webgui I want it to only listen on one of them. When checking netstat, I can see that it's listening on 0.0.0.0 (all) interfaces: root@pve:~# netstat -lntp|grep 8006 tcp 0 0 0.0.0.0:8006 0.0.0.0:*...
  6. I

    PCIe Passthrough of Atheros AR9280

    Thanks! That worked. For the record and for people landing on this page from google: I only had 1 pci device passtrough so it was named hostpci0 in the "/etc/pve/local/qemu-server/100.conf" config file, like this: hostpci0: 06:00.0 Added the following to the bottom solved the pci passtrough...
  7. I

    PCIe Passthrough of Atheros AR9280

    I have the same error on the same card. I have tried both ovmf and seabios. The same error message appears. As a test I used an Intel card in the same pci slot and that worked. However, this is not a suitable solution since the Intel card can only act as a client not AP. lspci: 06:00.0 Network...
  8. I

    container with physical disk

    Hi, Found an answer here: https://forum.proxmox.com/threads/lxc-cannot-assign-a-block-device-to-container.23256/ But it turns out that I actually don't need to add the block device as a block device after all. The mountpoint (mpX) config option solved everything for me. That makes my lxc...
  9. I

    container with physical disk

    Hi, I've got a spare physical disk (/dev/sdb) that I want to add to a container. How to do that? -Idar
  10. I

    fuckwit/kaiser/kpti

    thanks! please lock down this thread
  11. I

    fuckwit/kaiser/kpti

    are you sure that proxmox is based on ubuntu? a lsb_release -a tells me that my installation is debian: If that's the case, this should be the tracking of the released fixes: https://security-tracker.debian.org/tracker/CVE-2017-5754
  12. I

    fuckwit/kaiser/kpti

    Quoting https://insights.ubuntu.com/2018/01/04/ubuntu-updates-for-the-meltdown-spectre-vulnerabilities/ Ubuntu has also written a KB here; https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown Seems like we will get the kernels to upstream ubuntu january 9th.
  13. I

    fuckwit/kaiser/kpti

    you can disable it by adding "pti=off" to grub config..
  14. I

    fuckwit/kaiser/kpti

    it was what they called it before it got the fancy names meltdown and spectre; https://lkml.org/lkml/2017/12/4/709
  15. I

    fuckwit/kaiser/kpti

    according to @fabian, they are releasing updated kernels as soon as ubuntu does that. according to https://launchpad.net/ubuntu/+source/linux/+changelog ubuntu has not yet released such a kernel