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

Fix harmless typos #429

Merged
merged 2 commits into from
Dec 6, 2024
Merged

Fix harmless typos #429

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
376cd54
fix typo
lmagyar Nov 23, 2024
0bf5163
fix typo
lmagyar Dec 3, 2024
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 tailscale/rootfs/usr/bin/protect-subnet-routes
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,9 @@ then
bashio::log.info "Adding local subnets to ip rules with higher priority than Tailscale's routing,"
bashio::log.info "to prevent routing local subnets if the same subnet is routed within your tailnet."
if (( 0 == ${#routes[@]} )); then
# Do not remote this warning, usually this is superfluous,
# Do not remove this warning, usually this is superfluous,
# but I've run into situation where Supervisor needed a restart to return valid interface address data
# (that seems to be a hard to reproduce bug, better have some log in the future than not.)
# (that seems to be a hard to reproduce bug, better have some log in the future than not).
# See: https://github.com/home-assistant/supervisor/issues/5361
bashio::log.warning " There are no local subnets to protect!"
bashio::log.warning " Maybe this is a temporary situation due to configuration change underway."
Expand Down
Loading