You can add a secondary IP address for an additional network like 192.168.2.0/24. See below:
Router#sho run int fa1/0
Current configuration : 164 bytes
ip address 192.168.2.1 255.255.255.0 secondary
ip address 192.168.1.1 255.255.255.0
If the users are receiving their IP addresses dynamically (i.e. DHCP) you could switch over to a /23 network like 10.1.0.0/23. This would give you 10.1.0.2 - 10.1.1.254 for the user?s IP addressing assuming 10.1.0.1 would be the router's IP address.
Also note that depending on your user?s traffic and your layer 2 network design you could start to run into problems once you get over 200+ users.
Yes the two subnets can talk to each other. There might be some variability in how they do this. (1) Since both subnets are in the same broadcast domain they will hear each other's ARP requests and ARP responses and might learn each others MAC addresses and can communicate directly. (2) If a device in subnetA wants to communicate with a device in subnetB it might send the packets to the router and the router would forward the packet and the router would also generate an ICMP redirect packet to the originating device indicating that the device can communicate without needing the router to forward. If the device honors the redirect then the devices will communicate directly. (3) the devices might send their traffic to their default gateway (the router) since they believe that they are in different subnets and the router would forward traffic between the devices. This is the least efficient method, but it does work and communication would be successful.
One thing to note in your posting is that GWA and GWB are the same device. Your posting draws them as if they were separate, but they are the same device. So it is really:
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...