Re: [leaf-user] shorewall: dnat through `well known ports' ???

2005-10-22 Thread Michael D Schleif
Tom => * Tom Eastep <[EMAIL PROTECTED]> [2005:10:22:10:57:37-0700] scribed: > On Saturday 22 October 2005 10:28, Tom Eastep wrote: > > On Saturday 22 October 2005 06:39, Michael D Schleif wrote: > > > Tested Scenarios > > > > > > I. When I do this: > > > > > > DNAT net loc:$

Re: [leaf-user] shorewall: dnat through `well known ports' ???

2005-10-22 Thread Tom Eastep
On Saturday 22 October 2005 10:28, Tom Eastep wrote: > On Saturday 22 October 2005 06:39, Michael D Schleif wrote: > > Tested Scenarios > > > > I. When I do this: > > > > DNAT net loc:$A:22 tcp 60022 > > > > then, I can successfully ssh from [C] to [A]; but, the proxy at [B

Re: [leaf-user] shorewall: dnat through `well known ports' ???

2005-10-22 Thread Tom Eastep
On Saturday 22 October 2005 06:39, Michael D Schleif wrote: > > Tested Scenarios > > I. When I do this: > > DNAT net loc:$A:22 tcp 60022 > > then, I can successfully ssh from [C] to [A]; but, the proxy at [B] > prevents ssh from [B] to [A]. > > II. When I do this: > >

[leaf-user] shorewall: dnat through `well known ports' ???

2005-10-22 Thread Michael D Schleif
I need to make regular ssh connections to a host behind a Bering-uclibc firewall/router. Normally, this is _not_ a problem. In one case, described herein, special circumstances obtain; and I need advice on how to best deal with the situation. Basic Specifications Destination