# Logstash geoIP and dissect issues **URL:** \ **Category:** Logstash\ **Created:** [October 23, 2017, 5:55pm UTC](https://discuss.elastic.co/t/logstash-geoip-and-dissect-issues/104944 "2017-10-23T17:55:05Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 23, 2017, 10:02pm UTC](https://discuss.elastic.co/t/logstash-geoip-and-dissect-issues/104944/3 "2017-10-23T22:02:58Z")
As Magnus mentions, it would be better if you update the original thread with this extra info as it helps others understand the problem and what you've already worked through 🙂 > [@Logstash Dissect Filter](https://discuss.elastic.co/t/logstash-dissect-filter/104907): > > I have Logstash Kibana and Elasticsearch versions 5.6.2 installed on Windows 2012 R2. I have a grok pattern that reads in text file entries adequately. The end of each entry is a message field containing a couple different formats; sometimes an IP adress, sometimes 2 IP addresses and different messages attached. What I need is to pull only the entries that have an outside IP address and I need to pull that IP address and put it in a field and use it as the source for geoIP. I was thinking of usi… --- _[View the full topic](https://discuss.elastic.co/t/logstash-geoip-and-dissect-issues/104944)._