Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Web Security: HTTP/HTTPS/FTP, IM/P2P, Web Filtering and Antivirus

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-30-2009, 03:13 PM
Junior Member
 
Join Date: Jun 2009
Posts: 6
Default FTP Client fails to conenct when Transparent Mode is used

I am unable to connect to some FTP sites via Firefox, IE, or CMD when I am using the Astaro FTP Proxy and "Transparent" mode is selected. As soon as I change it to non-transparent mode, everything works fine.

Why exactly is this? Is there a security risk when not using it in Transparent mode? If I leave it in non-trans mode, does the virus scan and everything still work?

I have ASG320-7.306 (i know it needs updating)

In command line FTP, the client shows: "421 FTP server is sending you rubbish! Closing connection.
Connection closed by remote host."


The FTP log on the Astaro shows:
2009:06:30-09:35:41 (none) frox[4733]: Reloading configuration
2009:06:30-09:35:41 (none) frox[22048]: Connect from INTERNAL CLIENT IP
2009:06:30-09:35:41 (none) frox[22048]: ... to EXTERNAL SERVER IP()
2009:06:30-09:35:50 (none) frox[22048]: Server is sending us a badly formed control stream.
2009:06:30-09:35:50 (none) frox[22048]: Closing session

Also, when setting FTP Proxy to non-Transparent mode, nothing is logged when successful.

thanks, I appreciate the help and effort!
Reply With Quote
  #2 (permalink)  
Old 06-30-2009, 03:27 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 4,954
Default

In transparent mode, the FTP proxy captures ftp traffic and A-V scans the traffic. If you change the mode to non-transparent, the proxy "listens" on port 2121 instead, so, if you didn't make that change to your client's configuration, the non-transparent proxy doesn't handle your FTP traffic.

Probably, in non-transparent mode, the traffic is passing because you have a packet filter rule like 'Internal (Network) -> Any -> Any : Allow'.

Try putting the proxy back into transparent mode and looking at the packet filter log. If there's no indication there, look at the IPS log. If you see nothing in either one, try creating an A-V exception for one of the sites with which you are having a problem.

When you discover the fix, please post it.

Cheers - Bob
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #3 (permalink)  
Old 06-30-2009, 04:08 PM
Junior Member
 
Join Date: Jun 2009
Posts: 6
Default

BAlfson,

thank you for replying and doing it so quickly

Yes I see a dedicated PF rule to allow ftp = internal network >> ftp >> any

In reference to the information below, I turned OFF the above packet filter rule for FTP


-Whiel in Trans mode, FTP to the desired site still fails with "421 FTP server is sending you rubbish!"
-When looking at the live packet filter log while IN Transparent mode: I see no record of the connection attempt or a denial
-FTP connection fails to connect while in non-transparent mode (because i disabled the FTP packet filter rule above)
-I see no records in IPS live log when FTP connection fails
-I have turned off FTP Proxy Anti-Virus system wide temporarily, still doesn't connect while in Transparent Mode
-I also created an Exception for the destination FTP site and Client exempting it from all traffic checking -- still get the same problem while in Transparent Mode

checked FTP Proxy log, still getting:
Reloading configuration
Connect from INTERNAL CLIENT IP
... to EXTERNAL SERVER IP()
Server is sending us a badly formed control stream.
Closing session
Reply With Quote
  #4 (permalink)  
Old 07-02-2009, 10:03 AM
Simon Shaw's Avatar
Aussie moderator.
 
Join Date: Jun 2001
Location: Perth, Western Australia
Posts: 2,628
Default

Try also allowing FTP control port (I believe TCP port 20 from memory).
__________________
Simon Shaw
Systems Manager
Micromine PL

Intel 2.66GHz Quad Core, 4GB (2 x 2GB) PC-6400 800Mhz 4-4-4-12, WD 300GB 10K RPM VelociRaptor, Intel Pro/1000 Quad Port PCI-X
http://www.sputcorp.com/
Reply With Quote
  #5 (permalink)  
Old 07-02-2009, 03:17 PM
Junior Member
 
Join Date: Jun 2009
Posts: 6
Default

Simon,

thanks for the assistance. I have tried that. No dice :-(
Reply With Quote
  #6 (permalink)  
Old 07-02-2009, 05:11 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 4,954
Default

And you saw nothing in either the PF or IPS log?
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #7 (permalink)  
Old 07-02-2009, 09:33 PM
Junior Member
 
Join Date: Jun 2009
Posts: 6
Default

No definitely didn't see anything in the IPS log.

There is nothing in the Packet filter log either because when Astaro's FTP proxy service is on, the Packet Filter rules are not consulted for FTP outbound. Only when I disable the Astaro FTP proxy do I then see records in the packet filter's live log.

But all that aside, I have determined that it IS a problem with this one particular FTP site. When the FTP proxy is on, the Astaro froxy returns "421 FTP server is sending you rubbish!". When the Astaro froxy is off AND there is an FTP allow packet filter rule, connection to this particular FTP site functions fine through the Astaro.

I setup a test FTP site and I am able to connect when the Astaro froxy is enabled, so it is definitely something special about this one particular remote FTP server. I just have no idea what that special quality is and I am not disabling the Astaro froxy because of one site. The Astaro FTP proxy just seems to not be able to function properly with this remote FTP server.

lol, any ideas?
Reply With Quote
  #8 (permalink)  
Old 07-02-2009, 11:37 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 4,954
Default

That was why I was curious about the PF log - some other port that this particular server is trying to use to do something unanticipated in a standard FTP conversation. The FTP Proxy is not going to see such a thing.

Cheers - Bob
PS A thought... Have you enabled the FTP 'Connection tracking helper' on the 'Advanced' tab of 'Network Security >> Packet Filter'?
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!

Last edited by BAlfson; 07-02-2009 at 11:44 PM. Reason: PS
Reply With Quote
  #9 (permalink)  
Old 07-06-2009, 06:14 PM
Junior Member
 
Join Date: Jun 2009
Posts: 6
Default

BAlfson,

Thanks for continuing to try and help. Yes, FTP connection tracking is enabled for NAT passthrough.


....still stumped. Unfortunately I don't know anything about froxy and what this other server is doing that it doesn't like. It works fine when connecting to it via normal FTP and not going through froxy.
Reply With Quote
  #10 (permalink)  
Old 07-06-2009, 07:09 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 4,954
Default

Oops, I meant "that was why I was curious about the IPS log."
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!

Last edited by BAlfson; 07-06-2009 at 07:49 PM.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 02:02 PM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.