NewCs-1.50
Quote:
--- Index ------- --- -- - - -
1. Chameleon - the newcs P2P
2. Feynman
3. File Descriptions
4. Runtime Arguments
5. Configfile
6. TCP-Commands
7. FAQ
8. Changelog
9. Troubleshooting
10. Special Notes
11. Known Bugs
12. Greets
1.-- Chameleon - the newcs P2P ------- --- -- - - -
Here we will _try_ to make a little introduction on how the P2P network works.
You have to start by creating your own self-signed Certificate, this can be done with this command on a machine that has openssl installed:
openssl req -new -x509 -nodes -out newcs.pem -keyout newcs.pem
or you can create a certificate on a online site, there is some that creates self-signed certificates.
The connection from newcs<->newcs is encrypted with SSL.
After creating the certificate, place it somewhere and make sure the path in the <certificate> tag in the global section reflects that.
Go through the <chameleon> section, and set your port, create users if you need incomming connections, peers if you need outgoing connections.
If you want incomming connections, the tcp-port specified needs to be open in your router (NAT or similar).
When the server is started, it will generate a random 2byte hex serverID - this will be the ID of your server for this session, the other servers
in the network will locate you based on this ID _only_. Only your peers know your details, _noone_ else on the network know your details -to 3rd parties
the network is completely anonymous.
Clients have to connect to Chameleon through the Feynman server in NewCS, through here the client will send ECM to Chameleon. Chameleon will then
broadcast a ECM to all serverID's in the network that has this CAID/Provider, all that can, answer with a valid dcw. The 3 fastest replies will
be remembered, and Chameleon will continue now to send _only_ to the fastest replier. Chameleon will try to keep a timeing to the next fastest server
so it can switch when another one is faster.
For the moment, Mgcamd 1.2x can also get the chameleon cards through newcamd protocol IF the user it use to login has <cardlevel> set to 1.
If a client send more then 10 requests for a sid, and dont get a valid dcw - this client is blocked on this sid for another 100 requests to prevent
broadcast spamming.
2.-- Feynman Protocol ------- --- -- - - -
Feynman is a protocol written by us, it can handle multiple cards over one port, EMM, ECM - handle SIDS on both sides. It provides simple functions, so
client and server developers can think about other important stuff smile
We hope that this will be the new "standard" in the sat hobby - like newcamd has been in the past few years smile
Newcamd has been a great protocol, but it has its limitations - and we hope to phase out newcamd (and radegast) in the next major version of NewCS.
Would be nice if someone could make a sourceforge project, or some other opensource project site.
PLEASE, we give this as opensource, please keep it that way smile
Feedback is appriciated, hope someone will take this as a project to improve and nurse smile
Quote:
--- Index ------- --- -- - - -
1. Chameleon - the newcs P2P
2. Feynman
3. File Descriptions
4. Runtime Arguments
5. Configfile
6. TCP-Commands
7. FAQ
8. Changelog
9. Troubleshooting
10. Special Notes
11. Known Bugs
12. Greets
1.-- Chameleon - the newcs P2P ------- --- -- - - -
Here we will _try_ to make a little introduction on how the P2P network works.
You have to start by creating your own self-signed Certificate, this can be done with this command on a machine that has openssl installed:
openssl req -new -x509 -nodes -out newcs.pem -keyout newcs.pem
or you can create a certificate on a online site, there is some that creates self-signed certificates.
The connection from newcs<->newcs is encrypted with SSL.
After creating the certificate, place it somewhere and make sure the path in the <certificate> tag in the global section reflects that.
Go through the <chameleon> section, and set your port, create users if you need incomming connections, peers if you need outgoing connections.
If you want incomming connections, the tcp-port specified needs to be open in your router (NAT or similar).
When the server is started, it will generate a random 2byte hex serverID - this will be the ID of your server for this session, the other servers
in the network will locate you based on this ID _only_. Only your peers know your details, _noone_ else on the network know your details -to 3rd parties
the network is completely anonymous.
Clients have to connect to Chameleon through the Feynman server in NewCS, through here the client will send ECM to Chameleon. Chameleon will then
broadcast a ECM to all serverID's in the network that has this CAID/Provider, all that can, answer with a valid dcw. The 3 fastest replies will
be remembered, and Chameleon will continue now to send _only_ to the fastest replier. Chameleon will try to keep a timeing to the next fastest server
so it can switch when another one is faster.
For the moment, Mgcamd 1.2x can also get the chameleon cards through newcamd protocol IF the user it use to login has <cardlevel> set to 1.
If a client send more then 10 requests for a sid, and dont get a valid dcw - this client is blocked on this sid for another 100 requests to prevent
broadcast spamming.
2.-- Feynman Protocol ------- --- -- - - -
Feynman is a protocol written by us, it can handle multiple cards over one port, EMM, ECM - handle SIDS on both sides. It provides simple functions, so
client and server developers can think about other important stuff smile
We hope that this will be the new "standard" in the sat hobby - like newcamd has been in the past few years smile
Newcamd has been a great protocol, but it has its limitations - and we hope to phase out newcamd (and radegast) in the next major version of NewCS.
Would be nice if someone could make a sourceforge project, or some other opensource project site.
PLEASE, we give this as opensource, please keep it that way smile
Feedback is appriciated, hope someone will take this as a project to improve and nurse smile
