rodney@picasso.cssc-syd.tansu.oz.au (Rodney Campbell) (06/13/91)
We am having a number of problems attempting to set up a number of Class C
subnets (both local and remote networks) on a Class B address and we were
hoping that someone may have done this and would be able to help me.
We have a class B address (149.135) to use for a network.
We wish to create a number of networks:
1) A Local research subnet on a separate class C address. (149.135.44)
2) on the same physical ethernet a class C subnet containing a number of
file servers ( this may later be moved to a different physical net for
load sharing ). (149.135.36)
3) A local contract staff subnet on a Class C. (149.135.48)
4) A local PC network on a separate Class C. (149.135.56)
5) A local MAC network via a Webster Multiport Gateway on the same Class
C. (149.135.56)
6) A network for machines which will be connected to the outside world.
(149.135.32)
We also have a number (3-4 at the moment) of sites with basically a
similar configuration (different Class C subnets under the same Class B
address) which will be linked together using WAN lines to a Multiport
MultiProtocol Router at each site.
The UNIX networks are basically all Sun/Solbourne SPARC Based machines
running SunOS 4.0.3 to 4.1.1. We also have (locally) a Sun SPARC with two
ethernet interfaces - one on the Research Net (149.135.44) and the other
interface going to a network of diskless machines etc. (149.135.40). This
machine will be a slave YP server to the main server(s) on the Server
Network (149.135.36).
Now the problem is that SunOS defaults all of this to a Class B network
which is fine for the local network except that all traffic goes everywhere
which defeats the purpose of the subnetting. (BTW each physical ethernet
will eventually be plugged into a separate ethernet port of the Multiport
Router). Also when the separate sites are connected I don't want all the
traffic to go everywhere.
I would much rather all of this be a number of class C networks that can
all talk to each other easily and to varying degrees.
How do I set up things like /etc/networks /etc/netmasks /etc/rc.boot
/etc/rc.local and ifconfig and route and NIS (any others???) to work so
that:
1) NIS which goes to subnets (149.135.36, 149.135.40, 149.135.44,
149.135.48, {149.135.32}) still works.
2) Any machine on these nets can talk to any other machine on any
other net.
3) The same physical nets with multiple class C nets on it can
coexist happily and transparently - eg broadcasts etc.
4) I can run DNS. (later).
Also if anyone has an Idea about setting up the Webster Multiport Gateway
to work with this setup?
Also the broadcast address on Suns defaults to NET.0 is this right or
should it be NET.255?
Can replies be sent to me directly and I will summarise.
Thanks in Advance,
Rodney...
_______________________________________________________________________________
Rodney Campbell - Telecom Aust |MHSnet: rodney@cssc-syd.tansu.oz.au
Network Services |Snail : 8th Floor, 91 York Street, Sydney 2000.
Customer Applications Research | or PO Box A226, Sydney South 2000, Australia.
& Development |Phone : +61 (0)2 364 3345 Fax: +61 2 262 3813tom@wcc.oz.au (Tom Evans) (06/20/91)
In article <1991Jun13.065802.9433@picasso.cssc-syd.tansu.oz.au>, rodney@picasso.cssc-syd.tansu.oz.au (Rodney Campbell) writes: > We am having a number of problems attempting to set up a number of Class C I tried to reply by mail, but metro.su.oz has problems and it bounced. Other responders may be having problems too - you may not get m(any) replies. So here it is posted. >Now the problem is that SunOS defaults all of this to a Class B network The definition of a "default" setting is "As shipped the equipment will be set up exactly the way you don't want it" :-). So you have to change it. On all machines. Don't miss any. Don't let anyone connect new machines onto the network (with the "default" config) or it may mess up your network. The Sun Installation manuals probably tell you how to do all this properly. I'd probably grep for "ifconfig" in /etc/rc*, and change it there, but what do I know? Address and subnet mask and broadcast too... >Also the broadcast address on Suns defaults to NET.0 is this right or >should it be NET.255? Either is right - as long as it is the same on all machines. Unless you have something so old on your network that it can't be convinced to use "NET.255" you should probably use "255". > 2) Any machine on these nets can talk to any other machine on any > other net. Now it gets interesting. If I read this right you want multiple separate class c subnets on the same ethernet cable. Fortunately IP allows this, All good and conforming IP implementations SHOULD reject all packets not destined to the correct subnet. However, this is where any "rogue" machines configured wrongly (i.e. configured as default) may wrongly receive things that they shouldn't, or may ARP for addresses on the subnet that it isn't on (in which case other machines won't be able to return packets to it although it can send). You need to configure an IP router to have multiple LOGICAL IP interfaces, with different IP addresses, but all connected to the same physical Ethernet interface. I think Cisco can do this. >Also if anyone has an Idea about setting up the Webster Multiport Gateway >to work with this setup? Set it up as a "normal" IP host with the correct subnetmask and broadcast address, and let the router connect everything together. It might be easiest if the router is designated as the "default router" on all machines - but note that it has a different IP address on each subnet. You'll probably want all subnets in /etc/networks, and proper entries in /etc/gateways - not necessary but it does "document" the network somewhat. ======================== Tom Evans tom@wcc.oz.au ** ADD ".au" MANUALLY (don't trust "reply") ** Webster Computer Corp P/L, 1270 Ferntree Gully Rd Scoresby, Melbourne 3179 Victoria, Australia 61-3-764-1100 FAX ...764-1179 A.C.N. 004 818 455