pfSense » pfSense Plus

Intended to mention that having to manually add the interfaces back and DHCP not auto starting all began upon upgrading to the beta version 23.01.b.20230106.0600

Netgate staff member by the name of gonzopancho on Reddit ask for me to open a Redmine.

Here is the link if it is relevant.
https://www.reddit.com/r/PFSENSE/comments/10rhxwu/comment/j70f5cd/?context=3

tailscaled expects to solely own the tailscale0 interface.

pfSense is throwing an interface mismatch/change warning at startup because the tailscale interface doesn't exist that early in the startup process.

Unassign the tailscale interface and use the Tailscale interface group.

Christian McDonald wrote in #note-3:

tailscaled expects to solely own the tailscale0 interface.

pfSense is throwing an interface mismatch/change warning at startup because the tailscale interface doesn't exist that early in the startup process.

Unassign the tailscale interface and use the Tailscale interface group.

Jim Pingle wrote in #note-2:

The creation date you are referencing is the creation date of the default Boot Environment and that's normal/expected. It's going to show the date when that default BE was made. The BE entries created during upgrade or manually are branched off that and those will show the later dates.

The assignment issue is unusual but we need more information from the console output to even guess what is happening there. Please try to get a copy of the console output from before the assignment prompt. If it's a video console, press the Scroll Lock button on the keyboard and then page up or arrow up to view older console output. Press Scroll Lock again to get out of scrollback mode. If it's serial console, please save and attach the entire boot output. It should be printing a list of the interfaces it says it cannot match. If you can try assigning only the wireguard and/or tailscale interface (or neither) and rebooting that might also help narrow it down.

As for DHCP or other services not starting that will also need more information. Before manually starting DHCP, check the console boot output, main system log, and DHCP log to see if they have logged any errors regarding the DHCP service.

Thank you very much for clarifying that for me regarding the date. I wasn't aware and thought there might of been a issue at hand - considering when i upgraded to the beta version from 22.05 if showed a more recent time stamp and assumed the RC version would of as well. Moving forward I'll certainly remember and take into consideration the newly acquired knowledge.

Christian McDonald wrote in #note-3:

tailscaled expects to solely own the tailscale0 interface.

pfSense is throwing an interface mismatch/change warning at startup because the tailscale interface doesn't exist that early in the startup process.

Unassign the tailscale interface and use the Tailscale interface group.

Ok, rebooted again and only assigned the Wan, Lan, and Wireguard - leaving Tailscale out of the picture. Tested connecting with Tailscale afterwards when internet connectivity reestablished and it was successful with passing traffic. Checked the console and still only showed the three mentioned interfaces prior. Performed a reboot to test if the issue would replicate itself again and the system successfully booted all the way to the console menu without any issues retaining the configuration. Upon checking the GUI I verified that the DHCP service also started properly.

Certainly a very interesting approach and at the same time I learned something new in the process.

Both the Interface and DHCP issue appear resolved - Please feel free to mark/close out the ticket at your leisure.

Thank you for your assistance in regards the matter. An I cannot express enough the level of gratitude and appreciation for the work you all put into maintaining such a top notch product.