OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of frakkin64 »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

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.

  • Messages
  • Topics
  • Attachments

Messages - frakkin64

Pages: [1]
1
24.1 Legacy Series / Virtual IP Alias & DHCP client failure
« on: June 08, 2024, 01:46:44 am »
I am using 24.1.7_4, my WAN is connected to my cable modem (it is a bridged configuration) which OPNsense uses DHCP to acquire the public-facing network address.  I also have a Virtual IP setup as an IP Alias to setup an extra private network IP on the WAN interface and a route to my modem's administration interface.  This is all working fine (any computer on the network behind OPNsense can access the admin interface on the modem) until the modem goes down and the OPNsense DHCP client fails, it appear dhclient-script is wiping the route and the alias while I am expecting it not to do that.

I guess the question is am I using the wrong feature, or is this a bug?

2
24.1 Legacy Series / Re: Download Complete certificate chain for Intermediate CA
« on: April 04, 2024, 02:17:21 am »
Quote from: jsingh on April 04, 2024, 01:26:25 am
The Certificate

Usually the CN on the certificate is the DNS name of the web host, and I plug in a SAN of DNS:<host name>.  I usually bundle the server cert + intermediate cert and configure that as the certificate on the web server, and the server private key, and then install the root certificate in the OS trusted store.

Usually I miss marking it as a Server certificate.  But I have issued several certs in OPNsense and imported into other services/containers/etc that host web apps and everything just works fine.

3
23.7 Legacy Series / Re: CPU Performance after 23.7 upgrade
« on: August 09, 2023, 12:58:23 am »
Quote from: franco on August 08, 2023, 09:40:51 pm
Perhaps reloading the config is heavier than expected, but it would also depend on the the size of the config.xml. Additional pairs of eyes are appreciated.

Not really seeing the same problem here (CPU-usage wise, but it is the one with the most CPU time racked up), but I profiled it with xdebug and other than sleep the top two calls are:
- return_gateways_status, with most of the time spent in legacy_interfaces_details/php::exec
- parse_config, with almost all of the time spent in OPNsense\Core\Config->toArray (lots of recursive calls for this one, sounds like it is serializing XML into a PHP array?)

Perhaps a caching option, checking mtime to decide whether to reload?

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2