Search results

Hi, what is your exact version of PVE ? Best regards,

Hi, Have you check you had the latest version, it's been fixed with last updates. Best regards,

Hi, Well, with no real data we cannot help you, you need to give all the information. What is your IP, gateway, netmask, host file, resolv.conf, router IP (which should the gateway), hyper-v network config, etc. (preferably in text base with code balise tag rather than screenshot) Best regards,

Hi, Can you explain more and what you are trying to do exactly ? Here from my point you try to access another LAN without routing between the LAN so yeah it will not work like that by "magic". Note : quoting whole message is useless Best regards,

Hi, Huh, pve does not set a proxy. I don't know what you are trying, but can you respond to the questions and tell what you are already done as diagnostic and what are the results ? Best regards,

Hi, Do you ping your router ? If not you should look at your router security, maybe he doesn’t authorize static IP inside it's DHCP pool and then block that IP. Best regards,

Hi, From what I can see of your screenshot, you are running proxmox inside a hyper-v VM ? Have you checked your hyper-v settings ? Best regards,

Hi, You should open your thread and give more details about your setup. Best regards,

Hi, to display the file you need to use a command, for example cat cat /etc/network/interfaces Best regards,

Hi, What is your storage configuration ? Best regards,

Hi, It's a hardware issue, not a proxmox specific issue (same appear on vmware or other OS), if anyone should talk about this issue is miniforum, the hardware vendor, just like asrockind (Cf : https://www.asrockind.com/en-gb/index.php?route=newsblog/faq&faq_id=91). Or just use enterprise grade...

Hi, I know it's a consumer hardware/computer, not a server. When you tried this, the "other" has the same L2 connection as the proxmox server ? Well, I don't know your background, but I know that the same setup is working in my case, so I know that it's not simply a bug in proxmox (and you...

Hi, The NAT seems right if the HomeAssistant VM is 192.168.1.222 and you are not behind a CGNAT. For the UptimeRobot for me, it's normal since your monitor is HTTP/HTTPS (which look at 80 and 443 if I'm right) and not port monitor. Can you precise the IP of your VM and the external link used...

Hi, Wrong assumption, like said earlier proxmox modify nothing in the packet, it just passthrough. Well, good luck for your deployment (i assume your minisforum was just a lab and not the actual servers). Best regards,

Hi, Your wireshark capture looks normal, DHCP discovers with "0.0.0.0" as the source is normal since your client is asking to get an IP. And after that the offer is sending the result to your client who says, your client will have 10.184.68.10 as IP and 255.255.255.0 as subnet with a lease time...

Hi, Can you explain more about what is your setup ? From what I understand, you try to access "Nabu Casa" which is on the VM of the posted network config, but the connection failed ? Best regards,

Hi, Something seems off with your result. If I'm reading correctly, you say that you have to activate the firewall and allow DHCP to work and if you disable it it stops working ? Can you please give the result of this command when it's not working : pve-firewall status && pvesh get...

Hi, Well, it's a bridge so unless a firewall is activated on proxmox (or something was installed on the host), nothing should filter packet since bridge only forwards and nothing more. I quote what a proxmox staff said : Cf : https://forum.proxmox.com/threads/dhcp-on-vm.152401/#post-691180...

Hi, You need to filter on ports 67 AND 68 in wireshark (capture all, stop, and filter after capture). And at the same time do it on the host when forcing client to request IP via DHCP, and post both results (in code tag preferably). And make sure you have nothing that can block the request...

Hi, you should do the tcpdump inside your VM that act as DHCP as well, and use this filter tcpdump -i {INTERFACE} port 67 or port 68 -vv This way we should see the exchange between the client and the server, and we need to see this inside the VM and HOST to see if this gets "stuck" inside the...