Resolved: The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was ''

[jrey]

@JonathanLee

for Reference

and long shot. what's your build date?

[JonathanLee]

It's still gone after fresh firmware at setup wizard.

[JonathanLee]

@stephenw10

How do I fix this??

It was gone right after the new firmware was installed? So is my cryptID having issues with 23.09.01??

[stephenw10]

Fix what exactly? The missing cryptoID?

Did you do a full power cycle?

[JonathanLee]

@stephenw10 yes full power cycle and after fresh firmware again once I get to setup wizard I have no cyptoID listed and the log errors

[JonathanLee]

Any ideas??

[JonathanLee]

I opened a TAC they just send me firmware again and closed it. Does it need a different build?

[stephenw10]

Are you sure it ever showed a CryptoID? The later 2100s didn't have the chip as we moved away from that.

Mmm, this looks like bug. Harmless but a bug.

[stephenw10]

Opened an internal bug report to investigate.

[JonathanLee]

@stephenw10

Here is it showing in 23.05.01

Yes my SG-2100 has one, is this the same as a TPM chip for encrypting drives?

[JonathanLee]

@stephenw10 could it be my bios that is showing? I don't know could a new SSD cause this? The cyptoID is on the pcb mainboard right?

[JonathanLee]

@stephenw10 Thanks for looking into this. I opened a TAC ticket but they just sent me firmware, when I said I installed it and it did not fix it the ticket was closed. I think he got mixed up with my ticket.

[stephenw10]

It's not a TPM device, it doesn't have anything to do with drive encryption.

I wouldn't expect a driver to make any difference here. I could just about imagine causing problems communicating with the chip but that would be the same in 23.05.1.

I assume running ping-auth -s correctly returns the crypto ID there?

[JonathanLee]

@stephenw10 said in The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was '':

ping-auth -s

in 23.05.01

So its something with that build? I also have issues with experimental ethernet rules and compex ath0 driver they no longer separate the layer 2 broadcast domains for ARP requests from LAN to Compex card, this version is prone to ARP broadcast storms across different interfaces before it broke them up I never showed traffic between the two interfaces.

https://forum.netgate.com/topic/184894/ethernet-rules-on-two-networks

[JonathanLee]

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

[stephenw10]

Did you try 23.09.1 without the new SSD installed?

[JonathanLee]

@stephenw10 yes but I can't remember I think it also had the same issue. Could a SSD cause this?

[stephenw10]

It could if, for example it somehow had the same smbus address as the crypto chip. It shouldn't but it works fine for me here in 23.09.1 without an SSD.

Is that test from 23.05.1 also with the SSD?

[jrey]

@JonathanLee

So as you have already noticed, I'm guessing, what you're showing is different than the build date I'm showing and posted above

Curious was that image before or after TAC sent you the new image, or is/was the date the same on both.

Still think it is different than just a package here or there, as was discussed here.

https://forum.netgate.com/topic/184681/after-update-2-7-2-23-09-1?_=1702938917839

[jrey]

@stephenw10 said in The command '/usr/local/sbin/ping-auth -s > /etc/thoth/thothid 2>/dev/null' returned exit code '127', the output was '':

The later 2100s didn't have the chip as we moved away from that

define "later" by D.O.M. - please.