> Greg suggested that I do a tcpdump -s 96 -nleti pflog0 to see what was
> going on.
Do you have pflog_enable="YES"
Set in /etc/rc.conf ? Is pflog0 visible as up and running in the output of
ifconfig -a ?
>
> I tried that and got no data captured, not a single entry.
>
> one of my /etc/rc.con
Tirst Thanks to Volker and Greg
I did find an answer
I want to summarize it and then ask a second question.
Volker was right it was pass in proto udp rule that was needed but as
near as I could figure the bootps rule was not working for me.
so I added this rule to my firewall script
pass
On 12/23/-58 20:59, [EMAIL PROTECTED] wrote:
> I had a basic NAT setup that was almost working. dhcp requests on my
> lan were not
> getting answered by the gateway host.
>
> I looked at the firewall rules and figured it was because there wasn't a
> specific way to
> handle port 67 data (if shou
> could someone please explain the "right" way to do this, or point me
> to the right doc,
> I'm willing to learn if I can find the right teacher.
Make the 1st packet filtering rule
block log all
and from there read the firewall logs in real time with
tcpdump -s 96 -nleti pflo
Hello everyone, I'm a new freebsd user (been a linux user for some
time, so I'm
comfortable with unix-like os structures and the cli)
I'm trying to build a freebsd home router with the pf firewall, all
the documentation I'm
reading suggests that this is quite possible.
in fact, there are fa
