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

Other Useful Business Software
AI-generated apps that pass security review Icon
AI-generated apps that pass security review

Stop waiting on engineering. Build production-ready internal tools with AI—on your company data, in your cloud.

Retool lets you generate dashboards, admin panels, and workflows directly on your data. Type something like “Build me a revenue dashboard on my Stripe data” and get a working app with security, permissions, and compliance built in from day one. Whether on our cloud or self-hosted, create the internal software your team needs without compromising enterprise standards or control.
Try Retool free
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