> In my company every connection to the INTERNET must be "sockfied"
> (socks4 ou sock5) and sent to a maquine (which I will call
> "the.sock.machine") on port 1080. This machine listens on port 1080 for
> "sockfied" packets and filters then according to some rules. It's import
> to state that the connections to the internal network don't need to be
> "sockfied".
>
> In my Java application I have to open a connection to an external
> URL. At first, I used the java "new Socket" command and had no success.
> The the package reached "the.sock.machine" but NOT on port 1080.
>
> I did some research on the Web an found a "solution" :
>
> System.getProperties().setProperty("socksProxySet", "true");
> System.getProperties().setProperty("socksProxyHost",
> "the.sock.machine");
> System.getProperties().setProperty("socksProxyPort", "1080") ;
>
>
> It worked fine , until I discover that this was interfering in my
> other internal connections. I mean, after this commands, ALL my sockets
> connection where redirected to the "the.sock.machine" on port 1080. I dont
> want this behavour !
>
> What I wanted is that a specif connection, to a specif IP address,
> be "sockfied". I dont want that ALL sockets to be "sockfied", only some,
> depending on the address. I concluded that the previous commands affected
> the JVM as a hole.
>
> Has someone faced this problem before ? Is there an additional
> command that can let me specify a group of machines to which the JVM
> should "sockfy" the packets (maybe
> System.getProperties().setProperty("socksProxyMask", "200.233.0.0")) ?
>
> Thanks ,
>
> jk
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
