May 2001 - SUSE Proxy Suite - openSUSE Mailing Lists

Proxy is crashing
by Thiago Madeira de Lima 31 May '01

31 May '01

I use the ftpproxy to redirect inbounds connections to my servers. For that I made a little change in the source code. It allways use magic user and it rewrite the username to: username(a)username.mydomain.com . The DNS server that servers this machine knows all my usernames (1.4Million) and it points to one of 12 real ftp servers. So when the user FOO types foo into my proxy machine it rewrites it to foo(a)foo.mydomain.com and try to lookup. foo.mydomian.com point to an A 200.200.200.200. Everything is working very well, but sometimes the master process seens to DIE. Users stay connected, but no one can make a new connection. I have about 100 users simultaneos in this server. It has 1G of RAM and 1PIII600. I've never seen it without free RAM or using the swap. Any tips? Maybe some way to debug it and find what is the problem? Thanks alot Thiago Lima.

2 2

unsbscribe
by Markus Malina 29 May '01

29 May '01

Markus Malina update*com software Benelux BV Hessenbergweg 8-10 Phone: +31 (0)20 311 8000 NL-1101 BT Amsterdam Z.O. Fax: +31 (0)20 311 8001 internet: www.update.com mailto:Markus.Malina@update.com

1 0

unsbscribe
by Àåêñåé 29 May '01

29 May '01

1 0

Re: Problem ftp-proxy can't connect Cli-Data (fwd)
by Marius Tomaschewski 25 May '01

25 May '01

