I upgraded a 4.2-RELEASE machine to RELENG_4_3 tonight. This box has 2
nics, uses ipfw and bridging to act as a firewall. I've been using this
configuration with 4.2-RELEASE for ~200 days with superb results!
Now with the reboot into 4.3-RELEASE (RELENG4_3) 2001-06-05, I see this
message on console and in logs:
Jun 6 21:20:21 xxxxxx bdg_forward drop MULTICAST PKT
Jun 6 21:20:51 xxxxxx last message repeated 4 times
Jun 6 21:22:51 xxxxxx last message repeated 13 times
Jun 6 21:32:51 xxxxxx last message repeated 67 times
Jun 6 21:42:51 xxxxxx last message repeated 66 times
Jun 6 21:48:20 xxxxxx last message repeated 37 times
..etc..
Mind you, the bridging all appears to be working ok, at least from the hour
or two that it's been running. This is more of an annoyance, which I was
curious about. I managed to disable the log message by commenting line 462
of /usr/src/sys/net/if_ethersubr.c (1.70.2.15) and recompiling. Not the
best solution, which is why I'm writing here today.
My kernconf is quite basic, just these delta GENERIC:
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_FORWARD
options IPFIREWALL_VERBOSE_LIMIT=100
options IPFIREWALL_DEFAULT_TO_ACCEPT
options DUMMYNET
options BRIDGE
My firewall config in /etc/rc.firewall was not altered at all between
4.2-STABLE and 4.3-RELEASE.
I tried searching the mailing list archives and bug database, but didn't
come up with much.
Thanks for the time, anyone, who looks at this.
--
Christopher Schulte
Finger for PGP key, or for UNIX impaired:
http://noc.schulte.org/cgi-bin/noc/finger.cgi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message