Hello,
A couple friends and I are just getting back into Freelancer and decided to try out Crossfire with high expectations.
We would like to play this "co-op" with each other, but would rather host our own private server to zest about in, rather then use the provided RP only server.
However current attempts yield only the default Freelancer server which is 1.0, not the Crossfire 1.9/ Is it possible to for us to set up a server for our own use? or have I miss a Crossfire server download somewhere?
Or do you not allow private servers?
Hello Kharcov,
the Crossfire server implements the so-called "Open RP" system: whereas you are forbidden to avoid role play started upon you by another player, you are always free to decide whether to do RP on your own or not. This makes a big difference from other RP servers where you are forced to play your role all the time.
Hello there, I really love the Crossfire mod for Freelancer, but for some reason I cant seem to get a LAN server working for it. I go to flserver.exe with FLMM and click start server and all that but when I go into freelancer to play it the server says that it is version 1.0 and I cannot join. How do you host a server on the mod?
Also, are there any server managers like the IONCROSS one that work for Crossfire?
Thankyou for all your help,
Mikey
From the darkness we come to the darkness we all shall go
........................................................................................
Facilis descencus Averno. Qui non vetat peccare, cum possit, iubet. Sine cruce, sine luce, nihil interit. Pulvis et umbra sumus.
Originally posted by Mikey
Okay, Thankyou, the only problem with the server is that I am located in Australia, and whenever I connect to the server it is far too laggy for me to play happily... oh well, thanks anyway.
hm if you have tcpip aktivatet it would be a chance to help its direction between crossover and patch and it would help even though if you can also open ports for more speed. if you have like t1 connexion then you got speed enough also.
in ours country whe have not so much fust speed.
For LaserJet's info, a LAN is mostly used as a privite server for small groups to play on, most of the time those little empty servers that you seem to can't get on are mosty LAN's that show up on the internet screen.
But to answer Mikey's question, You will have to change FLservers version to the same version as CF with Reshacker.
O well, me and a group of people(about 12 or 15) play differnt mods on a LAN and we did play crossfire one weekend and all we had to do is change FLserver to it's version and it worked fine for us, we didn't use Ioncross, so there was never any need for the server files.
so is there any way a lan version of the server files could be released? I know that hacking ect is feared, but all I want to do is be able to play the thing with other people and when I try to get on the server it always lags and I can never shoot straight
Oh well, I suppose I will just have to keep on playing open SP.
To have your friends join your Refrag server, simply send the IP to them from your server dashboard and have them paste it into their console. Once they join, they can participate in virtually any mode available! They do not need a subscription to Refrag to join your server, but only the subscriber who launches the server can execute commands that change mode or map.
Crossfire works as it would as a solo player and can support up to 2 players. You can also enable PvP by typing .pvp in the in-game chat. This is great for building chemistry with friends and teammates!
No more waiting for empty spots on public Retake servers with your team. Simply type .retakes and have your friends join. .start will restart the game, and .ak, .m4, etc will modify your loadout to your liking. Retakes are best enjoyed when playing with at least 5 players.
Hosting your own private Deathmatch is possible with Refrag. simply type .deathmatch map-name-here to load the DM mod with the map of your choosing. You can even change between modes. Want headshot only with rifles? Type .rifles. Pistols only? .pistol. All commands can be found on the Refrag Wiki as always.
NADR allows you to show your saved grenades and grenade groups to your teammates. Simply launch NADR as you would if you were solo and have your friends join, and you can use general commands like .rethrow and .noflash to show your ideas to your friends. Note that .clear specifically does not work per player and will clear utility on the entire map, regardless of who threw it. A great way to use NADR as a team is to use the dry run functionality. Typing .dryrun will restart the round with everyone in spawn so you can practice getting into position for set tactics.
To summarize, virtually all modes are available for multiplayer, even ones like Waves that were not covered here. If you have any questions, chances are it will be answered on the Refrag Wiki, but if you require support or want to give feedback, join our Discord community!
Starting cf-serverd sets up a line of communication betweenhosts. This daemon authenticates requests from the network and processes themaccording to rules specified in theserver control body and server bundlescontaining access promises.
The only contact cf-agent makes to the server is via remote copyrequests. It does not and cannot grant any access to a system from thenetwork. It is only able to request access to files on the remote server.
Unlike other approaches to automation, CFEngine does not rely on SSH keyauthentication and configuring trust, the communication between hosts is verystructured and also able to react to availability issues. This means that youdon't have to arrange login credentials to get CFEngine to work. If largeportions of your network stop working, then CFEngine on each individual hostunderstands how to keep on running and delivering promises.
In particular, if the network is not working,CFEngine agents skip downloading new promises and continuewith what they already have. CFEngine was specifically designed to be resilientagainst connectivity issues network failure may be in question. CFEngine isfault tolerant and opportunistic.
If all of the above criteria are met, connection will be established and datawill be transferred between client and server. The client can only send shortrequests, following the CFEngine protocol. The server can return data in avariety of forms, usually files, but sometimes console output.
Bootstrap is the manual first run of cf-agent that establishescommunication with the policy server.Bootstrapping executes the failsafe.cf policy that connects tothe server, establishes trust to the server's key, and that starts theCFEngine daemon processes cf-execd, cf-serverd and cf-monitord.The host that other hosts are bootstrapped toautomatically assumes the role of policy server.
CFEngine will output diagnostic information upon bootstrap. In case of error,investigate the access promises the server is making (run cf-serverd inverbose mode on the policy hub for more informative messages). Note thatby default, CFEngine's server daemon cf-serverd trusts incoming connectionsfrom hosts within the same /16 subnet.
The key exchange model used by CFEngine is based on that used by OpenSSH. Itis a peer to peer exchange model, not a central certificate authority model.This means that there are no scalability bottlenecks (at least by design,though you might introduce your own if you go for an overly centralizedarchitecture).
Key exchange is handled automatically by CFEngine and all you need to do is todecide which keys to trust. The server (cf-serverd) trusts new keys onlyfrom addresses in trustkeysfrom. Once a key has beenaccepted you should close down trustkeysfrom list. Then, even if a malicious peeris spoofing an allowed IP address, its unknown key will be denied.
Once public keys have been exchanged from client to server and from server toclient, the issue of trust is solved according to public key authenticationschemes. You only need to worry about trust when one side of a connection hasnever seen the other side before.
All security is based on a moment of trust that is granted by a user at somepoint in time - and is assumed thereafter (once given, hard to rescind).Cryptographic key methods only remove the need for a repeat of the trustdecision. After the first exchange, trust is no longer needed, because thekeys allow identity to be actually verified.
Even if you leave the trust options switched on, you are not blindly trustingthe hosts you know about. The only potential insecurity lies in any new keysthat you have not thought about. If you use wildcards or IP prefixes in thetrust rules, then other hosts might be able to spoof their way in on trustbecause you have left open a hole for them to exploit. That is why it isrecommended to set the system to the state of zero trustimmediately after key transfer, by commenting or emptying out the trust options(trustkeysfrom on the server).
CFEngine normally runs as user "root" (except on Windows which doesnot normally have a root user), i.e. a privileged administrator. Ifother users are to be granted access to the system, they must alsogenerate a key and go through the same process. In addition, theusers must be added to the server configuration file.
However, the main role of encryption in configuration management is forauthentication. Secrets should not be transferred through policy, encrypted ornot. Policy files should be considered public, and any leakage should notreveal secret information.
In core/community as outgoing outlined in thebody copy_from encrypt documentation the initialconnection is encrypted using the public/private keys for the clientand server hosts. After the initial connection is establishedsubsequent connections and data transfer is encrypted by a randomlygenerated Blowfish key that is refreshed each session.
With the classic protocol cf-serverd has the ability to enforce that afile transfer be encrypted by setting theifencrypted access attribute. When ACLs thatrequire encryption have unencrypted access attempts cf-serverd logs anerror message indicating the file requires encryption. Access to filesthat cf-serverd requires to be encrypted can be logged by setting thebody server control logencryptedtransfers attribute.
b1e95dc632