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

#1
Wow, that will teach me for not reading the blog ahead of time...  I look forward to it. :D
#2
Perhaps I'm an odd one out on this because the machine I have OPNsense running on is a bit on the overkill side (Intel i7-2700k with 16 GB of RAM, a SSD and dual Intel PCIe gigabit network adapters), but the system/processor RRD graphs generated by my install are effectively useless because of how it graphs the number of running processes.  The running processes sets the graph scale to 200 when all other utilization is typically in the 1-3% range, I get a graph with one solid line of processes and a scattered bit of colored noise at the very bottom showing the utilization.

For an example, I have attached a recent System/Processor RRD graph to this post.  Perhaps an option to disable the graphing of processes, or to graph them separately from utilization would yield a more useful result on a system like this.
#3
I figured it would be a quick fix, thanks.
#4
Hello, I decided to try out turning one of my spare computers into a router and OPNsense seemed like a good distribution to start with.  However I am having an issue with multicast routing which is necessary for my ISP provided television streams...

When attempting to start or configure the IGMP proxy service, the webui will report that it successfully started, but the service will not be running.  The system log records the following error message:
OPNsense opnsense: /status_services.php: The command '/usr/local/sbin/igmpproxy -d4 -c /tmp/igmpproxy.conf' returned exit code '1', the output was 'igmpproxy: illegal option -- 4'

A workaround I have found is to log in to the shell at the console and execute the following command:
/usr/local/sbin/igmpproxy /tmp/igmpproxy.conf &
Doing so will successfully start the service and it will continue running from then.  Although any attempt to modify the service configuration, restart it from the webui, or rebooting the system will cause it to fail again requiring another manual start.

I'm not sure what the '-d4' or '-c' command line arguments applied by the webui are supposed to do, but either one will cause the service to fail if you try them at the shell.  The service will start with the -d and -v command line arguments though.