Messages

Fabian,
I'm still running into issues with ICAP.
1: No idea how to start ICAP. I tried using a shell, going to /usr/local/lib/ruby/gems/2.3/gems/icaprb-server-0.0.2/bin. and using start_server.rb. That didn't work. root@OPNsense:/usr/local/lib/ruby/gems/2.3/gems/icaprb-server-0.0.2/bin # ruby start_server.rb
/usr/local/lib/ruby/2.3/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler/setup (LoadError)
   from /usr/local/lib/ruby/2.3/rubygems/core_ext/kernel_require.rb:55:in `require'
   from start_server.rb:2:in `<main>'
2: What will the listen address become? The webpage uses Request Modify URL   icap://192.168.2.1:1344/avscanreq and Response Modify URL icap://191.168.2.1:1344/avscan.
However your website has it listed as icap://localhost:1344/echo
So which one is it? If it looks like yours, will it be the same thing listed twice?
I greatly appreciate the help you and the remainder of the forum members have posted.
Thank you,
Mike

Fourth option, and what I have running.
https://docs.opnsense.org/manual/how-tos/cachingproxy.html
Simple and works for me.

I have a Qotom Thin Mini PC with Intel Celeron j1900 processor onboard, quad core 2.42 GHz, 4GB RAM 64GB SSD, dual LAN dual display serial port(thank goodness for copy and paste).
I initially installed OPNSense, but it kept failing. Wife and family would contact me, irate as they were unable to go online.
Then I tried Sophos, and that too failed.
Then I tried the one that starts with a P, and had pretty good luck with that. It would run dangerously warm and only locked up a few times.
I was bored this past Tuesday and took it back down and re-installed OPNSense, RC1 and have all of my traffic running through the proxy for one machine only.  The four cores are running about 40 C and the sensor on the unit says 27 C.
So, with all of that in mind, is it possible that your unit locked up due to heat issues? Once they get warm, they do some really wonky things.

Franco and Fabian,
I thank you for your replies.
I did lock the package, and after a bit of finaggling, install icaprb-server, after I figured out I had to use ruby gem install. I then re-locked the package so I could fudge the the system.
Still can not get it to start and run, but that is a project to work on another day.
Again, thank you.
Mike

Fabian,
First post.
I tried installing ruby22-gems following your tutorial, and is what the terminal said:
root@OPNsense:~ # pkg install ruby22-gems
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01   
Fetching packagesite.txz: 100%    6 MiB   1.5MB/s    00:04   
Processing entries: 100%
FreeBSD repository update completed. 25860 packages processed.
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
   pkg: 1.9.3_3 -> 1.9.4_1 [FreeBSD]

Number of packages to be upgraded: 1

3 MiB to be downloaded.

Proceed with this action? [y/N]: N

So I thought I had read in the tutorial it was updated to 23, so I tried that, and I received the same error.
I am on OPNsense 17.1.r1 (amd64/OpenSSL)
Ideas?
Thank you.
Mike