Messages

 :'( :'( :'( :'( :'( :'( :'( :'(

ok, i just wanted to go back to planet earth anyway.

Not a joke. End of the line for you.

...said the king !

You can apologise for your toxic comment ...

Good joke !

Ok, let's all just settle down. Grab a beer or a Crown Royal or both and sit back...relax.

Sorry you got something wrong (same as franco did), but to criticize something factually does not mean to be vicious.

We all want to have running systems, that´s why (most of us) just report errors hoping they might be fixed soon.

franco complained about not being payed enough for his work, the admin wants an Intel NUC from the community for 550 € just to test Hyper-V.

franco also stated that the freeze-problems in 19.x with virtualized and some other bare metal systems might never be solved.

To me, no offence, this does not look very respectable.

I am afraid I have to look for alternatives again concerning our firewalls.

So you need a 550 €-NUC with an i5 for testing? Really?

Honestely, I don't care how you feel about me. IIf you've made your image on me based on the 14 (count 'em!) posts I've made so far, that's tells me more about you than about me.

As stated, I tried to be constructive, as do other people. But hey, we don't click. So whatever I offer is probably not any good. Too bad, I can live with that. I can't contribute code-wise if its <> .NET or gwbasic. But if my car's engine blows out, I can't fix it either. That doesn't mean I shouldn't drive one.

Anyway, it seems I can't help at all fixing this issue. Sorry community, my bad, I tried.

All good points, and I do see that you still try to stay matter-of-fact.

My advice to franco is not to blame the users for being upset, the serious people do not blame you, but the fact that there route to the WWW has been cut and - as you know - that´s a real show stopper today  ;)

Which actually amazes me is your statement about if this all can be fixed in OPNsense. That sounds really frustrated and makes me doubt if you still want to continue the project.

If that's how it is, please tell us, because, come on, not only you but we as the users also do not want to waste our time if it is useless.

No offense, but I think you should not be so sensitive.

It is very annoying indeed if you recommend updating to a version (19.x) which constantly crashes the total system of the users, while on the other site you take out a running (18.x) of support.

Besides you did not make it clear for days that the freezes were based on the update, so maybe I was not the only one who tried to find the mistake for hours on his own system.

After all it was quite a challenge to eliminate these mistakes and get back to running systems.

We all appreciate your work, but, sorry, those kind of bugs suck.

Seems to be solved now with a patch: https://forum.opnsense.org/index.php?topic=11456.msg53042#msg53042

Yep, seems to have solved the disconnects here. VPN stable since connection initiation for 8 hours now.

Thanks !

After upgrading to 19.1, the VPN-connection often but unregularly drops with a connection timeout, sometimes after half an hour, sometimes after some hours.

It has been rock solid before the upgrade.

Besides I have to mention that the OVPN-server runs on 19.1.1 (MBR boot) on Hyper-V, while the client under 18.7.10_4 (with UEFI-bios), so both Opensense are virtualized.

I can confirm that - with opnsense running as a VM under Hyper-V - is has something to to do with the bios of the server running the hypervisor: one old Siemens-Server of ours which just has MBR was upgrading the opnsense-VM to 19.x without problems, another Server with UEFI let the opnsense-VM freeze during updating as reported.

edit: forgot to mention that it made no difference to install the VM under Hyper-V as type 1 or 2

Ah, ok, I did not know this plugin yet (came from pfsense where it does not exist).

Works now.

Thanks a lot.

Where do I find the snort-vrt.xml file actually to paste the Oinkcode?

I did not find it under /usr/local/opnsense/scripts/suricata/metadata/rules .

You are absolutely right, we should have tried that before: no, they are still gone, even if we disable both services, so it should be something else. Strange...