Do secondary IP addresses on a router interface create, in effect, separate broadcast domains?
For example (using 24-bit masks):
ip address 192.168.1.1 secondary
ip address 10.1.1.1
Are PCs in the 192.168 subnet considered to be in a different broadcast domain than PCs in the 10.1 subnet? If so, then does that mean that broadcasts generated by devices in 192.168 will not be propagated across switches to devices in the 10.1?
More specifically, by default, a router will not forward a Layer 3 broadcast outisde the subnet. That's why, for example, when you create a user VLAN on a layer 3 switch and the DHCP server does NOT reside in the local VLAN, a "helper address" must be configured for that user VLAN. The router/L3 switch will NOT forward the DHCP Request broadcast from the end machine past the router's L3 boundary, so it will act as sort of a proxy and make the request to the DHCP server for the end user.
So, if I subnet 10.10.10.0 with a mask of 255.255.255.240 (/28), the first 2 subnets that would be created are:
For the 10.10.10.0 subnet, there will be 14 host addresses (10.10.10.1 - 14) with a broadcast address FOR THAT SUBNET ONLY of 10.10.10.15.
For the 10.10.10.16 subnet, there will be 14 usable host addresses, too, (10.10.10.17-10.10.10.30), and a braodcast address FOR THAT SUBNET ONLY of 10.10.10.31.
VLANs are separate broadcast domain, not subnets. Infact you can have 2 subnets on the same VLAN. The best practice is to have different subnets for different VLAN.
If you have 192.168.1.0/24 and 10.1.1.0/24 on the same VLAN, subnets are on the same broadcast domain. If 192.168.1.0/24 is in the VLAN A e 10.1.1.0/24 on VLAN B they are in different broadcast domains.
The answer to your question is: secondary IP addresses on a router interface don't create separate broadcast domains.
> Do secondary IP addresses on a router interface create, in effect, separate broadcast domains?
> Are PCs in the 192.168 subnet considered to be in a different broadcast domain than PCs in the 10.1 subnet?
Different IP subnet, same broadcast domain. All devices on that broadcast domain will listen to the same broadcast regardless their IP subnet. You need a switch to break IP subnets segments located in the same geographic location in order to have different broadcast domains.
> If so, then does that mean that broadcasts generated by devices in 192.168 will not be propagated across switches to devices in the 10.1?
Edison, so what you are saying is that a user on subnet 10.10.1.0/24 (Subnet A) and another on 10.10.2.0/24 (Subnet B) -- lets say these are 2 subnets hanging off of ethernet0 and ethernet1, respectively, of the same router -- are on different subnets but the same broadcast domain?
If so, do you mean that all users on Subnet B are going to receive the DHCP Request broadcast of a user on subnet A?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...