@rcoleman-netgate THANK YOU :)
That did the trick

@spectre-988 said in Netgate SG-1100 unable to install packages:

I've been working on using the device at my home for a HA fail over device. I've got the device to become part of the HA but when the primary wants to sync the packages they aren't able to due to packages not being installed. I try to install myself but package manager just sits at waiting for the update system to initiate. I am not sure if the version of Pfsense I am using is the problem or the Bios. I know both are older and tried to update Pfsense version and get that the system is on a later version than the official release.

Without physically separated interfaces the 1100 is not suited for HA. It could do it, sure, but the WAN, LAN, and OPT are all the same NIC in the system, just VLAN'd to a switch. Your expectations should be very tempered -- failover cannot happen based on physical disconnection and is going to be unreliable.

Hi,

The solution it'a in this link: https://github.com/rbicelli/pfsense-zabbix-template/pull/118

I hope help somebody.

@returntrip https://youtube.com/watch?v=Fg_jIPVcioY

@nasheayahu said in HAProxy - route by domain name:

wwwkohanyimcom Host matches: no no www.kohanyin.com
kohanyimcom Host contains: no no kohanyin.com

I found the problem, my domain was spelled incorrectly... 😧

I know that this question is old, but it actually helped me getting tcptraceroute on opnsense. The key thing was pkg add from freebsd. So for me it needed to be updated since I am on freebsd:13:amd64, I found https://freebsd.pkgs.org/13/freebsd-amd64/ with search :)

So for me the resulting command was:

pkg add http://pkg.freebsd.org/FreeBSD:13:amd64latest/All/tcptraceroute-1.5beta7.txz

Still same version of tcptraceroute 2 years later, but it is how to find the package name that is important

So thanks for this thread.

@buzz2912
Sounds like;
https://forum.netgate.com/topic/173074/22-05-upgrade-breaks-remote-access-openvpn/15

same problem.

Nvm im dumb... didn't read this line:

@mcury Thanks but this doesn't work in the users file. I think it's very restricted in what sort of entries can be made :(

@jimp Ok. So I took a few minutes and there's somthing I'm not getting.

When the Update setting is set to 22.05 the Package Manager shows two updatable packages, WireGuard 0.1.6_1 and ipsec-profile-wizard 1.0_4.
Screenshot 22.05 .png

And much to my surprise, when the Update setting is set to 22.01, I see one updatable package WireGuard 0.1.6_1 !:
Screenshot 22.01 .png

Is this correct? Is WireGuard 0.1.6_1 supposed to work on 22.01, or not? Upgrading WireGuard to 0.1.6_1 is the action that took down WireGuard in our NH router.

Here are the messages from the NH log that appear to describe the problem:

Jun 27 21:12:15 kernel linker_load_file: /boot/modules/if_wg.ko - unsupported file type
Jun 27 21:12:15 kernel KLD if_wg.ko: depends on kernel - not available or version mismatch

What's wrong?

@dvl Great. Option 2 would have been to reinstall and restore from backup. 😥

The upgrade thing catches lots of people. I put it in my sig a while back. One such problem is when the package is dependent on a PHP version that doesn't exist in the older pfSense, so it gets upgraded. There's a redmine to hopefully fix it or at least block/warn people.

Well one issue with the move to the new version. Previously bind was installed on my /cf now it is in /var/etc/named/etc/namedb/ a side effect, is whenever the router is restarted all my keys specified as global option will vanish

include "/etc/namedb/acme-keys.key";
include "/etc/namedb/ddns-key-inf.key";
include "/etc/namedb/ddns-key-sec.key";
include "/etc/namedb/ddns-key.key";

An idea would be to save them in the pfsense configuration.

@dennypage said in WebUI takes forever to load if UPS unreachable...:

I am assuming that the host running the NUT sever is using a fixed IP address, yes? And in the NUT config on pfSense, are you using the IP address (rather than hostname) to identify the NUT sever?

Yep, my whole network is based around fixed IP's, either both on the machine and dhcp server or only in dhcp server. And yes pfsense connects via IP.

@dennypage said in WebUI takes forever to load if UPS unreachable...:

You might want to consider moving to using pfSense as the NUT sever and having the other host as a client. NUT on pfSense is very stable.

Well my room is kinda limited because of the network cabling, the pfsense box and the UPS is on the opposite end of my room. Would require a 5 meter+ cable to connect the 2. Thats why i opted for a dedicated box and ATM this problematic box is the only one i can use. Done a few things to it including installing intel-microcode package and seems to be stable now ( knocks on wood ).

@jimp Thanks that worked. It seems like the install process did not recognize that the Patches package was there and re-installed it. But left the menu option in place.
420937b5-a131-4cd4-9c3e-8450d18f77e7-image.png

@bmeeks OK ... I understand

Hmm, looks like that was changed here:
https://github.com/pfsense/FreeBSD-ports/commit/7f64c9db1a0f5c0ffc18afe7a9f7a9b9f82f9c67

Not sure how you ended up with both though.