Bogus port status reporting
First of all, I am stuck with Comcast. Not by choice. Bear that in mind whilst reading.
I am currently seeding at an average of 720 kb/s, so no, this is definitely not a n00b question. I have popped into the IRC channel a few times, but I'm a quiet guy. Been here for several years seeding things in the background. I'm working on my 2 TB seeding goal. Please send me requests if you need me to seed anything. I will have another box, a linux host, set up this month as a seedbox.
I am experiencing an issue with port scanning. Normally, this is not a bad thing. On any website I visit to scan my external IP, the ports 6881-6999 are reporting closed on their web portal.
-
I have a TP-LINK Archer C9 set as DHCP reserved (Comcast: 10.0.0.X) DMZ behind a Comcast ARRIS modem/router set into bridge mode as TP-LINK Archer C9 is set to the reserved 10.0.0.X DMZ host on the Comcast router.
-
TP-LINK Archer C9 has DHCP reservation for host PC.
-
TP-LINK Archer C9 has Virtual server for DHCP reservation for host PC coming from ports 6881-6999 external to 15667 on host PC.
*** TP-LINK Archer C9 has port triggering for DHCP reservation for host PC triggering port 15667 internal to open 6881-6999 as needed on TP-Link Archer C9. -
PeerBlock on host PC is set to allow in/out from port 15667 UDP/TCP * Windows Firewall on host PC is set to allow in/out from port 15667 TCP/UDP ***** Windows Firewall on host PC is set to allow qBitTorrent 3.1.1 in/out from port 15667 TCP/UDP
Port scanners tell me I'm still closed, yet I can still seed correctly. Quite obviously my forwarding rules are all working. What gives with the bogus closed status on the web portals (elsewhere)? qBitTorrent reports working NAT.
You should also know that I have IPv6 to 4 tunneling turned on on the TP LINK Archer C9 as there is a known firmware bug which causes a crash on the Comcast ARRIS modems, resulting in packet data loss when you use certain IPv6 protocols.******
