The implementations of DNS and the Crossfire metaserver expect a range of known IP addresses for an address to be in. The Crossfire metaserver appears to expect a resolvable domain name or a static IP.

It appears, though, that by determining the Crossfire server's public IP address before each time it reports to the metaserver, we should be able to have a server hosted on a dynamic IP range controlled by an ISP, without having to set up a static IP nor a DNS entry. This would have the net effect of a few stale entries occasionally lingering in the metaserver itself, but those will be removed like any other server that stops sending updates to it, bring removed after a set amount of time.
This project is an attempt to implement that as a workaround, because I don't feel like interacting with my ISP nor DNS providers.

Project Activity

See All Activity >

License

GNU General Public License version 2.0 (GPLv2)

Follow cf-dynamic-address

cf-dynamic-address Web Site

nel_h2
Our Free Plans just got better! | Auth0 Icon
Our Free Plans just got better! | Auth0

With up to 25k MAUs and unlimited Okta connections, our Free Plan lets you focus on what you do best—building great apps.

You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
Try free now
Rate This Project
Login To Rate This Project

User Reviews

Be the first to post a review of cf-dynamic-address!

Additional Project Details

User Interface

Non-interactive (Daemon)

Programming Language

C

Related Categories

C Role-Playing Games (RPG), C Multi-User Dungeons (MUD) Game, C Multiplayer Game

Registered

2021-01-13