Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:dpi_options:opt_shaping:shaping_multi:start [2023/11/10 09:48] – [For CIDR] elena.krasnobryzh | en:dpi:dpi_options:opt_shaping:shaping_multi:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Policing of Virtual Channel (vChannel) ====== | ||
- | {{indexmenu_n> | ||
- | <note tip>More about VChannels configuration: | ||
- | |||
- | In case if the operator has several external (uplink) or internal channels often it is needed to control Channel Upper Boundary and limit low priority traffic independently of one another. Channel traffic is usually uneven and channels often are unequal. | ||
- | |||
- | < | ||
- | |||
- | {{ : | ||
- | ===== Setting up ===== | ||
- | |||
- | In the DPI setting **/ | ||
- | < | ||
- | where\\ | ||
- | * 1 different NICs will be used for different channels | ||
- | * 2 different VLANs will be used for different channels | ||
- | * 3 they will be defined via CIDR | ||
- | |||
- | Next, you need to specify which physical interfaces, VLANs, CIDRs form the virtual channel. | ||
- | |||
- | ==== For physical interfaces ==== | ||
- | < | ||
- | vchannels_list=60-00.0: | ||
- | </ | ||
- | |||
- | <note important> | ||
- | and traffic through **61-00.0 and 61-00.1 refers to the second.** \\ | ||
- | If the Stingray SG has other network interfaces specified in the in_dev/ | ||
- | </ | ||
- | |||
- | ==== For VLANs: ==== | ||
- | < | ||
- | vchannels_list=100: | ||
- | </ | ||
- | |||
- | <note important> | ||
- | Traffic that is not in VLANs defined in vchannels_list will be in common channel as before. It is managed as usual in [[en: | ||
- | |||
- | ==== For CIDR ==== | ||
- | Creating ipchannels.txt file: | ||
- | < | ||
- | 10.0.1.0/24 1 | ||
- | 10.0.2.0/24 1 | ||
- | 10.1.0.0/16 2 | ||
- | </ | ||
- | |||
- | To convert: | ||
- | < | ||
- | |||
- | To list vChannels in / | ||
- | < | ||
- | vchannels_list=1|2 | ||
- | </ | ||
- | <note important> | ||
- | Traffic that is not in the defined CIDR will refer to the common channel, which is managed and limited in the [[en: | ||
- | |||
- | ===== Policing Configuration ===== | ||
- | |||
- | Load the policing setting for channels 1 and 2 | ||
- | < | ||
- | fdpi_ctrl load --policing vchannel1.cfg --vchannel 1 | ||
- | fdpi_ctrl load --policing vchannel2.cfg --vchannel 2 | ||
- | </ | ||
- | |||
- | where vchannel1.cfg - file with policing definition (same as for the general channel, | ||
- | |||
- | **Example of the configuration file:** | ||
- | <code ini> | ||
- | htb_inbound_root=rate 10mbit | ||
- | htb_inbound_class0=rate 8bit ceil 10mbit | ||
- | htb_inbound_class1=rate 1mbit ceil 3mbit | ||
- | htb_inbound_class2=rate 8bit ceil 10mbit | ||
- | htb_inbound_class3=rate 8bit ceil 10mbit | ||
- | htb_inbound_class4=rate 8bit ceil 10mbit | ||
- | htb_inbound_class5=rate 8bit ceil 10mbit | ||
- | htb_inbound_class6=rate 100mbit static | ||
- | htb_inbound_class7=rate 8bit ceil 10mbit | ||
- | htb_root=rate 10mbit | ||
- | htb_class0=rate 8bit ceil 10mbit | ||
- | htb_class1=rate 1mbit ceil 3mbit | ||
- | htb_class2=rate 8bit ceil 10mbit | ||
- | htb_class3=rate 8bit ceil 10mbit | ||
- | htb_class4=rate 8bit ceil 10mbit | ||
- | htb_class5=rate 8bit ceil 10mbit | ||
- | htb_class6=rate 100mbit static | ||
- | htb_class7=rate 8bit ceil 10mbit | ||
- | </ | ||
- | |||
- | Let's check what setup is loaded: | ||
- | < | ||
- | fdpi_ctrl list all vchannel --policing | ||
- | </ | ||
- | |||
- | The settings for the virtual channels are stored in DPI UDR (internal database) and can be changed on the fly during operation as well as for subscribers. | ||
- | Configuration of policing for the channel can be loaded by the named profile eather. | ||
- | < | ||
- | fdpi_ctrl load --policing --profile.name vchannel_1 --vchannel 1 | ||
- | </ | ||
- | |||
- | The tariff plan can be set in [[en: | ||
- | |||
- | ===== Block List Setup - Service 4 ===== | ||
- | The profile is created similarly to creating Subscriber' | ||
- | < | ||
- | fdpi_ctrl load --service 4 --profile.name test_blocked ––vchannel 2 | ||
- | </ | ||
- | |||
- | ===== Allow List Setup - Service 5 ===== | ||
- | The profile is created similarly to creating Subscriber' | ||
- | < | ||
- | fdpi_ctrl load --service 5 --profile.name test_white ––vchannel 1 | ||
- | </ |