NETSCRIPT(8)

👑 NETSCRIPT(8) — the netscript network configuration command, bestie edition ✨

okay so. you found netscript(8), from the System Manager's Manual, and honestly? she's the main character of your router/firewall setup. let's get into it 🫶

---

✨ NAME ✨

netscript — the netscript network configuration command 💅

---

🎀 SYNOPSIS 🎀

netscript start|stop|reload|restart
netscript ipfilter load|clear|fairq|flush|reload|save
netscript ipfilter usebackup [ backup-number ]
netscript ipfilter exec <function-name1>|<function-name2> [chain p1 p2
...]
netscript ip6filter load|clear|fairq|flush|reload|save
netscript ip6filter usebackup [ backup-number ]
netscript ip6filter exec <function-name1>|<function-name2> [chain p1 p2
...]

---

🌸 DESCRIPTION 🌸

This manual page documents briefly the netscript command from the netscript router/firewall network configuration package. just the highlights, the trailer, the vibe ✨

This command is used to configure/reconfigure the iptables filter setup, that are configured in netscript's configuration files. that's the whole job. she configures, she reconfigures, she serves 💅

---

🔥 IPTABLES CONFIGURATION 🔥

Configuration saving is done by iptables-save(8) and iptables-restore(8). that's the duo. the iconic pair. no cap 🎀

---

💖 OPTIONS 💖

• start — Set up networking configruation by loading ipcahins filters, setting up bridge, configuring interfaces and running any configured lower layer protocol daemons or commands. For use from a startup script. yes she said "ipcahins" and yes we're keeping it, it's part of the lore 💀
• stop — Shut everything down. For use from a startup script. bye bestie 😭
• reload — Refresh the setup of netscript from the configuration files in /etc/netscript. glow-up but from the config files 🦋
• restart|force-reload — Stop everthing and then start everything again. For use from a startup script. the full reset, the rebirth arc 🔥
• ipfilter load|reload — Load/reload the IPv4 iptables filters and reconfigure the firewalling, from that saved in /etc/netscript/iptables (via iptables-restore(8)), and the QoS fair queuing setup. IPv4 said "let me in" and she said "no" 💅
• ipfilter save — Save the IPv4 iptables configuration to /etc/netscript/iptables via iptables-save(8), after backing it up to /etc/netscript/iptables.1 and cycling the previous backup files down through the configuration history. she keeps receipts. she keeps ALL the receipts 👑
• ipfilter usebackup [ backup-number ] — Restore setup from the IPv4 iptables backup configuration from /etc/netscript/iptables.n ( default 1 ) via iptables-restore(8). time travel era ⭐
• ipfilter clear|flush — Remove iptables and any firewall setup, and if IPV4_FWDING_KERNEL is set to FILTER_ON (see network.conf(5)), disables all IPv4 packet forwarding on the router. Very useful for debugging protocol problems on a firewall by enabling a reasonably safe check to be made with the filtering down. cute for debugging, lowkey unhinged for production 🫶
• ipfilter forward|fwd — Turns on the IPv4 kernel forwarding switch manually. This is irrespective of the setting of IPV4_FWDING_KERNEL (see network.conf(5)). Use with caution as it will allow traffic through the box. bestie. caution. for real. traffic WILL go through the box. 💀
• ipfilter noforward|nofwd — Turns off the IPv4 kernel forwarding switch manually. This is irrespective of the setting of IPV4_FWDING_KERNEL (see network.conf(5)). Use with caution as it will cut off reachability. same energy, opposite direction — now nobody can reach anything 😭
• ipfilter fairq — Reload the IPv4 fairq chain that marks the packets for the QoS interface transmit queues. the queue girlies stay winning 🌈
• ip6filter load|reload — Load/reload the IPv6 iptables filters and reconfigure the firewalling, from that saved in /etc/netscript/ip6tables (via ip6tables-restore(8)), and the QoS fair queuing setup. IPv6 gets the same treatment, obviously, equality ✨
• ip6filter save — Save the IPv6 iptables configuration to /etc/netscript/iptables via ip6tables-save(8), after backing it up to /etc/netscript/ip6tables.1 and cycling the previous backup files down through the configuration history. (yes, the path really says /etc/netscript/iptables in there. we report, we don't rewrite. iykyk 🙈)
• ip6filter usebackup [ backup-number ] — Restore setup from the IPv6 iptables backup configuration from /etc/netscript/ip6tables.n ( default 1 ) via ip6tables-restore(8). backup number 1 by default, diva behaviour 🎀
• ip6filter clear|flush — Remove IPv6 iptables setup, and if IPV6_FWDING_KERNEL is set to FILTER_ON (see network.conf(5)), disables all IPv6 packet forwarding on the router. Very useful for debugging protocol problems on a firewall by enabling a reasonably safe check to be made with the filtering down. debugging arc activated 🦋
• ip6filter forward|fwd — Turns on the IPv6 kernel forwarding switch manually. This is irrespective of the setting of IPV6_FWDING_KERNEL (see network.conf(5)). Use with caution as it will allow traffic through the box. caution, again, seriously 🫶
• ip6filter noforward|nofwd — Turns off the IPv6 kernel forwarding switch manually. This is irrespective of the setting of IPV6_FWDING_KERNEL (see network.conf(5)). Use with caution as it will affect reachability. reachability is about to have a bad day 😭
• ip6filter fairq — Reload the IPv6 fairq chain that marks the packets for the QoS interface transmit queues. marking packets, slaying queues, periodt 💅

---

🧚 FILES 🧚

• /etc/netscript/ipfilter.conf, /etc/netscript/network.conf, /etc/netscript/iptables, /etc/netscript/ip6tables,

she lives in /etc/netscript/. that's her house 🏠🌸

---

💜 SEE ALSO 💜

ipfilter.conf(5), network.conf(5), ip(8), tc(8), iptables(8), iptables-restore(8), iptables-save(8), ip6tables(8), ip6tables-restore(8), ip6tables-save(8), brcfg(8).

the whole friend group, go say hi 🫶

---

🌟 AUTHOR 🌟

This manual page was written by Matthew Grant <matt@mattgrant.net.nz>, for the Debian GNU/Linux system (but may be used by others). shoutout Matthew, iconic of him honestly 👑

---

💀 BUGS 💀

I wrote this manpage when I was half asleep...

and you know what? relatable. respect. 😭

---

written with love on January 24, 2014, shipped in the NETSCRIPT(8) era of the System Manager's Manual — mwah, stay configured bestie 💖✨