Sponsored Content
Special Forums IP Networking Proxy Server Need to build a quick FTP server, Advice?? Post 302920819 by rbatte1 on Monday 13th of October 2014 07:55:15 AM
Old 10-13-2014
You should be able to allow access on port 22, but be specific to their incoming address. They may have a proxy server somewhere, so it is the IP address that is seen on the public side you should code for.

Giving open access to port 22 is just asking for trouble.


I hope that this helps.
Robin
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Advice to build a cheap Unix machine?

Hello! In my perpetual quest to learn Unix, I want to build a cheap Unix server for my personal use. Do you guys have suggestions of web sites, vendors etc...where I could get info on things such as step-by-step instruction, 2nd hand hardware etc... I would like to go preferably with a HP... (2 Replies)
Discussion started by: alan
2 Replies

2. HP-UX

problem after server build...

Hi, I have installed HP-UX 11.31 on a rx6600 box. The installation went fine and was completed without any errors. But wheni connect to the server using ssh, it asks for a username, when i enter it, it doesnt prompt for a password: login:username blank-------- All i could see in... (1 Reply)
Discussion started by: sag71155
1 Replies

3. Web Development

Building LAMP server from scratch (build a server with compiled LAMP from CentOS mini)

Hello everyone, I would like to setup a lamp server from a minimal distro and to compile PHP, MySQL and Apache myself. I have chosen CentOS minimal for the OS and I am trying to build the stack by hand... But well, it appears I need some help! First: I am looking for good and recent... (3 Replies)
Discussion started by: freddie50
3 Replies

4. UNIX for Dummies Questions & Answers

What does it takes to Build a Mail Server?

Subject: What does it takes to build a mail server, its just for fun and learning. Am bad at being techinical, so in short, how to create a gmail-like thing? I have a registered domain, and want to setup a mail server. Have a spare laptop that is running Ubuntu 12.04. What I need to know is,... (4 Replies)
Discussion started by: Memberz Name
4 Replies

5. Red Hat

Implement FTP server on RHEL server without using FTP client

We have RHEL 5.8 in our environment, I had a query whether we can implement an FTP server using vsftpd package and Linux configurations like setsebool without using any external FTP clients like FileZilla etc. I am very confused on this. The FTP functionalities that should be present are download &... (3 Replies)
Discussion started by: RHCE
3 Replies

6. Solaris

How to build an install server for Solaris 8?

I need to boot again a server with solaris 8 because I have a problem with the file path_to_install and I have not a CD/DVD driver. So I'd like to build an install server for executing a boot by network. Could I use a server with solaris 10? Many thanks for your suggests Best Regards at... (2 Replies)
Discussion started by: ardgiu70
2 Replies

7. UNIX for Advanced & Expert Users

Build NFS Server on CentOS

Dear All, I'm using AWS EC2 instance for my application. My application is high disk I/O based and EFS could not be used in my case. So, i need to build my own NFS server on Ec2 instance. I'm looking for High availability solution for my disk which i shared for NFS. Looking for builtin... (5 Replies)
Discussion started by: Bala
5 Replies

8. Red Hat

Advice on allocating SAN storage to a virtual database server on VMware

I am relatively new to Linux and we are getting ready to convert our current oracle database servers from the AIX platform to RHEL7 servers on VMWare. I would appreciate any advice on how best to allocate storage to these machines. I plan on using LVM to maintain the disks/filesystems but am... (9 Replies)
Discussion started by: dkmartin
9 Replies
FTP-PROXY(8)						    BSD System Manager's Manual 					      FTP-PROXY(8)

NAME
ftp-proxy -- Internet File Transfer Protocol proxy daemon SYNOPSIS
ftp-proxy [-6Adrv] [-a address] [-b address] [-D level] [-m maxsessions] [-P port] [-p port] [-q queue] [-R address] [-T tag] [-t timeout] DESCRIPTION
ftp-proxy is a proxy for the Internet File Transfer Protocol. FTP control connections should be redirected into the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client. The proxy allows data connections to pass, rewriting and redirecting them so that the right addresses are used. All connections from the client to the server have their source address rewritten so they appear to come from the proxy. Consequently, all connections from the server to the proxy have their destination address rewritten, so they are redirected to the client. The proxy uses the pf(4) anchor facility for this. Assuming the FTP control connection is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is negotiated, then ftp-proxy adds the following rules to the various anchors. (These example rules use inet, but the proxy also supports inet6.) In case of active mode (PORT or EPRT): rdr from $server to $proxy port $port -> $client pass quick inet proto tcp from $server to $client port $port In case of passive mode (PASV or EPSV): nat from $client to $server port $port -> $proxy pass in quick inet proto tcp from $client to $server port $port pass out quick inet proto tcp from $proxy to $server port $port The options are as follows: -6 IPv6 mode. The proxy will expect and use IPv6 addresses for all communication. Only the extended FTP modes EPSV and EPRT are allowed with IPv6. The proxy is in IPv4 mode by default. -A Only permit anonymous FTP connections. Either user "ftp" or user "anonymous" is allowed. -a address The proxy will use this as the source address for the control connection to a server. -b address Address where the proxy will listen for redirected control connections. The default is 127.0.0.1, or ::1 in IPv6 mode. -D level Debug level, ranging from 0 to 7. Higher is more verbose. The default is 5. (These levels correspond to the syslog(3) levels.) -d Do not daemonize. The process will stay in the foreground, logging to standard error. -m maxsessions Maximum number of concurrent FTP sessions. When the proxy reaches this limit, new connections are denied. The default is 100 ses- sions. The limit can be lowered to a minimum of 1, or raised to a maximum of 500. -P port Fixed server port. Only used in combination with -R. The default is port 21. -p port Port where the proxy will listen for redirected connections. The default is port 8021. -q queue Create rules with queue queue appended, so that data connections can be queued. -R address Fixed server address, also known as reverse mode. The proxy will always connect to the same server, regardless of where the client wanted to connect to (before it was redirected). Use this option to proxy for a server behind NAT, or to forward all connections to another proxy. -r Rewrite sourceport to 20 in active mode to suit ancient clients that insist on this RFC property. -T tag The filter rules will add tag tag to data connections, and not match quick. This way alternative rules that use the tagged keyword can be implemented following the ftp-proxy anchor. These rules can use special pf(4) features like route-to, reply-to, label, rtable, overload, etc. that ftp-proxy does not implement itself. -t timeout Number of seconds that the control connection can be idle, before the proxy will disconnect. The maximum is 86400 seconds, which is also the default. Do not set this too low, because the control connection is usually idle when large data transfers are taking place. -v Set the 'log' flag on pf rules committed by ftp-proxy. Use twice to set the 'log-all' flag. The pf rules do not log by default. CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. All anchors are mandatory. Adjust the rules as needed. In the NAT section: nat-anchor "ftp-proxy/*" rdr-anchor "ftp-proxy/*" rdr pass on $int_if proto tcp from $lan to any port 21 -> 127.0.0.1 port 8021 In the rule section: anchor "ftp-proxy/*" pass out proto tcp from $proxy to any port 21 SEE ALSO
ftp(1), pf(4), pf.conf(5) CAVEATS
pf(4) does not allow the ruleset to be modified if the system is running at a securelevel(7) higher than 1. At that level ftp-proxy cannot add rules to the anchors and FTP data connections may get blocked. Negotiated data connection ports below 1024 are not allowed. The negotiated IP address for active modes is ignored for security reasons. This makes third party file transfers impossible. ftp-proxy chroots to "/var/empty" and changes to user "proxy" to drop privileges. BSD
February 26, 2008 BSD
All times are GMT -4. The time now is 08:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy