J
JW0914
Guest
Problem: Symbolic Substitution for an entire subnet returns errors, while all other Symbolic Substitutions apply without issue
I've spent 5+ hours searching online, reading through the ipfw manpages, and either I missed where it addressed this or this is such basic knowledge it's not mentioned lol I've come across other Unix based OSs where individuals have encountered this same error, but the fix for Ubuntu and other Linux distros don't work on FreeNAS, nor does advice given for FreeBSD (which I found odd since FreeNAS is, for all intents and purposes, FreeBSD. I don't recall exactly what someone on the FreeBSD forums posted that worked for them, but I know I did try what was suggested with an error similar to the ones above.
- LAN="$192.168.1.0/28"
net.inet.ip.fw.enable: 1 -> 0
net.inet6.ip6.fw.enable: 1 -> 0
ipfw: port list: invalid separator <.> in <92.168.200.0/26>
ipfw: missing ``to''
ipfw: port list: invalid separator <.> in <92.168.200.0/26>
ipfw: missing ``to''
Firewall rules loaded.
Firewall logging enabled.
net.inet6.ip6.fw.enable: 1 -> 0
ipfw: port list: invalid separator <.> in <92.168.200.0/26>
ipfw: missing ``to''
ipfw: port list: invalid separator <.> in <92.168.200.0/26>
ipfw: missing ``to''
Firewall rules loaded.
Firewall logging enabled.
- LAN="${192.168.1.0/28}"
net.inet.ip.fw.enable: 1 -> 0
net.inet6.ip6.fw.enable: 1 -> 0
/etc/rc.firewall: ${192....}: Bad substitution
Firewall rules loaded.
Firewall logging enabled.
net.inet6.ip6.fw.enable: 1 -> 0
/etc/rc.firewall: ${192....}: Bad substitution
Firewall rules loaded.
Firewall logging enabled.
- LAN="${ 192.168.1.0/28 }"
net.inet.ip.fw.enable: 1 -> 0
net.inet6.ip6.fw.enable: 1 -> 0
/etc/rc.firewall: ${ ...}: Bad substitution
Firewall rules loaded.
Firewall logging enabled.
net.inet6.ip6.fw.enable: 1 -> 0
/etc/rc.firewall: ${ ...}: Bad substitution
Firewall rules loaded.
Firewall logging enabled.
I've spent 5+ hours searching online, reading through the ipfw manpages, and either I missed where it addressed this or this is such basic knowledge it's not mentioned lol I've come across other Unix based OSs where individuals have encountered this same error, but the fix for Ubuntu and other Linux distros don't work on FreeNAS, nor does advice given for FreeBSD (which I found odd since FreeNAS is, for all intents and purposes, FreeBSD. I don't recall exactly what someone on the FreeBSD forums posted that worked for them, but I know I did try what was suggested with an error similar to the ones above.