home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vxworks
- Path: sparky!uunet!ukma!nsisrv!tpocc.gsfc.nasa.gov!slater
- From: slater@tpocc.gsfc.nasa.gov (Don Slater)
- Subject: Re: Ethernets and backplane networks
- Message-ID: <1992Nov17.032922.13756@nsisrv.gsfc.nasa.gov>
- Keywords: Backplane Networks, Subnetting
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: tpocc.gsfc.nasa.gov
- Organization: Integral Systems, Inc / TPOCC Project
- References: <9211161235.AA20384@pickle.uk.ate.slb.com>
- Date: Tue, 17 Nov 1992 03:29:22 GMT
- Lines: 23
-
- We have gone through the same problem as we transitioned to a production
- (operational) environment with our VME backplane networks. We run three
- MVME147s in a crate, so the first in the gateway and has two net addresses.
- We use a class C net address and subnet with the first three bits of the
- fourth octet. So the netmask on the workstations is 255.255.255.224 and is
- ffffffe0 on the 147. The address field look like:
- inet address 150.144.62.45
- backplane addr 150.144.62.129:ffffffe0
- host address 150.144.62.41
- On your workstation, you then can do a static route as follows:
- /etc/route add net 150.144.62.128 150.144.62.45 1
- The first address designates a subnet because the 5 host_id bits are zeros.
-
- Hope at least some of this is helpful.
-
-
- | Don Slater Senior Technical Staff | Occasional System |
- | Integral Systems, Inc. CSC/LR | Administrator |
- | <slater@tpocc.gsfc.nasa.gov> |--------------------------|
- | 1100 West Street | "What part of 'No' don't |
- | LAUREL MD 20707-3587 USA | you understand?" |
-
-
-