![]() ![]() if I request a static IP only in the router outside the DHCP range it still DHCP assigns the same MAC an IP address in it's DHCP range so I'm leaning towards the idea that the router doesn't feel like handling this kind of traffic on all devices :-/ Probably need a newer beefier router.īefore I try testing different router, am I missing anything in Proxmox? The pve manual isn't super clear on MAC addressing philosophy (or my study was a little too cursory) and I'm not sure if the different MACs in vmbrX and virtio are a real issue. The router doesn't seem to honor requests to keep static IPs - i.e. I'd prefer not to root my android device to do this (I'm not aware of a way to do this sans-root).ĪRP binding on my router (wired - TP Link TL-R600VPN) or assigning IP address doesn't seem to stick very well. ![]() I can force connection in the Linux machine to point to the correct MAC with an arp command or script in /etc/network/if-up.d and it will connect. Win/Apple devices connect correctly to the proper VM MAC. When trying to connect to the VM the problem devices are trying to connect to the MAC address on the vmbrX and not the MAC address in the VM. I tried to force the virtio MAC to be the same as the vmbrX MAC, but I lost connection from all devices to all VM/CT when I did this. This doesn't seem to be a problem except a few Linux devices and an Android device can't connect to VMs. In the VMs I can see that the MAC address is the one assigned in software (virtio). I have noticed that in pve (in shell when I run ifconfig), the MAC address assigned to the Linux Bridge (vmbrX) does not match the MAC addressed assigned in the network device virtio in the GUI hardware section of the associated VM. NIC ports are assigned to Linux Bridges and then connected individually to a particular VM or CT via the hardware GUI. Running a few VMs and CTs on Proxmox 6.2-4 on a server with multiple NICs. ![]()
0 Comments
Leave a Reply. |