Ashen "Sterno" Delalupe CarnotMy urge to turn a shotgun on this laptop is really skyrocketing.
Tries to ping to Hyper-V guest from host over internal type network switch: no problem
Tries the reverse: NOTHIN'
Firewall is open on host. Wireshark confirms pings make it through but the host just... decides not to return the ping. It KNOWS how to respond. It has an ARP address, is in the same subnet, and has a route.
I'm stumped and extremely frustrated.
PinballsWizard@speckled_doge does the host have ping responses enabled/on that interface? if you can connect but it won't respond to ping it's likely just turned off
@pinball Trying to understand right now if that's even a thing for Windows interfaces. The firewall is not blocking it so it SEEMS like it's something the interface just doesn't wanna do but unsure how to toggle it on if that's the problem. Digging in Regedit.
@pinball The answer could frustratingly be that this sort of thing is just straight-up disallowed by Hyper-V for reasons I don't understand. But that'd be weird as hell.
@speckled_doge it's been a while since i've needed to dig into changing it, but iirc some versions of windows firewall put the icmp rules in file and printer sharing, and be careful about what subnet it's actually enabling, you may need to set a rule with "any"
@pinball Yep I have a totally different rule that just allows ICMP. The traffic is totally getting through. It's not the firewall I think, else Wireshark wouldn't be able to see it.