Awesome, thanks! Sent from my mobile device please excuse. 11.11.2017 2:48 PM "Gedalya" <gedalya at gedalya.net> napisa?(a):> On 11/10/2017 11:03 PM, Joseph Tam wrote: > > > > The toughest situation (using script techniques) is for > > CIDR ranges just shy of a full octet boundary e.g. /25. > > Actually there is a great tool for that, grepcidr > > $ echo 10.11.12.127 | grepcidr 10.11.12.0/25 && echo OK > 10.11.12.127 > OK > $ echo 10.11.12.128 | grepcidr 10.11.12.0/25 && echo OK > $ > > But in your case you really probably should use postgres for the userdb > and just return everything from there in user fields / extra fields, and if > the logic doesn't fit in a simple query you can put it in a stored > procedure. That will likely be more efficient. > > >
I would still recommend using allow_nets instead. It will perform better, and can deal with multiple networks etc. Aki> On November 11, 2017 at 4:27 PM "j.emerlik" <j.emerlik at gmail.com> wrote: > > > Awesome, thanks! > > Sent from my mobile device please excuse. > > 11.11.2017 2:48 PM "Gedalya" <gedalya at gedalya.net> napisa?(a): > > > On 11/10/2017 11:03 PM, Joseph Tam wrote: > > > > > > The toughest situation (using script techniques) is for > > > CIDR ranges just shy of a full octet boundary e.g. /25. > > > > Actually there is a great tool for that, grepcidr > > > > $ echo 10.11.12.127 | grepcidr 10.11.12.0/25 && echo OK > > 10.11.12.127 > > OK > > $ echo 10.11.12.128 | grepcidr 10.11.12.0/25 && echo OK > > $ > > > > But in your case you really probably should use postgres for the userdb > > and just return everything from there in user fields / extra fields, and if > > the logic doesn't fit in a simple query you can put it in a stored > > procedure. That will likely be more efficient. > > > > > >
Great, thanks! Sent from my mobile device please excuse. 11.11.2017 6:00 PM "Aki Tuomi" <aki.tuomi at dovecot.fi> napisa?(a):> I would still recommend using allow_nets instead. It will perform better, > and can deal with multiple networks etc. > > Aki > > > On November 11, 2017 at 4:27 PM "j.emerlik" <j.emerlik at gmail.com> wrote: > > > > > > Awesome, thanks! > > > > Sent from my mobile device please excuse. > > > > 11.11.2017 2:48 PM "Gedalya" <gedalya at gedalya.net> napisa?(a): > > > > > On 11/10/2017 11:03 PM, Joseph Tam wrote: > > > > > > > > The toughest situation (using script techniques) is for > > > > CIDR ranges just shy of a full octet boundary e.g. /25. > > > > > > Actually there is a great tool for that, grepcidr > > > > > > $ echo 10.11.12.127 | grepcidr 10.11.12.0/25 && echo OK > > > 10.11.12.127 > > > OK > > > $ echo 10.11.12.128 | grepcidr 10.11.12.0/25 && echo OK > > > $ > > > > > > But in your case you really probably should use postgres for the userdb > > > and just return everything from there in user fields / extra fields, > and if > > > the logic doesn't fit in a simple query you can put it in a stored > > > procedure. That will likely be more efficient. > > > > > > > > > >