<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wifi on Findichgut.net</title><link>https://www.findichgut.net/de/tags/wifi/</link><description>Recent content in Wifi on Findichgut.net</description><generator>Hugo -- gohugo.io</generator><language>de</language><managingEditor/><copyright>Thorsten Habich</copyright><lastBuildDate>Sun, 19 Apr 2026 15:15:51 +0300</lastBuildDate><atom:link href="https://www.findichgut.net/de/tags/wifi/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Proxmox over WiFi</title><link>https://www.findichgut.net/de/howtos/proxmox/wifi/</link><pubDate>Sun, 19 Apr 2026 15:15:51 +0300</pubDate><guid>https://www.findichgut.net/de/howtos/proxmox/wifi/</guid><description>
&lt;p&gt;I read many times that using Proxmox with WiFi does not work well, and indeed there are some challenges compared to a wired connection. The setup I describe here will work for regular home environments. Using Proxmox with WiFi is most definitely not recommended for production use cases. In most cases using a Ethernet device, even via USB is the better - and easier, approach.&lt;/p&gt;
&lt;p&gt;In most cases, Linux refuses to use a WiFi adapter as a bridge port. Because of this, we will use an ARP proxy, which forwards ARP requests between two interfaces. The setup requires an IP address on all interfaces involved. I am using DHCP for the wireless interface itself, which is the default in my network and allows me to establish a connection quickly. &lt;strong&gt;Note that parprouted only supports unicast traffic.&lt;/strong&gt; If, for some reason, you want to use DHCP on the bridge device as well, you will need to install a DHCP relay.
Also other services, which require multicast (e.g. mDNS, some streaming solutions) will not work.&lt;/p&gt;</description></item></channel></rss>