f5b5de1a32
Currently ipfw has multiple components that are not parts of GENERIC kernel like dummynet etc. They can bring in important sysctls if enabled with rc.conf(5) and loaded with ipfw startup script by means of "required_modules" after initial consult with /etc/sysctl.conf at boot time. Here is an example of one increasing limit for dummynet hold queues that defaults to 100: net.inet.ip.dummynet.pipe_slot_limit=1000 This makes it possible to use ipfw/dummynet rules such as: ipfw pipe 1 config bw 50Mbit/s queue 1000 Such rule is rejected unless above sysctl is applied. Another example is a group of net.inet.ip.alias.* sysctls created after libalias.ko loaded as dependency of ipfw_nat. This is not a problem if corresponding code compiled in custom kernel so sysctls exist when sysctl.conf is read early or kernel modules loaded with a loader. This change makes it work also for GENERIC and modules loaded by means of rc.conf(5) settings. MFC after: 1 month |
||
|---|---|---|
| .. | ||
| rc.d | ||
| Makefile | ||
| netstart | ||
| network.subr | ||
| pccard_ether | ||
| rc | ||
| rc.bsdextended | ||
| rc.conf | ||
| rc.firewall | ||
| rc.initdiskless | ||
| rc.resume | ||
| rc.sendmail | ||
| rc.shutdown | ||
| rc.subr | ||
| rc.suspend | ||