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 - HatalaTitla48

#1
I found out that it was mistake in switch vlans config and ports connecting those two boxes. Its resolved now.
Thx guys for input.
#2
Hi, I have old box with multiple vlans/subnets connected to switch. On same network/vlan I have connected new opnbox to the same switch and created in opnsense direct route(192.168.12.0/24 192.168.12.1 - far gateway) to the subnet 192.168.12.0/24 on old box(it has own gw on 192.168.12.1).
Now comunication and routing works ok between boxes and subnets until I try access from openvpn client subnet(192.168.202.0/27) to the 192.168.12.0/24. On the old box i did put direct route to the networks on opnbox "route add -net 10.88.1.0 netmask 255.255.255.0 gw 10.88.1.254 eth5" and "route add -net 192.168.202.0 netmask 255.255.255.224 gw 10.88.1.254 eth5". Both work ok, I get even response from ip delegated to vpn user on its notebook. But ping from notebook to 192.168.12.1 is without response.
Ive been looking for a cause and found out about asymetric routing, both boxes have different gw. Ive tried on opnbox outbound(snat) NAT, to mask opnbox gw 10.88.1.254 for 192.168.12.5(ip of opnbox interface connecting to oldbox) but so far without success. Probably easy fix...where I should look?

Thx.
#3
Uf, I already tried this, but I forgot to put openvpn internal route subnet 192.168.202.0/27 to ipsec internal subnets...I need vacation for real.
Thx boss!
#4
Thx for reply.

Well situation is given and I cant switch from openvpn for roadwariors to something else. I already have functional IPsec s2s vpn running between boxes and there is not problem with that. Now I just need my openvpn users get to the subnets behind ipsec vpn on boxB(172.25.26.0/24). Iv get to the point of "Manual SPD entries in the IPSec Phase2", but even with this, its not working, I must just misst some crutial next step to get this working...
#5
Hi, Im searching for solution on howto let OpenVPN users access to the subnets behind IPsec vpn tunel. I did not find any up to date howto, just some hints here and there without any comprehensive text explaining how to setup this in current version of opnsense.

Connection schema is very basic, just: |*opnsensebox1 with (openvpn(for users) + ipsec vpn(s2s)*| --> |*opnsensebox1 with ipsec vpn(s2s)*|.

All I need right now is for users of openvpn(192.168.202.0/27 on box1) to access subnets(172.25.26.0/24) on box2 behind ipsec. So far I found only this "https://forum.opnsense.org/index.php?topic=40665.0" discussion, but it did not work for me. I must ommiting some additional steps needed for configuration. Do anybody has any functional instructions howto to achieve this?

Thx in sdvance.
#7
So, I read your bug description again "...wider issue in the API response handling which could affect other parts of the system...", it means that this bug corrupt only CA certs writen by acme plugin and other CA certs in opnsense certificate store arent afffected? Or all CA cert will be somehow affected? And if I remove them manually, what will prevent to happen this all over again if we are currently in phase "The actual source of why the CA certificate data is corrupted is unknown." Thx for clarification.
#8
Thx for the patch. I just updated to 25.7.5 and certs showing up as usual.
What would you think is outlook-timeframe for resolving this?
#9
Nope, its a VM. I even tried a new install and backup import and result is same. Are there any changes in how 25.7 handles certs compared to 25.1? Could it be a somehow cripled cert wich 25.7 cant chew up? This newer happened before through updates and it is a big problem for me, because I use this feature a lot...acme certs for haproxy, local CA for client cert access for haproxy, vpn crt etc.
#10
Backup restore didnt have any effect on this problem.
#11
I found out that certificates work ok, until upgrade to 25.7 version. Last working version is OPNsense 25.1.12-amd64. After upgrade to 25.7, certificate trust inside opnsense stop showing certificates, dashboard plugin "certificates" showing error and certificate part of opnsense is dead :(
#12
After update to 25.7, Certificates plugin in dashboard stop showing certs and get stack in constant loading.
When I go to "System: Trust: Authorities" it shows this error:
So Im efectively cut out from managing certificates on my box. Even if I cant access certificate management, certs are still in system because my HAproxy working ok with acme certs and even openvpn with internal certs. So there must be some bug when accessing internat cert storage.
Anybody with same problem here?
#13
Hello,

didnt found any results about goaccess, so I ask here. Did anybody managed to get goaccess working on opnsense? Has anybody working setup or functional workflow for using goaccess with haproxy or squid logs?

Thx.
#14
Virtual private networks / Broken OpenVPN s2s function
August 14, 2024, 09:46:46 PM
Hi, does anybody have functional s2s openvpn setup with latest opnsense(OPNsense 24.7.1)? Im getting on client side of openvpn setup message: "ERROR: FreeBSD route add command failed: external program exited with error status: 1. "
Problem is descripted here : https://github.com/opnsense/core/issues/7269 , but looks like nobody cares. Such a basic thing must be functional no matter what new upgrade is rolled up. How can I trust new updates if it results in problems like this? Opnsense team need to do more testing of basic things like this before roll up of new updates. This is home setup, now imagine you deploy this for your customer...cmon guys........
#15
This is a little bit older post, but for those who searching for possible solution for this, I can offer main:
I just roll up separate public service with 444 port and dedicated it to specific backends which I want to connect with client cert. I dont need those backends on 443, as these arent ment for public. This is simple and fast solution....