Quick question for those using ftpsesame on 3.4 that is up to date with
the stable source:
1. I was able to make the source but not make install the source.
I get:
install -c -s -o root -g bin -m 555 ftpsesame
usage: install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m
mode] [-o owner] file1 file2
install [-bCcpSs] [-B suffix] [-f flags] [-g group] [-m mode] [-o
owner] file1 ... fileN directory
install -d [-g group] [-m mode] [-o owner] directory ...
*** Error code 64
2. In the ruleset I can't use a line like the following...
anchor ftpsesame on { $int_if, $ext_if } pfctl issues an error.
3. I have four lines in the pf.conf that look like the following:
#for the anchors... rules placed in the macros section
all_exts = "{" vlan0 vlan2 vlan4 vlan6 vlan8 vlan10 vlan12
vlan14 vlan16 vlan18 vlan20 vlan22 "}"
all_ints = "{" vlan1 vlan3 vlan5 vlan7 vlan9 vlan11 vlan13
vlan15 vlan17 vlan19 vlan21 vlan23 "}"
#for ftpsesame to look up state on the 21 port
pass in log quick inet proto tcp from any to any port 21 flags
S/SA keep state
pass out log quick inet proto tcp from any to any port 21 flags
S/SA keep state
I need ftpsesame to listen on each or at least the external vlans,
right now I have not figured out a way to start ftpsesame so that it
will
listen on all the vlans. ftpsesame -i $ext_if will not work. It
gives the following:
# ftpsesame -i $all_exts
ftpsesame: option requires an argument -- i
usage: ftpsesame [-d] [-D level] [-i interface] [-q queue] [-t
tag] [expression]
I am assuming that $ext_if would be replaced by $all_exts in my
case. Is the $ext_if supposed to be a shell variable that I can expand
at the
shell with an echo or does ftpsesame look at the macro in pf.conf?
If the first case is the case, I can't.
Thanks,
Andrew Eaton
