Differences

This shows you the differences between two versions of the page.

--- vpn_site2site_usando_zerotier_con_bridge_en_lxc [2024/10/28 01:56] – [Uninstall Zerotier] oso
+++ vpn_site2site_usando_zerotier_con_bridge_en_lxc [2025/07/10 15:41] (current) – oso
@@ Line 107: / Line 107: @@
 ----
-===== Uninstall Zerotier =====
-**Uninstall**
-<code bash>apt remove zerotier-one</code>
-If you want to blow away the config it created:
-<code bash>dpkg -P zerotier-one</code>
-<code bash>rm -rf /var/lib/zerotier-one/</code>
-----
-====== Issue Summary: ZeroTier TUN/TAP Device Error in LXC ======
-**Problem:**
-After migrating an LXC container with ZeroTier from a Proxmox environment to an Ubuntu Hyper-V setup, ZeroTier failed to start, logging the following error:
-  ERROR: unable to configure virtual network port: could not open TUN/TAP device: No such file or directory
-This error suggested that ZeroTier was unable to open a TUN/TAP device, which it requires for creating virtual network interfaces.
-===== Troubleshooting Steps =====
-  - **Configuration Comparison:**
-    Compared the original Proxmox LXC configuration with the new setup. Verified that the TUN device was mounted with the line:
-      `lxc.mount.entry = /dev/net dev/net none bind,create=dir`
-  - **Verification of `/dev/net/tun`:**
-    Checked within the container to confirm that `/dev/net/tun` was present. However, access permissions were limited.
-  - **Adjusting Permissions:**
-    Set permissions on the TUN device with:
-      `chmod 0666 /dev/net/tun`
-  - **LXC Configuration Adjustments:**
-    Ensured the configuration included the following settings:
-      - `lxc.mount.entry = /dev/net dev/net none bind,create=dir`
-      - `lxc.apparmor.allow_nesting = 1`
-  - **Network Configuration Clarification:**
-    Noted that the `lxcbr0` bridge had a standard IP (`10.0.3.x/24` from `lxc-net`) and that the container's `eth0` address was `192.168.88.84/24`. Multiple addresses on `lxcbr0` could interfere with routing for ZeroTier.
-  - **`lxc-net` and `dnsmasq` Review:**
-    Confirmed that `lxc-net` was set to use `dnsmasq` for DHCP:
-      `USE_LXC_BRIDGE="true"`
-    No additional configurations in `/etc/default/lxc-net` pointed to multiple IP assignments.
-===== Resolution and Next Steps =====
-The TUN/TAP issue appears to be due to sandboxing of `/dev/net/tun` within the Ubuntu environment. Planned further steps:
-  * **Restart LXC services** to ensure TUN/TAP stability.
-  * **Monitor `/var/log/syslog`** for recurring errors after each change.
-  * Consider testing on **Debian as the host OS** to identify any host OS limitations affecting `/dev/net/tun` sandboxing in Ubuntu.
-This setup and troubleshooting can serve as a reference for similar ZeroTier and TUN/TAP issues within LXC containers.