OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 18.7 Legacy Series »
  • Best practice re: Opnsense and packages you are not using
« previous next »
  • Print
Pages: [1]

Author Topic: Best practice re: Opnsense and packages you are not using  (Read 1851 times)

tre4bax

  • Full Member
  • ***
  • Posts: 132
  • Karma: 3
    • View Profile
Best practice re: Opnsense and packages you are not using
« on: November 21, 2018, 05:43:09 pm »
I have a few options that come as standard with opnsense that I am not using, nor planning to use.

for example DynamicDNS, DNSMasq, OpenDNS etc.

Is best practice to leave these alone as they will get automatic updates and stuff ongoing?  Or is it to remove stuff that you are not using to release memory and drive space used?  The later is obviously easier.  Having unused software on my router though seems unnecessary and a potential route for malware if I'm not actually using it so don't notice issues.

What does everyone else do?
Logged

fabian

  • Hero Member
  • *****
  • Posts: 2768
  • Karma: 199
  • OPNsense Contributor (Language, VPN, Proxy, etc.)
    • View Profile
    • Personal Homepage
Re: Best practice re: Opnsense and packages you are not using
« Reply #1 on: November 21, 2018, 06:35:26 pm »
If you disable dnsmasq, it will not run and is therefore only bloat on the HDD but not a security risk. DynamicDNS is a plugin which is installed by default because many users expected it to be still here. It may be uninstalled. For OpenDNS I cannot tell you what exactly is the case but it is probably not removable from core without extracting it to its own plugin which needs some core changes.
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 18.7 Legacy Series »
  • Best practice re: Opnsense and packages you are not using
 

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