FRI 23 SEP 1988 22:26:20 CDT
The following errors occurred while attempting to send this mail file.
Best guess - SENDER is: TCP-IP @SRI-NIC.ARPA
*22.26.17 FROM: Invalid user/address string
----------------------------- ORIGINAL MESSAGE -------------------------------
Received: from ADMIN.BYU.EDU by SDSUVM.BITNET (Mailer X1.25) with BSMTP id
1067; Fri, 23 Sep 88 22:26:50 CST
Received: by BYUADMIN (Mailer X1.25) id 4721; Fri, 23 Sep 88 21:21:35 MDT
Date: Fri, 16 Sep 88 21:20:02 -0700
Sender: "(TCP-IP ARPA Discussions)" <Sender: "(TCP-IP ARPA Discussions)" <TCPIP-L@BYUADMIN>
From: "NASA ARC NSI Project Office Milo S. Medin"
Subject: Re: ICMP's & IP src addrs
X-To: Jerry Lotto <email@example.com>
To: jeff consoer <To: jeff consoer <CC57000@SDSUMUS>
In-Reply-To: Your message of 15 Sep 88 20:47:20 +0000. <firstname.lastname@example.org>
And I am sure that someones bridge will then decide that they know
where "the broadcast address" lives and stop forwarding it.
I have seen this (anti-social) behavior in DEC Lanbridges and it
does not bode well for the network until someone resets the beast.
Takes a while to find if you aren't looking for it.
Gerald Lotto - Harvard Chemistry Dept.
Actually, the Lanbridge, as all other bridges, looks at the source and
destination addresses in the ethernet frame, NOT in the IP header. So
this particular bug only is triggered by an ethernet frame with a
source address of FFFFFFFFFFFF. The Sun's do have an annoying bug when
turning around broadcast pings, but they do send them with the proper
ethernet frame addresses. I have seen Kinetics Appletalk 'gateways'
fail in such a way as to send ethernet frames with broadcast source addresses,
and this does cause problems on a Rev. E LANBridge. DEC is working a fix
though, and at least with LANBridges you can use RBMS to reset them
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:43:31 GMT