Sponsored Content
Special Forums IP Networking Routing across different subnets Post 302219237 by thomn8r on Monday 28th of July 2008 02:14:33 PM
Old 07-28-2008
Quote:
Originally Posted by era
Stupid question, can you ping 15.8.158.152 from the 15.255.16.xxx machines?
Yes, you can.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

communication problem between two subnets

We have two Sun Sparc systems running on the xxx.xxx.1.xxx network and can be access fine by machines on that subnet. We are able the ping one of the machines from the xxx.xxx.2.xxx network, but we are not able to ping or communicate with the other machine on the (1) subnet from the (2) subnet. ... (8 Replies)
Discussion started by: pyerj
8 Replies

2. AIX

Printing across subnets (Xerox)

All, I have a pSeries 550 and several Xerox printers I need to print to from there. I can define the printers via the Xerox "xpadmin" utility for all the machines locally (in my building, .244.xxx subnet), but if I go to a different subnet (say .131.xxx) I can not apply any changes. I can... (1 Reply)
Discussion started by: kjbaumann
1 Replies

3. Solaris

Solaris as router between two subnets

I have two networks which is not connected to each other. Each network has its own internet connection. I also have one Solaris machine with two NICs connected to both of the networks. How do I use the Solaris to connect both network so that hosts from either side of the network can... (9 Replies)
Discussion started by: Ahmad Pakhri
9 Replies

4. UNIX for Advanced & Expert Users

solaris zones on different subnets

Greetings, Having an issue with a multihomed global zone hosting zones on different subnets. The issue is with the dev zone that is hosted on the non-default network. Any help, other than going to exclusive IP, as I have one card for admin ntwk for both zones, would be appreciated. ... (1 Reply)
Discussion started by: 22blaze
1 Replies

5. Solaris

Jumpstart server over Multiple subnets

Hi, I need some recommendations as to how I can create a single jumpstart server over multiple subnets and what would be the best physical server for this purpose. Thanks . (1 Reply)
Discussion started by: gunnervarma
1 Replies

6. IP Networking

Using 'whois' to Retrieve all IPs/Subnets for an Organization

I manage a spam filter for the organization I work for. I've been trying to get the others here to stop white listing by domain name since that can be easily spoofed. One of the obstacles, however, is that there doesn't seem to be an easy way to determine the legitimate outgoing SMTP server IP... (0 Replies)
Discussion started by: deckard
0 Replies

7. IP Networking

routing to two subnets from a multi-homed server

We have two subnets, say 'domA' (192.168.0.0/24) and 'domB' (10.10.0.0/16). These subnets are connected through the router 'router01'. One server 'base01' has two network cards, configured to domA and domB subnets respectively. Now let's consider a host host01.domA (192.168.0.5) trying to... (0 Replies)
Discussion started by: amriksk
0 Replies

8. UNIX for Advanced & Expert Users

Rsyslog Monitoring Multiple Subnets

Hello, I have a rsyslog server configured on a server with two IP's on different Class C subnets. By default, it receives all logs from servers on these two subnets. The problem I have is that I want the Rsyslog server to monitor other subnets as well. Is there anyway to do this? I have searched... (0 Replies)
Discussion started by: mojoman
0 Replies

9. Shell Programming and Scripting

Breaking out ip subnet to smaller subnets

I have a script and it works fine, but I am sure this can be shrunk down to something much better. I would appreciate someone taking a crack at it for me. What it does is take the ip block submitted and breaks it out down to /24's. #!/bin/ksh ipadd=${1} octet1=`echo $ipadd | nawk -F.... (3 Replies)
Discussion started by: numele
3 Replies

10. IP Networking

DNS and two subnets

Hi guys I started to work in a small company which doesn't have infrastructure and I need to built it. My problem is: I am a student with theoretical knowledge but without practical one so I don't have any ideas how to solve my problem. I installed on CentOS 6.4 DNS and DHCP. This... (1 Reply)
Discussion started by: solaris_user
1 Replies
CIDR(7) 						 Miscellaneous Information Manual						   CIDR(7)

NAME
CIDR, cidr - Classless Inter-Domain Routing DESCRIPTION
Classless Inter-Domain Routing, also known as CIDR, is an Internet addressing architecture designed to solve two problems: the growth in the size of the routing tables in the top-level routers and the exhaustion of Class B address space. To solve these problems, CIDR relies on a new means of distributing the allocation of Internet address space and on a concept known as route aggregation. For an up-to-date list of Frequently Asked Questions (FAQ) about CIDR, retrieve the CIDR FAQ from either of the following locations: http://www.rain.net/faqs/cidr.faq.html http://www.ibm.net.il/~hank/cidr.html Address Space Allocation The traditional 32-bit Internet address is divided into a network part and a host part. The size of each part depends on the network class to which the address belongs. The following table shows the sizes of each part for Class A, Class B, and Class C networks. ----------------------------------------------------------------------- Network Size of Network Part (in bits) Size of Host Part (in bits) ----------------------------------------------------------------------- Class A 8 24 Class B 16 16 Class C 24 8 ----------------------------------------------------------------------- In this scenario, each physical network or LAN uses a single network number. While the idea seems sound, most organizations seldom create a single network containing thousands of hosts, choosing instead to divide their networks using routers. For organizations with Class B addresses, this wastes valuable addresses. To cope with the various network topologies, the concept of subnetworks or subnetting emerged. In a subnet, the network part of the address consists of the network part and a portion of the host part. The bitmask convering these two parts is called the subnet mask. The area of the host part that is covered by the subnet mask identifies the subnet. This process allows you to identify individual LANS by their subnet number within the larger network number. The only way to communicate between two or more subnets is through a router. Currently, routers make routing decisions by extracting the network portion of an IP address and looking it up in their routing table. This forces some IP routers to store each network number connected to the Internet in their routing table. For many organizations, a Class C network (254 hosts) is too small, whereas a Class B network (65534 hosts) is too large, resulting in poor address space utilization. Route Aggregation The Internet Advisory Board (IAB) and Internet Engineering Task Force (IETF) have decided to eliminate the notion of IP address classes and to direct routers to make routing decisions based on a variable-length, contiguous IP address prefix. This is what is meant by classless routing. Under this scenario, an Internet Service Provider (ISP) that had previously announced 256 contiguous Class C networks to the Internet, now only has to announce a single prefix, with 16 significant bits, for all these networks. This prefix is referred to as an aggregate, and the network is referred to as a supernet. If the ISP needed to add additional customers to its network, it could do so without modifying the routing announcements to the rest of the Internet. Aggregating networks reduces the number of routers in a network and enables you to make optimum use of bridges and high-speed switches. EXAMPLES
This section describes one example of a Class C supernet. If organization A requires 1000 addresses, it might have the following Class C networks: 212.221.32.0, 212.221.33.0, 212.221.34.0, and 212.221.35.0. Using current Class C addressing specifications, organization A's network mask and network numbers are as follows: /------------24 bits----------- 1111 1111 1111 1111 1111 1111 0000 0000 = mask 255.255.255.0 1101 0100 1101 1101 0010 0000 0000 0000 = network 212.221.32.0 1101 0100 1101 1101 0010 0001 0000 0000 = network 212.221.33.0 1101 0100 1101 1101 0010 0010 0000 0000 = network 212.221.34.0 1101 0100 1101 1101 0010 0011 0000 0000 = network 212.221.35.0 --------network address-------/ --host--/ address Typically, software compares all network address bits that are covered by the network mask (1 bits) to determine the effective network address. Because the network addresses covered by the 24-bit network mask are different, traffic from one network to another requires a router. In addition, routes to each of the four networks are advertised to the rest of the Inter- net, and occupy space in the routers' routing tables. Under CIDR rules, organization A could shorten their network mask from 24 bits under current rules to 22 bits. The result is a network mask of 255.255.252.0, as follows: /-----------22 bits---------- 1111 1111 1111 1111 1111 1100 0000 0000 = mask 255.255.252.0 1101 0100 1101 1101 0010 0000 0000 0000 = network 212.221.32.0 1101 0100 1101 1101 0010 0001 0000 0000 = network 212.221.33.0 1101 0100 1101 1101 0010 0010 0000 0000 = network 212.221.34.0 1101 0100 1101 1101 0010 0011 0000 0000 = network 212.221.35.0 1101 0100 1101 1101 0010 0011 0000 0000 = network 212.221.35.0 -------network address------/----host----/ address Because the network addresses covered by the 22-bit network mask are the same, traffic from one network to another does not require a router. Instead, the software uses Address Resolution Protocol (ARP) to acquire direct connection to the network. The address 212.221.32.0 with the mask 255.255.252.0 identifies all networks belonging to organization A. Expressed in CIDR format, orga- nization A's network address is 212.221.32.0/22. This effectively aggregates all routes under one network address. This also means that only one route is advertised to the rest of the Internet. If a router sees traffic addressed to 212.221.33.5 with the netmask of 255.255.252.0, the traffic is addressed to network 212.221.32.0. Using a network mask of 255.255.252.0, organization A can have a single bridged network of 1022 hosts (hosts 0 and 1024 are reserved for the broadcast address). Using a network mask of 255.255.254.0, organization A can have two bridged networks of 510 hosts (host 0 and 512 are reserved for the broadcast address). These techniques are not currently implemented in all host software, and should be implemented in networks with great care. However, the IETF suggests that host software be modified to allow for classless routing. RELATED INFORMATION
Commands: netstat(1), ifconfig(8), route(8). RFC1517, Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) RFC1518, An Architecture for IP Address Allocation with CIDR RFC1519, CIDR Address Strategy RFC1520, Exchanging Routing Information Across Provider Boundaries in the CIDR Environment delim off CIDR(7)
All times are GMT -4. The time now is 10:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy