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-09-2009, 04:42 PM
Junior Member
 
Join Date: May 2009
Posts: 24
Default Setting up FTP on different port

Dear All,


I have an FTP Server with ip adress: 10.*.*.36 (DMZ):
The ftp server is setup to listen to port 21 (gladly willing to change to 15470 if required)
The ftp server is setup with IIS
Now i would like when entering the following ip adress in IE:
FTP://62.*.*.237:15470
that this adress connects to the ftp server.

will it be required to set up an FTP Proxy ?
What should be the correct DNAT / SNAT setup ?
Which packet filters should i use ?
Intrusion protection is on / off ?


Thanks in advance for your assistance !
Eli_DS
Reply With Quote
  #2 (permalink)  
Old 06-09-2009, 08:02 PM
BAlfson's Avatar
Moderator
 
Join Date: Mar 2007
Location: Oklahoma City
Posts: 5,268
Default

Intrusion Protection should not affect this. You will need a DNAT rule for traffic that fits 'Any -> FTP -> [62.*.*.237]' and it should have a changed destination of [10.*.*.36], where the standard definition for "FTP" is '1:65535 -> 21'.

To allow Active FTP traffic, you need two packet filter rules:
  1. 'Any' -> [Port 21] -> [10.*.*.36] : 'Allow'
  2. [10.*.*.36] -> [Port 20] -> 'Any' : 'Allow'
You don't need the first rule if you select 'Automatic packet filter rule' in the DNAT definition.

Cheers - Bob
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #3 (permalink)  
Old 06-10-2009, 08:05 AM
Junior Member
 
Join Date: May 2009
Posts: 24
Default

Hello BAlfson,

Thanks for your swift reply.

The rule you provided indeed worked.
but now i have to use the following addres:
ftp://62.*.*.237

I would like to use FTP://62.*.*.237:15470
Is this also possible ?
Reply With Quote
  #4 (permalink)  
Old 06-10-2009, 08:10 AM
Moderator
 
Join Date: Jul 2001
Location: southern California
Posts: 5,099
Default

You could DNAT port 15470 to port 21.
Don't forget that FTP uses 2 ports though.

Barry
__________________
http://DealBert.net
Home & business end-user since v1.x
  • ASL 6.3x, HP DL145 Dual Opteron, 1GB RAM, 6 gigE NICs, 50-IP Platinum License
  • ASL 7.3x, Dell PE1550 Dual PIII 1GHz, 1GB RAM, 2 NICs, 50-IP Platinum License
  • ASL 7.5x, 17-watt fanless mini-ITX system: MSI IM-945GSE-A Atom n270, 2GB RAM, Morex T3310 case. 2 Intel GigE, 3 VLANs. 80G 5200rpm 2.5" HD
    Netgear GS108T gigE VLAN switch & Linksys WRT54G WAP
    Total network infrastructure: 27 watts. 100-IP Home User. FiOS 10mb/2mb
Reply With Quote
  #5 (permalink)  
Old 06-10-2009, 08:54 AM
Junior Member
 
Join Date: May 2009
Posts: 24
Default

Hello Barry,

I have tested with the following rules

Packet Filter

# 'Any' -> [Port 21] -> [10.*.*.36] : 'Allow'
# [10.*.*.36] -> [Port 20] -> 'Any' : 'Allow


DNAT

Any => [Port 15470] => Wan: 62.*.*.237

Traffic destination: 10.*.*.36 => [Port: 21]


But this doesn't work...
I can log in to the ftp website but then it just says Website found, Waiting for reply...

so probably the website is not answering back on port 15470 ?
Reply With Quote
  #6 (permalink)  
Old 06-11-2009, 01:38 AM
Moderator
 
Join Date: Jul 2001
Location: southern California
Posts: 5,099
Default

I'm not sure what 'ftp website' means.

Your DNAT looks OK, but what about the second port (port 20)? Do you have it on another port, and appropriate rules, etc.?

Barry
__________________
http://DealBert.net
Home & business end-user since v1.x
  • ASL 6.3x, HP DL145 Dual Opteron, 1GB RAM, 6 gigE NICs, 50-IP Platinum License
  • ASL 7.3x, Dell PE1550 Dual PIII 1GHz, 1GB RAM, 2 NICs, 50-IP Platinum License
  • ASL 7.5x, 17-watt fanless mini-ITX system: MSI IM-945GSE-A Atom n270, 2GB RAM, Morex T3310 case. 2 Intel GigE, 3 VLANs. 80G 5200rpm 2.5" HD
    Netgear GS108T gigE VLAN switch & Linksys WRT54G WAP
    Total network infrastructure: 27 watts. 100-IP Home User. FiOS 10mb/2mb
Reply With Quote
  #7 (permalink)  
Old 06-11-2009, 01:07 PM
Junior Member
 
Join Date: May 2009
Posts: 24
Default

Barry,


With FTP Website i just mean when I connect to ftp://62.*.*237:15470

for the second port we keep port 20.
Reply With Quote
  #8 (permalink)  
Old 06-16-2009, 12:11 PM
Junior Member
 
Join Date: May 2009
Posts: 24
Default

Hey all,


After doing some spitting in the logs the following is happening:

13:08:11 Packetfilter rule #4 TCP
WAN IP : 1929

DMZ IP : 15470

[SYN] len=48 ttl=117 tos=0x00

13:08:14 Packetfilter rule #4 TCP
WAN IP : 1930

DMZ IP : 15470

[SYN] len=48 ttl=117 tos=0x00

13:08:14 Packetfilter rule #4 TCP
WAN IP : 1892

DMZ IP : 15470

[ACK PSH] len=46 ttl=117 tos=0x00

These above rules pass when i am trying to acces the ftp server.

The rule is:

Any => DMZ IP
Over port 15470

So apperently on the firewall side everything gets passed, but still there is no response from the ftpserver...

after a minute i get:
The operation timed out...

If any one would be able to tell me what i'm doing wrong, I would be most thankful!
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 11:43 AM.

 

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.