On Wed, 25 Aug 2004, Frederick Page wrote:
> since upgrading to firmware 1.1 one client (Debian Linux) keeps
> complaining (every few seconds the following message appears on the
> root console):
> 192.168.100.100 (this is m0n0wall) sent an invalid ICMP type 3, code 0
> to a broadcast 192.168.100.255 on eth0
> This is just annoying, there does not seem to be a problem, the Linux
> client can access the LAN and WAN just fine.
> The other clients (Windows XP and OpenBSD 3.5) do not seem to mind.
> "ifconfig -a" on the Linux-machine shows nothing unusual, MTU is 1500
> on eth0.
> I'm however wondering, why m0n0wall would send ICMP type 3 to the
Does it really think that's a broadcast address? What's the
netmask? Inconsistent netmasks will lead to different opinions about
what's a broadcast address.
If FreeBSD isn't broken, then it must have received a packet *from*
192.168.100.255, and didn't consider that to be a broadcast.