[SOLVED] intervlan ssh connection gets closed

doing the VLAN stuff on the prox host would be an option. therefore it gets untagged to your pfsense, and is routed there and sent back to your vlan bridge in vlan100 in the correct tagging.
 
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 also want to use a trunk and a couple of bonds, so having understud this gives me a better insight on how to improve the design.

As an aside, I'll make another post about the proper way to tag proxmox NICs (I seem to see two different ways around, so need to choose one).

Thank you everybody!
 
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.
Sorry to wake this post up - i am having the exact same issue.. I have my backup pfsense as a VM via Proxmox and when I ssh into the mgmt IP 10.200.1.81 from vlan 100 192.168.2.4 then the SSH connection drops after 30 to 40 seconds. But if i ssh to the vlan 100 interface 192.168.2.81 then ssh is fine.

Would you please be able to provide some assistance on how I can get this fixed? Thank you!
 
Sorry to wake this post up - i am having the exact same issue.. I have my backup pfsense as a VM via Proxmox and when I ssh into the mgmt IP 10.200.1.81 from vlan 100 192.168.2.4 then the SSH connection drops after 30 to 40 seconds. But if i ssh to the vlan 100 interface 192.168.2.81 then ssh is fine.

Would you please be able to provide some assistance on how I can get this fixed? Thank you!
You should only have ip(s) for mgmt and internal vlans on pve, or properly use linux vlans to tag them
 
You should only have ip(s) for mgmt and internal vlans on pve, or properly use linux vlans to tag them
Thanks for the reply, the PVE eth port is on vlan 100 (192.168.2.1/24) and then I have the pfsense VM with 3 pass through nics and those 3 ports are on the mgmt clan switch ports. I am not sure how to properly set this up in this current stage. Appreciate the help.

If i move my desktop to the mgmt VLAN and then try ssh into on the mgmt vlan as well then its fine. Its only dropping when i am on a different vlan.
 
Last edited:
Ok so I created 3 Linux Bridge connections in PVE as per below and enabled VLAN aware. vmbr0 is the dedicated IP for PVE.
1714278092737.png

Then for the pfAdmin VM, i did this; I add the 3 Linux Bridge cards (WAN, LAN, SYNC interface for CARP) On the unifi switch side these 3 ports are set to default untagged network. I also made sure that hardware checksum option is disabled on this router.

But I am still having the dropping SSH issue when i connect from VLAN100 192.168.2.1/24 over to the MGMT interface on pfsense (10.200.1.1/24) and again if i SHH into the VLAN100 interface of pf then no drops.
1714278162201.png

1714280778249.png

Just tested something.. So this issue only occurs on the router that is in BACKUP Carp status. As soon as i cut it over to Master then SSH remains up.

So it seems like i cannot ssh via inter-vlan to the pfsense that is marked as BACKUP.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!