[SOLVED] Minecraft Forge server "no route to host"
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Dell Optiplex 780
Intel Core 2 Duo E7500
2x2 GB DDR3 RAM
2x500 GB HDDs RAID0
CentOS 6.7 basic server
X and default GNOME installed (runlevel 3 I believe)
Minecraft server 1.7.10
Forge 10.13.4.1558
24 mods installed
If I try to connect to the server from my desktop using the LAN IP I get "No route to host" and if I use the public IP according to IPChicken I get "Connection timed out"
okay, how do you "connect"? Via ping? Try a ping, tell us what that brings. Next, what is the Class of the IP addresses? If they are in a separate class, chances are they cannot connect...
Consider this:
Quote:
Workstation - 192.168.1.5-255.255.255.0
Server - 10.0.0.5-255.255.255.0
No way you'll get access to the server...
So, output the IFconfig and check the IP address, do that on both machines.
Consider, however, that the IP address has to be the same class as your devices...the D-link router as first...I assume that it has an internal IP address like 192.168.1.1...that means all hosts in the network should (ideally) have addresses that begin with 192.168.1 and have an address from 2 upwards...like 192.168.1.2 for the server and 192.168.1.3 for the workstation...
Good luck...
Melissa
By connect I mean using the Minecraft client. My inet is 192.168.0.100 and the server's is 192.168.0.121
I tried connecting to the server in Minecraft using 192.168.0.121 as well as the server's public IP from IPChicken. I'll try some pings.
Code:
x@KUALUS ~ $ ping 192.168.0.121
PING 192.168.0.121 (192.168.0.121) 56(84) bytes of data.
64 bytes from 192.168.0.121: icmp_seq=1 ttl=64 time=0.260 ms
64 bytes from 192.168.0.121: icmp_seq=2 ttl=64 time=0.248 ms
64 bytes from 192.168.0.121: icmp_seq=3 ttl=64 time=0.251 ms
64 bytes from 192.168.0.121: icmp_seq=4 ttl=64 time=0.251 ms
64 bytes from 192.168.0.121: icmp_seq=5 ttl=64 time=0.250 ms
64 bytes from 192.168.0.121: icmp_seq=6 ttl=64 time=0.251 ms
64 bytes from 192.168.0.121: icmp_seq=7 ttl=64 time=0.251 ms
64 bytes from 192.168.0.121: icmp_seq=8 ttl=64 time=0.251 ms
^Z
[3]+ Stopped ping 192.168.0.121
x@KUALUS ~ $ ping 121.219.235.60 <-- Public IP from IPChicken
PING 121.219.235.60 (121.219.235.60) 56(84) bytes of data.
64 bytes from 121.219.235.60: icmp_seq=1 ttl=64 time=2.81 ms
64 bytes from 121.219.235.60: icmp_seq=2 ttl=64 time=2.70 ms
64 bytes from 121.219.235.60: icmp_seq=3 ttl=64 time=1.82 ms
64 bytes from 121.219.235.60: icmp_seq=4 ttl=64 time=1.85 ms
64 bytes from 121.219.235.60: icmp_seq=5 ttl=64 time=24.7 ms
64 bytes from 121.219.235.60: icmp_seq=6 ttl=64 time=1.98 ms
^Z
[4]+ Stopped ping 121.219.235.60
How do I check to make sure I have set up port forwarding with iptables? Perhaps I have not done that properly. I know the router and modem are clearly port forwarding correctly as you can see in the menus for them. (the port is 25565)
Connecting from the client to the server does not require port forwarding by the router or MODEM. That allows teh internet to connect to your server which you may not want yet.
You need to open the port in the server's firewall. You can do that easily by using system-config-firewall. If not already installed you can do that via yum. Must be root to use the configuration tool.
Connecting from the client to the server does not require port forwarding by the router or MODEM. That allows teh internet to connect to your server which you may not want yet.
You need to open the port in the server's firewall. You can do that easily by using system-config-firewall. If not already installed you can do that via yum. Must be root to use the configuration tool.
In my experience Minecraft servers always require port 25565 to be port forwarded. I could never connect to a particular friend's unless he did so.
There's a lot of options to enable in system-config-firewall. None seem to be what I want or allow a custom entry. How can I ensure I port forward TCP and UDP 25565?
I sorta know what I'm doing, but I sorta don't. All I know is that port-forwarding must be done, and it must be TCP and UDP port 25565.
How many times is NAT done on this network? Two? Three? NAT has to be done once. Having three NAT capable devices does not mean the feature must be enabled in all of them.
Sorry, just read your post again michaelk, it was late and I misread it when I replied. So I disable any port forwarding rules I created on the router and modem, correct? (Just so you know, there is a reason for my odd network setup)
There's no "forward" option in system-config-firewall. It goes from "DNS" to "FTP" with nothing in between, and it isn't at the start or end.
So sorry, I found "forward", I was looking in the list and didn't see it right there...
Okay, so I think I set it up correctly, but there were a lot of options to select. It works through the local IP, but using the public gives connection refused.
Okay I port forwarded everything and it works using the public IP. I had already tried this and it did not work, but that was because the modem had to have destination IP set to the IP of the wireless repeater. (Not 192.168.0.121)
Thank-you so much all for your help. Hopefully others can connect now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
