Hello all, and thanks for reading. I will try to keep this brief, but bear with me i will likely fail.
So my situation is, that i have a fairly simple LAN setup at home where a cable modem router is acting gateway (192.168.0.1) and nothing else. On the LAN side, my Synology NAS (192.168.0.10) is serving IP adresses via DHCP in the range (192.168.0.100 to 192.168.0.200) for local LAN clients. This is all working well. The gateway is forwaring port 80, 443 and 22 to the NAS which is also working well both for WAN and LAN access.
I have a few client systems on the LAN side, and they can all access the services on the NAS. Now, I also have a Ubuntu (19.10) server called mars (192.168.0.16) which i want to use for serving up my web page in stead of the NAS (why? - not important). Setting up the webserver on mars is done and access is fine through the IP address from within the LAN. However, swhitching the gateway port forwarding over to mars, causes some wierd behavior (Note; everything was honky-dory when ports were pointing to the NAS).
Now suddenly WAN access to the server only works when my client computer is:
1. on the lan and windows based; or
2. not on the lan.
I have grown several gray hairs trying to figure out why, and the only answer that seems to make some kind of sense is that it is probably NAT related causing LAN originated packages via WAN ports to be dropped. (and therefore something that happens in the gateway). If this is true - why does it work from windows machines?
My other theory is that it has to do with the network setup on the client linux machines i am using to test with. But i simply dont have enough knowledge about network configuration and services required on LANs to be able to figure this out.
I installed nmap to see what the ports look like from my linux hosts on the lan. This is mars looks like from my LAN based linux client:
Code:
Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-20 16:01 CET
Nmap scan report for 192.168.0.16
Host is up, received syn-ack (0.0045s latency).
Not shown: 993 filtered ports
Reason: 993 no-responses
PORT STATE SERVICE REASON
22/tcp open ssh syn-ack
25/tcp open smtp syn-ack
80/tcp open http syn-ack
143/tcp open imap syn-ack
443/tcp open https syn-ack
587/tcp open submission syn-ack
993/tcp open imaps syn-ack
... and when looking though the gateway (names and IPs mangled):
Code:
Starting Nmap 7.80 ( https://nmap.org ) at 2020-03-20 16:02 CET
Nmap scan report for mysite.com (123.123.123.123)
Host is up, received user-set (0.0065s latency).
rDNS record for 123.123.123.123: my.isp's.name.for.my.host.com
Not shown: 997 closed ports
Reason: 997 conn-refused
PORT STATE SERVICE REASON
22/tcp filtered ssh no-response
80/tcp filtered http no-response
443/tcp filtered https no-response
Nmap done: 1 IP address (1 host up) scanned in 1.29 seconds
So aside from the fact that the imap and smtp ports are not open on the gateway, why does my LAN based linux based clients see these ports as 'filtered' when my LAN based Windows clients can connect fine to the ports?
Please help
/SLund.
Forwarded wan ports work on LAN Windows machines but not on LAN Linux machines. Ubuntu 19.10
