> More details please...  how do you start the proxies and what do the rules
in
> pf.conf look like?


Now I am starting the proxies via /etc/rc.local (or starting them by hand
with the same command and killing them with 'kill')

I'm just noticing that there is a binat on .217 (the ip that doesn't work)
and none on .146. Could this be the issue? Let's see. Yup. It was the binat
that was breaking it. Damn. Makes some sense I guess. Is there a way to do
this while using the binat?

> 
> 
> On 14-6-2012 18:31, James Chase wrote:
> > I already have 1 FTP server setup to use ftp-proxy with pf and it
> > works fine. I am trying to add a second. It seemed like this should be
> > straightforward - just add another ftp-proxy instance connected to the
> > proper servers and add some rules to pf.conf. This didn't work
> > (however the first FTP server continued to work).
> >
> >
> >
> > To debug, I tried swapping all the network settings from the working
> > server with the new FTP server I am trying to setup. So there would
> > still be only 1 FTP server coming through via pf and using the
> > syntax/rules that I already know work. This didn't work either. I
> > started the ftp-proxy in non-daemonize mode and I don't see any
> > connections coming in (OK, but now I see it doesn't show anything on the
> working connection either).
> >
> >
> >
> > Triple checked all my settings in WinSCP for my FTP connection. And
> > triple checked all my networking details in pf.conf and the ftp-proxy
> > startup. I see the packets arriving at the firewall, doesn't make it to
the FTP
> server.
> >
> >
> >
> > What am I missing here? Do I have to reboot the firewall or something?
> > If I sub in the network details from the original FTP server, that one
> > will work again.
> >
> >
> >
> > James

Reply via email to