/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Craig Baird <[EMAIL PROTECTED]> wrote:
>
> eth1 and eth2 are networks being masq'ed. The external IP address
> should be 192.168.0.3 (eth0), but for some reason it's using
> 192.168.0.34 (eth0:2).
Hmm. Actually, when you simply bind a socket, and direct it towards the
Interenet, what IP address do you expect to be used as the source
address? There is some ambiguity, as all of the interfaces are capable
of reaching the Net. This is probably what SOCKS is doing; just doing a
wildcard bind, and letting the OS choose the outgoing IP address.
> I think that this is a socks5 issue.
You could probably get the results you want by specifying particular
interfaces for the SOCKS daemon to bind to. Check socks5.conf(5), in
the "INTERFACE ENTRIES" section.
Send me some E-mail if you have trouble with it; I'm experimenting myself.
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience.
sometimes known as David DeSimone || Experience comes from bad judgment."
http://www.dallas.net/~fox/ || -- Life Lessons
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
