July 2001 - SUSE Proxy Suite - openSUSE Mailing Lists

Help: Transparent
by Robert Rottscholl 13 Jul '01

13 Jul '01

Hi, Now i have set up the config file like descirbed in the mini howto, but if I want to connect to any address over the proxy an error occurs: 501- Destination address unknown. I have kernel 2.4.5 and i redirected all trafic to ftp-proxy (via iptbales). Do I have to recompile the source to enable transparency? Doesn't work the binary distribution? Thanks? Robert Rottscholl Maurerweg 11 72116 Moessingen - DE Tel: 00497473-1245

1 0

new direction - telnet proxy
by Student Learner 12 Jul '01

12 Jul '01

Hi all, I found the ftp-proxy suite while doing a search on google, and it's proved a perfect match for my test lab. However, I'm thinking of extending its capabilities to also be a transparent telnet proxy. most of the telnet proxies I've come across are not transparent - the user always logs into the box first, and then needs to issue a connect stmt. Has anyone already modified the code to allow the Ftp-suite to act as a telnet proxy? OR Does anyone know of a product out there that acts as a transparent telnet proxy? (I'm trying to avoid using an entry in the user's .profile that automatically calls telnet/rlogin). Would appreciate ideas. Danke! __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/

1 0

Help in Compiling
by Michels, Gustavo [EES/BR] 12 Jul '01

12 Jul '01

Hi, I am quite new to linux and I am trying to set up a ftp proxy on a RH 7.0 box, running kernel version 2.4.5, so any help would be much appreciated. Here is what I have done so far: ./configure --enable-proc-mods --enable-so-linger --enable-rfc1579 Configuration is ok, next I run make and get the following output: ::::::::::::: make 'all' in ./doc make[1]: Entering directory `/home/src/proxy-suite-1.7/doc' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/src/proxy-suite-1.7/doc' ::::::::::::: make 'all' in ./common make[1]: Entering directory `/home/src/proxy-suite-1.7/common' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/src/proxy-suite-1.7/common' ::::::::::::: make 'all' in ./ftp-proxy make[1]: Entering directory `/home/src/proxy-suite-1.7/ftp-proxy' gcc -g -O2 -c -I. -I.. -I../common ftp-cmds.c ftp-cmds.c: In function `cmds_user': ftp-cmds.c:374: structure has no member named `regex' ftp-cmds.c:376: structure has no member named `regex' ftp-cmds.c:376: warning: assignment makes pointer from integer without a cast make[1]: *** [ftp-cmds.o] Error 1 make[1]: Leaving directory `/home/src/proxy-suite-1.7/ftp-proxy' make: *** [all] Error 1 The error has something to do with RegEx and I am not very known to this. I know there is an option called --with-regex[=PATH] but I don't have a clue what this path would be. Anyone would know how to help me? If you need more info on my linux system, just ask what you need to know. Regards Gustavo Michels Emerson Energy Systems IS/IT Operations +55 11 3145-3706 gustavo.michels(a)emersonenergy.com

2 1

Help: Transparent
by Robert Rottscholl 11 Jul '01

11 Jul '01

Hi, Is it possible to make the ftp - proxy fully transparent (like you can do with squid)? And if it is how does it work? Thanks? Robert Rottscholl Maurerweg 11 72116 Moessingen - DE Tel: 00497473-1245

1 0

Question about ftp - proxy
by mdeflorio＠cajval.sba.com.ar 11 Jul '01

11 Jul '01

Hi, How can i configure the ftp - proxy to assign one user to one re-direct address ? I add the following line: [rootadm] DestinationAddress d2500 but, not work properly. thanks. Marcelo Pablo De Florio Asistencia Técnica Caja de Valores S.A Tel: 4317-8900 int 8359

1 0

sss
by Thomas Demmel 09 Jul '01

09 Jul '01

unsubscribe demmel(a)dji.de

1 0

Re: [proxy-suite] 2 Problems: transparent mode and iptables, chroot with non root
by "Daniel Erdös" 03 Jul '01

03 Jul '01

