• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Linux DDoS Protection Script For iptables

now this error !
Code:
./build.sh: 88: ./build.sh: cannot create /proc/sys/net/ipv4/conf/all/mc_forwarding: Permission denied
./build.sh: 88: ./build.sh: cannot create /proc/sys/net/ipv4/conf/default/mc_forwarding: Permission denied
./build.sh: 88: ./build.sh: cannot create /proc/sys/net/ipv4/conf/eth0/mc_forwarding: Permission denied
./build.sh: 88: ./build.sh: cannot create /proc/sys/net/ipv4/conf/lo/mc_forwarding: Permission denied

I'm sure the script in the OP was helpful an one time, but that time has passed. Good network settings are a moving target.
And those entries are read only.

Websearch said:
Remember that the directories and files in the /proc directory tree
are "manufactured" on the fly by kernel components. While they exhibit the
expected permission structure, they do not necessarily behave like regular
files; the kernel components can impose additional restrictions, such
as "without write permission, even root cannot write", and "user processes
(including root user processes) cannot change the permission structure".

Thus, it appears that, by themselves, the mc_forwarding files are strictly
read-only, providing information on the current setting of multicast
forwarding, and not providing a mechanism to change it.

Which still leaves the question unanswered,

"Why is it not possible to turn on multicast forwarding on any interface?"

It /is/ possible. But it takes more than just an
echo 1 >.../mc_forwarding
to accomplish.
from here.
 
Back
Top