X
NMS Prime
Stay informed. No spam. Just content. This is our promise.
I agree to the privacy terms. I can unsubscribe at any time.
X
Thank You!
X
NMS PRIME - Konferenz
Anzahl der Teilnehmer:
Datenschutz gelesen und akzeptiert
X
Vielen Dank!
X Sign up to comment and create new topics

If you have unknown modems, NMS Prime generally doesn't send them DHCP.  This means they will reboot and range again trying to lock on.  This clutters up your DHCP logs.

There are a couple of ways you might want to address this, but right now I've added a hack on my system that does this:


In nmsprime/modules/ProvBase/Entities/Netgw.php change this:



case 'CM':
    $data .= "\n\t\t\t".'allow members of "CM";';
    $data .= "\n\t\t\t".'deny unknown-clients;';
    break;



To this:

case 'CM':
    $data .= "\n\t\t\t".'allow members of "CM";';
    $data .= "\n\t\t\t".'if not known { filename "cm/cm-disable.cfg"; ddns-hostname "unknown-modem"; }';
    break;


You then need to make or copy a disable config to /tftpboot/cm/cm-disable.cfg


I would like this to be a builtin feature of NMS Prime, but I'd like it to be more flexible.  Maybe a tickbox in the CMPool settings for if this is enabled, and maybe allow the options to be overridden.  In some cases rather than disabling a modem you might want to hand it an "unregistered" profile which restricts them to a signup page.  You might also want to hand them a different CMPool so they end up being proxied on the IP range.




Most Popular Post
There are no posts marked as being answered (liked) on this topic yet!!

1 Comment

  1. Thanks Robert. We will consider this for future updates. But it currently doesn't have priority. But you can fork the Github project and create a pull request at any time.