September 2001 - SUSE Proxy Suite - openSUSE Mailing Lists

ftp-proxy over M$-Proxy ?
by Peter Zabelt 28 Sep '01

28 Sep '01

Hallo Group! Meanwhile my ftp-Proxy from the proxy-suite is running well! :-) I've built up a construction like this (of course only for testing!): -----<ftp-proxy Nr.1>---------<ftp-proxy Nr.2>----------<squid-proxy>--INET In textform: I go from my intranet over the local ftp-proxy Nr.1 over a crossed patchcable to an (also local) ftp-proxy Nr.2 and than via ippp0 to the squid-proxy of my provider and all ftp-traffic is running fine! :-))) But the real thing is, that I have to connect from the output of ftp-proxy Nr.1 to a M$-ISA-Proxy!!! :-((( I don't know anything about this type of Proxy, because it's away from me and I'm not the administrator of it! In the ftp-proxy.log there appears the contact from my ftp-proxy to the M$-ISA-Proxy but there comes no reaction from the 'parent' ISA-proxy. Only a timeout! Can anybody help me, please? Thank you! Peter.

1 0

AW: [proxy-suite] Wrong Answer from FTP-Proxy
by Roloff, Dirk 28 Sep '01

28 Sep '01

Hi Marius, hi all, year, got it - was a hard work, but i figuered out the problem after i was able to compile it on my mashine. At the end you will find a patchfile. My first problem was to compile the source 1.7p8 on a Suse 6.4 Kernel 2.2.19 and gcc 2.95.3 20010315 (release). gcc -g -O2 -c -I. -I.. proc_ftp.c In file included from /usr/include/linux/sched.h:13, from /usr/include/linux/mm.h:4, from /usr/include/linux/slab.h:14, from /usr/include/linux/malloc.h:4, from proc_ftp.c:44: /usr/include/linux/times.h:5: parse error before `clock_t' ... and pages of more errors a -I/usr/src/linux/include or a line #define _LOOSE_KERNEL_NAMES just befor #include <linux/malloc.h> in proc_ftp.c will fix this. The problem here is that this compiler brings a new asm/posix_types.h which includes #include <features.h> and this will define __KERNEL_STRICT_NAMES. But in linux/types.h clock_t will only be defined if __KERNEL_STRICT_NAMES is NOT defiend. I am not sure what's going on here. So it looks like it is not the Suse 6.4 more the new gcc. Ok but now the problem with the strange server response 220 you know ? The problem could not be that we get more then one Welcome Message Line - Just have a look at ftp.suse.com it sends about 20 lines of 220-Wellcome .... and works of cause withe the proxy. a look in the debug output : (xxx replaces ip-adresses or hostnames etc. ) 13:17:05 < 5285> FD_SET Srv-Ctrl for R 13:17:05 < 5285> FD_SET Cli-Ctrl for R 13:17:05 < 5285> alloc 56 (com-socket.c:989): 0x8067608 13:17:05 < 5285> ll_read Srv-Ctrl 4=xx.xxx.xxx.xxx: 32 bytes 13:17:05 < 5285> client-loop ... 13:17:05 < 5285> gets Srv-Ctrl 4=xx.xxx.xxx.xxx: 19 bytes '220- XXX FTP-Server' 13:17:05 < 5285> from Server-PI (4): '220- XXX FTP-Server' 13:17:05 < 5285> client-loop ... 13:17:05 < 5285> free 0x8067608 (com-socket.c:547) 13:17:05 < 5285> gets Srv-Ctrl 4=62.225.156.157: 11 bytes '220 hinterp' 13:17:05 < 5285> from Server-PI (4): '220 hinterp' hmmm .. HighLevelSocket reads 32 Bytes ... 19 Bytes first Wellcome Line will be processed correct next 11 Bytes is the start of the second 220-Wellcome msg but just the start - the rest will be get by next recv() call. But this will not recognize it as 220- line because it dosen't start with 220 :-(. So if there is a buffer but it dosent has an end-of-line we just put it back in the list and set a switch readmore. So in next loop wie will select on all sockets again (even if there is a buffer in HLS). And try to proceed again. Ok please just have a look at the patch, if you have more questions - ask. I tried it at the ftp-back server, an wonder wonder it works. What will you do with the free time at the weekend now ? :-))) Thanks for your help and let me know if you agree with the source. Best regards Dirk Roloff Patch follows: > -------------------------------SCHNIP------------------------------ --- common/com-socket.c +++ common/com-socket.c Fri Sep 28 15:49:05 2001 @@ -371,8 +371,9 @@ memset(hls->peer, 0, sizeof(hls->peer)); } hls->kill = 0; + hls->readmore = 0; hls->flag = 0; hls->ctyp = "???-????"; hls->wbuf = NULL; @@ -540,13 +541,30 @@ /* ** Transfer at most one line of data */ + hls->readmore = 0; /* D.ROLOFF reset flag */ for (buf = hls->rbuf, cnt = 0; buf != NULL && cnt < len; ) { if (buf->cur >= buf->len) { hls->rbuf = buf->next; misc_free(FL, buf); - buf = hls->rbuf; + /* buf = hls->rbuf; D.ROLOFF old stuff */ + if(NULL == (buf = hls->rbuf)) + { + /* D.ROLOFF no more data in HighLevel Socket + restore a buffer and exit until more data + avail and end of line (CR/NL) found */ + hls->rbuf = (BUF *) misc_alloc(FL, sizeof(BUF) + cnt); + hls->rbuf->len = cnt; + hls->rbuf->cur = 0; + memcpy(hls->rbuf->dat, ptr, cnt); +#if defined(COMPILE_DEBUG) + debug(2, "gets preread %d Bytes waiting for end-of-line '%.128s'%s", + cnt, hls->rbuf->dat, (cnt > 128) ? "..." : ""); +#endif + hls->readmore = 1; + return NULL; + } continue; } if (buf->dat[buf->cur] == '\r') break; --- common/com-socket.h +++ common/com-socket.h Fri Sep 28 14:44:21 2001 @@ -83,8 +83,9 @@ struct hls_t *next; /* Next one in the chain */ int sock; /* The corresponding socket */ int kill; /* 1=kill socket after send */ int flag; /* Flag for send() (e.g. OOB) */ + int readmore; /* 1=read more if rbuf=!NULL */ u_int32_t addr; /* Peer's address (host order) */ u_int16_t port; /* Peer's port (host order) */ char peer[PEER_LEN]; /* Peer's readable address */ char *ctyp; /* Connection type identifier */ --- ftp-proxy/ftp-client.c +++ ftp-proxy/ftp-client.c Fri Sep 28 15:13:24 2001 @@ -225,12 +225,16 @@ ** if all input has been processed. ** (Data buffers are never split.) */ need = 1; + if (ctx.cli_ctrl && ctx.cli_ctrl->rbuf) need = 0; if (ctx.srv_ctrl && ctx.srv_ctrl->rbuf) need = 0; + if(( ctx.srv_ctrl && ctx.srv_ctrl->readmore!=0 ) || + ( ctx.cli_ctrl && ctx.cli_ctrl->readmore!=0 )) + need = 1; if (need != 0) { if (socket_exec(ctx.timeout, &close_flag) <= 0) break; /* Timed out or worse */ } --- ftp-proxy/proc_ftp.c +++ ftp-proxy/proc_ftp.c Fri Sep 28 12:18:33 2001 @@ -38,8 +38,10 @@ #if !defined(__KERNEL__) # define __KERNEL__ #endif +#define _LOOSE_KERNEL_NAMES + #include <linux/malloc.h> #include <linux/sched.h> #include <linux/kernel.h> #include <linux/fs.h> > -------------------------------SCHNAP------------------------------

1 0

AW: [proxy-suite] Wrong Answer from FTP-Proxy
by Roloff, Dirk 27 Sep '01

27 Sep '01

Hi George, > Indeed is very strange what is happening there. If I understand well, > there are other FTP proxies which are working well, right? If you are The first Part of my posting was the Proxy-output wich has the problem. I have no proxy-installation that work with this back-ftp. As well with hundrets of other back-ftp Server this proxy installation works very well. > connecting from a working FTP proxy to the same back FTP machine, does > it have the same problem? Try to look for strange characters > in the back > FTP server 220 reply. Do this for us: > > 1) Connect on shell on the machine running the FTP proxy > 2) telnet on the port 21 on the same back FTP server > 3) send us the output That was what i did in the second part of my posting. Ok i didnt use telnet but i think netcat will do the same for me. I also piped the output in a file an had a view with hexedit on it. No nonprintable chars in there and all lines ended with 0x0D 0x0A. Here again the output from netcat back-ftp 21: -> 220- XXX FTP-Server -> 220 xxxxxxxxxx.xxx.de FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.16) ready. <- USER someone -> 331 Password: <- QUIT -> 221 Goodbye. Thanks Dirk

2 1

Re: [proxy-suite] time is wrong for ftp-proxy
by Togan Muftuoglu 27 Sep '01

27 Sep '01

Hi * Marius Tomaschewski; <mt(a)suse.de> on 20 Sep, 2001 wrote: > > You have to copy the timezone file as well to the chroot; perhaps > this goes wrong in the script. Here is the output this was created at the time of installation of the proxy-suite /sbin/rcftp-proxy chroot /sbin/rcftp-proxy start sudo ls -l /var/ftp-proxy/rundir/usr/share/zoneinfo total 4 drwxr-xr-x 3 root root 1024 Sep 9 09:36 . drwxr-xr-x 3 root root 1024 Sep 9 09:36 .. drwxr-xr-x 2 root root 1024 Sep 9 09:36 Europe -rw-r--r-- 1 root root 993 Jan 19 2001 Istanbul So what else I need to check TIA -- Togan Muftuoglu

2 2

ldap integration ??
by Student Learner 27 Sep '01

27 Sep '01

Hello List, I'm looking at implementing proxy-suite with ldap integration. can someone specify a sample ftp-proxy.conf file that uses this feature? thanks, student __________________________________________________ Terrorist Attacks on U.S. - How can you help? Donate cash, emergency relief information http://dailynews.yahoo.com/fc/US/Emergency_Information/

2 1

Wrong Answer from FTP-Proxy
by Roloff, Dirk 26 Sep '01

26 Sep '01

Hi , we are using this proxy for our outgoning ftp-trafic and it works fine in inetd-mode. Just with one server we have some strange behavior. First use netcat to our proxy. -> 220 Proxy FTP server (Version 1.5 - 1999/10/04 11:55:39) ready. <- USER someone(a)host.de -> xxx.xxx.de FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.16) ready. -> 331 Password: <- QUIT 221 Goodbye. Just have a look at line 3 after sending user we get a message without number at start of line - This will kill our sending ftp-client. Next step i just do the same directly without proxy. (netcat server 21 ) -> 220- XXX FTP-Server -> 220 xxxxxxxxxx.xxx.de FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.16) ready. <- USER someone -> 331 Password: <- QUIT -> 221 Goodbye. Ahhh looks right (for me) an the misteries line 3 is here the rest of second 220 Line. Has anybody an idea ? I also tried it with the version 1.7 ( dont know witch Patch - but i came from the Suse Update RPM for 6.4) By the way - i try to compile the version 1.7p8 on a Suse 6.4 and get a lot of compiler errors. Have i got a chance to do so ? It looks like some probs with the include files. Thanks for your help Dirk Roloff

2 1

time is wrong for ftp-proxy
by Togan Muftuoglu 19 Sep '01

19 Sep '01

Hi, I am using the ftp-proxy 1.7tp7 running on SuSE 7.1 kernel 2.2.19. Except for the time eveything is fine. I am using Marc's compartment and teh timezone file points correctly to Istanbul so does the ftp-proxy chroot directory has the correct timezone pointing to Istanbul. However the logs show the time -3:00 Hrs behind. in /etc/rc.config GMT="" TIMEZONE="Europe/Istanbul" How can I correct this ? -- Togan Muftuoglu Sep 19 15:59:01 gardiyan /USR/SBIN/CRON[26836]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF connect from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF transparent proxy request to 144.122.166.65:21 from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF 'USER anonymous' dest 144.122.166.65:21 from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF reading data for 'anonymous' from cfg-file Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF 'PASS XXXX' from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-INF 'PWD' from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-WRN unknown 'FEAT' from 192.168.1.3 Sep 19 12:59:09 gardiyan ftp-child[26837]: USER-WRN unknown 'CLNT' from 192.168.1.3 Sep 19 12:59:12 gardiyan ftp-child[26837]: USER-INF PASV set to 192.168.1.2:1904 for 192.168.1.3

1 0

proxy-suite-1.7tp8 avaliable
by Marius Tomaschewski 19 Sep '01

19 Sep '01

Hi *! proxy-suite-1.7tp8 (minor changes) is avaliable on ftp://ftp.suse.com/pub/projects/proxy-suite/src/ * 1.7tp8 / 19.09.2001: - fixed sample run level script to be LSB compliant (I hope it is now) - added Solaris FIONREAD (broken pipe) patch from Stefan Landvoigt MD5 checksum Size Date Time Name 7c3a3aac8918ab3ce5b9ba7a368820de 87758 Sep 19 15:22 CHANGES.mt 15d157ee11d7a5a5358519d1163b59d1 2359 Sep 19 15:22 proxy-suite-1.7tp8.dif de879e5d0c6398fde9970db3c5877fad 170793 Jun 21 13:44 proxy-suite-1.7.tar.gz note, proxy-suite-1.7.tar.gz isn't changed I've done some LSB (Linux System Base) fixes to the sample run- level script and added a patch to avoid "broken pipe" problems with bigger files. The proxy reads the number of bytes via ioctl FIONREAD - solaris returns a "wrong" number of bytes. I've added this patch explicitely for solaris - it doesn't change anything for other platforms, but may be valid in similar form for other systems as well because it seems to be a BSD vs. SysV difference. common/com-socket.c: #if defined (SOLARIS) #include <stropts.h> #include <sys/conf.h> #include <netinet/in_systm.h> #define FIONREAD I_NREAD #endif Thanks again to Stefan Landvoigt for this patch and description. Kind regards, Marius Tomaschewski <mt(a)suse.de> -- SuSE GmbH, Hamburg --- SuSE Labs, Product Developement GPG/PGP public key see: http://www.suse.de/~mt/mt.pgp Key-FP: DF17 271A AD15 006A 5BB9 6C96 CA2F F3F7 373A 1CC0

1 0

DHCP won't start
by peter thesing 19 Sep '01

19 Sep '01

Greetings This is my first mail to this group. I am a newbie at SuSe 7.1. or any other distro. Please picture this. I have 3 pc's at home. 2 of them are window$ boxes 1 is SuSe 7.1. I would like to give both windows pc a ip address wich is not fixed. In NT this is done with a few mouseclicks and a little bit of typing. In Suse it should be done with dhcpd. and weeks of probing the internet. With kcmdhcpd i tried as root to assign address range 192.168.17.2 192.168.17.10 on to eth1 with ip 192.168.17.1/255.255.255.0. When i type in /usr/sbin/dhcpd start it displays the message "192.168.17.2 192.168.17.10 not on net 192.168.17.1/255.255.255.0" What do i do wrong and is there a tool to diagnose & correct this problem. If so where? If someone has a fix for this please email me directly at; peterthesing(a)hotmail.com peter.thesing(a)getronics.com j.thesing(a)chello.nl ps fixed ip-addresses is not my intention or an option

2 1

Re: [proxy-suite] DHCP won't start
by peter thesing 19 Sep '01

19 Sep '01

thanx for your reply i have tried so far (this will be a long list) oot@peter:/usr/sbin > dhcpd eth1 Internet Software Consortium DHCP Server 2.0pl5 Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved. Please contribute if you find this software useful. For info, please visit http://www.isc.org/dhcp-contrib.html Address range 192.168.17.2 to 192.168.17.10 not on net 192.168.17.1/255.255.255.0! exiting. root@peter:/usr/sbin > root@peter:/usr/sbin > ----- Original Message ----- From: "David Kempe" <david(a)solutionsfirst.com.au> To: "peter thesing" <peterthesing(a)hotmail.com>; "Suse Mailinglist" <suse-linux-e(a)suse.com>; <proxy-suite(a)suse.com> Sent: Wednesday, September 19, 2001 2:28 PM Subject: Re: [proxy-suite] DHCP won't start > 192.168.17.1/255.255.255.0. When i type in /usr/sbin/dhcpd start it displays > the message "192.168.17.2 192.168.17.10 not on net > 192.168.17.1/255.255.255.0" What do i do wrong > > > 192.168.17.1 is probably not the network you want... try 192.168.17.0 > instead.. that is a network not a host. > > > dave > > >

1 0