Search results

Ok, it was just a disk space problem, I was going with 4G, being the requirement 2,5G and it wasn0t enough. Went with 8 and everything worked out.

Hi, I'm having troubles installing ubuntu 22.04, already tryed some options and always keeps stopping with same error. See attached log from installer and pve/vm info. pve: proxmox-ve: 7.3-1 (running kernel: 5.15.85-1-pve) pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)...

Ok, the docs are quite clear, thank you.

Hi, I'd need to plan cluster-wise delay of VM startup. So, I'd put every node's startup delay option to say, 300. Then, on node1 I'd put VM1 in order 1 delay 300, on node2 VM2 order 2 delay 300, on node3 VM3 order 3. Will the three VM be ordered properly, even if they belong to different...

Hi, I'm getting this on all three of my nodes. Feb 02 22:11:17 pvenode1 systemd[1]: zfs-import-scan.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit zfs-import-scan.service has entered the 'failed'...

See here for tagging to access ports: https://forum.proxmox.com/threads/vlan-tagging-not-working.121707/

See here: https://forum.proxmox.com/threads/vlan-tagging-not-working.121707/

Ok, the normal way access ports work on switches, even if my model's documentation hinted differently. I'll just go with normal untagged ports going to the access ports on the switch. Thank you very much.

Sorry, the trunk port is working, I can ping upstream vlan 80 IP from a vlan 80 access port in the switch, and from inside proxmox too. Also can ping promxox from the PC on the access port. Still can't do it on vlan 100, and from proxmox I can't ping the upstream vlan 100 IP. auto enp5s0f0...

Hi, I can't seem to get vlan tagging working properly. This does work iface enp129s0f0 inet manual mtu 9000 auto vmbr6 iface vmbr6 inet static address 10.0.100.11/24 gateway 10.0.100.5 bridge-stp off bridge-fd 0 mtu 9000 This does not iface enp129s0f0 inet manual...

Ok, but let's say I only have that phisical nic and I want to give proxmox an ip on vlan 10.

Hi, I'm going to implement a trunk and some access ports on proxmox to the Cisco Switch in my homelab. Probably adding a bond or two but let's keep it to simple bridges for now. I'm studying the docs and different guides on how to implement vlan trunks and vlan tagging, and I see mostly two...

I also tried tagging, probably it was a bad setting as I could not resolve from the outside to the inside. Anyway, can confirm that without the "10" address, then the "10" to "100" ssh sessions are stable and working. I'll try another setting with vlan aware bridges and linux vlans, as I'd...

Ok, probably they got it explained from Netgate forum. So, cross-vlan to proxmox node is going to be tricky, I'll need to give only the management IP and the "internal networks" (cluster, ceph) IPs, and contact only to management. Thank you very much.

I'm also posting on Netgate (pfSense) forums, let's see if I can find out the culprit

netstat output (did not change while the other PC is in ssh): root@pvenode1:~# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:*...

I'll try that, and I'll also doublecheck pfSense' settings for interfaces and vlans (already thoguht I didn't need vlan-aware bridges). I'll also try a Linux machine instead of the two windows machines I'm using as clients. I'll get back with the output.

Well, quite sure they're correctly tagged right, 10 (eno1) and 100 (enp129s0f0). If I connect a PC to a similarly tagged port, I get the right IP on the right network from pfSense. I also can't access other vlans/networks due to psSense rules, but 10 and 100 should be communicating (and thay...

root@pvenode1:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.0.100.3 0.0.0.0 UG 0 0 0 vmbr9 10.0.10.0 0.0.0.0 255.255.255.0 U 0 0 0 vmbr1 10.0.20.0...

Hi, I think pfSense should be tagging the vlans, the switch is Cisco Nexus 3172tq. See the other thread about not being able to reach proxmox/pfsense from PC1 or PC2 when trying to manage vlans on proxmox network.