@Gertjan, thx very much for your awesome reply. I really appreciate it as I learned something new
To be honest, it's the first time I read something about the services.inc-file. Super interesting!!
Of course, I tried it and it works like a charm.
@IonutIT
I re edit my post above.
kea2unbound is innocent
The issue is deep in the GUI, and identical to my initial pfBlockerng issue.
I'll have a patch some where next week.
@NickJH
Check this one :
[image: 1720542373225-0a2b3de4-9ed3-4396-9d83-12078a0f97fa-image.png]
and hit the big bleu save button at the bottom of the page.
Worked for me
edit :
and we never believe a GUI as it nature is hiding all the info we're looking for :
a test !?!
Because I know I've entered this :
[image: 1720542563808-9d3fe825-15f5-4190-ad49-62c7c62fe8ec-image.png]
This must work :
C:\Users\Gauche>nslookup bureau2
Serveur : pfSense.bhf.tld
Address: 2a01:cb19:beef:a6eb:92ec:77ff:fe29:392c
Nom : bureau2.bhf.net
Addresses: 2a01:cb19:beef:a6eb::88
192.168.1.2
and this is correct ...
I'm also using static "IPv6 leases" because I really dont want to have to deal with IPv6 like '2a01:cb19:beef:a600:46d4:54ff:fe2a:36dc'.
My LAN IPv6 '2a01:cb19:beef:a6eb:92ec:77ff:fe29:392c' is already a horror. Gone are the day you can 'quickly' ping LAN using "192.168.1.1"
