[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Really strange interface behavior
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Really strange interface behavior
- From: coderman <coderman@xxxxxxxxx>
- Date: Sun, 4 Feb 2007 20:31:00 -0800
- Cc: or-talk@xxxxxxxx
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Sun, 04 Feb 2007 23:31:29 -0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RkipsfOTgkVgOOydRceXGJIaNdVbUvQo5ZcAx3xpNEJQ0LeP1bugyQGkNfggZV/isOUNBlyeagRbe9YWMlmqe/SR+mdFMLyUbiPIyw8R/G5zu5QCb4wx0pzX+sUlx76NBkh9BGN2r/16nvyLG8iDgGZEFS8AfqA6UOIgZOFUs0w=
- In-reply-to: <45C6B097.4010201@glaves.org>
- References: <45C6B097.4010201@glaves.org>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On 2/4/07, Matt Glaves <matt@xxxxxxxxxx> wrote:
...
Eth0: New TOR Interface (216.9.65.50). This was previously a
subinterface aka eth1:1
Eth1: Webserver/Mailserver/etc Interface - This is a separate
netblock/vlan. Call it 216.9.100.100 for this example.
...
Although netstat only shows TOR connections on the 216.9.65.50 address
and zero listening/open connections on 216.9.100.100 (other than the
listening web/email processes) my traffic is being split between the
interfaces.
let me guess, eth1 is default route, and if you look at outgoing Tor
packets the source address is correctly "216.9.65.50".
you can maybe fix via iproute2 and policy based routing (may also need
netfilter hooks).
best regards,