On Wed, May 23, 2001 at 02:12:11PM +0200, Thomas Boernert wrote: > > > -- > Mit freundlichen Grüssen > Best regards > > Thomas Börnert > Systemmanager IT > Geschäftsführer > > DO NOT GIVE OUR ADDRESS TO THIRD PARTYS, WE HATE JUNK-MAIL > __________________________________________________________________ > TBits.net GmbH | Fon: +49 (0)700 BOERNERT > Thomas Börnert | oder +49 (0)700 26376378 > Postfach 64 | Auto: +49 (0)170 6744415 > D-73551 Alfdorf | Fax: +49 (0)89 2443 31823 > http://www.tbits.net | Mail: info(a)tbits.net > > ---------- Forwarded message ---------- > Date: Thu, 17 May 2001 18:14:14 +0200 (CEST) > From: Thomas Boernert <tb(a)tbits.net> > To: wiegand(a)suse.de > Subject: Problem ftp-proxy can't connect Cli-Data > > Hallo Hr. Wiegand, > > habe ein kleines Prob mit ftp-proxy 1.7 > > log > <---- snip -----> > ftp-child [9267] <05/17-18:06:47> USER-INF connect from 10.130.2.193 > ftp-child [9267] <05/17-18:06:47> USER-INF 'USER tbitsnet' dest > 212.87.131.2:21 from 10.130.2.193 > ftp-child [9267] <05/17-18:06:47> USER-INF reading data for 'tbitsnet' > from cfg-file > ftp-child [9267] <05/17-18:06:47> USER-INF 'PASS XXXX' from 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> USER-INF 'PWD' from 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> USER-INF 'SYST' from 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> USER-INF 'PORT 10.130.2.193:1351' from > 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> USER-INF 'LIST' from 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> TECH-INF 'PORT 212.87.134.1:1371' for > 10.130.2.193 > ftp-child [9267] <05/17-18:06:48> TECH-ERR can't connect Cli-Data for > 10.130.2.193 The "TECH-ERR can't connect Cli-Data" is a known bug - you'll get this message if a bind(2) call is failed. FTP-Servers try's to call bind up to 10 times before they gives up; the proxy gives up after the first failure. It is on my TODO, I'll try to fix it next week (I hope to have the time :-). > <---- snip ----> > > conf > <----- snip -----> > AllowMagicUser yes > DestinationAddress 212.87.134.1 > Listen 10.130.2.70 > LogDestination /var/log/ftp-proxy.log > ServerType standalone > User ftpproxy > <----- snip -----> > > tcpdump eth0 internal > <----- snip -----> > 18:11:34.049891 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: S > 2206604325:2206604325(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) > 18:11:34.049959 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: S > 1960461970:1960461970(0) ack 2206604326 win 32120 <mss > 1460,nop,nop,sackOK> (DF) [tos 0x10] > 18:11:34.051328 eth0 < tboernert2.erni.de.1354 > > gate1-eth0.erni.de.ftp: . 1:1(0) ack 1 win 17520 (DF) > 18:11:34.052606 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 1:66(65) ack 1 win 32120 (DF) [tos 0x10] > 18:11:34.099076 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 1:34(33) ack 66 win 17455 (DF) > 18:11:34.099121 eth0 > gate1-eth0.erni.de.ftp > > tboernert2.erni.de.1354: . 66:66(0) ack 34 win 32120 (DF) [tos 0x10] > 18:11:34.184823 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 66:103(37) ack 34 win 32120 (DF) [tos 0x10] > 18:11:34.204609 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 34:49(15) ack 103 win 17418 (DF) > 18:11:34.221545 eth0 > gate1-eth0.erni.de.ftp > > tboernert2.erni.de.1354: . 103:103(0) ack 49 win 32120 (DF) [tos 0x10] > 18:11:34.249718 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 103:133(30) ack 49 win 32120 (DF) [tos 0x10] > 18:11:34.275126 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 49:54(5) ack 133 win 17388 (DF) > 18:11:34.283599 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 133:164(31) ack 54 win 32120 (DF) [tos 0x10] > 18:11:34.301927 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 54:60(6) ack 164 win 17357 (DF) > 18:11:34.308334 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 164:183(19) ack 60 win 32120 (DF) [tos 0x10] > 18:11:34.356986 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 60:84(24) ack 183 win 17338 (DF) > 18:11:34.357246 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 183:213(30) ack 84 win 32120 (DF) [tos 0x10] > 18:11:34.381134 eth0 < tboernert2.erni.de.1354 > gate1-eth0.erni.de.ftp: P > 84:90(6) ack 213 win 17308 (DF) > 18:11:34.387861 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 213:246(33) ack 90 win 32120 (DF) [tos 0x10] > 18:11:34.581545 eth0 > gate1-eth0.erni.de.ftp > tboernert2.erni.de.1354: P > 213:246(33) ack 90 win 32120 (DF) [tos 0x10] > 18:11:34.582361 eth0 < tboernert2.erni.de.1354 > > gate1-eth0.erni.de.ftp: . 90:90(0) ack 246 win 17275 (DF) > 18:11:34.583447 eth0 < tboernert2.erni.de.1354 > > gate1-eth0.erni.de.ftp: . 90:90(0) ack 246 win 17275 (DF) > <----- snip -----> > > tcpdump eth1 extern > <----- snip -----> > 18:12:26.076937 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: S > 2005935881:2005935881(0) win 32120 <mss 1460,sackOK,timestamp 2662550612 > 0,nop,wscale 0> (DF) [tos 0x10] > 18:12:26.081374 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: S > 2159835676:2159835676(0) ack 2005935882 win 32736 <mss 1460> > 18:12:26.081420 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 1:1(0) ack 1 win 32120 (DF) [tos 0x10] > 18:12:26.115269 eth1 < virtweb5.imos.net.16437 > > gate1-eth1.erni.de.auth: S 728091206:728091206(0) win 512 <mss 1460> > 18:12:26.115338 eth1 > gate1-eth1.erni.de > > virtweb5.imos.net: icmp: gate1-eth1.erni.de tcp port auth unreachable [tos > 0xc0] > 18:12:26.124315 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 1:93(92) ack 1 win 32736 (DF) [tos 0x10] > 18:12:26.124368 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 1:1(0) ack 93 win 32028 (DF) [tos 0x10] > 18:12:26.124505 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: P > 1:16(15) ack 93 win 32120 (DF) [tos 0x10] > 18:12:26.139257 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 93:130(37) ack 16 win 32736 (DF) [tos 0x10] > 18:12:26.141547 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 16:16(0) ack 130 win 32120 (DF) [tos 0x10] > 18:12:26.168521 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: P > 16:31(15) ack 130 win 32120 (DF) [tos 0x10] > 18:12:26.185160 eth1 < virtweb5.imos.net.ftp > > gate1-eth1.erni.de.1516: . 130:130(0) ack 31 win 32736 (DF) [tos 0x10] > 18:12:26.213774 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 130:160(30) ack 31 win 32736 (DF) [tos 0x10] > 18:12:26.231545 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 31:31(0) ack 160 win 32120 (DF) [tos 0x10] > 18:12:26.248855 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: P > 31:36(5) ack 160 win 32120 (DF) [tos 0x10] > 18:12:26.257228 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 160:191(31) ack 36 win 32736 (DF) [tos 0x10] > 18:12:26.271545 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 36:36(0) ack 191 win 32120 (DF) [tos 0x10] > 18:12:26.283926 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: P > 36:42(6) ack 191 win 32120 (DF) [tos 0x10] > 18:12:26.289229 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 191:210(19) ack 42 win 32736 (DF) [tos 0x10] > 18:12:26.301544 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 42:42(0) ack 210 win 32120 (DF) [tos 0x10] > 18:12:26.366328 eth1 > gate1-eth1.erni.de.1516 > virtweb5.imos.net.ftp: P > 42:67(25) ack 210 win 32120 (DF) [tos 0x10] > 18:12:26.371698 eth1 < virtweb5.imos.net.ftp > gate1-eth1.erni.de.1516: P > 210:240(30) ack 67 win 32736 (DF) [tos 0x10] > 18:12:26.391544 eth1 > gate1-eth1.erni.de.1516 > > virtweb5.imos.net.ftp: . 67:67(0) ack 240 win 32120 (DF) [tos 0x10] > <---- snip ----> > > Transparent Proxy will ich eigentlich nicht verwenden. > Was ist das Problem. > Es findet keine Kommunikation mit Port 20 statt. > Wenn ich von dem Rechner auf dem der ftp-proxy laueft ein ftp zu dem host > mache, dann geht es. > > Danke fuer Info. > > Gruss Thomas Boernert > > -- > Mit freundlichen Grüssen > Best regards > > Thomas Börnert > Systemmanager IT > Geschäftsführer > > DO NOT GIVE OUR ADDRESS TO THIRD PARTYS, WE HATE JUNK-MAIL > __________________________________________________________________ > TBits.net GmbH | Fon: +49 (0)700 BOERNERT > Thomas Börnert | oder +49 (0)700 26376378 > Postfach 64 | Auto: +49 (0)170 6744415 > D-73551 Alfdorf | Fax: +49 (0)89 2443 31823 > http://www.tbits.net | Mail: info(a)tbits.net > > > -- Gruesse, 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

