ftp through port 8080
Thomas Moseler
at the moment. Login is denied when trying to
connect from home.
I believe it's a port problem.
We're an institute of university hannover and thus
behind the firewall of the university. The only
port they left open for us is Port 8080.
As I understand the default port for ftp on
our server is 21. How can I allow ftp acess on port
8080 ? I did not find any menu option in ftp
setup to select ports.
The firewall of Mac Os Server is turned off
(at least I believe, since it has no green point
in the services overview in Server Admin).
We recently updated to 10.3, and with our old
10.04 it worked, so there must be some option
to do this.
Thanks for any Help
Thomas
Small Tree Communications
Can't you use ssh and port forward through 8080?
--
Small Tree Communications
10Gb Ethernet and Gigabit Ethernet solutions for your MAC
http://www.small-tree.com
1-866-STC-4MAC
Cyde Weys
I don't know how to do this in whatever FTP client Mac OS X uses by
default, but I know for sure that I definitely do it with pure-ftpd on
my Linux box. pure-ftpd is open source, so download it, compile it
under Mac OS X, set it up, and you'll be good to go.
J.Random Luser
tmos...@gmx.de (Thomas Moseler) wrote:
>
> I believe it's a port problem.
> We're an institute of university hannover and thus
> behind the firewall of the university. The only
> port they left open for us is Port 8080.
>
Firstly make sure your server is properly configured,
see the advice others have offered.
Now I also am behind a University firewall, so I can tell you
you must speak very nicely to the people who manage the
University firewall. Tell them exactly what you want to do,
and why, and they may open the port for you, or
they may offer some other way to acheive your result.
noman
> As I understand the default port for ftp on
> our server is 21. How can I allow ftp acess on port
> 8080 ?
You can edit /etc/services so that ftp is 8080 instead of 21. I don't
recommend it, for sure, but it does work (I just tested it). You'll
need to open 8080 explicitly in the firewall, or disable the firewall
altogether, if you want it to be externally accessible. Of course if
you do edit /etc/services, outging command-line ftp will require the
option '-P 21' to use the normal port. Other ftp clients might get
confused as well. Again, I don't recommend doing this.
In theory you could avoid modifying /etc/services by creating a new
entry in /etc/xinetd.d with http-alt as the service (this is 8080) and
/usr/libexec/ftp as the server. But this doesn't work, probably
because ftpd is consulting /etc/services.
noman
> In theory you could avoid modifying /etc/services by creating a new
> entry in /etc/xinetd.d with http-alt as the service (this is 8080) and
> /usr/libexec/ftp as the server.
Of course that should say /usr/libexec/ftpd. But since it doesn't
work anyway, I don't suppose my typo matters much...
Thomas Moseler
> I don't know how to do this in whatever FTP client Mac OS X uses by
> default, but I know for sure that I definitely do it with pure-ftpd on
> my Linux box. pure-ftpd is open source, so download it, compile it
> under Mac OS X, set it up, and you'll be good to go.
Hi Cyde !
Well, sounds good. Have heard elsewhere about pure-ftpd.
Here comes in the fact that osx is unix ... hey !
But: Is it hard to set up ?(the word compiling scares me
a bit being neither used to programming nor to linux.)
I'll do a reasonable effort, being an exploring character.
Sounds good to me too, not to slave oneself to the
built-in routines of Mac OS ;-)
Thanks Thomas
Robert
>
> I believe it's a port problem.
> We're an institute of university hannover and thus
> behind the firewall of the university. The only
> port they left open for us is Port 8080.
>
Are you looking for an FTP client that you can specify which port to
use?
If so, here are some possibilities...
MaxOS 10.2 comes with a command line ftp. The ftp program is the
standard Unix ftp program and can be run from the terminal. I have
started using it because I couldn't find a free GUI based ftp program.
Excrept of ftp man page:
SYNOPSIS
[-AadefginpRtvV] [-o output] [-P port] [-r retry] [-T
dir,max[,inc]]
[[user@]host [port]] [user@]host:[path][/] [file:///path]
[ftp://[user[:password]@]host[:port]/path[/]]
[http://[user[:password]@]host[:port]/path] [...]
-u url file [...]
It took me a little while to figure out how to invoke ftp. Here is
some quick help:
ftp littl...@ftp-www.earthlink.net
It will ask for your password.
commands to work with server
pwd
get
put
cd
ls
commands to work with files on your mac
lcd
lpwd
! ls
Can't people in educational institution still get Fetch for free.
I haven't tried the download file, but it may be that if you download
and edit this file, you will get the free copy of fetch 3.0.3.
Here are a bunch of ftp programs.
http://www.pure-mac.com/ftp.html
Robert
Tom Davies
Set up ssh to listen on port 8080 like this:
http://www.macosxhints.com/article.php?story=20040609190121868
And then you can set up a tunnel on your client to any port on the
server you like with the command:
ssh -L <portnumber>:<server hostname>:<portnumber> -l username -N
<server hostname> -p 8080
you can now connect a local program to localhost:<portnumber> and it
will be talking to a listening server on <server hostname>:<portnumber>,
even though <portnumber> is blocked by your university firewall.
Tom
Tom Davie
Tom
Tom Davies <tomd...@optusnet.com.au> wrote in message news:<40d2756b$0$16298$afc3...@news.optusnet.com.au>...
Tom Davies
> :o Dude, I was confused by your username!
>
> Tom
You're a singular person ;-)
Tom
Thomas Moseler
Sounds good. I'll have to work myself a bit deeper
into the system than I thouht, but this won't do
me bad anyway ; ).
With the help of the discussion in macoshints you
gave the link to, I should be able to make it.
Thanks from Hannover
Thomas
tom....@gmail.com (Tom Davie) wrote in message news:<8b70a98a.04061...@posting.google.com>...
Thomas Moseler
I should be able to pull off the trick now.
In the end I understand it like this: find the right
file, just change the right number from 21 to 8080,
maybe restart system and that's it.
But, @noman: you say distinctively that you don't
recommend it. So I'd like to know:
is that for security issues, or for issues of
system stability ?
For security issues aren't our major concern.
I just fear to corrupt our operating system
maybe by port conflicts.
Thomas
noman <no...@klassikal.net> wrote in message news:<2jeoqqF...@uni-berlin.de>...