Skip to content

Update KISSPORT default handling #333

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
Closed
wants to merge 2 commits into from
Closed

Update KISSPORT default handling #333

wants to merge 2 commits into from

Conversation

bjpetit
Copy link
Contributor

@bjpetit bjpetit commented Apr 26, 2021 •
edited
Loading

  • Do not require use of KISSPORT 0 to remove default setting from KISSPORT configuration
  • For existing config files with KISSPORT 0, the config file should work as it did previously, but the KISSPORT 0 setting will be ignored

bjpetit added 2 commits April 25, 2021 23:34
@bjpetit
Update KISSPORT default handling
eb94921 
- Do not require use of KISSPORT 0 to remove default setting from
  KISSPORT configuration
- For existing config files with KISSPORT 0, warn that the setting
  is not needed and ignore
@bjpetit
Update to fix using KISSPORT 0 to fully disable kiss ports
2343dd8 
This commit also removes the KISSPORT 0 warning from initial commit
@bjpetit bjpetit closed this Feb 12, 2022
@bjpetit bjpetit deleted the kissport_default_update branch April 24, 2022 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@bjpetit