On 2000-10-02 21:04:53, William Jensen wrote:
> Call me goofy because my firewall decided it was going to stop working. I
> have
> the following line in for allowing ftp info back and forth...
>
> $IPT -A INPUT -p tcp ! --syn --source-port 20 --destination-port 1024:65535
> -j ACCEPT
>
> I als
Call me goofy because my firewall decided it was going to stop working. I have
the following line in for allowing ftp info back and forth...
$IPT -A INPUT -p tcp ! --syn --source-port 20 --destination-port 1024:65535 -j
ACCEPT
I also tried..port 21
$IPT -A INPUT -p tcp ! --syn --source-port 21
On Fri, 01 Sep 2000, Christoph Simon wrote:
> > Hi all,
> >
> > I've three machines behind a firewall provided by IP Masquerading (all
> > machines running Potato). One of this machines is a web server updated
> > by Windows Users by FTP.
> >
> > The problem is that conections provided inside a IP
>
> The problem is that conections provided inside a IP Masquerading
> environment can't transfer files. But in your homes (using a real IP
> connection) he can.
>
> Any hints?
>
Have you tried using passive mode to transfer the files ?
Mike
> Hi all,
>
> I've three machines behind a firewall provided by IP Masquerading (all
> machines running Potato). One of this machines is a web server updated
> by Windows Users by FTP.
>
> The problem is that conections provided inside a IP Masquerading
> environment can't transfer files. But in
Hi all,
I've three machines behind a firewall provided by IP Masquerading (all
machines running Potato). One of this machines is a web server updated
by Windows Users by FTP.
The problem is that conections provided inside a IP Masquerading
environment can't transfer files. But in your homes (usin
6 matches
Mail list logo