Hi Antoniu-George, thank you for your answer. 1) Problem with transparent mode >What's your 'DestinationAddress' in the configuration file? I tried to use it without 'DestinationAddress' as it is written in the TRANSPARENT_PROXY.txt. When I use 'DestinationAddress' I can transparently connect to this server but connection to other servers fails I mean it doesn't work transparent. I would be great to have transparent outbound connections. 2) Problem with chroot >Its prety basic. The chrooted directory must be owned by the user under which the >ftp-proxy runs. Also, better be sure that the '/var/ftp-proxy/rundir' exists. >(mkdir -p /var/ftp-proxy/rundir) The directory exists and everything in /var/ftp-proxy/ and all subdirs is owned by the user ftpproxy (and group nogroup). I created the directories automatically as it is written in ftp-proxy-chroot.txt (with SuSE's script) and did a chown -R ftpproxy:nogroup /var/ftp-proxy/. >> (chroot with user root works fine.) >> >> Of course only root has the rights to do chroot(). Maybe it might be possible to >> set the uid just after the chroot() command. >> > >It is done already. Well, than it seems that I have another problem. >Send your configuration file also if this won't help you. Here is my configuration file (I stripped most of the comments :-) ------------------------------------------------------------------------------------------------------------------------------------------------> [-Global-] ActiveMinDataPort 40000 ActiveMaxDataPort 40001 AllowMagicUser yes AllowTransProxy yes DestinationAddress 192.168.202.4 #DestinationTransferMode client #DestinationTransferMode passive DestinationTransferMode active Group nogroup Listen 192.168.128.224 LogDestination /var/log/ftp-proxy.log MaxClients 64 PassiveMinDataPort 41000 PassiveMaxDataPort 41999 Port 1088 #SameAddress yes ServerRoot /var/ftp-proxy/rundir ServerType standalone User ftpproxy WelcomeMessage /etc/proxy-suite/ftp-welcome.txt <------------------------------------------------------------------------------------------------------------------------------------------------ Here is a strace output of the ftp-proxy: select(5, [4], [], NULL, {47, 270000} ) = 1 (in [4], left {38, 190000}) accept(4, {sin_family=AF_INET, sin_port=htons(32881), sin_addr=inet_addr("192.168.128.251")}}, [16]) = 5 setsockopt(5, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 setsockopt(5, SOL_SOCKET, SO_LINGER, [1], 8) = 0 setsockopt(5, SOL_SOCKET, SO_OOBINLINE, [1], 4) = 0 setsockopt(5, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0 setsockopt(5, SOL_IP, IP_TOS, [16], 4) = 0 getpeername(5, {sin_family=AF_INET, sin_port=htons(32881), sin_addr=inet_addr("192.168.128.251")}}, [16]) = 0 time(NULL) = 994170890 fork() = 5676 --- SIGCHLD (Child exited) --- wait4(-1, [WIFEXITED(s) && WEXITSTATUS(s) == 1], WNOHANG, NULL) = 5676 wait4(-1, 0xbfffec58, WNOHANG, NULL) = -1 ECHILD (No child processes) rt_sigaction(SIGCHLD, {0x804a870, [CHLD], SA_RESTART|0x4000000}, {0x804a870, [CHLD], SA_RESTART|0x4000000}, 8) = 0 sigreturn() = ? (mask now []) close(5) = 0 select(5, [4], [], NULL, {60, 0} I hope anybody can help. Regards Daniel

1 0

Re: [proxy-suite] Can't compile ftp-proxy under Suse 7.2
by "Daniel Erdös" 03 Jul '01

03 Jul '01

Hi Marius, >Use configure switches from spec file (from source-rpm in zq-series or in >ftp://ftp.suse.com/pub/projects/proxy-suite/suse/i386/7.2/proxy-suite.spec >don't forget aclocal ; autoheader ; autoconf! Thx this works fine. Gruß Daniel

1 0

2 Problems: transparent mode and iptables, chroot with non root
by "Daniel Erdös" 03 Jul '01

03 Jul '01

I have 2 problems using ftp-proxy (I tried 1.7tp5 - 1.7tp7) under Suse 7.2 1) Transparent proxying does not work. I used the following iptables command: iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 21 -j REDIRECT --to-port 2121 The ftp-proxy listens to 2121. When the client tries to connect in transparent mode the proxy closes the connection after I enter the login name. This is the corresponding log message: TECH-ERR can't eval DestAddr for [client ip address] I tried to set a listen address and TranslatedAddress (TranslatedAddress 0.0.0.0) but it dosn't help. Is it generally possible doing transparency with ftp-proxy and iptables or does it just works with ipchains? (Non transparent mode works fine.) 2) When I configure a chroot environment I cannot configure the proxy to use a non privileged user. I get the following error in the log file: TECH-ERR can't chroot to '/var/ftp-proxy/rundir' (chroot with user root works fine.) Of course only root has the rights to do chroot(). Maybe it might be possible to set the uid just after the chroot() command. Any ideas? TIA Daniel

1 0

Can't compile ftp-proxy under Suse 7.2
by "Daniel Erdös" 03 Jul '01

03 Jul '01

