Linux v69820.1blu.de 4.15.0 #1 SMP Mon Sep 30 15:36:27 MSK 2024 x86_64
Apache/2.4.58
Server IP : 195.90.215.149 & Your IP : 216.73.217.80
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
nftables /
examples /
Delete
Unzip
Name
Size
Permission
Date
Action
sysvinit
[ DIR ]
drwxr-xr-x
2026-04-26 19:49
README
475
B
-rw-r--r--
2023-10-19 14:02
all-in-one.nft
1016
B
-rw-r--r--
2026-02-24 08:16
arp-filter.nft
129
B
-rw-r--r--
2026-02-24 08:16
bridge-filter.nft
197
B
-rw-r--r--
2026-02-24 08:16
ct_helpers.nft
1.23
KB
-rwxr-xr-x
2026-02-24 08:16
inet-filter.nft
187
B
-rw-r--r--
2026-02-24 08:16
inet-nat.nft
251
B
-rw-r--r--
2026-02-24 08:16
ipv4-filter.nft
182
B
-rw-r--r--
2026-02-24 08:16
ipv4-mangle.nft
74
B
-rw-r--r--
2026-02-24 08:16
ipv4-nat.nft
246
B
-rw-r--r--
2026-02-24 08:16
ipv4-raw.nft
137
B
-rw-r--r--
2026-02-24 08:16
ipv6-filter.nft
186
B
-rw-r--r--
2026-02-24 08:16
ipv6-mangle.nft
78
B
-rw-r--r--
2026-02-24 08:16
ipv6-nat.nft
253
B
-rw-r--r--
2026-02-24 08:16
ipv6-raw.nft
141
B
-rw-r--r--
2026-02-24 08:16
load_balancing.nft
1.81
KB
-rwxr-xr-x
2026-02-24 08:16
nat.nft
1.14
KB
-rwxr-xr-x
2023-10-19 14:02
netdev-ingress.nft
128
B
-rw-r--r--
2026-02-24 08:16
overview.nft
1.05
KB
-rwxr-xr-x
2023-10-19 14:02
pf.os
28.21
KB
-rw-r--r--
2026-02-24 08:16
secmark.nft
2.35
KB
-rwxr-xr-x
2026-02-24 08:16
sets_and_maps.nft
1.25
KB
-rwxr-xr-x
2026-02-24 08:16
workstation.nft
817
B
-rwxr-xr-x
2023-10-19 14:02
Save
Rename
#!/usr/sbin/nft -f # This example file shows how to implement load balancing using the nftables # framework. # This script is meant to be loaded with `nft -f <file>` # You require linux kernel >= 4.12 and nft >= 0.7 # For up-to-date information please visit https://wiki.nftables.org flush ruleset table ip nat { chain prerouting { type nat hook prerouting priority -300; # round-robing load balancing between the 2 IPv4 addresses: dnat to numgen inc mod 2 map { 0 : 192.168.10.100, \ 1 : 192.168.20.200 } # emulate flow distribution with different backend weights using intervals: dnat to numgen inc mod 10 map { 0-5 : 192.168.10.100, \ 6-9 : 192.168.20.200 } # tcp port based distribution is also possible: ip protocol tcp dnat to 192.168.1.100 : numgen inc mod 2 map { 0 : 4040 ,\ 1 : 4050 } # consistent hash-based distribution: dnat to jhash ip saddr . tcp dport mod 2 map { 0 : 192.168.20.100, \ 1 : 192.168.30.100 } } } table ip raw { chain prerouting { type filter hook prerouting priority -300; # using stateless NAT, round-robing distribution (you could use hashing too): tcp dport 80 notrack ip daddr set numgen inc mod 2 map { 0 : 192.168.1.100, 1 : 192.168.1.101 } } } table netdev mytable { chain ingress { # mind the NIC devices, they must exist in the system type filter hook ingress device eth0 priority 0; # using Direct Server Return (DSR), connectionless approach: udp dport 53 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set numgen inc mod 2 map { 0 : aa:aa:aa:aa:aa:aa, 1 : bb:bb:bb:bb:bb:bb } fwd to eth1 # using Direct Server Return (DSR), connection-oriented flows: tcp dport 80 ether saddr set aa:bb:cc:dd:ff:ee ether daddr set jhash ip saddr . tcp sport mod 2 map { 0 : aa:aa:aa:aa:aa:aa, 1 : bb:bb:bb:bb:bb:bb } fwd to eth1 } }