Search results

  1. E

    Problem mit .pxarexclude

    hallo @CMC, habt ihr das hinbekommen? ich habe gerade die gleiche herausforderung: * !root/ !etc/ !opt/ !var/* !usr/local/ **/.[Cc]ache/ **/tmp/ var/apt/cache/archives/ var/lib/apt/lists/ var/lib/vz/ var/log/ var/tmp/ sollte alles im "/" ausschliessen, bis auf /root, /etc, /opt, /usr/local/...
  2. E

    LXC USB pass-through not accessible (rights, owner)

    @oguz, thank you for helping me with that one & sry, was away for a few days. > * are the laptops the same hardware? no, Laptop A (my laptop) is a TP E490, 2019 Laptop B (customer) are actually 2 laptops, One HP one TP X1 (2018/2019) > * separate standalone hosts or in a cluster? all are...
  3. E

    LXC USB pass-through not accessible (rights, owner)

    @oguz , sure, but doing that manual is not a solution. the initial question was, why do 2 identical systems behave differently on 2 different laptops? why does udev give the mobiles diff. rights and groups and why do the udev-rules not work? these would be the parts which where needed to get...
  4. E

    LXC USB pass-through not accessible (rights, owner)

    container yes, then it is accessible from adb as root. the goal is, to have it accessible from userid 1000 (+100000) crw-rw----+ 1 root root 189, 7 Sep 24 07:18 /dev/bus/usb/001/008 but the udev-rools on the laptop B are not working: SUBSYSTEMS=="usb", ATTRS{idVendor}=="04e8"...
  5. E

    LXC USB pass-through not accessible (rights, owner)

    hey @oguz has the same effect: $ l bus/usb/001/008 crw-rw----+ 1 nobody nogroup 189, 7 Sep 24 07:18 bus/usb/001/008 sry didn't mention, but they are the same: arch: amd64 cores: 2 features: mknod=1,nesting=1,fuse=1,keyctl=1 hostname: usb memory: 512 net0...
  6. E

    LXC USB pass-through not accessible (rights, owner)

    hello, on two different laptops, connecting a mobile (different mobiles, but both in ADB) and passing it through to an unpriv. LXC give different results. on laptop A, the device entry created looks like crw-rw-rw-+ 1 root dialout 189, 138 Sep 24 07:27 /dev/bus/usb/002/011 in the container...
  7. E

    find_mounted_device failed

    thx @fabian, that did the job. while talking about spamming the log – slightly OT: is there a way (planed) to dim the messages, which show up every 10 sec: proxmox-backup-api[1807]: successful auth for user 'backup@pbs'
  8. E

    find_mounted_device failed

    @fabian, when should the patch be roled out? this error spamming the log gets really annoing.
  9. E

    find_mounted_device failed

    same here, running on a Laptop in conjunction with PVE. PVE: 6.2--1 PBS: 0.8.9-1 Kernel: 5.4.44-2-pve The error did also appear, running on a priv/unpriv LXC (on another, dedi Host), but does only not appear when PBS runs in a KVM (on that dedi) Servus, günter
  10. E

    [SOLVED] wireguard / firewall: no connection

    meanwhile the fog lifted. In the beginning I faced a mixture of "culprits", all had a logical solution. ping to PVE-host was suppressed by FW, blocking ICMP ping to VMs with public interfaces on that host did not respond, due to routing issues that mixed up to a "picture of not working" sorry...
  11. E

    [SOLVED] wireguard / firewall: no connection

    @oguz, sry for not having been clearer. these are all separate hosts, in diff. locations. I have a Laptop with PVE (WG-config, not a peer) the 2 PVE are my main dedi-hosts (WG-config: peers), and a VM, which is running at another place@someprovider, (WG-config: peer). on the VM, which has just...
  12. E

    [SOLVED] wireguard / firewall: no connection

    hello, I have 4 hosts connected per WG. 2 are PVE with public IP 1 PVE Laptop 1 VM (public Cloud) the PVE hosts are not reachable. turning WG debugging on, exposes: wireguard: vpn-serv0: Failed to give packet to userspace from peer 1 (xxx.xxx.xxx.xxx:51820) … the moment I turn off FW, all...
  13. E

    externel ip:port not reachable from inside behind nat

    hello, I'm struggling with with a "simple" setup. vmbr0 has ext-IP vmbr1 is nat LXC is connected to vmbr1 only portforwarding from outside is working the service within the LXC needs to check the availability of the configured ext-IP an tries to reach it's port(forwarding) -> does not work...
  14. E

    /etc/lxc/default.conf not included on LXC create

    I understand, but I meant only PVE-related stuff, not what's running in the VMs/LXCs, except things like docker/VPN, which need special configuration. but I think you got my intention. thanks in advance
  15. E

    /etc/lxc/default.conf not included on LXC create

    @oguz, sorry for late reply, been very busy… * docker/containerd in LXC * nested virt. I have found a link to the wiki in the forum, but no link in the How-To section. * what else is documented but hidden? I might add to this in time…, or, if you prefer, you could open a new topic and ask the...
  16. E

    /etc/lxc/default.conf not included on LXC create

    thanks for the answer. I found tons of hints, to put my adds into /etc/lxc/default.conf – all wrong! @oguz, why are so often reoccurring topics not part of the how-to section? i.e. tun/tap on non-/privileged container, LXC-defaults, VM-name in the backups, etc? it's very tedious to read hundreds...
  17. E

    /etc/lxc/default.conf not included on LXC create

    hi, I tried to set some default entries (cgroup for tun/tap and mount) in /etc/lxc/default.conf, /etc/lxc/lxc.conf and ~/.config/lxc/lxc.conf, but non of this get's included on LXC create, for both, priv. and nonpriv. types cat /etc/lxc/default.conf conf:lxc.cgroup.devices.allow = c 10:200 rwm...