Internet lost in PfSense but VPN or everythingelse work well?

mucip

Hi @Gertjan,
Mine config looks good I guess;

Regards,
Mucip:)

stephenw10

What pfSense version are you running?

Where did you set those DNS servers? In the client or in pfSense directly?

Gertjan

@mucip

192.168.1.1 on WAN ?
So you've changed the default pfSense LAN to something else like 192.168.0.1 /24

Not monitoring ? because ?

mucip

Hi @stephenw10,
I use 2.7.0.

I have modem in the office with DMZ to PfSense box.

Regards,
Mucip:)

Gertjan

@mucip

You like the 2.7.0 bugs better as the 2.7.2 bugs ?

mucip

@Gertjan ,
I check and it says I use latest version?

mucip

@Gertjan ,
Is this bug?

stephenw10

At the command line run: certctl rehash

Then re-check.

That's probably also the pkg issue you are seeing.

mucip

@stephenw10 ,

Now I can see below screen;

Gertjan

@mucip

Aha !!
You saw that ?
Fiirst :

then, after the 'patch' (I sometimes have this strange feeling that @stephenw10 is an AI Netgate bot that is here to drop this "run: certctl rehash" command (sorry, stephenw10, I couldn't resist))

and then

which opens the path to 2.7.2.

Be ware that 2.7.2 won't free you from all misery, as you're like us : upgrading is great, but more then often, don't forget to upgrade the admin also (that's where most of the issues resides).
It will include a new OpenSSL and a way more recent OpenVPN.
If you are using the OpenVPN server you have to upgrade your clients also.
Easy enough : https://openvpn.net/client/client-connect-vpn-for-windows/ or : your phone app store etc.
Export a new OpenVPN client profile.
Import it into your OpenVPN client, and you're good.

stephenw10

Yup. You should upgrade though!

mucip

Hi @Gertjan,
Finally. Yes. Thanks.
I will try to update today.

Regards,
Mucip:)

mucip

Dear @stephenw10 ,
Finally...

Regards,
Mucip:)

mucip

Dear @Gertjan ,
I updated to 2.7.2 finally. I have one pfsense box in outer office.
As you advice I will update it to 2.7.2 too.
But first of all I apply "certctl rehash" command in other pfsense. :)

Thanks to all guys...

Regards,
Mucip:)

mucip

Dear @stephenw10 ,
It happend again. It's like dejavu? :)
I used "run: certctl rehash" and now everything turned to normal. But why? What is the reason?
Should I add this command in the cron or what?

Regards,
Mucip:)

Gertjan

@mucip said in Internet lost in PfSense but VPN or everythingelse work well?:

But why? What is the reason?

Afaik : when upgrading from pfSense <2.7.0 to 2.7.0, this command should have been part of the steps to do after the upgrade finishes.
The thing is : it was forgotten.

Don't worry, this situation only happened ones ^^ No need to thing about it anymore.

mucip

Dear @Gertjan,
I hope so. I already added this command to cron.
Well I will remove command from cron and check in the near future.

Regards,
Mucip:)

stephenw10

There should be no need to run that command manually in 2.7.2. The pkg scripts run it anyway when it's required.

How were you testing? If you simply ran pkg update from the CLI the client cert may have expired. Checking from the webgui should never hit that though.

mucip

Dear @stephenw10,
I updated from WEB GUI not CLI.
In any case this morning the people said me that there is no internet out from Linux server.
I applied our famous command "certctl rehash" from webgui command execute menu and everything turn to normal again.
I will check. If I need to apply same command again than I add this command in the cron and run every midnight.

Regards,
Mucip:)

stephenw10

Hmm, that is odd. The only thing that should help with is local certs on pfSense itself. So access to the pkg repos which requires a client side cert.

It shouldn't make any difference to routing traffic. Unless maybe that is going via VPN that requires a cert.