On Tue, 2005-03-08 at 02:01:43 -0600, Kevin proclaimed...
> IIRC, this is exactly what 'dup-to' is designed for.
> It is important to note that dup-to works *exactly* like route-to, which means
> that the *ether* frame (assuming the dup-to destination is a hop via Ethernet)
> will be recreated (
On Tue, 1 Mar 2005 16:59:53 -0600, eric <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-03-02 at 11:22:15 +1300, Russell Fulton proclaimed...
> > I want to monitor the output from pflog in more or less real time. It
> > isn't clear to me what is the best (read simplest ;) way to do this.
> > What
eric wrote:
> Actually, you bring up an interesting idea; multiple interfaces for
> logging.
>
> Is there any possibility that a far-off-wish-list couple include the
> ability to route packets from a pflog device onto the wire and then
> monitor that traffic? Say on a monitor network or somethi
On Wed, 2005-03-02 at 11:22:15 +1300, Russell Fulton proclaimed...
> I want to monitor the output from pflog in more or less real time. It
> isn't clear to me what is the best (read simplest ;) way to do this.
> What I really want is a version of tcpdump that will effectively do a
> tail -f
Russell Fulton wrote:
> HI,
> I want to monitor the output from pflog in more or less real
> time. It isn't clear to me what is the best (read simplest ;) way
> to do this.
> What I really want is a version of tcpdump that will effectively do
> a tail -f on /var/log/pf. Ideally it would
