On 10 March 2010 c. 12:09:07 tsg12...@gmx.de wrote:
> Apologies first.
>
> My first thought after waking up today was "I mixed IPs and IFs".
> Sorry for posting that...
>
> Remaining question second.
>
> The filtering does not seem to get "populated" by
> ftp-proxy.
>
> A rule like:
> pass in on $c
tsg12...@gmx.de wrote:
A rule like:
pass in on $client_if proto { tcp udp } from $client \
to 127.0.0.1 port ftp
does not do the trick, I still have to use something like:
pass in on $client_if proto { tcp udp } from $client \
to 127.0.0.1
(opening everything up for the ftp data connection myse
Apologies first.
My first thought after waking up today was "I mixed IPs and IFs".
Sorry for posting that...
Remaining question second.
The filtering does not seem to get "populated" by
ftp-proxy.
A rule like:
pass in on $client_if proto { tcp udp } from $client \
to 127.0.0.1 port ftp
does no
Hi list,
I was trying to set up ftp-proxy for use with a client
(OpenBSD 4.6 workstation, passive ftp only) behind a
firewall (4.5).
I have set up pf.conf on the firewall according to pf
user's guide.
All ftp-proxy anchors have been put first (nat/rdr before
any nat/rdr rules, filtering before a
4 matches
Mail list logo