Rob Landley wrote:
> On Thursday 30 October 2008 20:17:04 Ming-Ching Tiew wrote:
>> Ming-Ching Tiew wrote:
>>> Matt Johnston wrote:
On Thu, Oct 30, 2008 at 02:37:44PM +0100, Michael Wiedmann wrote:
> Hi,
>
> how deals dropbear with different clients which are requesting
> each
On Thursday 30 October 2008 20:17:04 Ming-Ching Tiew wrote:
> Ming-Ching Tiew wrote:
> > Matt Johnston wrote:
> >> On Thu, Oct 30, 2008 at 02:37:44PM +0100, Michael Wiedmann wrote:
> >>> Hi,
> >>>
> >>> how deals dropbear with different clients which are requesting each
> >>> a remote port forwardi
Ming-Ching Tiew wrote:
> Matt Johnston wrote:
>> On Thu, Oct 30, 2008 at 02:37:44PM +0100, Michael Wiedmann wrote:
>>> Hi,
>>>
>>> how deals dropbear with different clients which are requesting each
>>> a remote port forwarding to the same local port (on the server
>>> side), e.g.
>>>
>>> system-
Matt Johnston wrote:
> On Thu, Oct 30, 2008 at 02:37:44PM +0100, Michael Wiedmann wrote:
>> Hi,
>>
>> how deals dropbear with different clients which are requesting each
>> a remote port forwarding to the same local port (on the server
>> side), e.g.
>>
>> system-1> dbclient -l user1 -N -R
On Thu, Oct 30, 2008 at 02:37:44PM +0100, Michael Wiedmann wrote:
> Hi,
>
> how deals dropbear with different clients which are requesting each a remote
> port forwarding to the same local port (on the server side), e.g.
>
> system-1> dbclient -l user1 -N -R :client-ip-1:80 server-ip
> ...
>
Hi,
how deals dropbear with different clients which are requesting each a remote
port forwarding to the same local port (on the server side), e.g.
system-1> dbclient -l user1 -N -R :client-ip-1:80 server-ip
...
system-2> dbclient -l user2 -N -R :client-ip-2:80 server-ip
Doing a quick te
