+- Sinisterly (https://sinister.ly)
+-- Forum: Hacking (https://sinister.ly/Forum-Hacking)
+--- Forum: Network Hacking (https://sinister.ly/Forum-Network-Hacking)
+--- Thread: Port forwarding problems (/Thread-Port-forwarding-problems)
Pages:
1
2
RE: Port forwarding problems - Templar.Clown - 08-05-2014
(08-05-2014, 10:40 PM)Ligeti Wrote:(08-05-2014, 10:03 PM)Templar.Clown Wrote: I can ssh/putty into the ubuntu server and start the server but when I connect it fudges up.
That's why you should use nmap to scan the ports or wireshark to diagnose the traffic!
If you think it is a server issue then check the configuration of your server (which I think you already did).
If it is a router issue, then turn the machine into DMZ (in the router) and check the firewall configuration again with "iptables -vnL --line-numbers" and make sure that RELATED and ESTABLISHED are accepted (in the INPUT table).
If you want to test fast and dirty flush the tables "iptables -F"
That's all I can help you with mate... I am ashamed and sorry that I can't do more, and for that I kindly ask for forgiveness!
Peace
Lol I'll scan with nmap now and post the findings. I'm not turning it into DMZ, last time I tried that I had to factory reset my router....
RE: Port forwarding problems - Templar.Clown - 08-05-2014
Here are the results of a quick scan using nmap.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-08-05 17:49 Eastern Daylight Time
Nmap scan report for 192.168.254.19
Host is up (0.00017s latency).
Not shown: 99 closed ports
PORT STATE SERVICE
22/tcp open ssh
MAC Address: 08:00:27:0D:15:52 (Cadmus Computer Systems)
Nmap done: 1 IP address (1 host up) scanned in 30.05 seconds
I'm stuck... IDK how to let connections in. Maybe I'm doing the iptables wrong idk.
RE: Port forwarding problems - h3r0 - 08-05-2014
Just to verify from inside the network you are going from 192.168.254.31 and trying to connect to a minecraft server on 192.168.254.19:25565? If so this isn't a port forwarding issue (Yet) You aren't going "through" your router just yet. Make sure that port is open with nmap, and then test a connection with netcat (nc 192.168.254.19 25565). If any of that fails it is most likely an issue with your MC server. If not and it fails when you go {PUBLIC IP HERE}:25565 it is an issue with your port forwarding.
RE: Port forwarding problems - Templar.Clown - 08-05-2014
(08-05-2014, 10:54 PM)h3r0 Wrote: Just to verify from inside the network you are going from 192.168.254.31 and trying to connect to a minecraft server on 192.168.254.19:25565? If so this isn't a port forwarding issue (Yet) You aren't going "through" your router just yet. Make sure that port is open with nmap, and then test a connection with netcat (nc 192.168.254.19 25565). If any of that fails it is most likely an issue with your MC server. If not and it fails when you go {PUBLIC IP HERE}:25565 it is an issue with your port forwarding.
The public IP does the same thing just no "connection lost" in the server. And even after using iptables to try to open the port the only open port on the server is port 22 (ssh). I can assure you that everything is installed right. The server runs, it just will not let me connect.
RE: Port forwarding problems - h3r0 - 08-05-2014
(08-05-2014, 10:58 PM)Templar.Clown Wrote:(08-05-2014, 10:54 PM)h3r0 Wrote: Just to verify from inside the network you are going from 192.168.254.31 and trying to connect to a minecraft server on 192.168.254.19:25565? If so this isn't a port forwarding issue (Yet) You aren't going "through" your router just yet. Make sure that port is open with nmap, and then test a connection with netcat (nc 192.168.254.19 25565). If any of that fails it is most likely an issue with your MC server. If not and it fails when you go {PUBLIC IP HERE}:25565 it is an issue with your port forwarding.
The public IP does the same thing just no "connection lost" in the server. And even after using iptables to try to open the port the only open port on the server is port 22 (ssh). I can assure you that everything is installed right. The server runs, it just will not let me connect.
I would focus on getting it all working in LAN before moving out to WAN
RE: Port forwarding problems - Templar.Clown - 08-06-2014
(08-05-2014, 11:37 PM)h3r0 Wrote:(08-05-2014, 10:58 PM)Templar.Clown Wrote:(08-05-2014, 10:54 PM)h3r0 Wrote: Just to verify from inside the network you are going from 192.168.254.31 and trying to connect to a minecraft server on 192.168.254.19:25565? If so this isn't a port forwarding issue (Yet) You aren't going "through" your router just yet. Make sure that port is open with nmap, and then test a connection with netcat (nc 192.168.254.19 25565). If any of that fails it is most likely an issue with your MC server. If not and it fails when you go {PUBLIC IP HERE}:25565 it is an issue with your port forwarding.
The public IP does the same thing just no "connection lost" in the server. And even after using iptables to try to open the port the only open port on the server is port 22 (ssh). I can assure you that everything is installed right. The server runs, it just will not let me connect.
I would focus on getting it all working in LAN before moving out to WAN
The point of this is to get it working on LAN. I have stated many times I'm using it for personally testing of say maps/plugins before actual upload.
RE: Port forwarding problems - Templar.Clown - 08-06-2014
I'm closing this thread now. I have figured out what I needed to. For anyone looking do NOT use the recommended build. Use the latest release. That simple. Sorry and a big thanks to all who tried to help!