Binding to local virtual address problem.

[hdm at metasploit.com (H D Moore)]

The LHOST parameter does not result in the listener binding to that just 
that interface - it still binds to 0.0.0.0. The LHOST parameter is used 
to configure the payload's connect-back address, it has nothing to do 
with the local interface for the handler. We can't change this behavior, 
because LHOST isn't always a local interface address, it can be an 
external address that forwards the port back to the attacking system. If 
you can think of a solution to this that makes sense for both situations 
(virtual interfaces with other services bound and attacking from behind a 
NAT gateway), I would be interested in hearing about it.

-HD

On Thursday 29 December 2005 21:47, rrecaba at usb.ve wrote:
> So I have only one app bound to one virtual address port 1863, and
> nothing bound to port 4321 on any address. The framework seems to try
> to local bind to ALL IP addresses even though i am specifying only one
> with LHOST and LPORT. 
>
> What am i doing wrong??
>
> Any help would be greatly appreciated.