|
From: Michel B. <mi...@bo...> - 2005-06-26 14:06:56
|
Le Dimanche 26 Juin 2005 16:01, 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 sec= ond > > > dot should be any non-alpha character (-, _, ., digit), and to be s= afe > > > there should be at least 2 domain segments following and at least o= ne > > > 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 sample= s of > > existing hostnames that don't get properly classified. (i.e. your exa= mple > > may already get classified corresctly if the last byte of the IP addr= ess > > is part of the name) The more things you add in the regexp, the longe= r it > > will take to process, and the higher chances it could collide with ot= her > > non-dynamic names in an undesired manner. > > > > But feel free to experiment with your own copy and suggest improvemen= ts > > that show useful... > > All the samples of *.res.rr.com that I can find in my logs also include= the > IP address in their hostname, so SQLgrey's "smart" algo will already > consider them as "dyamic/enduser" without the need for making the regex= p > more complex. More, checking my logs, I don't see any other ISP besides rr.com and Veri= zon=20 that uses a ".res." part in their hostnames, and both rr.com and Verizon = also=20 put the IP address in... Verizon addresses also begin with "pool-", that = the=20 regexp already catches. Verizon samples: pool-151-200-35-11.res.east.verizon.net[151.200.35.11] pool-138-88-28-49.res.east.verizon.net[138.88.28.49] etc. --=20 Michel Bouissou <mi...@bo...> OpenPGP ID 0xDDE8AC6E |