@tedquade The matter is now resolved.

Ted Quade

@jimp Now being on 23.01.b.20221221.1946 problem is solved for me.

@jimp save/apply/reboot cleared the error.

Ted Quade

What error do you see when you try to use that?

0x125c should be supported as you say:
https://github.com/pfsense/FreeBSD-src/blob/devel-main/sys/dev/igc/igc_hw.h#L29

It could be the hardware revision or perhaps the PHY the driver is objecting to.

The igc driver in 2.7 is identical to that in 23.01 from what I can see.

Steve

Thanks @jimp for the fix. I've re-tested with 23.01.b.20221221.1946 snapshot and the issue seems to be resolved.

@pfsjap There's a 21.1946 version out today.

The crypto chip is working. Just not detected on the dashboard.

I asked the same thing recently here.

Unbound in forwarding mode is usually a better choice anyway. 😉

This will be fixed in tomorrows build though.

@jimp Issue resolved, back in business.

Ted Quade

Thanks for the quick turnaround, @stephenw10 and @jimp! I applied the patch and confirmed this fixed the issue:

dig @192.168.113.1 plug07.redacted.. ; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> @192.168.113.1 plug07.home..redacted.. ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 865 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1432 ;; QUESTION SECTION: ;plug07.redacted... IN A ;; ANSWER SECTION: plug07.redacted... 3600 IN A 192.168.104.177 ;; Query time: 0 msec ;; SERVER: 192.168.113.1#53(192.168.113.1) (UDP) ;; WHEN: Tue Dec 20 10:09:53 CST 2022 ;; MSG SIZE rcvd: 68

No I don't expect it to be in the RC.

@ltolbert I have modified the script to exclude records like "logfile turned over due to size" and new protocols like ",sctp,". These records seem to cause the function "parse_firewall_log_line" (in syslog.inc) to not populate index names in the array "flent" and that causes the error I noted above. I think Dshield needs to review the logic of this script. I have it working but any new protocol or unknown line in the flter.log will break it again. I will add it has been fun learning about php scripts as I am self trained so I'm sure I have made some mistakes..

@jimp Thank you. I'll wait until tomorrow, tickle the system for an update and go from there.

If you update to a current snapshot that will work. That regression was fixed late last week.

There is an issue with the way the dashboard is detecting it. It's built into the kernel at the moment so selecting it doesn't have any effect on whether or not it is active.

https://redmine.pfsense.org/issues/13779

We will probably move it back to a module so the detection and selection mechanisms work as they did before. AES-NI had a similar issue and that's what we did there.

My solution was delete de ifsentence at line 720 from /user/local/libexec/pfSense-upgrade

Then:

rm /usr/local/etc/pkg/repos/pfSense.conf ln /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf /usr/local/etc/pkg/repos/pfSense.conf pfSense-upgrade -fy

I find the solution in this threat
https://forum.netgate.com/topic/176064/attempting-to-update-to-23-01-devel-corrupts-my-pfsense-installation/41

@grandrivers said in Unable to upgrade 2.7.0 Community to pfsense plus Dev:

not sure if started from scratch 2.6-23.01 if i could then apply config from 2.7 ??

You can import a 2.7 config into 23.01 as long as the config remains the same version:
https://docs.netgate.com/pfsense/en/latest/releases/versions.html

At some point after 23.01 release 2.7 may move to a new config version at which point the config will warn you when you try to import it. You may get unexpected results if you are using anything where the config format has changed.

Srteve

If you are running an older snapshot and seeing that error:

failed to update the repository settings!!!

Then do this to pull in the fixes for it:

pkg upgrade -fy pfSense-upgrade pfSense-base

Then upgrade from the command line to reach the current snapshot:

pfSense-upgrade -dy

Steve

@jimp Issue is resolved.

Ted Quade