Offene WAN IN Ports sperren

**Mosconi** · 14. Januar 2022

Hallo alle Zusammen,

ich hatte mir heute mal vorgenommen, bei Netzwerk von außen etwas sicherer zu machen.

Dazu habe ich mir aus dem USG die externe IP geholt und mittels nmap von meinem internen Linux Rechner einen Portscan veranstaltet.

Komisch ist nur, dass mir online Portscanner (heise, etc) komplett unterschiedliche Ergebnisse anzeigen.

Irgendwo hatte ich mal gelesen, dass die Unifi USG's bei Auslieferung keine offenen Port von außen haben.

Das Resultat hatte mich dann doch überrascht bzw. erschrocken.

PORT STATE SERVICE VERSION

22/tcp open ssh OpenSSH 6.6.1p1 Debian 4~bpo70+1 (protocol 2.0)

53/tcp open tcpwrapped

80/tcp open http lighttpd

443/tcp open ssl/http Ubiquiti Edge router httpd

Da ich ab und an mal Probleme hatte mit dem Unifi Controller und der Provisionierung mancher Geräte, hatte ich SSH in den Site - Einstellung aktiviert. Damit wollte ich aber nur lokal auf die Geräte zugreifen.

Nun ist für mich die große Frage:

Welche Ports müssen zwingend offen bleiben bzw. können geschlossen werden

und

wie schließe ich diese in der Firewall korrekt?

Da es ja Ports von außen sind denke ich mal in (WAN IN). Nur auf was kommt es dort an?

Da ich mich ab und an mal auf mein Netzwerk draufschalten muss, mache ich das über einen VPN Zugang. Welchen Port diese benutzt weiß ich aber grad nicht auswendig.

Grüße und schonmal Danke!

Mosconi

**razor** · 14. Januar 2022

Hallo Mosconi ,

wenn Du aus dem LAN kommst, um Deine WAN-Schnittstelle zu testen, dann kommst Du noch immer von innen und deswegen sieht das bei Dir auch so aus - für misch normaaaaaaaal:

Code

