Can two legs of a router be configured to be in the same subnet?

can you provide a diagram similar to this
I am doing CNNA so this was created with Cisco Packet tracer which is only available to Cisco Students

I had this same issue on Win-7 machines with 6.1.1 packet tracer. I had to install Java 7.67 32-bit for the browser(IE 11-32-bit even though these are 64 bit boxes) and then uninstall and re-install packet tracer to get the psta player to work. Just installing 32-bit Java did not solve the problem out right. Java 7.65 had issues with running plugins. I had a lab of 30 machines to do this on. I assume 6.1 needs the 32-bit version of Java to run (7.65 or 8.25 32-bit would not work) and this corrupted the install because the psta player did not load. After installing the Java and re-installing PT 6.1 the ptsa player would load and run. You will be prompted to update Java-choose "later"-run and continue when prompted.

According to my experience and knoledge: the Cisco 2900 and 3900 series platforms have collaboration feature parity with the Cisco 2800 and 3800 Series platforms, so all of the following collaboration capabilities and solutions are present:
• Cisco Unified Survivable Remote Site Telephony (SRST)
• Cisco Unified Border Element
• Time-division multiplexing public-switched-telephone-network (TDM PSTN) and private-branch-exchange (PBX) gateways
• VoiceXML contact-center gateways
• Cisco Unified Communications Manager (UCM) media resources (allowing conferencing, transcoding, and Media Termination Point [MTP])
• Resource Reservation Protocol (RSVP) Agent
• Cisco Unified Communications Manager Express (CME)
• Cisco Unified SIP Proxy
• Gatekeeper

Cisco 3900 Series Routers

Bruce,

Is the goal to use a different VLAN for each access point (AP)? If so then you will need to configure each NetGear port to use the same VLAN as the AP that is connected to it. You will then need either a switched virtual interface (SVI) for each VLAN on the NetGear or a trunk port (802.1q) from the NetGear to the Cisco. I'm not sure the NetGear will support SVIs but it will support trunks. An SVI basically creates a gateway for each VLAN's subnet. For example, let's say AP1 uses VLAN 10 and the subnet is 10.0.10.0/24 while AP2 uses VLAN 20 with a 10.0.20.0/24 subnet. The NetGear will need 2 SVIs, one for each VLAN/subnet. The first SVI for VLAN 10 can be configured with IP address 10.0.10.1/24 while the second SVI can be configured with 10.0.20.1/24 for VLAN 20. These IP addresses will be the gateway for each VLAN. Finally, the NetGear would need to act as a router and route each VLAN's subnet to the Cisco device. Once again I don't believe the FS726TP supports this.

The other solution would be to create a VLAN trunk port between the NetGear and the Cisco device but I believe the Cisco RV042 does not support trunking. If it does the trunk would be configured to carry all of the VLANs to the Cisco device which would then have SVIs created on it.

If neither of the above is possible you would need to use the same VLAN for each AP and each of the interfaces on the NetGear and Cisco devices which negates the need for the VLANs.

I hope this helps.

Use an Ethernet cable to connect from the network-port on your computer to one of the LAN ports on the router.
Click Start
Click Run
Type CMD
Press Enter
Type IPCONFIG
Press Enter
You should see output like:
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

if the router has self-configured, and is ready for "wired" usage.

Then, start Internet Explorer.
Type http://192.168.1.1
Press Enter
Login to the web-server "inside" the router
Click to run the "Wireless Networking Setup Wizard" to configure it for "wireless" usage.

Its like router on stick configuration??enter the interface which you have to configure and in that interface as mentioned below
Hostname(config)#interface FastEthernet0/1
Hostname(config-if)#no ip address
Hostname(config-if)#no shutdown
Hostname(config)#interface FastEthernet0/1.1
Hostname(config-if)#encapsulation dot1Q 1 native
Hostname(config-if)#ip address x.x.y.y < subnet mask >
interface FastEthernet0/1.2
Hostname(config-if)#encapsulation dot1Q 2
Hostname(config-if)#ip address x.x.y.y < subnet mask >

Let's look at how to configure basic DHCP on an IOS-based router. For this example, we'll start off with the default configuration on a Cisco 2611 router running IOS 12.2. (The configuration should be the same—or very similar—on all IOS-based routers).
To begin, connect the router's Ethernet port to a switch, and connect the switch to a laptop, which will serve as the DHCP client.
To configure Cisco IOS DHCP, follow these steps, which include sample commands:
1.Configure an IP address on the router's Ethernet port, and bring up the interface. (On an existing router, you would have already done this.)
Router(config)# interface ethernet0/0
Router(config-if)#ip address 1.1.1.1 255.0.0.0
Router(config-if)# no shutdown2.Create a DHCP IP address pool for the IP addresses you want to use.
Router(config)# ip dhcp pool mypool3.Specify the network and subnet for the addresses you want to use from the pool.
Router(dhcp-config)# network 1.1.1.0 /8 4.Specify the DNS domain name for the clients.
Router(dhcp-config)#domain-name mydomain.com5.Specify the primary and secondary DNS servers.
Router(dhcp-config)#dns-server 1.1.1.10 1.1.1.116.Specify the default router (i.e., default gateway).
Router(dhcp-config)#default-router 1.1.1.17.Specify the lease duration for the addresses you're using from the pool.
Router(dhcp-config)#lease 78.Exit Pool Configuration Mode.
Router(dhcp-config)#exit

I hope this is helpfull for you.

Thanks

Vikrant

%SYS-4-P2_WARN: 1/Tag 0 The switch generates %SYS-4-P2_WARN: 1/Tag 0… messages.
This example shows the syslog output that you see when this error occurs:
%SYS-4-P2_WARN: 1/Tag [dec] on packet from [ether] port [chars],
but port's native vlan is [dec] This message indicates that an 802.1Q-tagged packet was received on a nontrunk port. The VLAN that is derived from the packet tag is different from the port native VLAN. In the error message:

• The Tag [dec] is the VLAN identifier from the packet.
  
• The [ether] is the host MAC address.
  
• The port [chars] is the port identifier.
  
• The second [dec] is the native VLAN number.
  

There is a possibility that the local port is incorrectly configured as an access port instead of a trunk port. Alternately, the remote side can have been configured as a trunk port instead of an access port.
Verify that the local port is not incorrectly configured as an access port instead of a trunk port. Also, verify that the remote side is not configured as a trunk port instead of an access port.