- Joined
- Dec 18, 2018
- Messages
- 86
- Reaction score
- 108
- Points
- 33
Changelog.
Code:
## Changelog
## r82-hellboy-V29
- [FIX] Solve possible crash condition when updating SID statistics
- [FIX] Make autorefresh work in profile page
- [ENH] Add options "SHARE CCCAM", "SHARE MGCAMD" and "SHARE NEWCAMD" to profile page
- [FIX] Remove option TIMEPERECM as it's not well implemented and can cause problems
- [ENH] Implement connection timeout to remote servers, instead of relying on linux timeouts. This will reduce configuration changes reload times that have to wait until current connections are established or timed-out (linux connect timeouts are typically arround 3 minutes, in multics we have reduced to 5 seconds).
- [ENH] Add logging for reread configuration in loglevels INFO and DEBUG for troubleshooting purpose
- [ENH] Allow changing runtime loglevel from webinterface (debug page). Things to consider:
* You will be able to change the loglevel at runtime from web interface, but the change will not persist between restarts.
* Also, once you change loglevel from web interface it will not be altered if you modify the configuration file. The change from web interface takes precedence over the change from config file, until you restart multics.
* It affects all logging, not only the logs currently shown in webinterface. So if you change loglevel to LOGTRACE and have file logging in /var/tmp consider you are changing the loglevel of all multics, not just the loglevel of what is shown in the webinterface (your log file will grow!!!!)
- [ENH] Implement alert module that will show a alert list in the web interface.
Alert conditions:
- String with alert message
- Simple checksum of the string (to be able to increment the alert count and not to duplicate the alert)
- Initial time and date the alert raised
- Last time the alert raised
- Alert count
- Alert status (open/closed): the admin can close alerts
Things that could trigger alert:
- Authentication failed to any cs protocol (ccam, newcamd, mgcamd, etc) in local server with indication if the access triggered failban also
- Cache access not authorized (not in my cache peers)
- Authentication failed to http web interface
Things to consider:
- This is a simple list of alerts triggered from the core logic of multics, not complex rules to generate alerts
- There will be no correlation of alerts with this design that is a simple string with alert message.
- Alerts will not persist between multics restarts
Telegram BOT.
Code:
TELEGRAM BOT
You need to create a telegram bot and enable telegram in config and configure the token and chatid.
The parameters are:
TELEGRAM ENABLE: 1 ## Enable or disable telegram
TELEGRAM TOKEN: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ## Token obtained for the telegram bot
TELEGRAM CHATID: "12345678" ## The chatid in your telephone for the conversation with the telegram bot
To create a telegram bot and obtain token and chatid you can look for multiple guides on the Internet like
www.shellhacks.com
Multics Cache Push to OSCAM and Multics Cache filtering.
Code:
To send cache from multics to oscam (without filtering):
CACHE PEER: host port { csp=1; cspsendcache=1 }
To filter cache sent from the multics to other peer (multics or oscam) now you can use "shares" with the syntax:
CAID1
ROVID1&PROVID2,CAID2ROVID1
Examples:
- Filter only for sending cache only from 1810:000000 to a oscam peer:
CACHE PEER: host port { csp=1; cspsendcache=1; shares=1810:000000 }
- Filter for sending cache only from 1810:000000, 0100:004106 and 0100:00006A to a multics peer:
CACHE PEER: host port { shares=1810:000000,0100:004106&00006A }
NOTE: PROVID is a must ! without won't work.
Multics Cache minimum replies.
Code:
To enable and adjust to 1000 replies per hour you have to add:
CACHE MINREPLIES: 1000
Every hour multics will check that the replies sent by each cache peer divided between the number of hours uptime of the server exceeds or equals the value setting of CACHE MINREPLIES. If it doesn't the cache peer will be disabled.
You can add an exception to certain peers with the parameter nominreplies, for instance:
CACHE PEER: hostname port { nominreplies=1 } # exclude this cache peer from disable
Multics Cache minimum hits.
Code:
Examples:
CACHE MINHITS: 0 # No effect. It will disable the check.
CACHE MINHITS: 1 # At least 1 hit per hour. So after 6 hours (when the task run for the first time) each peer should have at least 6 hits (adding Cache Hits and Instant Hits), after 12 hours (when the task runs for the second time) each peer should have at least 12 hits...
CACHE MINHITS: 10 # At least 10 hits per hour
The calculation is done considering the multics runtime, not the peer connection time which is not carried.
Once a peer is autodisabled for MINHITS or MINREPLIES cannot be reenabled (until you restart multics).
Peers not connecting to multics will be disabled by the task.
You can add an exception to certain peers with the parameter nominhits, for instance:
CACHE PEER: hostname port { nominhits=1 } # exclude this cache peer from disable
To prevent cache poisoning and fake requests with invalid PROFILES.
With this version of Multics you have to correct your PROFILES to able to run.
EX:
0100 (seca) as PROVID should not contain 000000
0500 (via) as PROVID should not contain 000000
0DXX (cryptoworks) as PROVID should not contain 000000
18XX (nagra) as PROVID should have only 000000 , EXCEPTION all tunneled Nagra cards like ( 1811,1863,1883 etc. )
0BXX (conax) as PROVID should have only 000000
09XX (nds) as PROVID should have only 000000
06XX (irdeto) as PROVID should have only 000000
4AXX (bulcrypt) as PROVID should have only 000000
NOTE: this version of multics will not let you start with invalid PROFILES!
First time users should start it manually with putty and check the output if there are ERROR Message(s).
All first users should correct their PROFILES before put it in your start scripts,
the ERROR Message will contains the PROFILE name and the ERROR what should be corrected.
Regards.
Have fun
Code:
## Changelog
## r82-hellboy-V29
- [FIX] Solve possible crash condition when updating SID statistics
- [FIX] Make autorefresh work in profile page
- [ENH] Add options "SHARE CCCAM", "SHARE MGCAMD" and "SHARE NEWCAMD" to profile page
- [FIX] Remove option TIMEPERECM as it's not well implemented and can cause problems
- [ENH] Implement connection timeout to remote servers, instead of relying on linux timeouts. This will reduce configuration changes reload times that have to wait until current connections are established or timed-out (linux connect timeouts are typically arround 3 minutes, in multics we have reduced to 5 seconds).
- [ENH] Add logging for reread configuration in loglevels INFO and DEBUG for troubleshooting purpose
- [ENH] Allow changing runtime loglevel from webinterface (debug page). Things to consider:
* You will be able to change the loglevel at runtime from web interface, but the change will not persist between restarts.
* Also, once you change loglevel from web interface it will not be altered if you modify the configuration file. The change from web interface takes precedence over the change from config file, until you restart multics.
* It affects all logging, not only the logs currently shown in webinterface. So if you change loglevel to LOGTRACE and have file logging in /var/tmp consider you are changing the loglevel of all multics, not just the loglevel of what is shown in the webinterface (your log file will grow!!!!)
- [ENH] Implement alert module that will show a alert list in the web interface.
Alert conditions:
- String with alert message
- Simple checksum of the string (to be able to increment the alert count and not to duplicate the alert)
- Initial time and date the alert raised
- Last time the alert raised
- Alert count
- Alert status (open/closed): the admin can close alerts
Things that could trigger alert:
- Authentication failed to any cs protocol (ccam, newcamd, mgcamd, etc) in local server with indication if the access triggered failban also
- Cache access not authorized (not in my cache peers)
- Authentication failed to http web interface
Things to consider:
- This is a simple list of alerts triggered from the core logic of multics, not complex rules to generate alerts
- There will be no correlation of alerts with this design that is a simple string with alert message.
- Alerts will not persist between multics restarts
Telegram BOT.
Code:
TELEGRAM BOT
You need to create a telegram bot and enable telegram in config and configure the token and chatid.
The parameters are:
TELEGRAM ENABLE: 1 ## Enable or disable telegram
TELEGRAM TOKEN: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" ## Token obtained for the telegram bot
TELEGRAM CHATID: "12345678" ## The chatid in your telephone for the conversation with the telegram bot
To create a telegram bot and obtain token and chatid you can look for multiple guides on the Internet like
Telegram API: Send Message - Personal Notification Bot - ShellHacks
How to create a Telegram bot that sends messages through the Telegram API from the web-browser, Linux command line (curl) or a Bash script.
www.shellhacks.com
Code:
To send cache from multics to oscam (without filtering):
CACHE PEER: host port { csp=1; cspsendcache=1 }
To filter cache sent from the multics to other peer (multics or oscam) now you can use "shares" with the syntax:
CAID1
ROVID1&PROVID2,CAID2ROVID1Examples:
- Filter only for sending cache only from 1810:000000 to a oscam peer:
CACHE PEER: host port { csp=1; cspsendcache=1; shares=1810:000000 }
- Filter for sending cache only from 1810:000000, 0100:004106 and 0100:00006A to a multics peer:
CACHE PEER: host port { shares=1810:000000,0100:004106&00006A }
NOTE: PROVID is a must ! without won't work.
Multics Cache minimum replies.
Code:
To enable and adjust to 1000 replies per hour you have to add:
CACHE MINREPLIES: 1000
Every hour multics will check that the replies sent by each cache peer divided between the number of hours uptime of the server exceeds or equals the value setting of CACHE MINREPLIES. If it doesn't the cache peer will be disabled.
You can add an exception to certain peers with the parameter nominreplies, for instance:
CACHE PEER: hostname port { nominreplies=1 } # exclude this cache peer from disable
Multics Cache minimum hits.
Code:
Examples:
CACHE MINHITS: 0 # No effect. It will disable the check.
CACHE MINHITS: 1 # At least 1 hit per hour. So after 6 hours (when the task run for the first time) each peer should have at least 6 hits (adding Cache Hits and Instant Hits), after 12 hours (when the task runs for the second time) each peer should have at least 12 hits...
CACHE MINHITS: 10 # At least 10 hits per hour
The calculation is done considering the multics runtime, not the peer connection time which is not carried.
Once a peer is autodisabled for MINHITS or MINREPLIES cannot be reenabled (until you restart multics).
Peers not connecting to multics will be disabled by the task.
You can add an exception to certain peers with the parameter nominhits, for instance:
CACHE PEER: hostname port { nominhits=1 } # exclude this cache peer from disable
To prevent cache poisoning and fake requests with invalid PROFILES.
With this version of Multics you have to correct your PROFILES to able to run.
EX:
0100 (seca) as PROVID should not contain 000000
0500 (via) as PROVID should not contain 000000
0DXX (cryptoworks) as PROVID should not contain 000000
18XX (nagra) as PROVID should have only 000000 , EXCEPTION all tunneled Nagra cards like ( 1811,1863,1883 etc. )
0BXX (conax) as PROVID should have only 000000
09XX (nds) as PROVID should have only 000000
06XX (irdeto) as PROVID should have only 000000
4AXX (bulcrypt) as PROVID should have only 000000
NOTE: this version of multics will not let you start with invalid PROFILES!
First time users should start it manually with putty and check the output if there are ERROR Message(s).
All first users should correct their PROFILES before put it in your start scripts,
the ERROR Message will contains the PROFILE name and the ERROR what should be corrected.
Regards.
Have fun