Re: [Sqlgrey-users] warn_if_reject to populate the db

[Michel B. <mi...@bo...>]

Le Dimanche 26 Juin 2005 15:37, Michel Bouissou a =E9crit :
>
> > I didn't figure the whole thing out, but I
> > did look for a string "\.res\." which is commonly used for dynamic
> > space, e.g., *.res.rr.com. (residential customers.) Perhaps the secon=
d
> > dot should be any non-alpha character (-, _, ., digit), and to be saf=
e
> > there should be at least 2 domain segments following and at least one
> > segment preceding (implied by the leading dot.)
>
> I don't pretend that the regexp is perfect, it's only heuristic, but it
> would be interesting adding your modification only if you find samples =
of
> existing hostnames that don't get properly classified. (i.e. your examp=
le
> may already get classified corresctly if the last byte of the IP addres=
s is
> part of the name) The more things you add in the regexp, the longer it =
will
> take to process, and the higher chances it could collide with other
> non-dynamic names in an undesired manner.
>
> But feel free to experiment with your own copy and suggest improvements
> that show useful...

All the samples of *.res.rr.com that I can find in my logs also include t=
he IP=20
address in their hostname, so SQLgrey's "smart" algo will already conside=
r=20
them as "dyamic/enduser" without the need for making the regexp more comp=
lex.

Some examples at random:
108-64.200-68.tampabay.res.rr.com
160-35.26-24.tampabay.res.rr.com
180-17.26-24.se.res.rr.com
193-135.207-68.elmore.res.rr.com
2-85.207-68.tampabay.res.rr.com
61.186.204.68.cfl.res.rr.com
67.147.204.68.cfl.res.rr.com
cpe-24-164-130-13.si.res.rr.com
cpe-24-165-149-211.midsouth.res.rr.com
cpe-24-166-0-41.indy.res.rr.com
cpe-24-166-232-151.columbus.res.rr.com
cpe-67-11-214-14.satx.res.rr.com
cpe-67-49-227-231.dc.res.rr.com
cpe-67-49-62-53.socal.res.rr.com
cpe-67-9-163-159.austin.res.rr.com

etc.

--=20
Michel Bouissou <mi...@bo...> OpenPGP ID 0xDDE8AC6E