Messages

if i understand you correctly then there is no issue here.

You have configured the Ip addresses of your truenas and proxmox interfaces manually. By doing so, those hosts will never issue a DHCP request and will therefore not appear in the list of DHCP leases.

If you want these hosts to appear in the list of DHCP leases, then you should configure your host (truenas & proxmox) interfaces as DHCP but configure a static DHCP assignment (mapping) in OPNsense.

Signal 6 is Abort Program.

What resources have you provisioned for your VM?

Do you have the IP pool range configured correctly for the interface it is enabled for?

Other than that I wouldnt know. If the above is correct, maybe just blow the VM away and reinstall since its just a VM for testing. Perhaps something didnt go right when installing.

In my case, the IOT device pulled a DHCP address from the pool.  I clicked on the + sign next to that lease entry and made that same address static.

I did exactly this apart from i changed the IP address to one from outside the pool as is best practice. If you leave it as static assignment to an address inside the dynamic pool, you will see the error message that i posted in my last post.

steps taken: Device aquired 192.168.10.9 via DHCP from the pool. > I clicked leases > clicked the + sign next to that dynamic lease which brings you to the static mapping page > I changed the IP address there to 192.168.10.109 (outside the pool as is best practice) > clicked save and apply changes. No problems following this.

Same issue for me (noobie as well. Had pfSense some time ago, but also far from Pro there).

So, double entries on Leases page for static-assigned devices. IP is the same, MAC is also the same (so it's not the case of LAN vs WLAN interfaces, or 2.4G WLAN vs 5G WLAN).

I can't replicate the issue. I just added a static DHCP mapping for a device which had 192.168.10.9 given from DHCP pool. I gave it a static mapping of 192.168.10.109 (outside the pool). No duplicates showing after a good while now.

I'm on:
OPNsense 22.1.6-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1n 15 Mar 2022

And static assignments are not overlapping with DHCP range. I think, OPNsense even wouldn't allow this.

It allows it but you get an error message in the DHCP logs. I think it logs, "Dynamic and static leases present for [IP address]"

Could there be multiple client UID's coming from those devices? Perhaps checking the "Ignore Client UIDs" may sort it?

ok no problem.

If there is any steps you wish me to perform for testing etc or any way i can help in that regard please let me know and i'll do my best.

Hi,

It should be blocked to add comments to the video. I'm going to look into it.

Hi @sy

Did you have a chance to look at this? Is there any steps you would like me to perform to help test/troubleshoot? Do you need me to create a bug report?


Thanks

thanks for the clarification.

I can confirm that i can both view and add comments to youtube videos while the Youtube Comment option is blocked in App Controls under the default policy

Hi

I've recently installed Zenarmor on OPNsense to do some testing on the application control functions of it and have a question about the "Youtube Comment" option with regards to what is specifically allows/blocks?

I blocked as per the attached screenshot and I had assumed that it would prevent the comments section of youtube videos from being displayed but this does not appear to be the case with my testing.

If i also block Youtube and refresh the page with ctrl + F5 then the page does not load and i can see that its blocked in the Live Sessions Explorer so i know that the blocking is working in that instance.

So should that option block Youtube comments or does it block something else?

Thanks


Im testing it via a Debian 10 host running Firefox v 91.6

Zenarmor versions:
Engine Version: 1.10.1
UI version: 22.1.29
Database version: 1.10.22011611

OPNsense version: 22.1.2_1-amd64