RE: [proxy-suite] Proxy Problem
by Hugo Ferreira 25 May '01

25 May '01

> -----Original Message----- > From: patric illi [SMTP:maillist@patricilli.net] > Sent: Sexta-feira, 25 de Maio de 2001 8:53 > To: Sajjad Ahmad > Cc: proxy-suite(a)suse.com > Subject: Re: [proxy-suite] Proxy Problem > > cheers ! > > 1. Copy and Paste the script below to your /etc/squid/squid.conf location. > > 2. Adjust it to your need ! > 3. Create a file with your allowed hosts ( IP only ) > "/etc/squid/allowed_surfers" > > 4. restart squid ! > > cheers ! > > > ----------------------------/etc/squid/squid.conf------------------------- > -------- > > > #/etc/squid/squid.conf > #Edited by Patric Illi may be used and distributed under GPL > http_port 8080 > cache_mem 8 MB > # > cache_swap_low 90 > cache_swap_high 95 > # > maximum_object_size 4096 KB > minimum_object_size 0 KB > > cache_dir ufs /var/spool/squid 100 16 256 > > > cache_access_log /var/log/squid/access.log > cache_log /var/log/squid/cache.log > cache_store_log /var/log/squid/store.log > pid_filename /var/run/squid.pid > > #Defaults: > acl all src 192.168.1.0/255.255.255.0 > acl allowed_users src "/etc/squid/allowed_surfers" > acl manager proto cache_object > acl localhost src 127.0.0.1/255.255.255.255 > acl SSL_ports port 443 563 > acl Safe_ports port 80 21 443 563 70 210 1025-65535 > acl Safe_ports port 280 # http-mgmt > acl Safe_ports port 488 # gss-http > acl Safe_ports port 591 # filemaker > acl Safe_ports port 777 # multiling http > acl CONNECT method CONNECT > > #Default configuration: > http_access allow manager localhost > http_access deny manager > http_access deny !Safe_ports > http_access deny CONNECT !SSL_ports > # > # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS > # > http_access allow allowed_users > http_access deny all > -------------------------------------------finish > squid.conf------------------------ > Sajjad Ahmad wrote: > > Hi folks, I am configuring Squid on SUSE 7.1 Prof. can some body > guide me how can I configure it transparently. Regards, Sajjad >

