Can someone explain this for me?
@selea ICMP blocked on the firewall.
That response is pretty weird though... :P
Yeah my brain is imploding because I can't understand why that was happening
I pinged 192.168.1.1, but I got a reply from 18.104.22.168?
@selea I don't know which version of Windows is this. I had similar problems on Windows 8.1 for about 1 year . The Wi-Fi network was entering in Schrödinger state - some stuff was working, some other stuff was not. Disabling and enabling the network adapter was the quick and dirty workaround. The problems disappeared after installation of some updates.
This is Windows 10 actually, I have never seen this before.
And I connected via ethernet aswell :S
@selea Possibly rate limiting for ICMP answers on 22.214.171.124 to avoid abuse with forged sender addresses.
To be honest, it does not make any sense :( Why that IP that is on the other side of the atlantic?
@selea Ah, I didn't notice the 192.168.1.1 yet (its outside the preview here). Normally, it should not be routed, and most home router will filter it.
Do you use some VPN and assigned the default route to it?
The VPN I used only routed a completely different subnet
@selea It happened to me once, and I couldn't understand it. Though it can be a sign of MITM, or you made a ddos on someone and the router's still dizzy a bit.
@selea use Linux, btw
I have not idea, :S
@selea Quantum computing? You are all addresses and no addresses at the same time 😁
haha, I wish!
@selea the default gateway might tell you that the desy network is not reachable
But why did 126.96.36.199 answer when I pinged 192.168.1.1 ?
@selea it is shy and doesn't want to get imvolved
@selea looks like the request timed out ? :p
Look further down
replace C:/Users to user@linux:~$
A instance dedicated - but not limited - to people with an interest in the GNU+Linux ecosystem and/or general tech. Sysadmins to enthusiasts, creators to movielovers - Welcome!