creating dedicated server - wrong ip address

[NHLfan]

Hi,

I have already created a server long time ago, today I tried to re-create a dedicated server again.
But the problem is, that the server cannot start, because it has a wrong ip-address

root@free-clan:~# openttd -Df -c /usr/share/games/openttd/openttd.cfg
dbg: [net] [core] starting network...
dbg: [net] [udp] initializing listeners
dbg: [net] [core] network online, multiplayer available
dbg: [net] Detected broadcast addresses:
dbg: [net] 0) 85.14.223.255 // <-- CORRECT ip address
dbg: [net] [udp] closed listeners
dbg: [net] [udp] initializing listeners
dbg: [net] [tcp] could not bind on IPv4 port 67.215.65.132:3979 (IPv4): // <-- I don't know from where this ip address comes
Cannot assign requested address
dbg: [net] [server] could not start network: Could not create listening socket
dbg: [net] Generating map, please wait...
dbg: [net] Map generation percentage complete: 5
dbg: [net] Map generation percentage complete: 11
dbg: [net] Map generation percentage complete: 15
dbg: [net] Map generation percentage complete: 20
dbg: [net] Map generation percentage complete: 25
dbg: [net] Map generation percentage complete: 30
dbg: [net] Map generation percentage complete: 35
dbg: [net] Map generation percentage complete: 40
dbg: [net] Map generation percentage complete: 45
dbg: [net] Map generation percentage complete: 50
dbg: [net] Map generation percentage complete: 55
dbg: [net] Map generation percentage complete: 60
dbg: [net] Map generation percentage complete: 65
dbg: [net] Map generation percentage complete: 70
dbg: [net] Map generation percentage complete: 75
dbg: [net] Map generation percentage complete: 80
dbg: [net] Map generation percentage complete: 85
dbg: [net] Map generation percentage complete: 90
dbg: [net] Map generation percentage complete: 95
dbg: [net] Map generated, starting game
dbg: [net] Dedicated server could not be started, aborting
dbg: [net] [udp] closed listeners
dbg: [net] [core] shutting down network

I have absolutly no idea where that ip comes from: 67.215.65.132:3979 - it's not mine
the correct ip would be: 85.14.223.255 (which is automaticly detected and correct)

I've checked the cfg serveral times, but I couldn't find a setting where the wrong ip is set.

It worked already with this configuration and with this command (a long time ago), but now it doesn't work anymore.

Any ideas where that wrong ip comes from?

I use OpenTTD 1.0.0 on Linux/Ubuntu as operating system

If you need more informations don't hesitate to ask

[Rubidium]

85.14.223.255 is probably not the correct IP address, as that's a broadcast address.

Having said that, OpenTTD binds by default to anything (0.0.0.0/::) unless you override that choice in openttd.cfg. As such, you have that (wrong) IP in your configuration file.

[NHLfan]

you were right, that was the wrong ip-address, I changed the server_bind_ip to the correct address, but still nothing changed
and I still don't know where that ip 67.215.65.132:3979 come from, according to a whois-query it belongs to openDNS, which I don't know

[NHLfan]

Any idea where that ip address comes from? - 67.215.65.132:3979
the ip is definitively NOT in the openttd.cfg. - In fact, it doesn't matter which ip I put next to server_bind_ip, even if I leave this line empty or if I fill it with 0.0.0.0, the console shows me the wrong ip.

So, is there another config where I can setup the ip-address?

[NHLfan]

Hi again
I still haven't solved this issue, but I've...

... updated ottd to 1.0.1
... removed the openttd.cfg
... uninstalled openttd
... installed openttd
... started openttd only with this command: openttd -Df


and still openttd "sees" a wrong ip-address.
I can't figure out, where it comes from, since there is no cfg file which states any ip-address
If I put the correct ip-address (server bind ip) in the cfg doesn't work, it seems openttd ignores that line.

[planetmaker]

Look through all possible places where a config file may reside. Consult them readme for path information, especially section 4

[peter1138]

... started openttd only with this command: openttd -Df

Not a bug. "f" is a option of -D in this case. Use "-fD" or "-D -f" to make openttd realise that "f" is meant to be a parameter.

(Dug this up because someone on IRC brought it up, and I figured it might be useful info.)