10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
I am using below code to ftp file and it errors out saying Servname not supported for ai_socktype ... if I do not use port number 2020 then it is not connected
#!/bin/sh
USER=$1
PASSWD=$2
server=$3
remoteFile=$4
localDir=$5
ftp -n -v << EOF
open $server 2020
user $USER $PASSWD
ascii
cd... (4 Replies)
Discussion started by: eskay
4 Replies
2. Shell Programming and Scripting
portsuf=25
port=20925
I need to replace 09 with 25
It should be like 22525.
Can some please help with command or script. (4 Replies)
Discussion started by: bhas85
4 Replies
3. HP-UX
Hi Experts,
Need your help in enabling the ftp port in HP-UX box.
Is there any command/config file that needs to be changed?
Also is it possible to open it only for few selected IPs only? (9 Replies)
Discussion started by: sai_2507
9 Replies
4. Solaris
Hello i'm newbie in solaris, anybody know how to change five port solaris 10?
exmpe: bge0, bge1, bge2, etc.
anybody can help me with the script implementasi... and logical how solaris work.
thank so much:b: (2 Replies)
Discussion started by: yanto85
2 Replies
5. IP Networking
Hi all,
Simple question.
What is the command to ftp to other port, says 55555
Astelnet we can use: telnet IPaddress portNumber right?
What about ftp? Thanks a lot (4 Replies)
Discussion started by: wilsonSurya
4 Replies
6. Red Hat
Hi,
Is it possible to change the nmap port name: For eg:
21/tcp open ftp
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
836/tcp open unknown
843/tcp open unknown
953/tcp open rndc
I need to change the port number 836 unknown to the name of the... (4 Replies)
Discussion started by: gsiva
4 Replies
7. SCO
Hello,
I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0.
My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls.
What i hyave noticed is that after a... (0 Replies)
Discussion started by: Amith
0 Replies
8. Shell Programming and Scripting
Hi Engg. ! :cool:
When I am trafering a file through ftp from windows to UNIX having size about 1.24 GB then at the end of file transfer I got a error message "Extended file size limit (coredump)" and finnally ftp stop, whenever on other UNIX server the same file from windows... (1 Reply)
Discussion started by: Niraj Gopal Sha
1 Replies
9. IP Networking
Hi,
Anyone have any pointers on how I would go about creating some sort of listener (preferably, but not exclusively in Java) that would monitor an ftp port and react to arrival of a new file?
Thanks in advance.
Selma (2 Replies)
Discussion started by: Selma
2 Replies
10. IP Networking
I changed the IP whit Ifconfig and I used ping to test the conetions the conection is rigth on my LAN (NetA)
But, I have two networks for example:
NetA route to NetB and vicevers
On NetB ping to any machine on NetA, it is respons successfully. but I ping to UNIX server no respons.
I... (1 Reply)
Discussion started by: lmena
1 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