Package: socks4-server
Version: 4.3.beta2-13
Severity: important
My machine has several tun-interfaces (OpenVPN) and an ethernet
interface.
I want sockd to use "lan" (eth0, 10.66.53.146) for inside traffic and
tun4 (172.16.0.3) for outside traffic. I have no sockd.fr (but
generating one doesn't hel). My sockd.route is
10.66.53.146 10.66.0.0 255.255.0.0
172.16.0.3 0.0.0.0 0.0.0.0
Removing the line with "10.66.53.146" doesn't help. Sockd never uses
172.16.0.3
I use policy based routing. My default route uses the "lan"-interface.
My special routing table for tun4 and the rule is:
james:~# ip ro ls table tun4.out
default dev tun4 scope link
james:~# ip rul ls
0: from all lookup local
32764: from 172.16.0.3 lookup tun4.out
[other rules]
32766: from all lookup main
32767: from all lookup default
So binding sockd to use 172.16.0.3 as outgoing address should do the
trick. But sockd seems not to use sockd.route although strace tells me
that the file is opened.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages socks4-server depends on:
ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii libident 0.22-3 simple RFC1413 client library - ru
ii libsocks4 4.3.beta2-13 SOCKS libraries
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
