Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update REMEDE.md, change example command name #75

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update REMEDE.md, change example command name #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ are some cases where reloading the configuration file is not enough and you
may need to "tickle" pfSense a little more to do what you want. This is not
common however a good example is getting newly defined network interfaces or
VLANs to be recognized. These situations are easily handled by calling the
**send_event** action with the payload **interface reload all** - see the example
**send_event** action with the payload **interface all reload** - see the example
included below and refer to a the resolution to [Issue #10](https://github.com/ndejong/pfsense_fauxapi/issues/10)

__NB:__ *As at FauxAPI v1.2 the **function_call** action has been introduced that
Expand Down Expand Up @@ -788,7 +788,7 @@ curl \
--insecure \
--header "fauxapi-auth: <auth-value>" \
--header "Content-Type: application/json" \
--data "[\"interface reload all\"]" \
--data "[\"interface all reload\"]" \
"https://<host-address>/fauxapi/v1/?action=send_event"
```

Expand Down