Entry in Router Log
Quote from: ejs The type of packet is a reply. The proper use for this packet is for replying. But anyone could malciously craft the packet and send it to you. Or someone sends a packet with a spoofed IP address to the other system so that the other system will send the reply to you. Or, especially if you recently changed IP addresses, it could be related to the previous user of your current IP address (unless you've got a static IP of course).
Yes, of course. Thanks for that bit of a reminder.
Quote from: ejs I see very few of these ICMP Destination Unreachable packets.
I see many, regularly, most especially when I'm playing my game. It's how I've come to confusion about them in reference to direction and the source of my particular problem.
@AO. Thanks for trying to explain. I'm still thinking it's not making sense. About the direction. Perhaps I haven't been clear about my confusion in that regard. With the quote I put from the article about Destination Unreachable being a response to a datagram from 'the device', implying it is the 'originating source', that is why I am confused when one sees a DU entry from another IP address to one's own, as with Jim's. What ejs said notwithstanding, the direction of the reply is of course from the other IP address, but the ultimate source is still 'the device'. Further to this, what compounds my confusion is that it sheds no light on the root of a problem I have and have previously posted about on forum. If I can understand 'direction' - i.e. source of the problem, I can perhaps move on.
I get a host of DU entries when playing my game. The greater amount are to do with the game server and they are port unreachable. If they are replies to 'the device' my device, then I think that means my device has tried to connect to a port on the game server and it was unreachable and the server replied as such. Fine, I can understand that (though quite how it replies if it's unreachable I don't know). What throws me is that if the direction - i.e. source, is the game server - as implied by the direction in the entry: IP address so and so to my IP address then that makes me think the game server has tried to connect to my device and my device was unreachable and the article is wrong - it isn't a reply.
This may help you understand these ICMP datagrams.
https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol
Personally I can't be bothered to get my head around these firewall logs. They are only the firewall boasting that's it's blocked some incoming packet.
IMO it's not the stuff in the logs we need be concerned about, it's the stuff that's not picked up
https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol
Personally I can't be bothered to get my head around these firewall logs. They are only the firewall boasting that's it's blocked some incoming packet.
IMO it's not the stuff in the logs we need be concerned about, it's the stuff that's not picked up
Quote from: npr This may help you understand these ICMP datagrams.
https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol
Well thanks npr, I appreciate the link. I am still confused because that hops back (as I read it) to ejs and the link I've already quoted and questioned before being correct. I think I fucking give up.
Quote Personally I can't be bothered to get my head around these firewall logs. They are only the firewall boasting that's it's blocked some incoming packet.
IMO it's not the stuff in the logs we need be concerned about, it's the stuff that's not picked up
It's important to me because when I know what is factually correct about my log entries I'll be able to tell whether my set-up (or router itself) is at fault or if it's a fault with the game servers.
Excuse me Jim. I hadn't intended to hijack your thread. Please do split it off if you think that's necessary.
Quote from: ejs A timeout is probably the most incorrect example possible.
You are of course technically correct there as it's not due to a packet of data sent to your IP address, more the lack of!! I hope you appreciate I was just trying to illustrate that in normal circumstances, the program that's being run, browser, game, whatever, will normally give you relevant information.