"if I'm creating network rules, I try to do it one at a time. And while I'm doing it, from one host or vm, I'll open a command prompt and run:
ping -t <destination ip>
e.g. ping -t 192.168.1.100
the -t parameter (in windows only I think) keeps ping "pinging" until it's told to stop.
If I'm trying to create a rule to connect two networks together, I'll have the machine just ping away to the new network to connect to for a specific host on the other side. It'll fail repeatedly. Once I make a change in routing, then you can see if the change works or not. Just a silly trick, but it helped me keep my sanity decades ago."
"if I'm creating network rules, I try to do it one at a time. And while I'm doing it, from one host or vm, I'll open a command prompt and run:
e.g. ping -t 192.168.1.100
the -t parameter (in windows only I think) keeps ping "pinging" until it's told to stop.
If I'm trying to create a rule to connect two networks together, I'll have the machine just ping away to the new network to connect to for a specific host on the other side. It'll fail repeatedly. Once I make a change in routing, then you can see if the change works or not. Just a silly trick, but it helped me keep my sanity decades ago."