安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
"As Rust does not currently support dedicated IP addresses, all servers on a node share the same IP address. DNS amplification attacks target the main IP and not specific ports, so there is no way to determine which service was the attacker's target. All services on the node therefor receive the attack.
We are currently working on a way to have dedicated IP addresses in Rust. We have no ETA on when this will be available, but hope to have it out soon."
There are at the very least 23 other servers sitting on the same switch your server is on, if not more if this is a virtual server with many more VPSs on the same machine.
They could instantly remove the null route, yet 23 other customers or more would be affected. It is a numbers game. They can piss you off or piss off 23 others. Money wise which do you think is more important? One or 23? This also could affect countless other routers and customers.
This was my job to do this at my previous company and I assure you their SLA, TOS etc include this as an option that you agreed to, or your provider/host agreed to.
It sucks, but their point of view, it is the least intrusive to the most customers.