Open hamid0901 opened 4 weeks ago
ikd why
Could be a few reasons:
is configured to forward requests to the actual target IP or domain, rather than stopping at your VMware box’s IP. Sometimes, proxies are set to direct traffic to the IP where they receive it unless explicitly instructed otherwise.
If NAT or port forwarding isn’t properly set up, the requests might not reach the intended target. This can result in the traffic being "stuck" at the VM’s IP address. Double-check your NAT/port forwarding rules if your proxy is on the same network as your VMware instance.
Sometimes, firewalls rules can interfere, causing requests to loop back to the origin (your VMware box) rather than being forwarded externally. Double check your firewall configurations on your proxy and VMware box. This could help identify if something is blocking the intended routing.
If your L7 request configuration is set to target 192.168.219.128 instead of the actual external website, all traffic will go there. Ensure that the destination IP or URL is explicitly set to the desired website, not the VMware IP, in your L7 attack configuration. Essentially double check an entry doesn't exist in /etc/hosts for 192.168.219.128 forumzar.com
Perhaps this setup is incorect given it loops back to local. Not too sure as I cant do muchj traceing through it.
I hope this helps.
that 192.168.219.128 is my vmware ip adress. The proxy works well. But why is the L7 attack through the proxy directed at "me" rather than at the website? This is a clear error. i want to know reason