well, ARPs still take up bandwidth, and I'm not sure the scale you're talking about. I would recommend a tiered structure of gateways, each handling, say, 80bits worth of hosts or whichever you prefer, then route the gateways through each other. This also makes it easier for protocols such as SMB and NMB to function correctly, if they ever function ever again. Also, this allows you to create scopes for any incurred broadcasts you wish to send out:
you -.
__|__
your gateway-[ gateway A ]
| |
gateway B gateway C
| |
: : <-etc...
where A is 3ffe:0:0:1:1::, B is 3ffe:0:0:1:2::, and C is 3ffe:0:0:1:3::, you can easily make your broadcasts specific on one, many, specific, or all routers (and from each, hosts) without getting carpal tunnel syndrome.
don't forget anycast :)
--dan
Thu, 20 Feb 2003 16:42:56 +0100, "BEGIN, Thomas" <tbegin@tf1.fr> ×ÙÛÅÕÐÏÍÑÎÕÔÙÊ:
> Hello to all,
> I am wondering on IPv6 impacts over a company network's architecture.
> I mean, a big IPv4 network has to be divided in several VLANs in order to lighten the available bandwidth (sometimes for security reasons but it is not my interest in this case). And this because broadcast messages are received and examined by all network adapter.
> Thus comes my question: As there is no more broadcast messages but only multicast messages in IPv6, is there still a need to divide a big network in smaller networks (VLANs) ?
>
> Thanks
>
> Thomas BEGIN
>
>
> --
> To UNSUBSCRIBE, email to debian-ipv6-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Attachment:
pgptsP71hkv9e.pgp
Description: PGP signature