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

#1
switching to OpenSSL - reboot - freeradius is working again. TOP!!!

many thanks,

Ralf
#2
Hi,

the freeradius wouldn't start with the error message:

Error: /usr/local/etc/raddb/mods-enabled/pap[13]: Failed to link to module 'rlm_pap': Cannot open "/usr/local/lib/freeradius-3*/rlm_pap.so"

Could you please help

best regards,

Ralf
#3
Hi MB,

creating a new interface for a child wifi and installing SENSEI again as a content filter fonly for this interface and block the categories "child porn", "adult", "pornography" and some more. Connecting with an iPAD, switching to private mode in safari and searching for "porn" at google. 60% of listed results are accessible. The rest are blocked by the Sensei splash screen.

Are the content filter under development? What about the other categories?

best

Ralf
#4
@mb:
thank you for your answer. But the premium edition is to expensive for home use - only for the feature excluding IP addresses. I looking forward to your next releases. In the meantime, I'll use my Sophos XG home on an APU for transparent content/security filtering.
#5
exclude devices?

Hi,

is it possible to bypass/exclude internal devices from scanning? i.e. there are streaming devices like Amazon FireStick  or Roon Rock that have issues with content.

I'm settimg all filters to allow - there are issues
I'm settimg the sensei engine in bypass mode - there are no issues

OpnSense are running on LANNER hardware with Intel C2558, 8GB RAM and server SSD.

best regards,

Ralf
#6
16.7 Legacy Series / Re: Routing for ports and ranges
November 12, 2016, 05:03:33 PM
Hi Franco,

sorry about my late reply. At the first step, I tried to route the internal net to an internal host. The result for HTTP should a loop and no internet connection. But this also doesn't work. see screenshot. The second step is to route only a range of the internal network.

The result should be:
- all traffic for a range of the internal network (192.168.101.30-100) for port 80 and 443 should routed to 192.168.101.18.

Until now I'm using Sonicwall and I've realized this request by a routing rule.

maybe you could help

Ralf
#7
16.7 Legacy Series / Routing for ports and ranges
November 08, 2016, 09:43:25 AM
Hi,

I'm trying to route a range of ip adresses from the internal lan to a separate content filter/web protection. The routing is only needed for port 80 and 443.
In the GUI I only found to create rules for complete networks and all ports.

How can I realise this ruleset?

Ralf