/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Hey, it worked! Not only did it work, but it makes a lot of sense! I
simply put the following in my socks5.conf:
interface 192.168.0. - eth0
and now my ICQ stuff is actually coming from eth0 instead of eth0:2.
Thanks to everyone who helped with this!
Craig
On Wed, 19 Jan 2000, Fuzzy Fox wrote:
> 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.
