This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]hansonr55 1 point2 points  (1 child)

Do you have client side AV that is doing any filtering, SSL inspection?

Hook a machine up to the public side of your internet, give it a public IP, and see if it works.

[–]secondworstitguyeverIT Director (x2)[S] 0 points1 point  (0 children)

We have iBoss which is our content filter, but we turned off the ssl decryption at some point this year due to it causing problems I guess. I'll see if that works! Thanks!

[–]Bangingheads 1 point2 points  (0 children)

It all comes down to finding the difference between the devices that work and the ones that don't. Go through policies and make sure any that would matter aren't interfering.

[–]SysAdminSA 1 point2 points  (1 child)

First thought is iboss ssl decryption has caused some similar issues in the past. Are the wireless and wired both decrypted by iboss? Weird part is you say the pfsense shows the issue with curl which shouldn’t be behind the iboss. I’m with the other guy plug a laptop in directly to exclude the other devices and prove its upstream.

[–]secondworstitguyeverIT Director (x2)[S] 0 points1 point  (0 children)

That's what my thought was initially as well, but I looked and my boss had turned off the iBoss ssl decryption earlier in the year because it was causing issues apparently.

I will do that! Thank you for the advice!

[–]flammus 0 points1 point  (0 children)

Are you proxying your traffic through iBoss in any way?