jelegend 0 Posted ... (edited) Hi I am looking to forward one of my ports through TCP on IPv4. I have connected to the vpn (tried both udp and tvp ports . Then setup Port Forwarding on the ports section. (BEWARE: My ISP has CGNAT so there's double a NAT that I have to punch through) Before connecting NetStat output is: Active Connections Proto Local Address Foreign Address State TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11333 20.54.37.64:https ESTABLISHED TCP 192.168.29.205:11343 172.67.202.182:https ESTABLISHED TCP 192.168.29.205:11368 ec2-15-207-57-185:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:10941 [2600:9000:2075:2000:a:15d0:77c0:93a1]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11346 upload-lb:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11347 airvpn:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11353 [2606:4700::6812:126e]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11354 [2a00:c6c0:0:154:4:d8aa:b4e6:c89f]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11355 del12s08-in-x04:https ESTABLISHED After connecting to vpn output of netstat is: Active Connections Proto Local Address Foreign Address State TCP 10.16.55.31:11421 upload-lb:https ESTABLISHED TCP 10.16.55.31:11451 37.218.245.111:https ESTABLISHED TCP 10.16.55.31:11593 104.18.11.207:https ESTABLISHED TCP 10.16.55.31:11595 104.18.11.207:https TIME_WAIT TCP 10.16.55.31:11600 172.67.214.69:https TIME_WAIT TCP 10.16.55.31:11603 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11604 104.16.87.20:https ESTABLISHED TCP 10.16.55.31:11606 104.16.87.20:https TIME_WAIT TCP 10.16.55.31:11608 104.16.19.94:https TIME_WAIT TCP 10.16.55.31:11609 ams15s40-in-f3:https ESTABLISHED TCP 10.16.55.31:11610 ams15s41-in-f14:https TIME_WAIT TCP 10.16.55.31:11614 204.79.197.219:https ESTABLISHED TCP 10.16.55.31:11623 ec2-52-202-215-126:http TIME_WAIT TCP 10.16.55.31:11627 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11628 104.16.126.175:https TIME_WAIT TCP 10.16.55.31:11629 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11630 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11631 1:https ESTABLISHED TCP 10.16.55.31:11632 1:https ESTABLISHED TCP 10.16.55.31:11637 ec2-15-207-57-185:https ESTABLISHED TCP 10.16.55.31:11638 ec2-15-207-57-185:https ESTABLISHED TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11393 213.152.186.42:https ESTABLISHED TCP 192.168.29.205:11633 20.199.120.182:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11396 airvpn:https ESTABLISHED However Port Forwarding over tcp does not work ? Edited ... by jelegend Quote Share this post Link to post
Staff 10015 Posted ... Hello @jelegend "Connection refused" usually implies that the packets reached your node and were actively refused. A firewall, or maybe the final service, might have dropped them. If you had had the packets lost between the server and you, or not forwarded at all, you would have seen "Connection timeout" error. Kind regards Quote Share this post Link to post
jelegend 0 Posted ... (edited) 3 hours ago, Staff said: Hello @jelegend "Connection refused" usually implies that the packets reached your node and were actively refused. A firewall, or maybe the final service, might have dropped them. If you had had the packets lost between the server and you, or not forwarded at all, you would have seen "Connection timeout" error. Kind regards My windows firewall is off so I know that's not the issue. My ISP is shitty so maybe they are behind it or I don't know. I thought a VPN might help get beyond any shitty practices that my ISP might be doing. So is there any way to know what this service etc might be that's refusing it ? I am not very well verse in the current tech that might be involved in this packet obstruction process Edited ... by jelegend Quote Share this post Link to post
Staff 10015 Posted ... @jelegend Quote My ISP is shitty so maybe they are behind it or I don't know. I thought a VPN might help get beyond any shitty practices that my ISP might be doing. Hello! About remote port forwarding you though right. Your ISP can't interfere because the data stream is still encrypted in the ISP devices, up to your own node. Quote is there any way to know what this service etc might be that's refusing it ? Strange question... It's the software that must receive the packets, in other words the software you run in your system which must be reachable from the Internet, the only software you forwarded an inbound port for. Kind regards Quote Share this post Link to post
Not connected, Your IP: 3.144.40.90
Online: 26459 users - 321879 Mbit/s total BW