Peach with dynamic ip

I set up the perforce server on an old constantly running laptop, which is always assigned a reserved address by the router. I have an account at no-ip.com, which sends to my router, which in turn redirects requests to port 1666 to this laptop.

when I try to install p4port to this no-ip.org address, this part is fine, but when I run p4d, I get:

Perforce server error: Listen to USERNAME.no-ip.org:1666 failed. Failed to listen to TCP at USERNAME.no-ip.org:1666. bind: USERNAME.no-ip.org:1666: WSAEADDRNOTAVAIL

While if I just installed p4port in 192.168.0.6, I can access the server from behind the network using this ... but I could also access it from the outside.

I read another post in which someone was working with the same setting (http://stackoverflow.com/questions/2397642/online-perforce-repositories, the user was gaminghorror), but he didn’t have like me, obviously needed.

tried with the router and windows xp firewall, and the xp and router firewalls switched to 1666 on this local ip

Hooray!

+1
source share
3 answers

, perforce, : sourceforge.net SVN, . Perforce, , WAN IP , . , , perforce , .

-1

p4d,

p4d -p 1666

p4d -p USERNAME.no-ip.org:1666

USERNAME.no-ip.org , NAT , IP-. p4port , (0.0.0.0). p4port USERNAME.no-ip.org:1666, NAT .

, , - NAT, , , , - . , .

+3

I think the problem is that p4d is trying to associate its listening socket with USERNAME.no-ip.org:1666, and this address is not the "correct" address for the PC running p4d.

The solution would be to make p4d bind to 0.0.0.0:1666 (somewhere in p4d config?) Or to convince the PC that USERNAME.no-ip.org is really its address - by entering it in / etc / hosts ( or for Windows in a hidden system file: c: \ windows \ system32 \ drivers \ etc \ hosts)

+1
source

All Articles