home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!das.wang.com!wang!fitz
- From: fitz@wang.com (Tom Fitzgerald)
- Subject: Re: Broadcasting and Subnets
- Organization: Wang Labs, Lowell MA, USA
- Distribution: world,local
- Date: Mon, 07 Sep 92 07:58:23 GMT
- Message-ID: <bu77hc.i0l@wang.com>
- References: <2490@cronos.metaphor.com> <184hnoINN7tu@early-bird.think.com> <1992Sep3.090735.3657@arizona.edu> <186505INN7ei@early-bird.think.com> <1992Sep5.052037.19896@ccu1.aukuni.ac.nz>
- Sender: news@wang.com
- Lines: 18
-
- graeme@ccu1.aukuni.ac.nz ( Graeme Moffat) writes:
-
- > What I have observed in this situation (multiple subnets on same physical
- > cable) is that *many* hosts don't recognise x.y.z.255 as a broadcast on
- > subnet x.y.z when they are in subnet x.y.w, and respond by resending the
- > packet to MAC address 00FFBAD1DEAD, and an ICMP redirect to the original
- > sender! Lovely.
-
- Wow, I thought I'd seen all the bad side effects of mixing subnets on the
- same cable. What kind of systems are these?
-
- Another common side effect is that all the systems on x.y.w ARP for the IP
- address x.y.z.255, causing a real broadcast storm.
-
- --
- Tom Fitzgerald Wang Labs fitz@wang.com "I went to the universe today;
- 1-508-967-5278 Lowell MA, USA It was closed...."
-
-