diff --git a/Source/NETworkManager.Localization/Resources/Strings.cs-CZ.resx b/Source/NETworkManager.Localization/Resources/Strings.cs-CZ.resx index b20d624e70..83d8e246db 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.cs-CZ.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.cs-CZ.resx @@ -4948,7 +4948,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.de-DE.resx b/Source/NETworkManager.Localization/Resources/Strings.de-DE.resx index b707715539..d19caa92d9 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.de-DE.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.de-DE.resx @@ -4948,7 +4948,7 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Esc - Pingen, tracen, scannen... + Es ist immer DNS. Bis es das mal nicht ist. IP-Adresse zur Hand? Einfach hier eingeben... @@ -4960,7 +4960,7 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Jedes Tool – nur eine Zeile entfernt... - Etwas ausgefallen? Schauen wir mal nach... + Irgendwas down? Finden wir's raus... Ist es DNS? Es ist immer DNS... @@ -4975,7 +4975,7 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Bereit, wenn das Netzwerk es nicht ist... - Vor dem Neustart erst mal pingen... + Erst pingen, dann neu starten... Pingen, tracen, fixen... @@ -4984,7 +4984,7 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Ist es erreichbar? Finden wir es heraus... - Verbindung gefällig? Einfach den Host eingeben... + Verbinden? Einfach den Host eingeben... Es liegt nicht am Netzwerk. Vermutlich... @@ -4993,7 +4993,7 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Erst pingen, dann der Firewall die Schuld geben... - Gestern ging's noch? Schauen wir mal nach... + Auf meinem Rechner geht's. Auf deinem auch? Irgendwo zwischen hier und dort ist ein Paket verloren gegangen... @@ -5004,4 +5004,71 @@ Cloudflare speichert möglicherweise Ihre IP-Adresse und Netzwerkinformationen. Port-Profil + + Es werden {0} IP-Adressen gescannt. Dies kann längere Zeit dauern und benötigt viel Arbeitsspeicher. + +Scan starten? + + + Es können nicht mehr als {1} IP-Adressen gleichzeitig gescannt werden (angegeben: {0}). Den Eingabebereich in kleinere Bereiche aufteilen. + + + {0} Ports werden gescannt ({1} Hosts × {2} Ports). Dies kann längere Zeit dauern und benötigt viel Arbeitsspeicher. + +Scan starten? + + + Es können nicht mehr als {3} Ports gleichzeitig gescannt werden ({1} Hosts × {2} Ports = {0}). Die Eingabe auf weniger Hosts oder Ports aufteilen. + + + Erreichbar oder nur pingbar? + + + Das Netzwerk ist down. Der Kaffee nicht. + + + Jedes Timeout hat eine Geschichte. + + + Deine Netzwerktools direkt zur Hand. + + + Keine Route zur Vernunft. + + + Die Firewall sagt Nein. + + + Ein Befehl näher an „Es geht wieder“. + + + Befehle sind schneller als Maus-Expeditionen. + + + Pakete lügen nicht. Monitoring manchmal schon. + + + Erst mal prüfen, ob es wirklich kaputt ist. + + + Kein Bug. Paketverlust. + + + Es gibt keine Cloud. Nur das Netzwerk von jemand anderem. + + + Das ist ein Feature. Vermutlich. + + + Vertrauen ist gut, Pingen ist besser. + + + Die Pakete wissen, was sie getan haben. + + + Schon das Naheliegende geprüft? + + + Wenn es aufgelöst wird, existiert es. Sonst: Cache leeren. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.es-ES.resx b/Source/NETworkManager.Localization/Resources/Strings.es-ES.resx index a4fb289ac9..b8216cc338 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.es-ES.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.es-ES.resx @@ -4945,7 +4945,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4957,7 +4957,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5001,4 +5001,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.fr-FR.resx b/Source/NETworkManager.Localization/Resources/Strings.fr-FR.resx index 723c290f84..b0f31b531e 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.fr-FR.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.fr-FR.resx @@ -4948,7 +4948,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.hu-HU.resx b/Source/NETworkManager.Localization/Resources/Strings.hu-HU.resx index c5df016cf1..495dee2898 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.hu-HU.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.hu-HU.resx @@ -4948,7 +4948,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.it-IT.resx b/Source/NETworkManager.Localization/Resources/Strings.it-IT.resx index 26f689cc05..eb841ddc53 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.it-IT.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.it-IT.resx @@ -5047,7 +5047,7 @@ Per i dettagli consulta l'informativa sulla privacy di Cloudflare. Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -5059,7 +5059,7 @@ Per i dettagli consulta l'informativa sulla privacy di Cloudflare. Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5103,4 +5103,71 @@ Per i dettagli consulta l'informativa sulla privacy di Cloudflare. Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.ja-JP.resx b/Source/NETworkManager.Localization/Resources/Strings.ja-JP.resx index 1e15d8e0c8..69b067e182 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.ja-JP.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.ja-JP.resx @@ -4948,7 +4948,7 @@ Cloudflareは、お客様のIPアドレスおよびネットワーク情報を Esc - Ping、トレース、スキャン... + It's always DNS. Until it's not. IP アドレスをお持ちですか? ここにドロップ... @@ -4960,7 +4960,7 @@ Cloudflareは、お客様のIPアドレスおよびネットワーク情報を すべてのツールを 1行で... - 何かあった? 確認してみよう... + Something down? Let's investigate... DNS のせいかな? いつも DNS のせいなんだよね…… @@ -5004,4 +5004,71 @@ Cloudflareは、お客様のIPアドレスおよびネットワーク情報を ポートのプロファイル + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.ko-KR.resx b/Source/NETworkManager.Localization/Resources/Strings.ko-KR.resx index c108a1a9c3..8fd17914ea 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.ko-KR.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.ko-KR.resx @@ -4945,7 +4945,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4957,7 +4957,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5001,4 +5001,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.lb-LU.resx b/Source/NETworkManager.Localization/Resources/Strings.lb-LU.resx index 9177b7353c..b20a15a9da 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.lb-LU.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.lb-LU.resx @@ -4948,7 +4948,7 @@ Cloudflare späichert méiglecherweis är IP-Adress an Netzwierkinformatiounen. Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare späichert méiglecherweis är IP-Adress an Netzwierkinformatiounen. Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare späichert méiglecherweis är IP-Adress an Netzwierkinformatiounen. Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.nl-NL.resx b/Source/NETworkManager.Localization/Resources/Strings.nl-NL.resx index 05b85eb49c..47666d6ee0 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.nl-NL.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.nl-NL.resx @@ -4945,7 +4945,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4957,7 +4957,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5001,4 +5001,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.pl-PL.resx b/Source/NETworkManager.Localization/Resources/Strings.pl-PL.resx index bf8591b2b8..75ecd27996 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.pl-PL.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.pl-PL.resx @@ -4945,7 +4945,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4957,7 +4957,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5001,4 +5001,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.pt-BR.resx b/Source/NETworkManager.Localization/Resources/Strings.pt-BR.resx index c55f4f206c..f78aebb292 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.pt-BR.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.pt-BR.resx @@ -4948,7 +4948,7 @@ A Cloudflare pode registrar seu endereço IP e informações de rede. Consulte a Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ A Cloudflare pode registrar seu endereço IP e informações de rede. Consulte a Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ A Cloudflare pode registrar seu endereço IP e informações de rede. Consulte a Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.ru-RU.resx b/Source/NETworkManager.Localization/Resources/Strings.ru-RU.resx index 29519e45c7..3508873e4a 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.ru-RU.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.ru-RU.resx @@ -4948,7 +4948,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.sl-SI.resx b/Source/NETworkManager.Localization/Resources/Strings.sl-SI.resx index 09575a17fa..d7c9a23511 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.sl-SI.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.sl-SI.resx @@ -4938,7 +4938,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4950,7 +4950,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -4994,4 +4994,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.sv-SE.resx b/Source/NETworkManager.Localization/Resources/Strings.sv-SE.resx index a80ec6acee..03fb50c602 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.sv-SE.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.sv-SE.resx @@ -4945,7 +4945,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4957,7 +4957,7 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5001,4 +5001,71 @@ Cloudflare may log your IP address and network information. See Cloudflare's pri Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.zh-CN.resx b/Source/NETworkManager.Localization/Resources/Strings.zh-CN.resx index 2681e9ff0e..8c3cdc5ace 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.zh-CN.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.zh-CN.resx @@ -4949,7 +4949,7 @@ The new rule may apply to more traffic than the original rule (e.g. to all servi Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4961,7 +4961,7 @@ The new rule may apply to more traffic than the original rule (e.g. to all servi Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5005,4 +5005,71 @@ The new rule may apply to more traffic than the original rule (e.g. to all servi Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. + diff --git a/Source/NETworkManager.Localization/Resources/Strings.zh-TW.resx b/Source/NETworkManager.Localization/Resources/Strings.zh-TW.resx index 73fda9b7d2..37ccfcb07b 100644 --- a/Source/NETworkManager.Localization/Resources/Strings.zh-TW.resx +++ b/Source/NETworkManager.Localization/Resources/Strings.zh-TW.resx @@ -4948,7 +4948,7 @@ Cloudflare 可能會記錄您的 IP 位址與網路資訊。詳情請參閱 Clou Esc - Ping it, trace it, scan it... + It's always DNS. Until it's not. Got an IP address? Drop it here... @@ -4960,7 +4960,7 @@ Cloudflare 可能會記錄您的 IP 位址與網路資訊。詳情請參閱 Clou Every tool, one line away... - Something down? Let's check it... + Something down? Let's investigate... Is it DNS? It's always DNS... @@ -5004,4 +5004,71 @@ Cloudflare 可能會記錄您的 IP 位址與網路資訊。詳情請參閱 Clou Port profile + + {0} IP addresses will be scanned. This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} IP addresses cannot be scanned at once (maximum {1}). Split the input into smaller ranges. + + + {0} ports will be scanned ({1} hosts × {2} ports). This can take a long time and needs a lot of memory. + +Do you want to start the scan? + + + {0} ports cannot be scanned at once ({1} hosts × {2} ports, maximum {3}). Split the input into fewer hosts or ports. + + + Can you reach it, or just ping it? + + + The network is down. Your coffee isn't. + + + Every timeout has a story. + + + Your network tools, at your fingertips. + + + No route to sanity. + + + The firewall says no. + + + One command closer to "it's working". + + + Commands are faster than mouse adventures. + + + Packets don't lie. Monitoring sometimes does. + + + First, establish whether it's actually broken. + + + It's not a bug. It's packet loss. + + + There is no cloud. Just someone else's network. + + + It's a feature. Probably. + + + Trust, but verify with ping. + + + The packets know what they did. + + + Have you checked the obvious? + + + If it resolves, it exists. If it doesn't, clear the cache. +