Authentication problem

Post here if you need help setting up your server, etc.
Post Reply
regedit
On Lightcycle Grid
Posts: 42
Joined: Sat Jun 27, 2009 12:41 pm

Authentication problem

Post by regedit »

I feel stupid for posting another problem but:

When ever i try to authenticate via regedit@forums i get the following error:
Login failed, reason: Server adress mismatch, 86.144.17.231:4534 <sent by client>
!=86.144.17.231:52451 (our address). Pharming suspected. If you are connecting
from LAN and get this error, either set "TRUST_LAN" on the server (only if your
LAN can be fully trusted, of couse) or use "SERVER_IP" to make the local IP known to the server.

I have set Trust_Lan to 1.
How can this problem be fixed?

THank You in advance.
User avatar
AI-team
Shutout Match Winner
Posts: 1020
Joined: Tue Jun 23, 2009 6:17 pm
Location: Germany/Munich
Contact:

Re: Authentication problem

Post by AI-team »

This is a serverside problem afaik
  
 
"95% of people believe in every quote you post on the internet" ~ Abraham Lincoln
 
 
regedit
On Lightcycle Grid
Posts: 42
Joined: Sat Jun 27, 2009 12:41 pm

Re: Authentication problem

Post by regedit »

can it be fixed?
User avatar
Z-Man
God & Project Admin
Posts: 11587
Joined: Sun Jan 23, 2005 6:01 pm
Location: Cologne
Contact:

Re: Authentication problem

Post by Z-Man »

Ah. You're a victim of port mangling, where the port forwarding you set up causes the master servers to see your server under a different port. To compensate, set

Code: Select all

SERVER_DNS 86.144.17.231
(or, if your public IP changes often, get a dynamic DNS entry that always points to it and enter the name of it there instead)

We're quite unprepared for other evil kinds of port mangling.
regedit
On Lightcycle Grid
Posts: 42
Joined: Sat Jun 27, 2009 12:41 pm

Re: Authentication problem

Post by regedit »

Thank You!
Its working now :)
regedit
On Lightcycle Grid
Posts: 42
Joined: Sat Jun 27, 2009 12:41 pm

Re: Authentication problem

Post by regedit »

uhhh, no.
Its not working.
Just tried it again and got the same message.

Code: Select all

[0] Command ACCESS_LEVEL_VOTE_REMOVE unknown.
[0]
[0] Bound socket to *.*.*.*:1550.
[0] Bound socket to *.*.*.*:4534.
[0] Setting CYCLE_BRAKE_DEPLETE (Group: Annoying) deviates from its default valu
e; clients older than 0.2.5.0 may experience problems.
[0] Connecting to Master Server 1...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 109.156.215.179:60910.
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.199688.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 2...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 109.156.215.179:61142.
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[33] Killing user 33, ping 1.25.
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.272117.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 3...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 109.156.215.179:61143.
[0] Login Succeeded. User Nr. 2
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.182154.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Connecting to Master Server 4...
[0] Killing user 0, ping 1.25.
[0] Login information sent. Waiting for reply...
[0] Got address 109.156.215.179:61144.
[0] Login Succeeded. User Nr. 1
[0] Syncing with server...
[0] Relabeling NetObjects...
[0] Syncing again...
[0] Done!
[0] Sending my server info...
[0] Logging out...
[0] Done!
[0] Killing user 0, ping 0.179139.
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[0] Ping charity changed from 0 to 500.
[0] Nobody there. Taking a nap...
[0] Timestamp: 2010/10/12 18:16:53
[0] Closing socket bound to *.*.*.*:4534
[0] Bound socket to *.*.*.*:4534.
[1] Received login from 109.156.215.179:61230 via socket *.*.*.*:4534, network v
ersion: 0.2.8.3.X (ID: 16).
[1] New user: 1
[1] regedit entered the game.
[0] Time:     27.4105 seconds
Sent:     13922 bytes in 141 packets (507.907 bytes/s)
Received: 5772 bytes in 88 packets (210.576 bytes/s)
[0] Timestamp: 2010/10/12 18:17:09
[0] Creating grid...
[0] Ping charity changed from 500 to 440.
[0] LaTeX entered the game.
[0] Gcc entered the game.
[0] Gdb entered the game.
[0] done!
[0] Resetting scores...
[0] New Match
[0] Go (round 1 of 10)!
[0] 3
[0] 2
[1] User 1 requests authentication as "regedit@forums".
[0] Password request sent to user 1, username "regedit", method md5, message "Lo
gin with Authority forums".
[0] 1
[0] 0
[0] LaTeX core dumped regedit for 3 points.
[0] regedit lost 2 points since it caused a general protection fault.
[1] Login failed, reason: Server adress mismatch, 109.156.215.179:4534 (sent by
client) != 86.144.17.231:4534 (our address). Pharming suspected. If  you are con
necting from the LAN and get this error, either set "TRUST_LAN" on the server (o
nly if your LAN can be fully trusted, of course) or use "SERVER_IP" to make the
local IP known to the server.
[0] AI team was awarded 10 points for being last active team.
[0] Winner: AI team
[0] Deleting objects...
[0] Deleting grid...
[0]
[0] Time:     13.3798 seconds
Sent:     15740 bytes in 162 packets (1176.4 bytes/s)
Received: 6918 bytes in 144 packets (517.047 bytes/s)
[0] Timestamp: 2010/10/12 18:17:23
[0] Creating grid...
[0] Ping charity changed from 440 to 103.
[0] done!
[0] Go (round 2 of 10)!
[0] 3
[0] 2
[0] 1
[0] 0
Anhy idea what could be causing it this time?
User avatar
theroze
Match Winner
Posts: 596
Joined: Mon Aug 10, 2009 7:30 am
Location: 47 72 69 64

Re: Authentication problem

Post by theroze »

nvm.
apparition wrote:You being able to kill so many players that quickly and efficiently is evidence that the community skill level must be dropping... Sad :/
Reigning champion of: Sir-spam-a-lot 2011
User avatar
Z-Man
God & Project Admin
Posts: 11587
Joined: Sun Jan 23, 2005 6:01 pm
Location: Cologne
Contact:

Re: Authentication problem

Post by Z-Man »

Well, your public IP changed. You either need to watch for that yourself and adapt SERVER_DNS every time, or get an account at, say, at dyndns.com (they recently reduced their free service, but it should still be good for your purposes), keep that up to date (they provide tools) and set SERVER_DNS to the hostname of that account.

Or you wait for the code to be able to handle your scenario by request of another setting.
Post Reply