Recent posts

#1

26.1 Series / Re: NAT Reflection / Hairpinni...

Last post by Patrick M. Hausen - Today at 05:23:56 PM

Tricksy NATsesss ...

#2

General Discussion / Re: ddclient and deSEC

Last post by skywalker007 - Today at 05:18:32 PM

The easiest fix would be to add "preserve" to both options, so you can individually update A and AAAA without deleting the other one.
I use the native backend, not sure if ddclient haves different

#3

General Discussion / Re: ddclient and deSEC

Last post by Ampfinger - Today at 05:16:22 PM

As far as I know it's the same situation as before.

But I would also like to see this one fixed!

#4

General Discussion / Re: ddclient and deSEC

Last post by skywalker007 - Today at 05:12:16 PM

Hello,
I just came across exactly the same issue.
Is this something being worked on? Did you open a FR ticket for it?
The only workaround I see right now is to create separate hosts for v4 and v6 in deSEC.
I would really love to have ab option to update both A and AAAA record in one go.
Did someone try to implement this as custom?

thanks, Till

#5

26.1 Series / Re: NAT Reflection / Hairpinni...

Last post by Monviech (Cedrik) - Today at 05:10:22 PM

Or using IPv6 in general, ahh so nice no nat trickeries anymore. :)

#6

General Discussion / dynamic dns

Last post by pvpaulo - Today at 04:59:31 PM

I am currently using OPNsense and, while reviewing the official Dynamic DNS documentation, I noticed that the traditional ddclient backend is described as being in "sunsetting" mode, with a native Python-based backend provided as an alternative maintained by the project. However, the os-ddclient plugin is still available in the system, which raises some uncertainty regarding its current support and maintenance status. My question is: is ddclient still officially supported and actively maintained within OPNsense, or is it only kept for compatibility purposes while the native backend becomes the default solution? Is there any plan for complete deprecation of the ddclient backend in future releases?

Is there another option to implement a dynamic DNS since I can't switch providers?

#7

26.1 Series / Re: Divert mode "Write to ipfw...

Last post by Hantritor - Today at 04:42:53 PM

Thank you franco.
I thought that somehow the error "Invalid argument" is same nature. This error is very annoying and crushes Suricata almost every few minutes. Is there a way that i can gather more information from the system regarding the error and to provide it in some kind of more structured and correct way?   

#8

Q-Feeds (Threat intelligence) / Re: Looking for testers Q-Feed...

Last post by Q-Feeds - Today at 04:38:45 PM

I'm still seeing after the upgrade

{
  "status": "OK",
  "action": "Pass"
}

Did you check with a domain which is in the feed? This is one is:

Code Select Expand

kondmatex-app.com

#9

French - Français / Re: WireGuard entre 2 OpnSense...

Last post by SebTintin27 - Today at 04:33:50 PM

Bonjour,

Merci pour ton superbe retour, je n'ai pu y travaillé que ce jour.
J'avais enlevé le 0.0.0.0 dans le peer de FW en effet, je ne sais pourquoi à un moment donné tout mon trafic internet voulait sortir par A.
Je peux maintenant pinger depuis mon B.63 vers 1.1.1.1 et 8.8.8.8. et les autres IP publique.
Lorsque je regarde mes traces je sors bien par le site A.

Cependant subsiste encore une problématique, lorsque je ping une adresse (ex : www.google.fr), je n'ai pas de retour, mais l'IP de google cela fonctionne. (mon DNS de mon b.63 est mon opnsense en B.1) j'ai essayé de mettre un 8.8.8.8 > KO, A.1 > KO.

aurais-tu une idée ?

#10

26.1 Series / Re: Instant reboot wchen i che...

Last post by franco - Today at 04:30:59 PM

Could be a disk issue.


Cheers,
Franco