Open IamTaoChen opened 1 month ago
are you actually able to send traffic from the devices from current_user
towards abcd
or is it just that they are shown?
The output of status
is only trimmed if there is no connections from either to each other, if one host can access another, but not vice versa, it will have to be in the status.
I see. Yes, you are right. abcd
can ping current_user
, but current_user
can’t ping abcd
. However, the information of abcd
is shown on current_user
.
C:\Users\Admin>ping 100.64.0.b
Pinging 100.64.0.b with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 100.64.0.b:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Admin>ping 100.64.0.d
Pinging 100.64.0.d with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 100.64.0.d:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Admin>tailscale status
100.64.0.a a current_user windows -
100.64.0.b b abcd iOS active; direct x.x.x.x:49501, tx 724 rx 188
100.64.0.c c abcd iOS offline
100.64.0.d d abcd macOS active; direct x.x.x.x:57392, tx 2136 rx 940
I understand the logic now, but it seems a little weird. Since abcd
is the administrator, I don’t want everyone to know its information. Additionally, not only does tailscale status
output abcd
’s information, but the GUI of current_user
also displays the hostnames under the abcd account.
I understand, but this is how it is, Tailscale does the same for the upstream software as a service.
I see. Thanks.
I have the same problem
I see. Yes, you are right.
abcd
can pingcurrent_user
, butcurrent_user
can’t pingabcd
. However, the information ofabcd
is shown oncurrent_user
.C:\Users\Admin>ping 100.64.0.b Pinging 100.64.0.b with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 100.64.0.b: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Admin>ping 100.64.0.d Pinging 100.64.0.d with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 100.64.0.d: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Admin>tailscale status 100.64.0.a a current_user windows - 100.64.0.b b abcd iOS active; direct x.x.x.x:49501, tx 724 rx 188 100.64.0.c c abcd iOS offline 100.64.0.d d abcd macOS active; direct x.x.x.x:57392, tx 2136 rx 940
I understand the logic now, but it seems a little weird. Since
abcd
is the administrator, I don’t want everyone to know its information. Additionally, not only doestailscale status
outputabcd
’s information, but the GUI ofcurrent_user
also displays the hostnames under the abcd account.
I may be wrong, I forgot to disable the firewall of 100.64.0.d
. I'll double-check again.
UPDATE
tailscale status
. ping
command or tailscale ping
. tailscale ping
. This sounds correct to me
Is this a support request?
Is there an existing issue for this?
Current Behavior
my
policy.json
isThe client can access(show) the admins' devies.
Expected Behavior
The admins' devices shouldn't show
Steps To Reproduce
policy.json
tailscale status
Environment
Runtime environment
Anything else?
No response