xavier666@lemmy.umucat.day Well, at the time, there was no AI. So a lot of this was just me and stack overflow. I imagine it’s a lot easier now.
I had 3 Ethernets. 2x 10Gbe. 1x 1Gbe.
My Synology would directly connect to the proxmox directly using the 10Gbe since it has immich on it and the source of truth is on the Synology.
The other 10Gbe went into the 10Gbe switch which had ports for 2.5Gbe and my wifi 7 connects to this.
The main WAN would come in on the 1Gbe.
Any random settings that I updated, I would lose everything and have to plug in a keyboard and redo the .conf.
What I ended up doing was just have one the 10Gbe as the router WAN and then the 1Gbe became the console/different VLAN and so I don’t count on the router to connect to my pfsense.
I still at the very end just gutted pfsense out and gave it a proper box. Never a problem since.
Dultas@lemmy.world 23 hours ago
It will come back if you set it to start on boot. Make sure you set its priority to start before anything else that requires network connectivity. If you ever move to having a cluster it’ll be a real headache because you won’t have a network for quorum and so you’ll have to physically access the box to force start it. I would highly recommend going out and getting a NUC or some other dedicated hardware as a priority before any other expansion.