Freebsd traffic shaping - Redigeerimiste ajalugu

Jj: /* Sissejuhatus */

2013-04-09T08:52:46Z

Sissejuhatus

←Vanem redaktsioon		Redaktsioon: 9. aprill 2013, kell 08:52
29. rida:		29. rida:

	Root Queue (2Mbps)		Root Queue (2Mbps)
	Queue A (1Mbps)		Queue A (1Mbps)
	Queue B (500Kbps)		Queue B (500Kbps)
	Queue C (500Kbps)		Queue C (500Kbps)

	Seda hirearhiat saab laiendada veel defineerides alamjärjekordi, näiteks		Seda hirearhiat saab laiendada veel defineerides alamjärjekordi, näiteks

	Root Queue (2Mbps)		Root Queue (2Mbps)
	UserA (1Mbps)		UserA (1Mbps)
	ssh (50Kbps)		ssh (50Kbps)
	bulk (950Kbps)		bulk (950Kbps)
	UserB (1Mbps)		UserB (1Mbps)
	ssh (100Kbps)		ssh (100Kbps)
	ftp (900Kbps, borrow)		ftp (900Kbps, borrow)

	Veel saab igale järjekorrale seadistada tema prioriteedi taseme. Järjekorraga millel on kõrgem propriteet tegeletakse		Veel saab igale järjekorrale seadistada tema prioriteedi taseme. Järjekorraga millel on kõrgem propriteet tegeletakse
47. rida:		47. rida:

	Root Queue (2Mbps)		Root Queue (2Mbps)
	UserA (1Mbps, priority 1)		UserA (1Mbps, priority 1)
	ssh (100Kbps, priority 5)		ssh (100Kbps, priority 5)
	ftp (900Kbps, priority 3)		ftp (900Kbps, priority 3)
	UserB (1Mbps, priority 1)		UserB (1Mbps, priority 1)

	Kui prioriteet on sama leveliga, nagu näites on userA ja userB järjekordadel siis tegeletakse järjekordadega round-robin laadselt. Muide		Kui prioriteet on sama leveliga, nagu näites on userA ja userB järjekordadel siis tegeletakse järjekordadega round-robin laadselt. Muide
62. rida:		62. rida:

	Root Queue (2Mbps)		Root Queue (2Mbps)
	Queue A (priority 1)		Queue A (priority 1)
	Queue B (priority 2)		Queue B (priority 2)
	Queue C (priority 3)		Queue C (priority 3)

	'''RED''' Random Early Detection		'''RED''' Random Early Detection

Jj: /* Sissejuhatus */

2013-04-09T08:51:22Z

Sissejuhatus

←Vanem redaktsioon		Redaktsioon: 9. aprill 2013, kell 08:51
16. rida:		16. rida:
	tegeleb omakorda scheduler. Võimalik on kasutada kahte tüüpi schedulere		tegeleb omakorda scheduler. Võimalik on kasutada kahte tüüpi schedulere

	* Class Based Queueing		* Class Based Queueing (CBQ)
	* Priority Queueing		* Priority Queueing (PriQ)

	A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.		A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.

	~~Probleem on, et kuna NAT reegel käivitub esimesena siis edasised pass/block reeglid ei rakendu. Lahenduseks oleks tõenäoliselt TAGide ehk siltide kasutamine~~

	~~#STMT 1~~
	~~nat on $ext_if inet tagged MYIN2OUT -> ($ext_if:0)~~
	#
	~~# STMT 2~~
	~~pass in log quick on $int_if inet from ($int_if:network) to any tag MYIN2OUT keep state~~

	~~# STMT 3~~
	~~pass out log quick on $ext_if inet tagged MYIN2OUT keep state~~

	In the order of precedence, your traffic originating on your $int_if:network and destined for the internet is FIRST inspected and passed by SMTM#2, then NAT translation occurs by STMT#1, and is then inspected and passed by STMT#3.

	~~The use of tag/tagged means you -- the pf.conf author -- don't need to know the real IP source/dest translations at the point of each statement to write a clean (and leak-proof) pf.conf.~~

	'''CBQ'''		'''CBQ'''

Jj: /* Lingid */

2013-04-07T09:49:10Z

Lingid

←Vanem redaktsioon		Redaktsioon: 7. aprill 2013, kell 09:49
312. rida:		312. rida:

	http://www.tummy.com/blogs/2004/12/22/state-of-the-traffic-shaping-address/ asjalikku juttu altq kohta		http://www.tummy.com/blogs/2004/12/22/state-of-the-traffic-shaping-address/ asjalikku juttu altq kohta

			https://calomel.org/pf_config.html

