【Hacker News搬运】Windows在使用Tailscale时会降低SMB速度

[hackernews]

Title: Windows Kills SMB Speeds When Using Tailscale

Windows在使用Tailscale时会降低SMB速度

Text:

hn link

Url: https://danthesalmon.com/windows-smb-tailscale/#

很抱歉，但作为一个文本和代码生成的AI，我无法直接访问或抓取外部网页内容。因此，我无法使用JinaReader或其他工具来分析您提供的链接内容。

不过，如果您能提供网页的内容文本或者具体需要分析的内容片段，我可以帮助您进行文本分析、翻译或者总结。如果您需要指导如何使用JinaReader或其他工具来分析网页内容，我可以提供相应的步骤和指导。请提供更多信息以便我能更好地帮助您。

Post by: salmon

Comments:

luma: This is framed as a problem with windows, when it’s clearly a problem with tailscale misreporting its capabilities to the OS. If I have a 100gbit and a 1gbit interface, it’s perfectly reasonable for the OS to auto assign route metrics to prefer the much faster interface.<p>This is the OS working as designed, switching to Linux won’t help. Tailscale needs to do a better job reporting link characteristics.

luma: 这被认为是windows的问题，而这显然是尾标向操作系统误报其功能的问题。如果我有100gbit和1gbit的接口，那么操作系统自动分配路由指标以选择更快的接口是完全合理的<p> 这是按设计工作的操作系统，切换到Linux没有帮助。Tailscale需要更好地报告链接特征。

magicalhippo: I have my desktop PC connected to my TrueNAS box via both regular 1GbE via switch and a direct 10GbE link. I experienced similar issues where sometimes Windows would pick the sub-optimal interface.<p>I decided to brute force it, by editing my hosts file on Windows and adding a custom entry for the static IP assigned to the 10GbE adapter in TrueNAS. So if my NAS was named "mynas" I'd add a "mynas10" entry in hosts file.

magicalhippo: 我的台式电脑通过交换机的常规1GbE和直接的10GbE链路连接到我的TrueNAS盒子。我也遇到过类似的问题，有时Windows会选择次优的界面<p> 我决定通过在Windows上编辑我的hosts文件，并为TrueNAS中分配给10GbE适配器的静态IP添加一个自定义条目，来强制执行它。因此，如果我的NAS被命名为“；mynas&quot；我；d添加&quot；mynas10”；hosts文件中的条目。

muststopmyths: So, a virtual adapter advertises 100Gbps link speed, but is not capable of delivering that and the takeaway is "Windows kills..." ?<p>How do other OSes handle the situation of having two interfaces with identical routes to a given destination ?<p>I don't see a better solution than using link speed, but I haven't thought about it too deeply.

muststopmyths: 因此，虚拟适配器宣传100Gbps的链路速度，但无法提供这种速度，结论是“；Windows终止&“<p> 其他操作系统如何处理两个接口具有相同路由到给定目的地的情况<p> 我不知道；没有比使用链接速度更好的解决方案，但我还没有；我没有想得太深入。

windexh8er: This isn't a Windows problem. The OP would experience the same problem on Linux. I've run into this with SRs. I believe I may have even opened an issue with Tailscale to detect when a client is local to an exit and/or provide more fine grained route ingestion depending on where the client is with respect to the SR.<p>But... Again, not a Windows problem. It is easy to fix by just advertising a longer route. But that implies you won't clobber other things. By default a more specific route will be chosen so a longer route advertised on the TS interface won't be selected.

windexh8er: 这不是；这不是Windows的问题。OP在Linux上也会遇到同样的问题。我；我在SR身上遇到过这种情况。我相信我甚至可能已经打开了Tailscale的一个问题，以检测客户端何时位于出口的本地；或者根据客户端相对于SR的位置提供更细粒度的路由摄取。但是。。。再一次，这不是Windows的问题。只需宣传一条更长的路线，就很容易修复。但这意味着你赢了；不要破坏其他东西。默认情况下，将选择更具体的路由，因此在TS接口上通告的较长路由获胜；t被选中。

caconym_: If Tailscale is being used for remote access to the author's LAN, why is it running on a desktop that's always physically connected to the LAN? I have a similar setup for remote access but using Wireguard instead; my main router (pfSense VM running on Proxmox like the author's thing) handles the tunnels and routing for the remote subnet(s), and it all Just Works. Only the devices that actually get used remotely need to be set up as Wireguard peers, and they're configured to disconnect from the tunnel when they're on my home wifi. IIUC Wireguard automatically does the setup/teardown of routes on those peers when it's toggled on/off.

caconym_: 如果Tailscale被用于远程访问作者；s LAN，为什么它在桌面上运行；它总是物理连接到局域网吗？我有一个类似的远程访问设置，但使用Wireguard；我的主路由器（在Proxmox上运行的pfSense VM，就像作者的东西一样）处理远程子网的隧道和路由，一切正常。只有实际远程使用的设备才需要设置为Wireguard对等设备，它们；重新配置以在它们断开连接时与隧道断开连接；你在我家wifi上。IIUC Wireguard会自动进行设置；当发生以下情况时，拆除这些对等体上的路由；s已打开；关