OK, good to know.
EDIT: Some of my early scripts accepted a range of IPs as arguments, but this script was never tested to accept a group range of IPs on the commandline denoted by '
-' without the group file '
/jffs/configs/IPGroups' existing.
e.g. you can see that normally on
my router the initialisation request fails gracefully because '/
jffs/configs/IPGroups' currently exists (for use by my other scripts), but does not have the
perceived range XEON-POWER defined.
However if I delete '/
jffs/configs/IPGroups' and request the script again then the script does indeed panic
....... (until I reinstate the file)
You can temporarily try manually creating an empty
'IPGroups' file
Code:
touch /jffs/configs/IPGroups
to see if the script will now initialise until I can post a patched/tested version of the script (that has been unaltered on GitHub for nearly 2 1/2 years!) that either removes the reference to function
ExpandIPRange()
or includes it.