Hi!
The only requirement would be to reassign the interfaces.
What do you do when they are not an exact match?
My pfSense box is behaving very erratically (my guess is bad caps on the motherboard) and I tried to, temporarily, setup a new box…
Unfortunately even though both machines were more or less from the same era (Atom 330) they had different slots (PCIe vs PCI) and my real pfSense box had a mini-PCIe wireless NIC (Atheros based).
They also had different onboard NICs...
My real box has a PCIe Intel I340-T4 quad NIC and in the temporary replacement box I decided to reuse the old PCI Intel 21143 quad NIC I used in my previous non-pfSense based firewall.
The onboard NIC was not used in my real pfSense box so I assigned it to the onboard NIC of the new machine.
My WAN, LAN and DMZ which were provided by my I340-T4 were easy to match to to equivalent ports on the Intel 21143 based NIC...
The last port on the I340-T4 I was no longer using. I used to use it to connect a wireless access point.
The onboard mini-PCIe wifi card I could not match to anything... I am not sure if I was immediately able to delete it so it is possible I temporarily assigned to another port, I am not sure...
Once everything was done I deleted the unused onboard NIC (which I had created anyway) and the port assigned to the wifi...
What I ended up with was able to connect to the Internet since I was able to ping outside IPs but none of my Internal DNSes were working anymore...
I also had this error message (or variants on it):
There were error(s) loading the rules: /tmp/rules.debug:85: syntax error - The line in question reads [85]: altq on priq queue { qLink, qACK, qVoIP }
I believe this is traffic shapping stuff… Obviously it was quite unhappy about something I had done....
Was it the cause of my internal DNSes not working?
I don't know and could not investigate further when I tried this... I had to go back to the unstable box until I have time to try this again...
Thank you and have a nice day!
Season's Greetings!
Nick