Forum Discussion
Steve_Magnuson_
Nimbostratus
NimbostratusHow can I force the LTM SOCKS Service to send connect requests out a specific interface?
Hello,
I've set up an LTM running 11.6 to act as an stunnel server (see stunnel.org). A client on the Internet is configured as an stunnel client. The stunnel client is listening on TCP port 1080...
Brad_Parker_139
Nacreous
NacreousRather than an additional route domain you should consider using the
nexthopBrad_Parker_139Nacreous
NacreousYou could try setting a variable and use that to set the nexthop in SERVER_CONNECTED.
when SOCKS_REQUEST {
if { [class match [SOCKS::destination] ends_with SOCKS_whitelist] } {
log -noname local6.notice "[virtual name]: SOCKS request from client at [IP::remote_addr] for host [SOCKS::destination] allowed"
set socksAllowed 1
SOCKS::allowed 1
} else {
log -noname local6.warning "[virtual name]: SOCKS request from client at [IP::remote_addr] for host [SOCKS::destination] blocked"
set socksAllowed 1
SOCKS::allowed 0
}
}
when SERVER_CONNECTED {
if { $socksAllowed }{
nexthop destination
}
}
