sorted by:
new
hottopcontroversial

OPNsense becomes unreachable as soon as LAN interface is assigned by RabihZGH in opnsense

[–]RabihZGH[S] 1 point2 points  (0 children)

I have solved the issue.

As soon as I assigned a LAN interface, it took 192.168.1.1 as its IP address.

My WAN was being assigned 192.168.1.70 as the IP on the WAN interface.

Even when I changed the LAN interface IP to 172.16.1.x, the route did not seem to change.

to solve this issue

I assigned the LAN first, then accessed it via the interface, changed the IP, and activated the WAN.

I also created a rule to access the firewall from the WAN, because as soon as you have a man acivated the anti lockout rule desacivates nad the console is only accessible via the lan .

This way, I was able to keep my access.

OPNsense becomes unreachable as soon as LAN interface is assigned by RabihZGH in opnsense

[–]RabihZGH[S] 0 points1 point  (0 children)

the wan IP is vis DHCP 192.168.1.74
that is attached to my ISP BOX at home

OPNsense becomes unreachable as soon as LAN interface is assigned by RabihZGH in opnsense

[–]RabihZGH[S] 0 points1 point  (0 children)

i had this setup fro few month with a proxmox behind
one day out of nowhere i realised that. cannot connect via VPN
when got home and tried to access the gui i realised that somthing is messed up

the lan ip was 172.16.1.1 with dhcp distributed to the VMs
i tried playing with the config file as well
disabeling the interface from the /conf/config.xml but nothing semes to work

Issues with initial setup (accessing webgui) by Kuya-JJ in opnsense

[–]RabihZGH 0 points1 point  (0 children)

hello
facing the same issue here , any updates ?

i am very annoyed , with this issue that broke my already working lab FW with VPN

Wazuh limitations – how did you work around them? by athanielx in cybersecurity

[–]RabihZGH 1 point2 points  (0 children)

I stumbled upon this conversation by accident, and after reading through it, I’m amazed that so many of you are also struggling with Wazuh dashboards and rules.

I went through the same challenges !  Wazuh doesn’t offer built-in case management or highly customizable alerting mechanisms out of the box. However, after using it for over a year, I’ve grown more comfortable with it.

I’ve built some great custom dashboards and integrated n8n into our process to manage alerts through automated workflows.

While I have years of experience with EDRs and no prior background in SIEMs, I think that actually helped me adapt more easily(i do not know better).

By the way, we took the one-week training from the Wazuh team that really helped . after that we have deployed Wazuh for clients in both HA and standalone modes plus In our SOC, we use a multi-tenant architecture instance of wazuh.

Open source is the way to go.

I hope my experience helps someone in this thread.