@stephenw10 said in Missing tags in the repo: @ohmantics said in Missing tags in the repo: 3008f30d2c2cabdd7e17f7fb922139da8681ffbd That is in 25.11 builds. Thanks! I think my next step is to change off of vtnet to some other virtual NIC type and try to keep the same MACs.

@stephenw10 I tried ppp-ipv6 pppoe0 up and it made no difference. In my case IPv6 works fine, its just the gateway monitoring doesn't go 'online', so I need to restart the Gateway service. IPv6 may continue to work in my case because the subnets are hard coded in the LAN pages, so configuration is manual of IPv6 addresses for each LAN, and the ISP just sends through anything in my /48. Hope that helps.

@IonutIT thanks

Aha, nice!

@bmeeks Yep, in this case I am just talking about the kernel source. The head for CE kernel is still public from what I can see, its for whatever reason the 2.8.0 and 2.8.1 branches are not.

Also see: https://docs.netgate.com/pfsense/en/latest/development/develop-packages.html

Yup, seeing that here. Likely related to the upstream firmware API issue. But those drivers shouldn't need to load anything without the hardware present anyway.

I suspect the root cause here is the same as this: https://redmine.pfsense.org/issues/15770

@luckman212 I use a manually added FreeBSD package, 'munin' that came with a file to be placed in /usr/local/etc/rc.d/ As per pfSense needs, I renamed it - added the .sh extension, and now the munin process get started at boot, and stopped at shutdown. I made this install many years ago, and as far as I know, the script only executes during boot and system shutdown. Not for network or other events etc. If FreeBSD would look like a Debian system (or clone) using init or systemd I could tell you way more, and I even think pfSEnse isn'tv really FreeBSD (no surprise, at it is, and it isn't ^^). Look at the kea script for an example, the first 3 / 4 lines. Afaik, pfSense it self, see here /etc/, all de rc...... files - for example rc.bootup - will all all these files. pfSense handle the hardware and software system events, and call whatever is needed, if system processes like 'unbound' needed to be restarted. So : and also during certain system events (e.g. interface link changes, IP address changes, and gateway events). never saw that happening with my own processes - as pfSense isn't really aware that these are running ones the system is up.

@RobbieTT There isn’t an official guide for trimming pfSense boot times since most delays come from legacy compatibility layers and service startup waits. A practical starting point is looking through /boot/loader.conf and /boot/loader.conf.local. Things like long USB probe delays, console waits, and unused driver modules can often be disabled or shortened.

Not currently, it would require some development.

@dennypage said in pfsense-tools.git clang gcc: @phil80 said in pfsense-tools.git clang gcc: portsnap fetch properly fetches freebsd ports collection FWIW, portsnap is very dead as far as the FreeBSD folk are concerned. All references to it were removed from the documentation 5 years ago, and its use is no longer supported. The original announcement is here: [HEADS UP] Planned deprecation of portsnap. Thank you for the reminder. I usually only use Latest. I always use git for collaboration In short life or one use jails, portsnap is way faster to fetch than git for one package compile Based on your linked article, I'll favor git in the future

Mmm, so prevent source tracking for specific IPs or subnets? I did wonder if sticky connections could be per gateway group. That seems like it should be possible. You could then use rules to route specific clients or subnets to a non-sticky group.

OK so it looks like you had two issues: The installer didn't work as you expected it to but you were able to get 2.8 installed and booted. The resulting install didn't behave as you expected. That's independent of the installer and 2.7.2 would have behaved identically in that situation. So after install you assigned two interfaces, pfSense names them WAN and LAN but any interface can be anything. And you configured them both to be DHCP since both subnets already have a DHCP server? The typical subnet conflict that users hit when installing behind another firewall if that pfSense uses 192.168.1.1/24 as the default LAN address and that subnet is also used by the upstream firewall WAN side. I assume you didn't hit that since both subnets already existed in your network so must be using different subnets? What are they? However you then say you set the LAN back to a static address? Presumably in the same subnet? By default pfSense creates firewall rules on the LAN interface to allow access to the webgui there. That applies whether the LAN is static or DHCP. How exactly were you trying to connect? From where?

Currently nothing I'm aware of but going forward some functions will likely be written in go and hence in the Nexus package. Obviously that assumes the Nexus package is always present so it is automatically re-installed at upgrade.