1
22.1 Legacy Series / Re: Giant filter.log
« on: April 25, 2022, 08:01:20 pm »
So, no plan to put it back ?
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.
Pages: [1]
2
19.1 Legacy Series / Re: pkg.opnsense.org not reachable via IPv6
« on: April 11, 2019, 04:19:16 pm »
Hi,
Are you 100% sure your IPv6 connectivity is correct ?
Are you 100% sure your IPv6 connectivity is correct ?
3
19.1 Legacy Series / Re: Security Audit Notification
« on: April 11, 2019, 04:17:50 pm »
Hi,
In my Security Audit I have this :
I looked into ClamAV website, and the last version is 0.101.2
But when I click on check update inside OPNsense web GUI, it seems that 0.101.2 isn't yet on the repo.
Anyone achieved to update it anyway ?
In my Security Audit I have this :
Code: [Select]
***GOT REQUEST TO AUDIT SECURITY***
vulnxml file up-to-date
clamav-0.101.1,1 is vulnerable:
clamav -- multiple vulnerabilities
CVE: CVE-2019-1798
CVE: CVE-2019-1785
CVE: CVE-2019-1786
CVE: CVE-2019-1788
CVE: CVE-2019-1789
CVE: CVE-2019-1787
WWW: https://vuxml.FreeBSD.org/freebsd/84ce26c3-5769-11e9-abd6-001b217b3468.html
1 problem(s) in the installed packages found.
***DONE***I looked into ClamAV website, and the last version is 0.101.2
But when I click on check update inside OPNsense web GUI, it seems that 0.101.2 isn't yet on the repo.
Anyone achieved to update it anyway ?
4
18.7 Legacy Series / Re: Timeout while connecting to the selected mirror.
« on: April 11, 2019, 03:06:31 pm »
Hi,
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
5
18.7 Legacy Series / Re: OPNSense System|Firmware|Update fails: Timeout connecting to selected mirror
« on: April 11, 2019, 03:06:14 pm »
Hi,
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
6
19.1 Legacy Series / Re: Timeout while connecting to the selected mirror opnsense
« on: April 11, 2019, 03:05:51 pm »
Hi,
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
Since I added in the web GUI a static route 0.0.0.0/0 to my ISP WAN gateway, all web GUI wizards/tools who connect to internet seems to work well.
It seems that some web GUI tools don't use the existing system routes table...
7
18.7 Legacy Series / Re: OPNSense System|Firmware|Update fails: Timeout connecting to selected mirror
« on: April 09, 2019, 04:15:58 pm »
Hi,
If you're stuck, this workaround works for me : https://forum.opnsense.org/index.php?topic=11341.0
212.32.245.132 stands for the repo pkg.opnsense.org
If you're stuck, this workaround works for me : https://forum.opnsense.org/index.php?topic=11341.0
212.32.245.132 stands for the repo pkg.opnsense.org
8
19.1 Legacy Series / Re: Timeout while connecting to the selected mirror opnsense
« on: April 09, 2019, 03:57:36 pm »
Hi,
Just registered here to say that I have same problem on v19.1 x64 on ESXi 6.5.
I read the other topic, and for me adding a static route to 212.32.245.132/32 through my ISP gateway solve the problem.
But this behavior sounds very strange, for me this workaround is like DIY stuff...
Just registered here to say that I have same problem on v19.1 x64 on ESXi 6.5.
I read the other topic, and for me adding a static route to 212.32.245.132/32 through my ISP gateway solve the problem.
But this behavior sounds very strange, for me this workaround is like DIY stuff...
Pages: [1]