Bering-uClibc 4.x - User Guide - IPv6 Networking - Configure Shorewall6
| IPv6 Networking - Configure Shorewall6 | ||
|---|---|---|
| Prev | Bering-uClibc 4.x - User Guide | Next |
Earlier Bering-uClibc versions provided a package called 6wall.lrp which implemented an IPv6 firewall.
Bering-uClibc 4.x provides shorwall6.lrp instead.
Unlike 6wall.lrp, shorwall6.lrp is an official variant of the IPv4 shorwall.lrp and is supported by the same team.
Improvements in the Linux kernel since 2.6.24 make Bering-uClibc 4.x a rather better IPv6 firewall platform than Bering-uClibc 3.x.
Note: The full name "Shorewall" was abbreviated to "shorwall" in order to comply with the 8 character filename length limit for MS-DOS floppy disks, hence the package file is shorwall.lrp. The name of the Shorewall6 package, shorwall6.lrp, is based on the name of the Shorewall package even though the 8 character filename length limit is no longer in effect.
In general, configuration of Shorewall6 is equivalent to configuration of Shorewall, so refer to the Shorewall chapter of this guide. However, note the following differences:
- There are far fewer macros defined specifically for Shorewall6 than for Shorewall (in other word far fewer matches for
/usr/share/shorewall6/macro.*than for/usr/share/shorewall/macro.*)but all of the Shorewall(4) macros can be used for Shorewall6. Where both files are present (e.g. for mDNS) the Shorewall6 macro takes priority.
Important: If you are running both Shorewall and Shorewall6 (rather than only Shorewall6) you need to make a modification to the Shorewall configuration otherwise Shorewall6 will be stopped whenever Shorewall is restarted.
In file /etc/shorewall/shorewall.conf ensure that DISABLE_IPV6 is set to No.
| Prev | Up | Next |
