Remote syslog localip #8061
Open
Remote syslog localip #8061
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
just add a static route and you should be fine, this is a quite common and easy to fix issue (you need to make sure traffic is send into the trap). See also the note in https://docs.opnsense.org/manual/diagnostics_interfaces.html#ping |
AdSchellevis
force-pushed
the
master
branch
5 times, most recently
from
6586a65
to
607e32a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We ran into a problem where remote syslog from branch offices won't be sent through an IPSEC tunnel to the central log server.
Solution to this issue is binding syslog-ng's source to a specific ip using syslog-ng's "localip" option.