• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Update required after manual edit of config.xml?

Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
2 Posts 2 Posters 2.6k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    Tenzen
    last edited by Mar 27, 2007, 9:12 PM Mar 27, 2007, 12:02 AM

    Hi,

    I'm exploring scripting the import of multiple-IP-address rules (e.g., authorized lists of servers, blocklists, etc) from a *bsd setup to pfsense.

    I'm trying to avoid entering the rules one at a time via the gui … and am looking at adding/editing the rules directly in /cf/conf/config.xml.

    The host-lists-as aliases feature planned for v2.x should solve this; but, installing HEAD without the "thumbs up" from the devs here is too much of a risk at the moment.

    If I manually edit /cf/conf/config.xml -- e.g., add a fw rule -- are the changes dynamically pushed to (pulled by?) pfsense?

    Or, do i have to -HUP something, or reboot?

    Iiuc, rules entered via the GUI are dynamically updated, not requiring a reboot for them to take effect, so I'm guessing something simply needs to be refreshed.

    The question is what? and, do I need to do it manually?

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by Mar 27, 2007, 12:20 AM

      Do something like this:

      vi /cf/conf/config.xml
      rm /tmp/config.cache
      /etc/rc.filter_configure_sync

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received