Andre Oliveira wrote:
>
> [my service]
> only allows me top connect to internet via SOCKS Client using port 1080 (TCP).
>
> The nortel IPSEC Client uses the following ports:
>
> - UDP 500 / TCP 17 (isa kmp/oakley);
> - TCP 50 (ipsec esp).
Nope. Not "TCP", "IP"!
More specifically, IP protocol number 50 (NOT a port number!).
> I've tried to include this ports ons the socks client configuration, but didn't
> worked.
I somehow doubt that you'll get this to work through the socks connection
since IPsec implementations like to sit on a really low level in the
protocol
stack. (probably below your socks client).
Also, IPsec (normally) cannot be address translated, which is exactly
what happens in a socks scenario, so that'd _also_ break functionality.
My advice is to start looking for a different kind of connection,
preferably one including at least one public IP address.
--
Mikael Olsson, EnterNet Sweden AB, Box 393, SE-891 28 �RNSK�LDSVIK
Phone: +46-(0)660-29 92 00 Fax: +46-(0)660-122 50
Mobile: +46-(0)70-66 77 636
WWW: http://www.enternet.se E-mail: [EMAIL PROTECTED]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
