I think this has something to do with the way our multiple gateways
work.  Since pftpx traffic isn't being affected by route-to since its
coming from the local machine.  Maybe Bill can chime in here.

Scott


On 9/13/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> yeah.. thats what scott's instructions say.  which I did before saying
> that it didn't work :)
> 
> -Matt
> 
> On Tue, 2005-09-13 at 12:22 -0500, Erik Kristensen wrote:
> > Log into command line and run pftpx.
> >
> > -Erik
> >
> >
> > On Tue, 13 Sep 2005 12:13:37 -0500, Matthew Lenz wrote
> > > Nope.  I can still ftp just fine from a box on my LAN net .. But
> > > can't ftp out from my OPT2 net.  I can http and ntp out from my OPT2
> > > net just fine.
> > >
> > > -Matt
> > >
> > > On Tue, 2005-09-13 at 11:21 -0400, Scott Ullrich wrote:
> > > > Does "killall pftpx && pftpx" from the shell fix it?
> > > >
> > > > Scott
> > > >
> > > > On 9/12/05, Matthew Lenz <[EMAIL PROTECTED]> wrote:
> > > > > I've a:
> > > > >
> > > > > *   LAN net   *   *   *   Default LAN -> any
> > > > >
> > > > > for my LAN.. but on OPT 2 I've got:
> > > > >
> > > > > TCP/UDP   OPT2 net   *   hostaliashere   21 (FTP)
> > > > > TCP/UDP   OPT2 net   *   hostaliashere   20
> > > > >
> > > > > I can ftp anywhere I want on from the LAN network but I cannot for the
> > > > > life of me get ftp to work on OPT 2.  Any ideas on what to check?  
> > > > > I've
> > > > > taken a look at the status.php page to make sure all the rules are 
> > > > > being
> > > > > added and that the hostalias is translated into the correct internet 
> > > > > ip.
> > > > > Everything looks perfect but its a no go (yeah I have outbound nat
> > > > > enabled for all my LAN/OPT interfaces.  I am accessing internet ntp 
> > > > > and
> > > > > internet http sites just fine from these networks.
> > > > >
> > > > > -Matt
> > > > >
> > > > >
> >
> >
> >
> 
>

Reply via email to