Output of "shorewall show br0_fwd"
Shorewall-2.4.0 Chain br0_fwd - Wed Jul 13 12:19:46 ADT 2005
Counters reset Wed Jul 13 12:10:53 ADT 2005
Chain br0_fwd (1 references)
pkts bytes target prot opt in out source destination
10 1921 dynamic all -- * * 0.0.0.0/0 0.0.0.0/0
state INVALID,NEW
10 1921 br0_mac all -- * * 0.0.0.0/0 0.0.0.0/0
state NEW
0 0 loc2net all -- * eth0 0.0.0.0/0 0.0.0.0/0
10 1921 ACCEPT all -- * br0 0.0.0.0/0 0.0.0.0/0
On Wed, 2005-07-13 at 07:38 -0700, Tom Eastep wrote:> Tom Eastep wrote:
> > Supernaut wrote:
> >
> >>Depending on which of the two adapters the DHCP request originates
from
> >>on the bridge. I have been trying to get rid of this from the log,
but
> >>I have not been successful. Other that this, shorewall works great
in
> >>this configuration. Does anyone have a suggestion?
> >>
> >
> > Please apply the attached patch:
> >
>
> Also, please forward the output of "shorewall show br0_fwd". The
patch
> shouldn''t be necessary if the current code is working correctly.
> -Tom
> --
> Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
> Shoreline, \ http://shorewall.net
> Washington USA \ teastep@shorewall.net
> PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
-------------------------------------------------------
This SF.Net email is sponsored by the ''Do More With Dual!''
webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar