Ftping through router and Airport

I have just set up a network in my new flat. The ISP connects to a DLink
DSL-504 modem/router, on one connection of the router I have my airport.
Connected to the airport through wireless is an Imac and my Albook. All
seems to work well, but I'm having problems connecting to the computers
from outside. I have used DYNDNS.org to give them an address and
forwarded the appropriate ports through the Airport, but I still can't
get connected. Anyone used a setup like this or have any suggestions for
things to try?

Don

Don McKenzie Paul <phrje@warwick.ac.uk> wrote:

> I have just set up a network in my new flat. The ISP connects to a DLink
> DSL-504 modem/router, on one connection of the router I have my airport.
> Connected to the airport through wireless is an Imac and my Albook. All
> seems to work well, but I'm having problems connecting to the computers
> from outside. I have used DYNDNS.org to give them an address and
> forwarded the appropriate ports through the Airport, but I still can't
> get connected. Anyone used a setup like this or have any suggestions for
> things to try?
>
> Don

You need to open the relevant port in the DLink as well, presumably
through some sort of browser interface


--
~/ireland/dublin

gp <guttapercha@oceanfree.net> wrote:

> Don McKenzie Paul <phrje@warwick.ac.uk> wrote:
>
> > I have just set up a network in my new flat. The ISP connects to a DLink
> > DSL-504 modem/router, on one connection of the router I have my airport.
> > Connected to the airport through wireless is an Imac and my Albook. All
> > seems to work well, but I'm having problems connecting to the computers
> > from outside. I have used DYNDNS.org to give them an address and
> > forwarded the appropriate ports through the Airport, but I still can't
> > get connected. Anyone used a setup like this or have any suggestions for
> > things to try?
> >
> > Don
>
> You need to open the relevant port in the DLink as well, presumably
> through some sort of browser interface

Probably...I was afraid of that since the instructions for the DLink are
complex and I'm no expert. Anyone out there want to point me in the
right direction. Is it Port Redircetion although that seems to be more
useful to filter out unwanted stuff rather than the other way around.

Don

On 6/3/04 3:47 pm, in article 1ga8h3a.cfkpbm1lr4aoN%phrje@warwick.ac.uk,
"Don McKenzie Paul" <phrje@warwick.ac.uk> wrote:

> Probably...I was afraid of that since the instructions for the DLink are
> complex and I'm no expert. Anyone out there want to point me in the
> right direction. Is it Port Redircetion although that seems to be more
> useful to filter out unwanted stuff rather than the other way around.

Port redirection is for when you've got several machines connected to the
router and using NAT. When there's a connection to your public IP address
(ie the router's) from the Internet, port direction is used by the router to
work out which internal machine to send it to.

Getting incoming ftp to work is a bit of a bugger, because it is a very
broken protocol that requires multiple ports, and you don't know what
they'll be ahead of time (<URL:http://slacksite.com/other/ftp.html>). See
if you can find a better protocol.

Cheers,

Chris

Chris Ridd <chrisridd@mac.com> wrote:

> On 6/3/04 3:47 pm, in article 1ga8h3a.cfkpbm1lr4aoN%phrje@warwick.ac.uk,
> "Don McKenzie Paul" <phrje@warwick.ac.uk> wrote:
>
> > Probably...I was afraid of that since the instructions for the DLink are
> > complex and I'm no expert. Anyone out there want to point me in the
> > right direction. Is it Port Redircetion although that seems to be more
> > useful to filter out unwanted stuff rather than the other way around.
>
> Port redirection is for when you've got several machines connected to the
> router and using NAT. When there's a connection to your public IP address
> (ie the router's) from the Internet, port direction is used by the router to
> work out which internal machine to send it to.
>
> Getting incoming ftp to work is a bit of a bugger, because it is a very
> broken protocol that requires multiple ports, and you don't know what
> they'll be ahead of time (<URL:http://slacksite.com/other/ftp.html>). See
> if you can find a better protocol.
>
> Cheers,
>
> Chris

Ok Port Redirection is not the answer. Anyone know enough about DLink
software to suggest the correct method. I would also appreciate another
method , than ftp, to solve my large transfer needs between work and
home.

Don

On 6/3/04 21:23, in article 1ga8wny.4h6zbo1yxldoN%phrje@warwick.ac.uk, "Don
McKenzie Paul" <phrje@warwick.ac.uk> wrote:

>> Getting incoming ftp to work is a bit of a bugger, because it is a very
>> broken protocol that requires multiple ports, and you don't know what
>> they'll be ahead of time (<URL:http://slacksite.com/other/ftp.html>). See
>> if you can find a better protocol.

> Ok Port Redirection is not the answer. Anyone know enough about DLink
> software to suggest the correct method. I would also appreciate another
> method , than ftp, to solve my large transfer needs between work and
> home.

FTP gets very messy through firewalls. Try simply using AFP. But first I
would get the Airport out of the loop to prove that you can t least get
through the firewall. Then add complexity until something breaks.



Yours,

Clive Sweeting,

Sweet-Apple: Mac technical support & sales in Bath, Bristol and Wiltshire.
Tel 01225 864689, mobile 0777 6075050
email: info@sweet-apple.co.uk
web: http://www.sweet-apple.co.uk

Bonge Boo! <sweetapple@btinternet.com> wrote:

> On 6/3/04 21:23, in article 1ga8wny.4h6zbo1yxldoN%phrje@warwick.ac.uk, "Don
> McKenzie Paul" <phrje@warwick.ac.uk> wrote:
>
> >> Getting incoming ftp to work is a bit of a bugger, because it is a very
> >> broken protocol that requires multiple ports, and you don't know what
> >> they'll be ahead of time (<URL:http://slacksite.com/other/ftp.html>). See
> >> if you can find a better protocol.
>
> > Ok Port Redirection is not the answer. Anyone know enough about DLink
> > software to suggest the correct method. I would also appreciate another
> > method , than ftp, to solve my large transfer needs between work and
> > home.
>
> FTP gets very messy through firewalls. Try simply using AFP. But first I
> would get the Airport out of the loop to prove that you can t least get
> through the firewall. Then add complexity until something breaks.
>
>
>
> Yours,
>
> Clive Sweeting,
>
> Sweet-Apple: Mac technical support & sales in Bath, Bristol and Wiltshire.
> Tel 01225 864689, mobile 0777 6075050
> email: info@sweet-apple.co.uk
> web: http://www.sweet-apple.co.uk

....but at work I have a unix box. Would that do AFP?? Or am I being
silly?

Don

On 7/3/04 12:42 am, in article 1ga95wt.wyqo6r11hv1eeN%phrje@warwick.ac.uk,
"Don McKenzie Paul" <phrje@warwick.ac.uk> wrote:

> ...but at work I have a unix box. Would that do AFP?? Or am I being
> silly?

You've got a Unix box at both ends ;-) so try scp. You'll need to allow port
22 through your router, and enable "Remote Login" in your Mac's System
Preferences. "Remote Login" is Apple-speak for ssh/scp.

Cheers,

Chris

On 7/3/04 0:42, in article 1ga95wt.wyqo6r11hv1eeN%phrje@warwick.ac.uk, "Don
McKenzie Paul" <phrje@warwick.ac.uk> wrote:

> ...but at work I have a unix box. Would that do AFP?? Or am I being
> silly?

If you stick netatalk on it. But if you are happy going the SSH route, then
do as Chris says.

Personally I don't like the idea of remote login, mainly due to the fact
that it enables remote control of the machine, whereas FTP or ASP are just
file sharing. Also I would (in my ignorance) imagine your average hacker
would be pretty bored by the idea of hacking AFP, but might be more
interested in trying to have a peek at SSH/SCP. Security through being
inconspicuous.

But as long as you have secure passwords I guess its fine.

Not being silly. I was assuming you would have a Mac at the other end. I
forget OS X has made things a much expanded ecosystem. My bad.

Chris Ridd <chrisridd@mac.com> wrote:

> > ...but at work I have a unix box. Would that do AFP?? Or am I being
> > silly?
>
> You've got a Unix box at both ends ;-) so try scp. You'll need to allow port
> 22 through your router, and enable "Remote Login" in your Mac's System
> Preferences. "Remote Login" is Apple-speak for ssh/scp.

I use rsync to move stuff between some Linux severs I use. This is how I
do it (you run this command on the source machine, not the destination.
You may need to do it as sudo if you're trying to copy files for which
you don't have all the requisite permissions)

rsync -avz -e ssh <path> <username>@<destination>:<destination path>

<path> is the file or directory you want to copy
<username> is your username on the destination machine
<destination> is the address of the destination machine
<destination path> is the directory you want <path> to end up in

The options for the rsync are:

-a = preserve user/permissions metadata, v = verbose, z = compress
-e ssh = use ssh

This uses ssh, which is port 23.

Daniele
--
Apple Juice Ltd
Chapter Arts Centre
Market Road www.apple-juice.co.uk
Cardiff CF5 1QE 029 2019 0140

On 7/3/04 4:32 pm, in article
1gaachu.4jw634pv60mtN%real-not-anti-spam-address@apple-juice.co.uk, "D.M.
Procida" <real-not-anti-spam-address@apple-juice.co.uk> wrote:

> This uses ssh, which is port 23.

22 :-)

Telnet's port 23. I forget what's what too, but a quick look at
/etc/services usually helps.

Cheers,

Chris