This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Internal Ip's not as host names

In Reports , why all internal ip's not showing as hostnames ?

Or I have reservations in DHCP with hostnames-Ipadresses
Or I have DNS entries with hostnames-Ipadresses

So the information is available.....?



This thread was automatically locked due to age.
Parents
  • Hi Timoline,

    Greetings.

    This is not possible in XG, the reports you generate will be based on IP address. 

    This is because the host name and IP address association could changed.

    You can still raise a feature request on this regards and cast your vote, through:

    http://feature.astaro.com/forums/330219-sophos-xg-firewall

    Thanks

    Sachin Gurung

  • Sachin,

    can you check this internally? AlanT has marked the feature request as "Already possible" but other users complain that this is not working. I am not able to test it. Can you reply to us with a confirmation answer?

    Thanks.

  • Has anyone seen this work?  I just logged into 5 different customers' XGs, all of which are pointing to their Internal DNS servers and have request route setup for the domain, but every report and ATP etc only show the IP.  

    This has actually caused a little hardship as one customer had an alert pop up in ATP and it only showed the IP Address, by the time he went to go check on that machine, the IP had changed so we weren't really sure which machine it was.  If it had showed the hostname of the PC it would have made it easier.

    Thanks

  • Hi All,

    I request if anyone can raise a case with Support. I am unable to recreate this instance. Also curious to see what support has to say on this.

    Please DM me ticket# personally to keep a track on the case.

    Thanks

    Sachin Gurung

  • Hi Sachin, 

    I'm a home user but would be willing to provide whatever is needed to get this fixed. How do I go about creating a support ticket?

  • Hi  

    report by hostname is still not possible. Were you able to conduct some tests?

    A feature request for that has been opened:

    http://ideas.sophos.com/forums/330219-sophos-xg-firewall/suggestions/16036801-resolve-private-ip-addresses-in-reports-to-hostnam

    At the moment even on v16.01.1 is not working

    Thanks

  • So, I created a support case for this and I had the support engineer escalate this to the dev team, and then I found later my support case closed.

    I was then told that this is a new feature and that it won't be worked on until after v17 - yet Alan Towes has marked this feature as "Already Possible".

     

    Which one is it? Is it an existing feature that is broken, or is it a new feature? Cann you please advise your community as to what Sophos is doing about it, and mark the feature requests in the applicable way so that we can be clear on this?

     

    Thanks,

    Erik

  • This case looks like the Country blocking not working from wan to lan and Sophos did not give an official answer for more than 1 year.

    Another disaster's example. Dear Sophos, do not ask why people will move to another UTM product once the license expires.

  • Is this still not possible?  The reports are slowly becoming more useful but having to cross reference IP address to host separately makes the reports absolutely useless.

    @alantoews any update on this?

  • It's way past v17.0 and mine still don't work. The logic they are using is so backwards "the IP might change". Yes that's true, that would be a problem to write the code to input hostname into report as of the date the report got generated. For example, If you were running a report for the past week, the data might be misleading since ip have probably changed. But that's why you don't write the feature code that way. You are obviously going to want the system to track devices by a metric such as MAC address in the logs, so when report time comes, there's something to tie it all together By the way, as is currently, when ip change, the reports are going to be useless anyways... Because the device at 192.168.5.x might not even be the same anymore. So i don't think they should be using that as a reason why to leave it as is
  • I have to agree with both your points.  This was very possible with UTM, but they can't seem to get it together 2 years later with XG.  Rather than just say it's not a feature we plan on bringing to XG, we're getting these weird and pretty lame excuses.  I think many of us would be ok with a truthful explanation or answer even if it's not the one we're hoping for.  At this point, I don't even bother with the reports because having to cross reference IP's to hostname is just plain stupid and tedious.  I keep contemplating going back to UTM until they get some of these issues resolved, such as being able to create automatic monthly reports.  

Reply
  • I have to agree with both your points.  This was very possible with UTM, but they can't seem to get it together 2 years later with XG.  Rather than just say it's not a feature we plan on bringing to XG, we're getting these weird and pretty lame excuses.  I think many of us would be ok with a truthful explanation or answer even if it's not the one we're hoping for.  At this point, I don't even bother with the reports because having to cross reference IP's to hostname is just plain stupid and tedious.  I keep contemplating going back to UTM until they get some of these issues resolved, such as being able to create automatic monthly reports.  

Children
No Data