Actually, we have an interesting condition here. On general
ethernet applications we want to drop / reject the broadcasts.
On a home network using a cable modem as our link we will
want to not drop these. It seems (I'm still looking for the RFC
on this) that by design most cable modems send a steady
stream of BCAST packets destined for bootpc from the
ethernet side of the modem. This is presumably somekind of
IP management technique. While I can't think of the necesity
for this, it is aparently the way they are intended to behave.
That said, while looking into not logging these rejections,
would it be possible to add support for accepting broadcast
packets from specific hosts even though the DSTADDR is
255.255.255.255 ? TRUSTED does not pick these up as the
DSTADDR is not that of the extif.
Many thanks for all of your hard efforts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Neil,
Actually, we have an interesting condition here. On general
ethernet applications we want to drop / reject the broadcasts.
On a home network using a cable modem as our link we will
want to not drop these. It seems (I'm still looking for the RFC
on this) that by design most cable modems send a steady
stream of BCAST packets destined for bootpc from the
ethernet side of the modem. This is presumably somekind of
IP management technique. While I can't think of the necesity
for this, it is aparently the way they are intended to behave.
That said, while looking into not logging these rejections,
would it be possible to add support for accepting broadcast
packets from specific hosts even though the DSTADDR is
255.255.255.255 ? TRUSTED does not pick these up as the
DSTADDR is not that of the extif.
Many thanks for all of your hard efforts.
Logged In: NO
My apologies for not including my address in that comment
regarding cable modems. I'm using lynx and missed the login.
Dave
d-monnier@insightbb.com