Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Nicolassimond

#1
It's solved, it was unplugging it for the lunch and restart it, that's all...

But we have another bug leading to 100%cpu usage by Python when we check the logs of ipsec.


You should really get into a ticketing system for MSP and professionals, apart from the "anydesk" remote session like all the other vendors with full log analysis and everything.

The problem, even if we pay for support hours by default when buying your product, it that legally, I can't let you connect to our systems and customer's one without a NDA with each of your staff that may connect, which is a bit complicated you will agree.
#2
I asked what else I could look 5th post ago and didn't get any feedback on this.
I didn't know there was another way beside "opnsense-revert" to actually revert to previous version, so I didn't write further indeed.

If I get through the professional service that we paid for this firewall (and others) will I get the same answers?
#3
So, it won't change anything, I have already done this as written in my first post.

Where can I get the traffics logs and ipsec logs from command line? Web interface shows everything empty for ipsec (and as I said, I don't have any incoming traffic inside the tunnel on the watchguard so I can't see any error on it).
#4
I will test this afternoon, as I don't have access to the firewall right now.
But this won't reverse kernel and all the packages?
#5
The auto-update is suspected because it was working just before, you will agree that is has something to do with it.

Anyway, what could we check? To get rid of this?

Best regards,
#6
The cron update the firewall every 1 hour, that why I said it was the release just before (this one is on our test labs to check if we are going to resell opnsense firewalls)

We already check the other side, I don't think it comes from here, as we have the same watchguard on another location, with same update and same tunnels settings (except for the networks and public ip of course) that works flawlessly, this where it gets strange.

#7
Hello,

Last is: OPNsense 22.1.7_1-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1o 3 May 2022

The last working was the update before, we did the update yesterday (the firewall have a cron to auto-update, so I don't monitor the version number closely to be honest).
#8
Hello,

We have updated the OPNSense at our office to the latest release yesterday (auto-update in fact) and one of our two IPSEC tunnel won't let data goes through.

Both IPSEC tunnel goes to two up-to-date Watchguard's firewall at two different locations.

We have the same configuration on both site-to-site tunnels:
IPv4 IKEv2
Phase 1:  main   AES (128 bits) + SHA256 + DH Group 20   Mutual PSK
Phase 2: ESP IPv4 tunnel   AES256 + SHA256+ DH Group 20

The first tunnel work as expected:
State
INSTALLED
Routed

Stats
Time : 459
Bytes in : 70596
Bytes out : 59200


But the second won't accept traffic anymore:
State
INSTALLED
Routed

Stats
Time : 459
Bytes in : 0
Bytes out : 19228


We restarted both firewall, deleted the IPSEC config completly then made it from scratch, rolled back to the previous version on the opnsense firewall but nothing works.
We don't see the traffic comming to the watchguard or being rejected at all, it seems that nothing is going outside the opnsense firewall.

Any idea?
#9
Hardware and Performance / Very Slow IPSEC bandwith
August 17, 2021, 02:09:29 PM
Hello,

We have two OPNsense DEC3840 running the business edition
Here is the information on both of them:
OPNsense 21.4.3-amd64
FreeBSD 12.1-RELEASE-p19-HBSD
OpenSSL 1.1.1k 25 Mar 2021
AES-SNI enabled

We have an IPSec tunnel with the following settings:
PH1 : 128 bit AES-GCM with 128 bit ICV + SHA256 + DH Group 28
PH2 : aes128gcm16 + + 28 (Brainpool EC 256 bits)

I have tested different combination with and without hash and everything, and it doesn't seem to impact IPSEC performance.

We have 1Gbps professional connection on both side, and we only get 100mbps throughput on IPSEC (tested on smb copy, iperf).

Any idea of what is blocking IPSEC performance? The cpu usage doesn't move.


Thanks
#10
Hello,

I have a small problem.

Here is the deal.
We have a firewall at our main office that is connected to our two datacenters via two ipsec tunnels that works fine.

We want to connect via OpenVPN to our main office (this part is actually working too) and we also want to have access to our two datacenter subnets via this vpn.

Is it possible? I tried via pushing route throught ovpn client config but I don't get it working.

Thanks and best regards,