Replies: 2 comments 4 replies
-
|
It needs to accept routes to send traffic to pods on other nodes; without this pods won't be able to communicate. What routes do you have that are preventing lan traffic from remaining local? Have you tried correcting your tailscale routing tables? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I already have a machine with --advertise-routes=192.168.6.0/24, and the Raspberry Pi's local IP address is 192.168.6.225. I consulted Gemini, and it informed me that this configuration could create a routing loop. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
In my local network environment, I have a Linux machine already deployed with Tailscale and advertise-routes enabled. After installing K3s on my Raspberry Pi, it causes a network issue where I can no longer connect to the Raspberry Pi using its local IP address.
Upon reviewing the code, I found that it executes tailscale set --accept-routes. I am unsure about the specific role of this mandatory accept-routes setting. Is it possible to make this configuration optional?
Beta Was this translation helpful? Give feedback.
All reactions