razor@ubu-20-lts:/mnt# nmap -v zuhause.meine-geile-domain.de
Starting Nmap 7.80 ( https://nmap.org ) at 2022-01-14 17:48 UTC
Initiating Ping Scan at 17:48
Scanning zuhause.meine-geile-domain.de (Telekom-IP) [4 ports]
Completed Ping Scan at 17:48, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 17:48
Completed Parallel DNS resolution of 1 host. at 17:48, 0.00s elapsed
Initiating SYN Stealth Scan at 17:48
Scanning zuhause.meine-geile-domain.de (Telekom-IP) [1000 ports]
Discovered open port 443/tcp on Telekom-IP
Discovered open port 22/tcp on Telekom-IP
Discovered open port 80/tcp on Telekom-IP
Discovered open port 53/tcp on Telekom-IP
Completed SYN Stealth Scan at 17:48, 0.05s elapsed (1000 total ports)
Nmap scan report for zuhause.meine-geile-domain.de (Telekom-IP)
Host is up (0.0013s latency).
rDNS record for Telekom-IP: 123456789.dip0.t-ipconnect.de
Not shown: 996 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
53/tcp  open  domain
80/tcp  open  http
443/tcp open  https

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.47 seconds
           Raw packets sent: 1004 (44.152KB) | Rcvd: 1001 (40.044KB)

Alles anzeigen

Wenn ich nun von meinem VPS scanne, dann erhalte ich beim ersten Versuch folgendes Ergebnis:

Code

root@vps101:~# nmap -v zuhause.meine-geile-domain.de -p U:53,111,137,T:21-25,80,139,8080,443,10000,51820,S:9 -sV --version-trace -Pn

Starting Nmap 7.40 ( https://nmap.org ) at 2022-01-14 19:04 CET
--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 1000, min 100, max 10000
  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
  parallelism: min 0, max 0
  max-retries: 10, host-timeout: 0
  min-rate: 0, max-rate: 0
---------------------------------------------
NSE: Using Lua 5.3.
NSE: Arguments from CLI:
NSE: Loaded 40 scripts for scanning.
mass_rdns: Using DNS server 212.91.*.*
mass_rdns: Using DNS server 212.91.*.*
Initiating Parallel DNS resolution of 1 host. at 19:04
mass_rdns: 0.00s 0/1 [#: 2, OK: 0, NX: 0, DR: 0, SF: 0, TR: 1]
Completed Parallel DNS resolution of 1 host. at 19:04, 0.00s elapsed
DNS resolution of 1 IPs took 0.00s. Mode: Async [#: 2, OK: 1, NX: 0, DR: 0, SF: 0, TR: 1, CN: 0]
Initiating SYN Stealth Scan at 19:04
Scanning zuhause.meine-geile-domain.de (Telekom-IP) [11 ports]
Packet capture filter (device eth0): dst host 212.91.*.* and (icmp or icmp6 or ((tcp or udp or sctp) and (src host Telekom-IP)))
Completed SYN Stealth Scan at 19:04, 5.01s elapsed (11 total ports)
Overall sending rates: 4.39 packets / s, 193.29 bytes / s.
Initiating Service scan at 19:04
NSE: Script scanning Telekom-IP.
NSE: Starting runlevel 1 (of 2) scan.
Initiating NSE at 19:04
Completed NSE at 19:04, 0.00s elapsed
NSE: Starting runlevel 2 (of 2) scan.
Initiating NSE at 19:04
Completed NSE at 19:04, 0.00s elapsed
Nmap scan report for zuhause.meine-geile-domain.de (Telekom-IP)
Host is up.
rDNS record for Telekom-IP: 123456789.dip0.t-ipconnect.de
Scanned at 2022-01-14 19:04:19 CET for 5s
PORT      STATE    SERVICE          VERSION
21/tcp    filtered ftp
22/tcp    filtered ssh
23/tcp    filtered telnet
24/tcp    filtered priv-mail
25/tcp    filtered smtp
80/tcp    filtered http
139/tcp   filtered netbios-ssn
443/tcp   filtered https
8080/tcp  filtered http-proxy
10000/tcp filtered snet-sensor-mgmt
51820/tcp filtered unknown

Read from /usr/bin/../share/nmap: nmap-payloads nmap-service-probes nmap-services.
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 10.43 seconds
           Raw packets sent: 22 (968B) | Rcvd: 5 (404B)

Alles anzeigen

Beim zweiten Versuch das:

Code

root@vps101:~# nmap -v zuhause.meine-geile-domain.de -p U:53,111,137,T:21-25,80,139,8080,443,10000,51820,S:9 -sV --version-trace -Pn
Starting Nmap 7.80 ( https://nmap.org ) at 2022-01-14 18:04 UTC
--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 1000, min 100, max 10000
  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
  parallelism: min 0, max 0
  max-retries: 10, host-timeout: 0
  min-rate: 0, max-rate: 0
---------------------------------------------
NSE: Using Lua 5.3.
NSE: Arguments from CLI:
NSE: Loaded 45 scripts for scanning.
mass_rdns: Using DNS server 127.0.0.53
Initiating Parallel DNS resolution of 1 host. at 18:04
mass_rdns: 0.04s 0/1 [#: 1, OK: 0, NX: 0, DR: 0, SF: 0, TR: 1]
Completed Parallel DNS resolution of 1 host. at 18:04, 0.04s elapsed
DNS resolution of 1 IPs took 0.04s. Mode: Async [#: 1, OK: 1, NX: 0, DR: 0, SF: 0, TR: 1, CN: 0]
Initiating SYN Stealth Scan at 18:04
Scanning zuhause.meine-geile-domain.de (Telekom-IP) [11 ports]
Packet capture filter (device ens160): dst host 10.10.104.50 and (icmp or icmp6 or ((tcp or udp or sctp) and (src host Telekom-IP)))
Discovered open port 443/tcp on Telekom-IP
Discovered open port 22/tcp on Telekom-IP
Discovered open port 80/tcp on Telekom-IP
Completed SYN Stealth Scan at 18:04, 0.00s elapsed (11 total ports)
Overall sending rates: 4941.60 packets / s, 217430.37 bytes / s.
Initiating Service scan at 18:04
Scanning 3 services on zuhause.meine-geile-domain.de (Telekom-IP)
NSOCK INFO [1.4480s] nsock_iod_new2(): nsock_iod_new (IOD #1)
NSOCK INFO [1.4480s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:22 (IOD #1) EID 8
NSOCK INFO [1.4480s] nsock_iod_new2(): nsock_iod_new (IOD #2)
NSOCK INFO [1.4480s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #2) EID 16
NSOCK INFO [1.4480s] nsock_iod_new2(): nsock_iod_new (IOD #3)
NSOCK INFO [1.4480s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:443 (IOD #3) EID 24
NSOCK INFO [1.4480s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 8 [Telekom-IP:22]
Service scan sending probe NULL to Telekom-IP:22 (tcp)
NSOCK INFO [1.4490s] nsock_read(): Read request from IOD #1 [Telekom-IP:22] (timeout: 6000ms) EID 34
NSOCK INFO [1.4490s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 16 [Telekom-IP:80]
Service scan sending probe NULL to Telekom-IP:80 (tcp)
NSOCK INFO [1.4490s] nsock_read(): Read request from IOD #2 [Telekom-IP:80] (timeout: 6000ms) EID 42
NSOCK INFO [1.4490s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 24 [Telekom-IP:443]
Service scan sending probe NULL to Telekom-IP:443 (tcp)
NSOCK INFO [1.4490s] nsock_read(): Read request from IOD #3 [Telekom-IP:443] (timeout: 6000ms) EID 50
NSOCK INFO [1.5260s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 34 [Telekom-IP:22] (42 bytes): SSH-2.0-OpenSSH_6.6.1p1 Debian-4~bpo70+1..
Service scan match (Probe NULL matched with NULL line 3492): Telekom-IP:22 is ssh.  Version: |OpenSSH|6.6.1p1 Debian 4~bpo70+1|protocol 2.0|
NSOCK INFO [1.5260s] nsock_iod_delete(): nsock_iod_delete (IOD #1)
NSOCK INFO [7.4510s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 42 [Telekom-IP:80]
Service scan sending probe GetRequest to Telekom-IP:80 (tcp)
NSOCK INFO [7.4510s] nsock_write(): Write request for 18 bytes to IOD #2 EID 59 [Telekom-IP:80]
NSOCK INFO [7.4510s] nsock_read(): Read request from IOD #2 [Telekom-IP:80] (timeout: 5000ms) EID 66
NSOCK INFO [7.4510s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 50 [Telekom-IP:443]
Service scan sending probe SSLSessionReq to Telekom-IP:443 (tcp)
NSOCK INFO [7.4510s] nsock_write(): Write request for 88 bytes to IOD #3 EID 75 [Telekom-IP:443]
NSOCK INFO [7.4510s] nsock_read(): Read request from IOD #3 [Telekom-IP:443] (timeout: 5000ms) EID 82
NSOCK INFO [7.4510s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 59 [Telekom-IP:80]
NSOCK INFO [7.4510s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 75 [Telekom-IP:443]
NSOCK INFO [7.4520s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 82 [Telekom-IP:443] (7 bytes): ......(
Service scan hard match (Probe SSLSessionReq matched with SSLSessionReq line 13306): Telekom-IP:443 is ssl
NSOCK INFO [7.4520s] nsock_iod_delete(): nsock_iod_delete (IOD #3)
NSOCK INFO [7.4520s] nsock_iod_new2(): nsock_iod_new (IOD #4)
NSOCK INFO [7.4520s] nsock_connect_ssl(): SSL connection requested to Telekom-IP:443/tcp (IOD #4) EID 89
NSOCK INFO [7.4530s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 66 [Telekom-IP:80] (146 bytes)
NSOCK INFO [7.4550s] nsock_read(): Read request from IOD #2 [Telekom-IP:80] (timeout: 4996ms) EID 98
NSOCK INFO [7.4550s] nsock_trace_handler_callback(): Callback: READ EOF for EID 98 [Telekom-IP:80]
NSOCK INFO [7.4550s] nsock_iod_delete(): nsock_iod_delete (IOD #2)
NSOCK INFO [7.4550s] nsock_iod_new2(): nsock_iod_new (IOD #5)
NSOCK INFO [7.4550s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #5) EID 104
NSOCK INFO [7.4560s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 104 [Telekom-IP:80]
Service scan sending probe HTTPOptions to Telekom-IP:80 (tcp)
NSOCK INFO [7.4560s] nsock_write(): Write request for 22 bytes to IOD #5 EID 115 [Telekom-IP:80]
NSOCK INFO [7.4560s] nsock_read(): Read request from IOD #5 [Telekom-IP:80] (timeout: 5000ms) EID 122
NSOCK INFO [7.4560s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 115 [Telekom-IP:80]
NSOCK INFO [7.5690s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 122 [Telekom-IP:80] (146 bytes)
NSOCK INFO [7.5710s] nsock_read(): Read request from IOD #5 [Telekom-IP:80] (timeout: 4885ms) EID 130
NSOCK INFO [7.5720s] nsock_trace_handler_callback(): Callback: READ EOF for EID 130 [Telekom-IP:80]
NSOCK INFO [7.5720s] nsock_iod_delete(): nsock_iod_delete (IOD #5)
NSOCK INFO [7.5720s] nsock_iod_new2(): nsock_iod_new (IOD #6)
NSOCK INFO [7.5720s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #6) EID 136
NSOCK INFO [7.5720s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 136 [Telekom-IP:80]
Service scan sending probe RTSPRequest to Telekom-IP:80 (tcp)
NSOCK INFO [7.5730s] nsock_write(): Write request for 22 bytes to IOD #6 EID 147 [Telekom-IP:80]
NSOCK INFO [7.5730s] nsock_read(): Read request from IOD #6 [Telekom-IP:80] (timeout: 5000ms) EID 154
NSOCK INFO [7.5730s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 147 [Telekom-IP:80]
NSOCK INFO [7.5900s] nsock_trace_handler_callback(): Callback: SSL-CONNECT SUCCESS for EID 89 [Telekom-IP:443]
Service scan sending probe NULL to Telekom-IP:443 (tcp)
NSOCK INFO [7.5900s] nsock_read(): Read request from IOD #4 [Telekom-IP:443] (timeout: 6000ms) EID 162
NSOCK INFO [7.5900s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 154 [Telekom-IP:80] (495 bytes)
Service scan match (Probe RTSPRequest matched with GetRequest line 10568): Telekom-IP:80 is http.  Version: |lighttpd|||
NSOCK INFO [7.5900s] nsock_iod_delete(): nsock_iod_delete (IOD #6)
NSOCK INFO [13.5970s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 162 [Telekom-IP:443]
Service scan sending probe GetRequest to Telekom-IP:443 (tcp)
NSOCK INFO [13.5970s] nsock_write(): Write request for 18 bytes to IOD #4 EID 171 [Telekom-IP:443]
NSOCK INFO [13.5970s] nsock_read(): Read request from IOD #4 [Telekom-IP:443] (timeout: 5000ms) EID 178
NSOCK INFO [13.5970s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 171 [Telekom-IP:443]
NSOCK INFO [13.7260s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 178 [Telekom-IP:443] (347 bytes)
Service scan match (Probe GetRequest matched with GetRequest line 10127): Telekom-IP:443 is SSL/http.  Version: |Ubiquiti Edge router httpd|||
NSOCK INFO [13.7260s] nsock_iod_delete(): nsock_iod_delete (IOD #4)
Completed Service scan at 18:04, 12.28s elapsed (3 services on 1 host)
NSE: Script scanning Telekom-IP.
NSE: Starting runlevel 1 (of 2) scan.
Initiating NSE at 18:04
NSE: Starting hnap-info against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSOCK INFO [13.7280s] nsock_iod_new2(): nsock_iod_new (IOD #1)
NSOCK INFO [13.7340s] nsock_connect_ssl(): SSL connection requested to Telekom-IP:443/tcp (IOD #1) EID 9
NSE: Starting http-trane-info against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSE: Starting https-redirect against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSOCK INFO [13.7340s] nsock_iod_new2(): nsock_iod_new (IOD #2)
NSOCK INFO [13.7350s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #2) EID 16
NSE: Starting vmware-version against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSOCK INFO [13.7350s] nsock_iod_new2(): nsock_iod_new (IOD #3)
NSOCK INFO [13.7360s] nsock_connect_ssl(): SSL connection requested to Telekom-IP:443/tcp (IOD #3) EID 25
NSE: Starting vmware-version against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSOCK INFO [13.7360s] nsock_iod_new2(): nsock_iod_new (IOD #4)
NSOCK INFO [13.7370s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #4) EID 32
NSE: Starting http-trane-info against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSOCK INFO [13.7370s] nsock_iod_new2(): nsock_iod_new (IOD #5)
NSOCK INFO [13.7380s] nsock_connect_tcp(): TCP connection requested to Telekom-IP:80 (IOD #5) EID 40
NSE: Starting hnap-info against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: https-redirect against zuhause.meine-geile-domain.de (Telekom-IP:80) threw an error!
/usr/bin/../share/nmap/nselib/unicode.lua:34: attempt to get length of a nil value (local 'buf')
stack traceback:
        /usr/bin/../share/nmap/nselib/unicode.lua:34: in function 'unicode.decode'
        /usr/bin/../share/nmap/nselib/url.lua:226: in function 'url.parse'
        /usr/bin/../share/nmap/scripts/https-redirect.nse:62: in function </usr/bin/../share/nmap/scripts/https-redirect.nse:29>
        (...tail calls...)

NSE: [vmware-version Telekom-IP:80] Couldn't download file: /sdk
NSE: Finished vmware-version against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: [http-trane-info Telekom-IP:80] HTTP: Host returns 301 Moved Permanently instead of 404 File Not Found.
NSE: [hnap-info Telekom-IP:80] HTTP: Host returns 301 Moved Permanently instead of 404 File Not Found.
NSE: [vmware-version Telekom-IP:443] Couldn't download file: /sdk
NSE: Finished vmware-version against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSE: Finished http-trane-info against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: [hnap-info Telekom-IP:443] HTTP: Host returns proper 404 result.
NSE: Finished hnap-info against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: [http-trane-info Telekom-IP:443] HTTP: Host returns proper 404 result.
NSE: Finished hnap-info against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSE: Finished http-trane-info against zuhause.meine-geile-domain.de (Telekom-IP:443).
Completed NSE at 18:04, 0.82s elapsed
NSE: Starting runlevel 2 (of 2) scan.
Initiating NSE at 18:04
NSE: Starting http-server-header against zuhause.meine-geile-domain.de (Telekom-IP:443).
NSE: Starting http-server-header against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: Finished http-server-header against zuhause.meine-geile-domain.de (Telekom-IP:80).
NSE: Finished http-server-header against zuhause.meine-geile-domain.de (Telekom-IP:443).
Completed NSE at 18:04, 0.78s elapsed
Nmap scan report for zuhause.meine-geile-domain.de (Telekom-IP)
Host is up (0.00054s latency).
rDNS record for Telekom-IP: 123456789.dip0.t-ipconnect.de
Scanned at 2022-01-14 18:04:42 UTC for 14s

PORT      STATE  SERVICE          VERSION
21/tcp    closed ftp
22/tcp    open   ssh              OpenSSH 6.6.1p1 Debian 4~bpo70+1 (protocol 2.0)
23/tcp    closed telnet
24/tcp    closed priv-mail
25/tcp    closed smtp
80/tcp    open   http             lighttpd
139/tcp   closed netbios-ssn
443/tcp   open   ssl/http         Ubiquiti Edge router httpd
8080/tcp  closed http-proxy
10000/tcp closed snet-sensor-mgmt
51820/tcp closed unknown
Service Info: OS: Linux; Device: router; CPE: cpe:/o:linux:linux_kernel
Final times for host: srtt: 536 rttvar: 585  to: 100000

Read from /usr/bin/../share/nmap: nmap-payloads nmap-service-probes nmap-services.
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 15.34 seconds
           Raw packets sent: 11 (484B) | Rcvd: 11 (452B)

Alles anzeigen

Ich habe noch nicht alle 2^16 Ports von außen gescannt, reiche das aber gern nach, wenn Bedarf bestehen sollte. Von innen ist das sinnfrei - zumindest für mich.

Wenn Du Deinen Clients nicht traust, dann musst Du alles verbieten und nur die "paar" Ports öffnen, die Du brauchst. Spontan würden mit da nur für den Zugriff auf's Internet 53/udp und 80,443/tcp einfallen. Vielleicht noch RADUIS, LDAP, ADS, ... Keine Ahnung, welche Services Du noch erreichen können musst. Aber die musst Du dann eben alle öffnen.

**Mosconi** · 14. Januar 2022

Danke Dir!

Habs nun auch mal über ein Handy Hotspot versucht. Da läuft Nmap ins Leere.

Nur kann mir einer erklären, warum es von Innen nicht funktioniert... man will ja nicht dumm sterben.

**razor** · 14. Januar 2022

Zitat von Mosconi

Nur kann mir einer erklären, warum es von Innen nicht funktioniert... man will ja nicht dumm sterben.

Weil Du eben von innen kommst und damit aus UniFi-Sicht als sicherer Absender verstanden wirst.

Tuxtom007 · 15. Januar 2022

Zitat von Mosconi

....
Das Resultat hatte mich dann doch überrascht bzw. erschrocken.

PORT STATE SERVICE VERSION
22/tcp open ssh OpenSSH 6.6.1p1 Debian 4~bpo70+1 (protocol 2.0)
53/tcp open tcpwrapped
80/tcp open http lighttpd
443/tcp open ssl/http Ubiquiti Edge router httpd

Alles anzeigen

Wundert mich nicht - da du von innen testet und das funktioniert nicht.

Wenn du einen Portscan machst, immer von extern - gibt genug Testseiten, die das anbietet oder du machst es von einem anderen Anschluss aus.

**Peterfido** · 15. Januar 2022

Die UDM Pro macht dicht:

**Mosconi** · 15. Januar 2022

@Tuxtom007:

Die Online Testseiten hatte ich auch mehrfach ausprobiert. Nur kam da immer ein unterschiedliches Ergebnis raus. Mal waren es 2 offene Ports, mal keiner und bei der Nmap- Onlineseite waren es gleich über 6 offene Ports. Den traue ich nicht mehr so recht, solange ich nicht verstehe, warum diese Unterschiede auftauchen. Nachher gehts erstmal zu den Schwiegerleuten. Von dort wird auch nochmal getestet.

**Forum System** · 22. Januar 2022

defcon hat das Thema gepusht.

Willkommen! Melden Sie sich an oder registrieren Sie sich.

Offene WAN IN Ports sperren

5 Benutzer haben hier geschrieben

Wer ist war online

Benutzer online 90

Wer war online 272