TribesNext

Welcome, Guest. Please login or register.
Did you miss your activation email?


TribesNext >  TribesNext.com Forums >  Support >  Server Support >  Dedicated Server and LAN users « previous next »
Pages: [1] Print
Author Topic: Dedicated Server and LAN users
kvgeorge1
Nugget
Posts: 6

View Profile
June 06, 2011, 11:05:32 AM »
I wanted to host a dedicated server and also be able to play against it on the same LAN that I have the server on.  When I startup the server, everything appears fine and the server is listed in the server list when I go online.  However, any client connecting to the server gets a UE immediately upon connection.  However, if I stop the server and run it as a LAN server (-nologin), then the users on my LAN can use the server with no issues, but as expected, will not show-up in the server list on Tribes Next.

Any suggestions?
Krash
Administrator
Posts: 257

View Profile
1: June 06, 2011, 01:02:44 PM »
Users within a network cannot join using the server's external address.  You can hit your 'Insert' key in the list to manually add the LAN address to your listing, and click in the 'Favorite' column to save it to you list.

kvgeorge1
Nugget
Posts: 6

View Profile
2: June 06, 2011, 07:18:32 PM »
So,  if I want users to play online that are on my local network, they will have to connect as described (pressing INSERT and connecting directly to the IP address), but outside users will be able to connect via the Master Servers?
Krash
Administrator
Posts: 257

View Profile
3: June 06, 2011, 07:59:30 PM »
Yes, that sounds about right. If the server is displaying on the list and the server was able to retrieve its own address, outside users shouldn't have any trouble connecting. 
The error you described wherein LAN connections cause the client to crash is a known issue that generally occurs when attempting to connect (usually multiple times in succession) to the external address from a local connection.  It's basically just a glitch on the client end caused by a quick server disconnection following an IP sanity check failure due to the server and client reporting mismatching addresses.


Alternatively to inserting the IP, local users could open up the console(~) and enter: 'queryLanServers(28000);' - where 28000 is your server's port.  This query is normally run on refresh, but was accidentally transposed for a similar function in the current version of the patch.

Virus
Nugget

Posts: 16

View Profile WWW
4: July 02, 2013, 12:51:36 AM »
I'm still having issues connecting to my public server from both the WAN and LAN addresses. Has this issue been resolved or is there a work-around for it?

Heat Killer
Scout

Posts: 479

View Profile
5: June 03, 2015, 07:00:17 PM »
I'm still having issues connecting to my public server from both the WAN and LAN addresses. Has this issue been resolved or is there a work-around for it?

This is generally always due to firewall issues.  Where is your server located in relation to where you're connecting from?

Virus
Nugget

Posts: 16

View Profile WWW
6: June 03, 2015, 11:57:27 PM »
The server is located on my network. Other peoples can join it, but when I connect from within the LAN, I get denied with a MITM attack.

Ragora
Seņor Nugget

Posts: 221

View Profile WWW
7: June 04, 2015, 04:58:45 PM »
The server is located on my network. Other peoples can join it, but when I connect from within the LAN, I get denied with a MITM attack.

Try connecting to the internet IP that the other people connect from. The way TN detects MITM attacks is a little odd.

"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Supposedly Einstein
Virus
Nugget

Posts: 16

View Profile WWW
8: June 05, 2015, 10:57:57 PM »
This is what I get when I connect to the server with the Local IP


This is what I get when I connect to the server with the WAN IP



Thyth
Apotheosis Incarnate

Posts: 798

View Profile
9: June 06, 2015, 04:54:41 PM »
What is your LAN IP addressing scheme? 192.48.26.0/24 network address in your LAN connection error corresponds to an Internet routable segment of Boeing's network. You cannot use Internet routable non-RFC1918 IP addresses in combination with NAT, or it will appear as if a man-in-the-middle IP routing attack is taking place.

You must use RFC1918 standardized IP addresses for your LAN to perform this kind of hosting with TribesNext. You will want to use RFC1918 addresses for your LAN anyway, because other applications will break in (perhaps more subtle) ways that are hard to predict. Acceptable addresses in the RFC1918 spec for non-routed networks are 10.0.0.0 through 10.255.255.255, 172.16.0.0 through 172.31.255.255, and 192.168.0.0 through 192.168.255.255.

Sarcastic, narcissistic, genius, resurrecting the game with brilliant strokes of wizardry.
Virus
Nugget

Posts: 16

View Profile WWW
10: June 06, 2015, 10:01:52 PM »
What is your LAN IP addressing scheme? 192.48.26.0/24 network address in your LAN connection error corresponds to an Internet routable segment of Boeing's network. You cannot use Internet routable non-RFC1918 IP addresses in combination with NAT, or it will appear as if a man-in-the-middle IP routing attack is taking place.

You must use RFC1918 standardized IP addresses for your LAN to perform this kind of hosting with TribesNext. You will want to use RFC1918 addresses for your LAN anyway, because other applications will break in (perhaps more subtle) ways that are hard to predict. Acceptable addresses in the RFC1918 spec for non-routed networks are 10.0.0.0 through 10.255.255.255, 172.16.0.0 through 172.31.255.255, and 192.168.0.0 through 192.168.255.255.

Words can not express how much I appreciate you. You are absolutely right. I reverted my IP scheme back to the default 192.168.x.x
Please... allow me to buy you a 6-pack.

Connecting via the WAN prompts an unhandled exception and crashes the client.
Connecting via the LAN (which is the preferred method anyway) works wonderfully.
« Last Edit: June 07, 2015, 07:55:38 AM by Virus »

Thyth
Apotheosis Incarnate

Posts: 798

View Profile
11: June 07, 2015, 06:07:45 PM »
Good to hear. I've added a note in the FAQ answer regarding these error messages clarifying that LAN servers must use RFC1918 addressing schemes.

Sarcastic, narcissistic, genius, resurrecting the game with brilliant strokes of wizardry.
Pages: [1] Print 
« previous next »
Jump to:  

irc.quakenet.org / #TribesNext Powered by SMF  © Simple Machines
anything