I can access the services behind SWAG from the internet. That’s fine.
I can’t reach the SWAG dashboard.
A ping from 192.168.200.21 to 192.168.100.11 works!
ping 192.168.100.11
PING 192.168.100.11 (192.168.100.11) 56(84) Bytes an Daten.
64 Bytes von 192.168.100.11: icmp_seq=1 ttl=64 Zeit=0.310 ms
64 Bytes von 192.168.100.11: icmp_seq=2 ttl=64 Zeit=0.234 ms
64 Bytes von 192.168.100.11: icmp_seq=3 ttl=64 Zeit=0.226 ms
64 Bytes von 192.168.100.11: icmp_seq=4 ttl=64 Zeit=0.213 ms
64 Bytes von 192.168.100.11: icmp_seq=5 ttl=64 Zeit=0.260 ms
64 Bytes von 192.168.100.11: icmp_seq=6 ttl=64 Zeit=0.237 ms
^C
--- 192.168.100.11 Ping-Statistiken ---
6 Pakete übertragen, 6 empfangen, 0% packet loss, time 5076ms
rtt min/avg/max/mdev = 0.213/0.246/0.310/0.031 ms
When I type http://192.168.100.11:81 into firefox nothing happens.
Firefox try to get a connection. After some minutes I get the Error message Der Server unter 192.168.100.11 braucht zu lange, um eine Antwort zu senden. (The server at 192.168.100.11 takes too long to send a response.)
Any ideas what the problem could be?
Which ports does the SWAG Dashboard respond to?
When I connect a PC to the network 192.168.100.x I can access the SWAG Dashboard. Do I have to allow access from a sub-network like 192.168.200.x first?