Hi! I have some problems to compile ftp-proxy 1.7 (1.7.p7). I use Suse 7.2 with kernel 2.4.4. When I first tried : ./configure --with-regex make I got an output that said to delete some includes in proc_ftp.c and to change the makefile. I deleted the specified includes and changed the Makefile in the ./ftp-proxy directory to include the right files from the new kernel. Here are the corresponding lines: proc_ftp.o: proc_ftp.c $(CC) -g -O2 -c -I. -I.. -I/lib/modules/2.4.4-4GB/build/include $< But make still gives many warnings and errors (please see below). Surely I did something wrong. Please give me a more exact help on install under Suse 7.2. I have the originally installed glibc-2.2.2-38 and gcc-2.95.3-52. Any hints? TIA Regards Daniel ---------------------------------------------------------------------------------------------------------------------------------------------------------- falcon1:/usr/src/packages/SOURCES/proxy-suite-1.7 # make ::::::::::::: make 'all' in ./doc make[1]: Entering directory `/usr/src/packages/SOURCES/proxy-suite-1.7/doc' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/packages/SOURCES/proxy-suite-1.7/doc' ::::::::::::: make 'all' in ./common make[1]: Entering directory `/usr/src/packages/SOURCES/proxy-suite-1.7/common' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/src/packages/SOURCES/proxy-suite-1.7/common' ::::::::::::: make 'all' in ./ftp-proxy make[1]: Entering directory `/usr/src/packages/SOURCES/proxy-suite-1.7/ftp-proxy' gcc -g -O2 -c -I. -I.. -I/lib/modules/2.4.4-4GB/build/include proc_ftp.c proc_ftp.c:84: warning: `struct file' declared inside parameter list proc_ftp.c:84: warning: its scope is only this definition or declaration, which is probably not what you want. proc_ftp.c:84: warning: `struct inode' declared inside parameter list proc_ftp.c:86: warning: `struct file' declared inside parameter list proc_ftp.c:86: warning: `struct inode' declared inside parameter list proc_ftp.c:132: variable `proc_ftp_operations' has initializer but incomplete type proc_ftp.c:133: warning: excess elements in struct initializer proc_ftp.c:133: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:134: warning: excess elements in struct initializer proc_ftp.c:134: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:135: warning: excess elements in struct initializer proc_ftp.c:135: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:136: warning: excess elements in struct initializer proc_ftp.c:136: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:137: warning: excess elements in struct initializer proc_ftp.c:137: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:138: warning: excess elements in struct initializer proc_ftp.c:138: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:139: warning: excess elements in struct initializer proc_ftp.c:139: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:140: warning: excess elements in struct initializer proc_ftp.c:140: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:141: warning: excess elements in struct initializer proc_ftp.c:141: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:142: warning: excess elements in struct initializer proc_ftp.c:142: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:143: warning: excess elements in struct initializer proc_ftp.c:143: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:144: warning: excess elements in struct initializer proc_ftp.c:144: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:145: warning: excess elements in struct initializer proc_ftp.c:145: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:146: warning: excess elements in struct initializer proc_ftp.c:146: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:147: warning: excess elements in struct initializer proc_ftp.c:147: warning: (near initialization for `proc_ftp_operations') proc_ftp.c:150: variable `proc_ftp_inode_operations' has initializer but incomplete type proc_ftp.c:151: warning: excess elements in struct initializer proc_ftp.c:151: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:152: warning: excess elements in struct initializer proc_ftp.c:152: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:153: warning: excess elements in struct initializer proc_ftp.c:153: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:154: warning: excess elements in struct initializer proc_ftp.c:154: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:155: warning: excess elements in struct initializer proc_ftp.c:155: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:156: warning: excess elements in struct initializer proc_ftp.c:156: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:157: warning: excess elements in struct initializer proc_ftp.c:157: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:158: warning: excess elements in struct initializer proc_ftp.c:158: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:159: warning: excess elements in struct initializer proc_ftp.c:159: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:160: warning: excess elements in struct initializer proc_ftp.c:160: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:161: warning: excess elements in struct initializer proc_ftp.c:161: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:162: warning: excess elements in struct initializer proc_ftp.c:162: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:163: warning: excess elements in struct initializer proc_ftp.c:163: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:164: warning: excess elements in struct initializer proc_ftp.c:164: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:165: warning: excess elements in struct initializer proc_ftp.c:165: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:166: warning: excess elements in struct initializer proc_ftp.c:166: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:167: warning: excess elements in struct initializer proc_ftp.c:167: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:168: warning: excess elements in struct initializer proc_ftp.c:168: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:169: warning: excess elements in struct initializer proc_ftp.c:169: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:170: warning: excess elements in struct initializer proc_ftp.c:170: warning: (near initialization for `proc_ftp_inode_operations') proc_ftp.c:173: variable `proc_ftp' has initializer but incomplete type proc_ftp.c:174: warning: excess elements in struct initializer proc_ftp.c:174: warning: (near initialization for `proc_ftp') proc_ftp.c:174: warning: excess elements in struct initializer proc_ftp.c:174: warning: (near initialization for `proc_ftp') proc_ftp.c:174: warning: excess elements in struct initializer proc_ftp.c:174: warning: (near initialization for `proc_ftp') proc_ftp.c:175: `S_IFREG' undeclared here (not in a function) proc_ftp.c:175: `S_IRUSR' undeclared here (not in a function) proc_ftp.c:175: `S_IWUSR' undeclared here (not in a function) proc_ftp.c:175: warning: excess elements in struct initializer proc_ftp.c:175: warning: (near initialization for `proc_ftp') proc_ftp.c:175: warning: excess elements in struct initializer proc_ftp.c:175: warning: (near initialization for `proc_ftp') proc_ftp.c:175: warning: excess elements in struct initializer proc_ftp.c:175: warning: (near initialization for `proc_ftp') proc_ftp.c:175: warning: excess elements in struct initializer proc_ftp.c:175: warning: (near initialization for `proc_ftp') proc_ftp.c:176: warning: excess elements in struct initializer proc_ftp.c:176: warning: (near initialization for `proc_ftp') proc_ftp.c:176: warning: excess elements in struct initializer proc_ftp.c:176: warning: (near initialization for `proc_ftp') proc_ftp.c:177: warning: excess elements in struct initializer proc_ftp.c:177: warning: (near initialization for `proc_ftp') proc_ftp.c:177: warning: excess elements in struct initializer proc_ftp.c:177: warning: (near initialization for `proc_ftp') proc_ftp.c:178: warning: excess elements in struct initializer proc_ftp.c:178: warning: (near initialization for `proc_ftp') proc_ftp.c:179: warning: excess elements in struct initializer proc_ftp.c:179: warning: (near initialization for `proc_ftp') proc_ftp.c:179: warning: excess elements in struct initializer proc_ftp.c:179: warning: (near initialization for `proc_ftp') proc_ftp.c:180: warning: excess elements in struct initializer proc_ftp.c:180: warning: (near initialization for `proc_ftp') proc_ftp.c:181: warning: excess elements in struct initializer proc_ftp.c:181: warning: (near initialization for `proc_ftp') proc_ftp.c:181: warning: excess elements in struct initializer proc_ftp.c:181: warning: (near initialization for `proc_ftp') proc_ftp.c:182: warning: excess elements in struct initializer proc_ftp.c:182: warning: (near initialization for `proc_ftp') proc_ftp.c:183: warning: excess elements in struct initializer proc_ftp.c:183: warning: (near initialization for `proc_ftp') proc_ftp.c:183: warning: excess elements in struct initializer proc_ftp.c:183: warning: (near initialization for `proc_ftp') proc_ftp.c:204: warning: `struct file' declared inside parameter list proc_ftp.c:204: warning: `struct inode' declared inside parameter list proc_ftp.c:206: conflicting types for `proc_ftp_read' proc_ftp.c:84: previous declaration of `proc_ftp_read' proc_ftp.c:239: warning: `struct file' declared inside parameter list proc_ftp.c:239: warning: `struct inode' declared inside parameter list proc_ftp.c:241: conflicting types for `proc_ftp_write' proc_ftp.c:86: previous declaration of `proc_ftp_write' proc_ftp.c: In function `init_module': proc_ftp.c:360: `proc_root' undeclared (first use in this function) proc_ftp.c:360: (Each undeclared identifier is reported only once proc_ftp.c:360: for each function it appears in.) proc_ftp.c:360: dereferencing pointer to incomplete type proc_ftp.c:361: dereferencing pointer to incomplete type proc_ftp.c:370: dereferencing pointer to incomplete type proc_ftp.c:370: dereferencing pointer to incomplete type proc_ftp.c:371: dereferencing pointer to incomplete type proc_ftp.c: In function `cleanup_module': proc_ftp.c:402: invalid use of undefined type `struct proc_dir_entry' proc_ftp.c:403: invalid use of undefined type `struct proc_dir_entry' proc_ftp.c:403: invalid use of undefined type `struct proc_dir_entry' proc_ftp.c:404: invalid use of undefined type `struct proc_dir_entry' make[1]: *** [proc_ftp.o] Error 1 make[1]: Leaving directory `/usr/src/packages/SOURCES/proxy-suite-1.7/ftp-proxy' make: *** [all] Error 1

2 1