But why shouldn't I be able...

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #106,361 by bepatient 6/17/03 5:10:28 PM Reply	But why shouldn't I be able... ...to say I want to send traffic from port x here and connect to port y there? That is what I want to do...even if it isn't possible;-) If you push something hard enough, it will fall over. _{Fudd's First Law of Opposition} [link\|mailto:bepatient@aol.com\|BePatient]
Post #106,389 by tseliot 6/17/03 7:30:14 PM Reply	You are saying that. ...but your firewall admins have determined your particular connection is a no-no. My guess is they wanted to block incoming traffic on port 22, and just blocked it all because it was easier. Ask them...? Many fears are born of stupidity and ignorance - Which you should be feeding with rumour and generalisation. BOfH, 2002 "Episode" 10
Post #106,391 by pwhysall 6/17/03 7:48:19 PM Reply	man netcat Peter [link\|http://www.debian.org\|Shill For Hire] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Blog]

SSH question. - (bepatient) - (10) - June 17, 2003, 02:39:14 PM EDT

I would say: - (folkert) - (7) - June 17, 2003, 02:55:25 PM EDT

Okay. - (folkert) - (6) - June 17, 2003, 03:01:21 PM EDT

So the real answer is... - (bepatient) - (5) - June 17, 2003, 03:19:42 PM EDT

That's why they close ports - (drewk) - (4) - June 17, 2003, 04:46:32 PM EDT

But why shouldn't I be able... - (bepatient) - (2) - June 17, 2003, 05:10:28 PM EDT

You are saying that. - (tseliot) - June 17, 2003, 07:30:14 PM EDT

man netcat -NT - (pwhysall) - June 17, 2003, 07:48:19 PM EDT

You are right about that, but unfortunately... - (ben_tilly) - June 21, 2003, 05:26:37 PM EDT

have the server listen on 23 or wherever - (boxley) - June 17, 2003, 03:02:07 PM EDT

Several methods - (kmself) - June 22, 2003, 01:17:25 AM EDT

Who sliced the cheddar?
57 ms