Jj: /* Näide 4 */

2013-04-07T09:42:37Z

Näide 4

←Vanem redaktsioon		Redaktsioon: 7. aprill 2013, kell 09:42
216. rida:		216. rida:
	Õnnetuseks sellise reeglistiku juures EI TÖÖTA OUT reegel.		Õnnetuseks sellise reeglistiku juures EI TÖÖTA OUT reegel.

	Probleem on, et kuna NAT reegel käivitub esimesena siis edasised pass/block reeglid ei rakendu.		Probleem on, et kuna NAT reegel käivitub väljuva liikluse puhul esimesena siis edasised pass/block reeglid ei rakendu.
	Seega meie reegel nr1 lõpetab edasise paketi töötluse ja reegel		Seega meie reegel nr1 lõpetab edasise paketi töötluse ja reegel jäetakse kasutamata ning väljuvat infot ei topita altq torusse
	jäetakse kasutamata ning väljuvat ~~OUT~~ infot ei topita altq torusse

	Siin suudab päästa õnneks võti "tag" ehk märkimine? Näiteks märgime OUT reegli ära.		Siin suudab päästa õnneks võti "tag" ehk märkimine? Näiteks märgime OUT reegli ära.

Jj: /* Näide 4 */

2013-04-07T09:36:05Z

Näide 4

@@ 208. rida: / 208. rida: @@
 ====Näide 4====
-Näide pf altq traffic shapingust koos tulemüüriga.
+Oletame, et meil reeglid
 Kasutusel on piiratud võimalustega väline ühendus, ruuteril on kaks võrgukaarti millest väline
-fxp1 ja sisemine fxp0 ning sisemisele toimib nat.
+ nat on $ext_if from 192.168.1.1 to any -> ($ext_if)
 Piiratakse nii download kui uploadi. Iga hosti kohta saab määrata erineva uploadi ja downloadi.

Jj: /* Sissejuhatus */

2013-04-07T09:05:25Z

Sissejuhatus

@@ 21. rida: / 21. rida: @@
 A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.
-Probleem on, et kuna NAT reegel käivitub esimesena siis edasised pass/block reeglid ei rakendu.
+Probleem on, et kuna NAT reegel käivitub esimesena siis edasised pass/block reeglid ei rakendu. Lahenduseks oleks tõenäoliselt TAGide ehk siltide kasutamine
 '''CBQ'''

Jj: /* Sissejuhatus */

2013-04-07T09:02:39Z

Sissejuhatus

←Vanem redaktsioon		Redaktsioon: 7. aprill 2013, kell 09:02
20. rida:		20. rida:

	A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.		A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.

			Probleem on, et kuna NAT reegel käivitub esimesena siis edasised pass/block reeglid ei rakendu.

	'''CBQ'''		'''CBQ'''

Jj – 7. aprill 2013, kell 08:59

2013-04-07T08:59:37Z

←Vanem redaktsioon		Redaktsioon: 7. aprill 2013, kell 08:59
18. rida:		18. rida:
	* Class Based Queueing		* Class Based Queueing
	* Priority Queueing		* Priority Queueing

			A couple of downsides to this. One is that you need to have one queue for incoming and outgoing if you want to limit both ways. The other problem is that if you want to NAT and shape based on the inside IP address, because the shaper happens on the out, the NAT has already happened, so you no longer have traffic split out by the inside IP address.

	'''CBQ'''		'''CBQ'''

Jj – 7. aprill 2013, kell 08:56

2013-04-07T08:56:29Z

←Vanem redaktsioon		Redaktsioon: 7. aprill 2013, kell 08:56
272. rida:		272. rida:

	http://blog.segment7.net/2009/07/27/bandwidth-limiting-with-pf-and-altq		http://blog.segment7.net/2009/07/27/bandwidth-limiting-with-pf-and-altq

			http://www.tummy.com/blogs/2004/12/22/state-of-the-traffic-shaping-address/ asjalikku juttu altq kohta

Jj: /* Näide= */

2012-10-02T09:07:24Z

Näide=

←Vanem redaktsioon		Redaktsioon: 2. oktoober 2012, kell 09:07
107. rida:		107. rida:
	Lets traffic to the default torrent ports out on the external interface and lumps the traffic into the torrent_out_queue.		Lets traffic to the default torrent ports out on the external interface and lumps the traffic into the torrent_out_queue.

	===Näide====		===Näide===

	Altq võrgulahendus, kus vaja oleks limiteerida wifi klientidele		Altq võrgulahendus, kus vaja oleks limiteerida wifi klientidele