Load balancing - Revision history

Fmyhr: /* Using Direct Server Return (DSR) */ Upated link to mangling packet headers.

2021-04-16T20:55:41Z

Using Direct Server Return (DSR): Upated link to mangling packet headers.

← Older revision		Revision as of 20:55, 16 April 2021
Line 77:		Line 77:

	Note that xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy need to be replaced by the real destination MAC address.		Note that xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy need to be replaced by the real destination MAC address.
	This is [[~~Mangle packet header fields~~ \| mangling packet ~~header fields~~]] as well.		This is [[Mangling_packet_headers\|mangling packet headers]] as well.

2021-04-16T20:54:43Z

Using stateless NAT: Update link to mangling packet headers.

← Older revision		Revision as of 20:54, 16 April 2021
Line 60:		Line 60:
	</source>		</source>

	This is more lightweight that stateful NAT given there is no flow tracking in place. This is indeed [[~~Mangle packet header fields~~ \| mangling packet ~~header fields~~]].		This is more lightweight that stateful NAT given there is no flow tracking in place. This is indeed [[Mangling_packet_headers\|mangling packet headers]].

	== Using Direct Server Return (DSR) ==		== Using Direct Server Return (DSR) ==

2019-11-27T14:37:56Z

Round Robin: mod 100

← Older revision		Revision as of 14:37, 27 November 2019
Line 35:		Line 35:
	<source>		<source>
	% nft add rule nat prerouting numgen random mod 2 vmap { 0 : jump mychain1, 1 : jump mychain2 }		% nft add rule nat prerouting numgen random mod 2 vmap { 0 : jump mychain1, 1 : jump mychain2 }
	% nft add rule nat prerouting numgen random mod 99 vmap { 0-49 : jump mychain1, 50-99 : jump mychain2 }		% nft add rule nat prerouting numgen random mod 100 vmap { 0-49 : jump mychain1, 50-99 : jump mychain2 }
	</source>		</source>

2019-11-27T09:58:23Z

Round Robin: add example using random and probability

← Older revision		Revision as of 09:58, 27 November 2019
Line 29:		Line 29:
	0 : 4040 ,\		0 : 4040 ,\
	1 : 4050 }		1 : 4050 }
			</source>

			Support for random and probability-based distributions also exists:

			<source>
			% nft add rule nat prerouting numgen random mod 2 vmap { 0 : jump mychain1, 1 : jump mychain2 }
			% nft add rule nat prerouting numgen random mod 99 vmap { 0-49 : jump mychain1, 50-99 : jump mychain2 }
	</source>		</source>

2017-09-13T11:18:25Z

Using Direct Server Return (DSR): add reference to article about packet header mangling

← Older revision		Revision as of 11:18, 13 September 2017
Line 70:		Line 70:

	Note that xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy need to be replaced by the real destination MAC address.		Note that xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy need to be replaced by the real destination MAC address.
			This is [[Mangle packet header fields \| mangling packet header fields]] as well.

2017-09-13T11:17:33Z

Using stateless NAT: add reference to packet header mangling.

← Older revision		Revision as of 11:17, 13 September 2017
Line 53:		Line 53:
	</source>		</source>

	This is more lightweight that stateful NAT given there is no flow tracking in place.		This is more lightweight that stateful NAT given there is no flow tracking in place. This is indeed [[Mangle packet header fields \| mangling packet header fields]].

	== Using Direct Server Return (DSR) ==		== Using Direct Server Return (DSR) ==

2017-06-19T22:57:46Z

Using Direct Server Return (DSR)

← Older revision		Revision as of 22:57, 19 June 2017
Line 57:		Line 57:
	== Using Direct Server Return (DSR) ==		== Using Direct Server Return (DSR) ==

	This example performs a DSR topology for ~~non connection oriented~~ flows from ingress:		This example performs a DSR topology for connectionless flows from ingress:

	<source>		<source>
	% nft add rule t c udp dport 53 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set numgen inc mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0		% nft add rule netdev t c udp dport 53 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set numgen inc mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0
	</source>		</source>

	An approach for connection oriented flows can be performed as shown below.		An approach for connection oriented flows can be performed as shown below:

	<source>		<source>
	% nft add rule t c tcp dport 80 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set jhash ip saddr . tcp sport mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0		% nft add rule netdev t c tcp dport 80 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set jhash ip saddr . tcp sport mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0
	</source>		</source>

			Note that xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy need to be replaced by the real destination MAC address.

2017-06-19T22:33:34Z

Using Direct Server Return (DSR)

← Older revision		Revision as of 22:33, 19 June 2017
Line 57:		Line 57:
	== Using Direct Server Return (DSR) ==		== Using Direct Server Return (DSR) ==

	~~TODO~~.		This example performs a DSR topology for non connection oriented flows from ingress:

			<source>
			% nft add rule t c udp dport 53 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set numgen inc mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0
			</source>

			An approach for connection oriented flows can be performed as shown below.

			<source>
			% nft add rule t c tcp dport 80 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set jhash ip saddr . tcp sport mod 2 map { 0 : xx:xx:xx:xx:xx:xx, 1: yy:yy:yy:yy:yy:yy } fwd to eth0
			</source>

2017-06-19T18:01:19Z

fix broken example

← Older revision		Revision as of 18:01, 19 June 2017
Line 50:		Line 50:

	<source>		<source>
	% nft add rule t c ~~ip protocol~~ tcp dport 80 \		% nft add rule t c tcp dport 80 ip daddr set numgen inc mod 2 map { 0 : 192.168.1.100, 1 : 192.168.1.101 }
	ip daddr set numgen inc mod 2 map { 0 : 192.168.1.100, 1 : 192.168.1.101 }
	</source>		</source>

2017-06-14T17:02:29Z

Using stateless NAT

← Older revision		Revision as of 17:02, 14 June 2017
Line 45:		Line 45:
	== Using stateless NAT ==		== Using stateless NAT ==

	You can perform load balancing ~~also by using~~ stateless NAT approach as well~~, combining it~~ with round robin and consistent hash-based distribution.		You can perform load balancing through stateless NAT approach as well. You can combine this either with the round robin and consistent hash-based distribution approaches.

	The example below uses Round Robin flow distribution:		The example below uses Round Robin flow distribution:
Line 53:		Line 53:
	ip daddr set numgen inc mod 2 map { 0 : 192.168.1.100, 1 : 192.168.1.101 }		ip daddr set numgen inc mod 2 map { 0 : 192.168.1.100, 1 : 192.168.1.101 }
	</source>		</source>

			This is more lightweight that stateful NAT given there is no flow tracking in place.

	== Using Direct Server Return (DSR) ==		== Using Direct Server Return (DSR) ==

	TODO.		TODO.