From your diagram, it looks like you have a 3COM switch between the 1841 and the 172.16.0.6 device (Cisco Switch ?).
Any reasons you aren't connecting the 1841 directly to this device avoiding the extra hop on the 3COM switch ?
You can create the subinterfaces in the 1841 as you stated but keep in mind you need to trunk the link at the other end (3COM switch) so it can tag each VLAN you've created.
Based on your diagram, I recommend performing the interVLAN routing at the Core (4507 switch), send the default route over to the 1841 running as single interface -let's say 192.168.1.100/24- and do the NAT there.
You mentioned you don't have any VLANs, but that's what you are creating in the 1841 when configuring subinterfaces. You are terminating multiple LANs into the LAN port (trunk). In order for this to work, both links 3COM and 1841 must be in trunk mode. Your sample config, employing subinterfaces, will take care of the 1841 (make sure to denote the encapsulation dot1q) but you need to manually configure trunking in the 3COM, as well as VLANs.
Your diagram does not show a flat network on the 1841 LAN Port. You have four /24 networks when creating subinterfaces.
If your network is FLAT, what's the reason for creating subinterfaces ?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...