Meterpreter on WAN

I asked a classmate if I can hack his computer after he recently built it and he said yes.

I configured my Verizon router for 192.168.1.10 to be a DMZ host. If I were to set up a meterpreter payload where my LHOST was 192.168.1.10 and my LPORT to be 4444 and have my victim, who is on a totally different wireless network and totally different area, open it, would it start a meterpreter session?

Also, I have set up port forwarding on my router. If the above does not work, what do I do next? I know that I have a "tunnel" between IP addresses, but how can I start meterpreter?

And what should I learn next?

7 Responses

Did you set the LHOST to your public IP when generating the payload?

I have set my payloads LHOST to be my public and the listener to be 192.168.1.10. What's next?

I also have read about setting up a VPS. I am confused now and I do not know what I have done correctly. In my Verizon settings,

I clicked port toward, and specify IP as my victims public with port 445. Help?

No, you need to set the options to your local IP and selected port.

So to recap:

I set my IP to be static thru Control Panel.
I access my Verizon router's settings thru Default Gateway: 192.168.1.1
I go to Firewall Settings/Port Forwarding, and specify my IP as 192.168.1.10, and the port to be open as 4444.
I go to my Kali VM. I set a msfpayload with meterpreter with my LHOST as my Public IP
I open msfconsole, and set up a listener with the meterpreter payload, with the LHOST as 192.168.1.10, or my local IP and my LPORT as the port I port forwarded, aka 4444.
I exploit, and when .exe payload is opened, I start a meterpreter session.

Is that correct? Is there anything else I need to add?

Thanks for the advice! I have been getting quite confused after reading about networks, and watching stuff on YT.

If you did it correctly, that should be all. :)

But when you are starting the listener, use your own internal IP then the router would know who to forward to in the network but the payload needs your external / public IP because its is looking for your machine on a different network.

Yup, think of it as finding a house. You first need the city address (public IP), but you then need to find one house in the city with a different address (local IP). Make sense, Alan?

Share Your Thoughts