1 0

Proxy Problem
by Sajjad Ahmad 25 May '01

25 May '01

Hi folks, I am configuring Squid on SUSE 7.1 Prof. can some body guide me how can I configure it transparently. Regards, Sajjad

2 1

Error compiling on Solaris 7
by Alexandre Marquis 17 May '01

17 May '01

When I'm trying to compile proxy-suite-1.7 on Solaris 7, I get this error. Does somebody can give me a hint to solve this problem ? Thanks. gcc -g -O2 -I. -I.. -c com-socket.c In file included from com-socket.c:74: /usr/include/netinet/ip.h:130: parse error before `n_long' /usr/include/netinet/ip.h:130: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:130: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:133: parse error before `n_long' /usr/include/netinet/ip.h:133: warning: no semicolon at end of struct or union /usr/include/netinet/ip.h:134: warning: data definition has no type or storage class /usr/include/netinet/ip.h:135: parse error before `}' /usr/include/netinet/ip.h:135: warning: data definition has no type or storage class /usr/include/netinet/ip.h:136: parse error before `}' com-socket.c: In function `socket_ll_read': com-socket.c:934: `FIONREAD' undeclared (first use in this function) com-socket.c:934: (Each undeclared identifier is reported only once com-socket.c:934: for each function it appears in.) gmake[1]: *** [libcommon.a(com-socket.o)] Error 1 gmake[1]: Leaving directory `/mis/users/amarquis/software/solaris/build/proxy-suite-1.7/common' gmake: *** [all] Error 1 -- ASCII ribbon campaign ( ) - against HTML email X & vcards / \ ***************************************** * Alexandre Marquis * * Groupe UNIX Group * * Département IT Department * * Matrox Electronic Systems Ltd. * * (514) 822-6000 x.7780 * * amarquis(a)matrox.com * *****************************************

1 0

WG: [proxy-suite] unsubscribe
by Manfred.Behlen＠t-online.de 17 May '01

17 May '01

1 0

unsbscribe
by Herr Illner 17 May '01

17 May '01

Mit freundlichen Grüßen Frank Illner

1 0

Newbie Question: Proper configuation
by Arthur Kahwa 17 May '01

17 May '01

Hi, I've read the documentation to the proxy suite, but I am still not able to get it to work at all on SuSE 6.4. Could someone please send me an example of a working configuration, please. I'd be extremely grateful. Thank you for all your help, Arthur Kahwa

1 0