IP address matching

oliverm has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: IP address matching by Abigail-II (Bishop) on Jun 04, 2004 at 22:39 UTC
`use Regexp::Common; /$RE{net}{IPv4}/ and print "Contains a valid IP address\n"; /$RE{net}{IPv4}{hex}/ and print "Contains a valid IP address in hex\n" +; /$RE{net}{IPv4}{oct}{-sep => ':'}/ and print "..."; # Etc.` [download] Abigail	[reply] [d/l]
Re: IP address matching (potentially relevant thread) by ybiC (Prior) on Jun 05, 2004 at 01:11 UTC
While not directly answering your question brother oliverm, you might find the "Don't Use Regular Expressions To Parse IP Addresses!" thread to be an informative and relevant read. Oh yeah, and welcome to the Monastery! 8^) cheers, ybiC striving toward Perl Adept (it's pronounced "why-bick")	[reply]
Re: IP address matching by u235sentinel (Hermit) on Jun 04, 2004 at 23:52 UTC
I was wondering if you have written any code so we can help you. I've written something like this a few times recently. No error checking but then again I was pulling from my apache access_log. I wanted it all including any invalid. Let us know what you have tried.	[reply]
Re: IP address matching by Anonymous Monk on Jun 04, 2004 at 22:15 UTC
Thats trivial and I wont give you the spoiler. But consider first - IP addresses can come in one or two forms. IP6, IP4 etc. How broad do you want your match to be? Any valid IP? Or just ones from sensible domains?	[reply]
Re^2: IP address matching by oliverm (Initiate) on Jun 04, 2004 at 22:30 UTC
IPv4, and i want it to be any valid IP	[reply]
Re^3: IP address matching by Anonymous Monk on Jun 05, 2004 at 02:10 UTC
and if you want to be extra careful (or just plain pedantic :)... some IP addresses while valid in form are not valid in practice. these are the martians and the unallocated. the martians are reserved addresses that shouldn't be seen on the internet as a whole. but some of them can be used on local networks. the unallocated are IP addresses that have not been allocated out of the global pool. these you shouldn't see at all (and shouldn't accept either). you can find the current lists through a handy `whois` query. $ whois -h whois.radb.net fltr-martian filter-set: fltr-martian filter: { 0.0.0.0/8^+ , 10.0.0.0/8^+ , 127.0.0.0/8^+ , 169.254.0.0/16^+ , 172.16.0.0/12^+ , 192.0.2.0/24^+ , 192.168.0.0/16^+ , 198.18.0.0/15^+ , 224.0.0.0/3^+ } descr: Special use and reserved IPv4 prefixes. remarks: For the complete set of bogons, please see: fltr-unallocated - unallocated prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: Rob Thomas RT624 tech-c: Rob Thomas RT624 notify: radb@cymru.com mnt-by: MAINT-BOGON-FILTERS changed: radb@cymru.com 20021229 changed: radb@cymru.com 20021230 changed: radb@cymru.com 20021230 source: RADB ... [download] do the same to find fltr-unallocated.	[reply] [d/l]
Re: IP address matching by CountZero (Bishop) on Jun 04, 2004 at 22:48 UTC
It is considered polite and good form to at least start your request with a nice salutation to the Monks and show some effort in solving your problem. CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply]