replies coming from localhost

[p1r473]

Why are the replies coming from localhost? The replies are coming from my local IPV4 address
Is it failing? The results are all 'unknown'. If so, the output should be more clear
Why are they failing? Normal ping works fine
It looks like 0% loss

[Killeroo]

I'm having issues reproducing this. The only thing I can suggest is to prehaps wait for the next version which is quite a big jump in .NET versions.

[p1r473]

@Killeroo sure I will test the new version

[Killeroo]

Thanks 👍

[p1r473]

@Killeroo any ETA for next version?

[Killeroo]

Unfortunately the final release is not going to be ready for a while. However, I will look to put together some sort of pre-release version which you can test out in the next week or so.

[p1r473]

It seems to be working now, thanks.
No idea what changed.

[p1r473]

@Killeroo Seems to be happening again so lets go forward with the debugging!

[p1r473]

Dont know if you saw the above message @Killeroo - just bumping this

[Killeroo]

Dont know if you saw the above message @Killeroo - just bumping this

Apologies, been extremely busy at the moment. I still intend to release a pre-release version which you can use for testing soon.

[Killeroo]

Hi, did you notice this happening when you were running another instance of PowerPing in listening mode (--listen)?

I have found that doing this causes one PowerPing instance to just receive replies while the listening instance seems to 'swallow' all response packets.

[p1r473]

No I was unaware of Listen mode

[Killeroo]

I see, I think that something might be opening a socket that is grabbing all ICMP packets before PowerPing can recieve them. This is what happens when using the --listen command and trying to send pings in another PowerPing instance. It's a tricky issue that I would like to address at some point but can't give an ETA right now.

In the meantime there is a new version of PowerPing that is worthing trying out (download it here if you haven't already), I have unfortunately noticed it still occuring on the latest release however.

I will update this thread when I look into this again.