Just connect the trunk port on your switch to FastEthernet0 on your router which you have configured as a trunk port. Also make sure that whatever equipment you have on those two networks have configured 192.168.10.80 and 192.168.1.69 respectively as default gateways. You should also have ip routing
enabled which it should be by default.
It's very much like the typical "router on a stick" except for using vlan interfaces instead of subinterfaces.
If it doesn't work, verify the trunk link with show interface status
and show interfaces trunk
. You can also verify the vlan interfaces with show ip int brief
and make sure they are up. If they are down it's probably because you haven't created the layer 2 vlans or because they are not allowed on the trunk.
The non-Cisco switch will be running MST if it is using Rapid STP. You need to make sure your Cisco switches are also running MST, not the default PVST+ or Rapid PVST+. You need to run the same STP version on all the connected switches for STP to work correctly.
Once you fix all that, make sure that the native VLANs on each end of a link are the same. Cisco switches will use CDP to verify this, but your non-Cisco switch probably doesn't have CDP, so it may ignorant of the mismatch.
EDIT per the comment:
Different versions of STP use different BPDUs to establish the root switch and root ports. Cisco PVST+ (including Rapid PVST+) uses a separate STP instance for each VLAN, while MST uses one instance of STP for each user-defined group of VLANs, and, unless you take pains to do this, the two STP versions probably won't match in this regard. When mixing the two, it is normally best to use MST, and correctly match the VLANs to the STP groups. This works well, but it is certainly more work than using the Cisco STP version everywhere.
It is possible to interoperate the two versions, but it can be difficult to get it right so that the root and root ports are correctly identified on each switch in the layer-2 domain. Having inconsistent root switches and root ports can cause STP loops resulting in broadcast storms which can bring down the entire layer-2 domain.
It is much easier to use a single STP version across all your switches, and, unfortunately for added complexity, that would probably be be MST when mixing Cisco and non-Cisco switches.
Best Answer
In your sheme you need 3 trunk links (if there is only one physical connection between these switches):
The routing between these subnets will be handled by the L3 switch. so if pc 0 wants to ping to pc 1:
PC0 > (gets it on his vlan 1 port) switch 1 (trunk) > switch 0 (trunk) > switch 2 (trunk) > L3SW (vlan1 > vlan2) (sends it out of its trunk port) > switch 2 (trunk) > switch 0 (trunk) > switch 1 (vlan2) > pc1