So I decided to run an external vulnerability scan against my home network. My scanning source computer was connected to my mobile hotspot and I targeted my home ISP IP. The scan came back with several ports open. I tested these same ports with nmap and they also show as open. However, testing the ports from several online port checker tools, they show as closed.
Ports 21, 53, 80, 443, 554 and 1723 are reported as being open on my router. I have a fiber connection going into a Frontier ONT, and the router is connected directly to that. I have Skynet installed and enabled. I have some port forwarding set up, and some OpenNAT rules for gaming, but I double checked and none of those ports listed earlier are in the list.
These are my WAN port forwarding settings:
Browsing to my DDNS name via http on the scanning computer (connected to my phone hotspot), I received a 504 Gateway Timeout. "The server is unreachable at this moment." I don't have a web server running so there shouldn't be anything listening on 443, or 80. I don't have those ports forwarded in the router.
I decided to check the router iptables configuration. Here is the iptables -L output:
The rules that stick out to me are in the INPUT Chain.
ACCEPT all -- anywhere anywhere state NEW
ACCEPT all -- anywhere anywhere state NEW
Should these rules be here? Doesn't that accept all inbound new connections? And why are there duplicates? I'm really trying to get to the bottom of why those ports listed above are showing as open on my WAN IP (They come bask as open using the vuln scanner, and nmap. They come back as closed with several online 3rd party port checker tools.)
Ports 21, 53, 80, 443, 554 and 1723 are reported as being open on my router. I have a fiber connection going into a Frontier ONT, and the router is connected directly to that. I have Skynet installed and enabled. I have some port forwarding set up, and some OpenNAT rules for gaming, but I double checked and none of those ports listed earlier are in the list.
These are my WAN port forwarding settings:
Browsing to my DDNS name via http on the scanning computer (connected to my phone hotspot), I received a 504 Gateway Timeout. "The server is unreachable at this moment." I don't have a web server running so there shouldn't be anything listening on 443, or 80. I don't have those ports forwarded in the router.
I decided to check the router iptables configuration. Here is the iptables -L output:
Code:
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
INPUT_PING icmp -- anywhere anywhere icmp echo-request
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
logdrop all -- anywhere anywhere state INVALID
PTCSRVWAN all -- anywhere anywhere
PTCSRVLAN all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state NEW
ACCEPT all -- anywhere anywhere state NEW
OVPN all -- anywhere anywhere state NEW
ACCEPT udp -- anywhere anywhere udp spt:bootps dpt:bootpc
INPUT_ICMP icmp -- anywhere anywhere
logdrop all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
REJECT udp -- anywhere anywhere udp dpt:ntp reject-with icmp-port-unreachable
REJECT tcp -- anywhere anywhere tcp dpt:ntp reject-with icmp-port-unreachable
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
other2wan all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
logdrop all -- anywhere anywhere state INVALID
SECURITY all -- anywhere anywhere
NSFW all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate DNAT
OVPN all -- anywhere anywhere state NEW
DNSFILTER_DOT tcp -- anywhere anywhere tcp dpt:853
logdrop all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain ACCESS_RESTRICTION (0 references)
target prot opt source destination
Chain DNSFILTER_DOT (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere MAC 38:F9:D3:62:FA:02
REJECT all -- anywhere !RT-AX88U-F610. reject-with icmp-port-unreachable
Chain FUPNP (0 references)
target prot opt source destination
Chain ICAccept (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
Chain ICDrop (0 references)
target prot opt source destination
logdrop all -- anywhere anywhere
Chain INPUT_ICMP (1 references)
target prot opt source destination
RETURN icmp -- anywhere anywhere icmp echo-request
RETURN icmp -- anywhere anywhere icmp timestamp-request
ACCEPT icmp -- anywhere anywhere
Chain INPUT_PING (1 references)
target prot opt source destination
logdrop icmp -- anywhere anywhere
Chain NSFW (1 references)
target prot opt source destination
Chain OVPN (2 references)
target prot opt source destination
Chain PControls (0 references)
target prot opt source destination
logdrop all -- anywhere anywhere
Chain PTCSRVLAN (1 references)
target prot opt source destination
Chain PTCSRVWAN (1 references)
target prot opt source destination
Chain SECURITY (1 references)
target prot opt source destination
RETURN tcp -- anywhere anywhere tcpflags: FIN,SYN,RST,ACK/SYN limit: avg 1/sec burst 5
logdrop tcp -- anywhere anywhere tcpflags: FIN,SYN,RST,ACK/SYN
RETURN tcp -- anywhere anywhere tcpflags: FIN,SYN,RST,ACK/RST limit: avg 1/sec burst 5
logdrop tcp -- anywhere anywhere tcpflags: FIN,SYN,RST,ACK/RST
RETURN icmp -- anywhere anywhere icmp echo-request limit: avg 1/sec burst 5
logdrop icmp -- anywhere anywhere icmp echo-request
RETURN all -- anywhere anywhere
Chain default_block (0 references)
target prot opt source destination
Chain logaccept (0 references)
target prot opt source destination
LOG all -- anywhere anywhere state NEW LOG level warning tcp-sequence tcp-options ip-options prefix "ACCEPT "
ACCEPT all -- anywhere anywhere
Chain logdrop (11 references)
target prot opt source destination
DROP all -- anywhere anywhere
Chain other2wan (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
logdrop all -- anywhere anywhere
The rules that stick out to me are in the INPUT Chain.
ACCEPT all -- anywhere anywhere state NEW
ACCEPT all -- anywhere anywhere state NEW
Should these rules be here? Doesn't that accept all inbound new connections? And why are there duplicates? I'm really trying to get to the bottom of why those ports listed above are showing as open on my WAN IP (They come bask as open using the vuln scanner, and nmap. They come back as closed with several online 3rd party port checker tools.)