On Sat, 2002-06-01 at 07:54, A. Harry Williams wrote: > If the network folks have an open mind, it isn't that much > different for them, they'll just have difficulty believing you'll > need that many subnets.
Pick a private address range that's different from what's used in the rest of the network, and you can use whatever you want (within reason). For example, if your network uses 10.x.y.z networks, and the network people are reluctant to give you many subnets in that range, just get them to give you as many addresses in that range to cover the number of hosts you have (plus some expansion room) and use a different RFC1918 network range (such as 172.[16-31].y.z) for the interfaces and zLANs in your Colony. As long as you set up your routing environment to suppress advertisement outside the Colony of the range you have used, this will work fine. Using other 'unused' ranges also lets you do more creative things with address allocation and naming conventions, to make configuration a bit easier. Oh, BTW, a slightly unrelated tip: set up a DNS server somewhere to manage the appropriate reverse-lookup (in-addr.arpa) zones for the address ranges you choose. It's really helpful for when you're troubleshooting, when you issue commands such as traceroute and friends, to see meaningful names appear instead of IP numbers. You can either give the address and name information to your LAN DNS admins, or set up a DNS server in your Penguin Colony somewhere and ask for the zones to be delegated to you. This is a relatively simple thing to do which is often overlooked or ignored by network admins. Cheers, Vic -- Vic Cross MACS mailto:[EMAIL PROTECTED] Networking, Linux, on zSeries and S/390
