Search results for query: 192.168.100.2

It works with only one VLAN in there: auto lo iface lo inet loopback iface eno1 inet manual iface eno2 inet manual iface eno3 inet manual iface eno4 inet manual iface eno5np0 inet manual pre-up ethtool -K $IFACE rx-vlan-offload off pre-up ethtool -K $IFACE rx-vlan-filter off iface...

Thanks! vnet1 gateway == 192.168.0.1 vnet2 gateway == 192.168.100.1 Physical LAN Proxmox host is connected to is 192.168.1.0/24 with host ip of 192.168.1.99.

You can. it works. Its a bad idea, but it can be done. (as an aside, its a bad idea on vmware too; iscsi interfaces dont like to share the link.) the interfaces would look like this: iface nic0 inet manual mtu 9000 iface nic1 inet manual mtu 9000 auto bond0 iface bond 0 inet...

solved but on another noter im writing a helper class for the api like how proxmox datacenter manager works for python here is the class so far: #this script is called datacenter.py import requests class DC(): def __init__(self,ip,port,token,verify): self.DC = DC self.ip =...

i keep getting authentication failed - no authentication credentials provided. can anyone give me a curl example or postman for example? i have setup a user just using the default root@pam and the name of the token is root@pam!datacenter but cant seem to get it to work out side the browser. i...

those numbers seem fine? note that the bitmap was cleared, so the backup had to read the full disk contents (and did so at roughly 400MB/s!)

No sorry, on my previous message i was wrong, it is MTU 9000 actually.... This is my PVE lan config: auto lo iface lo inet loopback auto eno1np0 iface eno1np0 inet manual auto eno2np1 iface eno2np1 inet manual auto eno3np2 iface eno3np2 inet manual mtu 9000 auto eno4np3 iface eno4np3...

wtf reverted to 6.14 and issue here : INFO: starting new backup job: vzdump 802 --remove 0 --storage pbs01 --mode snapshot --notification-mode auto --notes-template '{{guestname}}' --node apex INFO: Starting Backup of VM 802 (qemu) INFO: Backup started at 2025-12-02 14:30:07 INFO: status =...

You mean in the ceph.conf file? that is no problem, as the /24 defines the subnet, so the last octet does not matter. What is interesting is that, according to the ceph -s and the config file, only one MON is known to the running Ceph cluster. The other MONs might be shown in the Proxmox VE UI...

No unfortunately, just tested : on PVE 8.4.14: root@apex:~# iperf3 -c 192.168.100.8 -t 600 -i 10 Connecting to host 192.168.100.8, port 5201 [ 5] local 192.168.100.11 port 54128 connected to 192.168.100.8 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5]...

I don't know if this poses a problem, but the network is not 100% correct. Instead of 192.168.1.210/24, it should be 192.168.1.0/24

I did a fresh install today, and its still failing: root@server5:~# uname -a Linux server5 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) x86_64 GNU/Linux Its a proxmox 9.1.1 install, freshly fetched from the website. Here are my network interfaces root@server5:~# ip a...

I've got several PVE running 8.4.14 Not all backup went wrong, here some logs from one PVE with 6 VMs failed backup: INFO: Starting Backup of VM 502 (qemu) INFO: Backup started at 2025-11-28 18:33:14 INFO: status = running INFO: VM Name: SRVQUA INFO: include disk 'ide0'...

Hi all! I configured a server like this: Proxmox on 192.168.1.150 ---> VPS CT is on vmbr1 and IP 192.168.100.100 (CloudPanel, using it only for Nginx Proxy) ---> VPS1 vmbr1 and IP 192.168.100.101, then other VPS2 192.168.100.102 etc... Working all good. All sites are on CloudFlare DNS. But...

Hi everyone. My current setup is Proxmox Host is running on a 2.5GB LAN with CIDR 192.168.0.100/24, GW 192.168.0.1 with vmbr0 Im trying to setup an LXC container to use a 10GB netcard - and only that specific card with CIDR 192.168.0.250/24, GW none with vmbr1 All my containers works just...

I had time to check with Wireshark from PC. The traffic when trying to load 192.168.1.100 on browser once is below. Looks like the PC doesn't receive an anser back and retries a few times till timing out, right? I'm not sure if it is the ISp router causing thereturn package drop at this point...

Hi, It looks like some asymmetry here: VM A in 192.168.101.0/24 can reach VM1 in 192.168.100.0/24, but VM1 doesn’t know how to return traffic to that subnet, so it sends TCP resets. You can try to move VM A into the shared LAN 192.168.1.0/24 (so both Proxmox networks are reachable directly)...

...My goal is to use VM A on Proxmox 2 as a reverse proxy for every VM on both my Proxmox servers. My main router is my Freebox, on 192.168.100.254/24. Proxmox 1 is using the subnet 192.168.100.0/24 for the VMs. 192.168.1.200/24 is its IP for the LAN. Proxmox 2 (hostname miniprox) is using...

The IP address you set your PVE: 192.168.2.3 Is not in the same subnet as the rest of your infrastructure: IPv4 is 192.168.1.100 default gateway is 192.168.1.253 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

IPv4 is 192.168.1.100 default gateway is 192.168.1.253 Lan connection from router to dumb switch then to separate switch which has the prox node and a test laptop [to ensure lan connection] if that makes sense I have 192.168.1.2 to 192.168.1.20 free for static IP's Tried same settings bar...