[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#401992: marked as done (socks4-server: fails to use address of tun-interface for outgoing connections on multi-homed host)

Your message dated Tue, 28 Jan 2020 06:56:44 +0000
with message-id <[🔎] E1iwKnk-0006sb-48@fasolo.debian.org>
and subject line Bug#949632: Removed package(s) from unstable
has caused the Debian Bug report #401992,
regarding socks4-server: fails to use address of tun-interface for outgoing connections on multi-homed host
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
401992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401992
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (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

--- End Message ---
--- Begin Message --- 
Version: 4.3.beta2-20+rm

Dear submitter,

as the package socks4-server has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/949632

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: