Cisco Systems Getting router to talk to client subnet/VLAN

Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Getting router to talk to client subnet/VLAN David L. West 08-23-08
Posted by David L. West on August 23, 2008, 4:33 pm
Please log in for more thread options


Having a routing problem I need help with:

* All my routers and switches are on 172.16.0.0/23, VLAN 2 (mgmt vlan)

* My client VLANs are: VLAN101=172.16.2.0/23, VLAN102=172.16.4.0/23, etc

* The machine I use to manage the network is called NMS and is on
172.16.3.99 (VLAN 101)

* A linux machine runs NAT/DHCP/DNS for the clients. It has IPs in each
VLAN *except* VLAN 2.

* iptables on the linux machine prohibits interVLAN routing but expressly
allows all traffic to/from NMS.

Here's the problem: all the routers and switches can ping each other, and
NMS can ping them as well. But the routers/switches cannot ping NMS, and I'm
don't understand why. I tried making an interface on the linux
box within VLAN2, and can then ping that interface from the router, but that
eliminates the ability of NMS
to ping the router.

More config info follows.

=====================================================
Core router:

interface GigabitEthernet0/1.2
description v002-internal-mgt-vlan
encapsulation dot1Q 2
ip address 172.16.0.1 255.255.254.0
!
interface GigabitEthernet0/1.20
description v020-public-ip-inside
encapsulation dot1Q 20
ip address 76.61.48.1 255.255.255.240
no ip unreachables
!
ip default-gateway 208.05.19.73
ip route 0.0.0.0 0.0.0.0 208.05.19.73
ip route 76.61.48.0 255.255.255.0 Null0 15

======================================================

Core Switches (there are a series of these, 172.16.0.2-172.16.0.6)

interface Vlan2
description v002-internal-mgt-vlan
ip address 172.16.0.2 255.255.254.0
no ip redirects
no ip route-cache

======================================================

Linux box ROMULUS (NAT, DHCP, DNS, NTP)

eth0 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FD
inet addr:76.61.48.3 Bcast:76.61.48.15 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1586 errors:0 dropped:0 overruns:0 frame:0
TX packets:1894 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:395674 (386.4 KiB) TX bytes:479735 (468.4 KiB)
Interrupt:17

eth1 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2284 errors:0 dropped:0 overruns:0 frame:0
TX packets:1712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:603934 (589.7 KiB) TX bytes:431245 (421.1 KiB)
Interrupt:18

eth1.101 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
inet addr:172.16.2.1 Bcast:172.16.3.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1266 errors:0 dropped:0 overruns:0 frame:0
TX packets:890 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:392524 (383.3 KiB) TX bytes:203254 (198.4 KiB)

eth1.102 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
inet addr:172.16.4.1 Bcast:172.16.5.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:490 errors:0 dropped:0 overruns:0 frame:0
TX packets:255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83958 (81.9 KiB) TX bytes:55310 (54.0 KiB)

<and so on for each subnet>

NMS Workstation:

Physical Address. . . . . . . . . : 00-19-21-13-FB-FD
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.3.99(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 172.16.2.1
DHCP Server . . . . . . . . . . . : 172.16.2.1
DNS Servers . . . . . . . . . . . : 172.16.2.1 172.16.2.2


Posted by Trendkill on August 23, 2008, 5:52 pm
Please log in for more thread options


> Having a routing problem I need help with:
>
> * All my routers and switches are on 172.16.0.0/23, VLAN 2 (mgmt vlan)
>
> * My client VLANs are: VLAN101=3D172.16.2.0/23, VLAN102=3D172.16.4.0/23, =
etc
>
> * The machine I use to manage the network is called NMS and is on
> 172.16.3.99 (VLAN 101)
>
> * A linux machine runs NAT/DHCP/DNS for the clients. =A0It has IPs in eac=
h
> VLAN *except* VLAN 2.
>
> * iptables on the linux machine prohibits interVLAN routing but expressly
> allows all traffic to/from NMS.
>
> Here's the problem: all the routers and switches can ping each other, and
> NMS can ping them as well. But the routers/switches cannot ping NMS, and =
I'm
> don't understand why. =A0I tried making an interface on the linux
> box within VLAN2, and can then ping that interface from the router, but t=
hat
> eliminates the ability of NMS
> to ping the router.
>
> More config info follows.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> Core router:
>
> =A0 =A0interface GigabitEthernet0/1.2
> =A0 =A0 description v002-internal-mgt-vlan
> =A0 =A0 encapsulation dot1Q 2
> =A0 =A0 ip address 172.16.0.1 255.255.254.0
> =A0 =A0!
> =A0 =A0interface GigabitEthernet0/1.20
> =A0 =A0 description v020-public-ip-inside
> =A0 =A0 encapsulation dot1Q 20
> =A0 =A0 ip address 76.61.48.1 255.255.255.240
> =A0 =A0 no ip unreachables
> =A0 =A0!
> =A0 =A0ip default-gateway 208.05.19.73
> =A0 =A0ip route 0.0.0.0 0.0.0.0 208.05.19.73
> =A0 =A0ip route 76.61.48.0 255.255.255.0 Null0 15
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
> Core Switches (there are a series of these, 172.16.0.2-172.16.0.6)
>
> =A0 =A0interface Vlan2
> =A0 =A0 description v002-internal-mgt-vlan
> =A0 =A0 ip address 172.16.0.2 255.255.254.0
> =A0 =A0 no ip redirects
> =A0 =A0 no ip route-cache
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>
> Linux box ROMULUS (NAT, DHCP, DNS, NTP)
>
> =A0 =A0eth0 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FD
> =A0 =A0 =A0 =A0 =A0 =A0 =A0inet addr:76.61.48.3 =A0Bcast:76.61.48.15 =A0M=
ask:255.255.255.240
> =A0 =A0 =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0=
Metric:1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX packets:1586 errors:0 dropped:0 overruns:0 =
frame:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0TX packets:1894 errors:0 dropped:0 overruns:0 =
carrier:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:1000
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX bytes:395674 (386.4 KiB) =A0TX bytes:479735=
(468.4 KiB)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Interrupt:17
>
> =A0 =A0eth1 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> =A0 =A0 =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0=
Metric:1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX packets:2284 errors:0 dropped:0 overruns:0 =
frame:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0TX packets:1712 errors:0 dropped:0 overruns:0 =
carrier:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:1000
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX bytes:603934 (589.7 KiB) =A0TX bytes:431245=
(421.1 KiB)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Interrupt:18
>
> =A0 =A0eth1.101 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> =A0 =A0 =A0 =A0 =A0 =A0 =A0inet addr:172.16.2.1 =A0Bcast:172.16.3.255 =A0=
Mask:255.255.254.0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0=
Metric:1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX packets:1266 errors:0 dropped:0 overruns:0 =
frame:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0TX packets:890 errors:0 dropped:0 overruns:0 c=
arrier:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX bytes:392524 (383.3 KiB) =A0TX bytes:203254=
(198.4 KiB)
>
> =A0 =A0eth1.102 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> =A0 =A0 =A0 =A0 =A0 =A0 =A0inet addr:172.16.4.1 =A0Bcast:172.16.5.255 =A0=
Mask:255.255.254.0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0=
Metric:1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX packets:490 errors:0 dropped:0 overruns:0 f=
rame:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0TX packets:255 errors:0 dropped:0 overruns:0 c=
arrier:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0RX bytes:83958 (81.9 KiB) =A0TX bytes:55310 (5=
4.0 KiB)
>
> =A0 =A0 <and so on for each subnet>
>
> NMS Workstation:
>
> =A0 =A0Physical Address. . . . . . . . . : 00-19-21-13-FB-FD
> =A0 =A0DHCP Enabled. . . . . . . . . . . : Yes
> =A0 =A0Autoconfiguration Enabled . . . . : Yes
> =A0 =A0IPv4 Address. . . . . . . . . . . : 172.16.3.99(Preferred)
> =A0 =A0Subnet Mask . . . . . . . . . . . : 255.255.254.0
> =A0 =A0Default Gateway . . . . . . . . . : 172.16.2.1
> =A0 =A0DHCP Server . . . . . . . . . . . : 172.16.2.1
> =A0 =A0DNS Servers . . . . . . . . . . . : 172.16.2.1 172.16.2.2

Can you paste a show ip route 172.16.2.0 on the routers please. Can
you source a ping (type ping, hit enter, when it gets to extended
commands, hit 'y', then use a source of the 172.16.2.0 address on the
router. Does it work?

Posted by David L. West on August 23, 2008, 6:31 pm
Please log in for more thread options


Solution: Add a subinterface on the router in the subnet and VLAN that also
contains the NMS. D'oh.

> Having a routing problem I need help with:
>
> * All my routers and switches are on 172.16.0.0/23, VLAN 2 (mgmt vlan)
>
> * My client VLANs are: VLAN101=172.16.2.0/23, VLAN102=172.16.4.0/23, etc
>
> * The machine I use to manage the network is called NMS and is on
> 172.16.3.99 (VLAN 101)
>
> * A linux machine runs NAT/DHCP/DNS for the clients. It has IPs in each
> VLAN *except* VLAN 2.
>
> * iptables on the linux machine prohibits interVLAN routing but expressly
> allows all traffic to/from NMS.
>
> Here's the problem: all the routers and switches can ping each other, and
> NMS can ping them as well. But the routers/switches cannot ping NMS, and
> I'm don't understand why. I tried making an interface on the linux
> box within VLAN2, and can then ping that interface from the router, but
> that eliminates the ability of NMS
> to ping the router.
>
> More config info follows.
>
> =====================================================
> Core router:
>
> interface GigabitEthernet0/1.2
> description v002-internal-mgt-vlan
> encapsulation dot1Q 2
> ip address 172.16.0.1 255.255.254.0
> !
> interface GigabitEthernet0/1.20
> description v020-public-ip-inside
> encapsulation dot1Q 20
> ip address 76.61.48.1 255.255.255.240
> no ip unreachables
> !
> ip default-gateway 208.05.19.73
> ip route 0.0.0.0 0.0.0.0 208.05.19.73
> ip route 76.61.48.0 255.255.255.0 Null0 15
>
> ======================================================
>
> Core Switches (there are a series of these, 172.16.0.2-172.16.0.6)
>
> interface Vlan2
> description v002-internal-mgt-vlan
> ip address 172.16.0.2 255.255.254.0
> no ip redirects
> no ip route-cache
>
> ======================================================
>
> Linux box ROMULUS (NAT, DHCP, DNS, NTP)
>
> eth0 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FD
> inet addr:76.61.48.3 Bcast:76.61.48.15 Mask:255.255.255.240
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1586 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1894 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:395674 (386.4 KiB) TX bytes:479735 (468.4 KiB)
> Interrupt:17
>
> eth1 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2284 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1712 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:603934 (589.7 KiB) TX bytes:431245 (421.1 KiB)
> Interrupt:18
>
> eth1.101 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
> inet addr:172.16.2.1 Bcast:172.16.3.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1266 errors:0 dropped:0 overruns:0 frame:0
> TX packets:890 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:392524 (383.3 KiB) TX bytes:203254 (198.4 KiB)
>
> eth1.102 Link encap:Ethernet HWaddr 00:0D:56:FE:AD:FE
> inet addr:172.16.4.1 Bcast:172.16.5.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:490 errors:0 dropped:0 overruns:0 frame:0
> TX packets:255 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:83958 (81.9 KiB) TX bytes:55310 (54.0 KiB)
>
> <and so on for each subnet>
>
> NMS Workstation:
>
> Physical Address. . . . . . . . . : 00-19-21-13-FB-FD
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IPv4 Address. . . . . . . . . . . : 172.16.3.99(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.254.0
> Default Gateway . . . . . . . . . : 172.16.2.1
> DHCP Server . . . . . . . . . . . : 172.16.2.1
> DNS Servers . . . . . . . . . . . : 172.16.2.1 172.16.2.2
>


Posted by Trendkill on August 24, 2008, 7:56 am
Please log in for more thread options


> Solution: Add a subinterface on the router in the subnet and VLAN that al=
so
> contains the NMS. D'oh.
>
6S3VnZ2dnUVZ_oTinZ2d@comcast.com...
>
> > Having a routing problem I need help with:
>
> > * All my routers and switches are on 172.16.0.0/23, VLAN 2 (mgmt vlan)
>
> > * My client VLANs are: VLAN101=3D172.16.2.0/23, VLAN102=3D172.16.4.0/23=
, etc
>
> > * The machine I use to manage the network is called NMS and is on
> > 172.16.3.99 (VLAN 101)
>
> > * A linux machine runs NAT/DHCP/DNS for the clients. =A0It has IPs in e=
ach
> > VLAN *except* VLAN 2.
>
> > * iptables on the linux machine prohibits interVLAN routing but express=
ly
> > allows all traffic to/from NMS.
>
> > Here's the problem: all the routers and switches can ping each other, a=
nd
> > NMS can ping them as well. But the routers/switches cannot ping NMS, an=
d
> > I'm don't understand why. =A0I tried making an interface on the linux
> > box within VLAN2, and can then ping that interface from the router, but
> > that eliminates the ability of NMS
> > to ping the router.
>
> > More config info follows.
>
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> > Core router:
>
> > =A0 interface GigabitEthernet0/1.2
> > =A0 =A0description v002-internal-mgt-vlan
> > =A0 =A0encapsulation dot1Q 2
> > =A0 =A0ip address 172.16.0.1 255.255.254.0
> > =A0 !
> > =A0 interface GigabitEthernet0/1.20
> > =A0 =A0description v020-public-ip-inside
> > =A0 =A0encapsulation dot1Q 20
> > =A0 =A0ip address 76.61.48.1 255.255.255.240
> > =A0 =A0no ip unreachables
> > =A0 !
> > =A0 ip default-gateway 208.05.19.73
> > =A0 ip route 0.0.0.0 0.0.0.0 208.05.19.73
> > =A0 ip route 76.61.48.0 255.255.255.0 Null0 15
>
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>
> > Core Switches (there are a series of these, 172.16.0.2-172.16.0.6)
>
> > =A0 interface Vlan2
> > =A0 =A0description v002-internal-mgt-vlan
> > =A0 =A0ip address 172.16.0.2 255.255.254.0
> > =A0 =A0no ip redirects
> > =A0 =A0no ip route-cache
>
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
>
> > Linux box ROMULUS (NAT, DHCP, DNS, NTP)
>
> > =A0 eth0 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FD
> > =A0 =A0 =A0 =A0 =A0 =A0 inet addr:76.61.48.3 =A0Bcast:76.61.48.15 =A0Ma=
sk:255.255.255.240
> > =A0 =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0M=
etric:1
> > =A0 =A0 =A0 =A0 =A0 =A0 RX packets:1586 errors:0 dropped:0 overruns:0 f=
rame:0
> > =A0 =A0 =A0 =A0 =A0 =A0 TX packets:1894 errors:0 dropped:0 overruns:0 c=
arrier:0
> > =A0 =A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
> > =A0 =A0 =A0 =A0 =A0 =A0 RX bytes:395674 (386.4 KiB) =A0TX bytes:479735 =
(468.4 KiB)
> > =A0 =A0 =A0 =A0 =A0 =A0 Interrupt:17
>
> > =A0 eth1 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> > =A0 =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0M=
etric:1
> > =A0 =A0 =A0 =A0 =A0 =A0 RX packets:2284 errors:0 dropped:0 overruns:0 f=
rame:0
> > =A0 =A0 =A0 =A0 =A0 =A0 TX packets:1712 errors:0 dropped:0 overruns:0 c=
arrier:0
> > =A0 =A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
> > =A0 =A0 =A0 =A0 =A0 =A0 RX bytes:603934 (589.7 KiB) =A0TX bytes:431245 =
(421.1 KiB)
> > =A0 =A0 =A0 =A0 =A0 =A0 Interrupt:18
>
> > =A0 eth1.101 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> > =A0 =A0 =A0 =A0 =A0 =A0 inet addr:172.16.2.1 =A0Bcast:172.16.3.255 =A0M=
ask:255.255.254.0
> > =A0 =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0M=
etric:1
> > =A0 =A0 =A0 =A0 =A0 =A0 RX packets:1266 errors:0 dropped:0 overruns:0 f=
rame:0
> > =A0 =A0 =A0 =A0 =A0 =A0 TX packets:890 errors:0 dropped:0 overruns:0 ca=
rrier:0
> > =A0 =A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
> > =A0 =A0 =A0 =A0 =A0 =A0 RX bytes:392524 (383.3 KiB) =A0TX bytes:203254 =
(198.4 KiB)
>
> > =A0 eth1.102 =A0Link encap:Ethernet =A0HWaddr 00:0D:56:FE:AD:FE
> > =A0 =A0 =A0 =A0 =A0 =A0 inet addr:172.16.4.1 =A0Bcast:172.16.5.255 =A0M=
ask:255.255.254.0
> > =A0 =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0M=
etric:1
> > =A0 =A0 =A0 =A0 =A0 =A0 RX packets:490 errors:0 dropped:0 overruns:0 fr=
ame:0
> > =A0 =A0 =A0 =A0 =A0 =A0 TX packets:255 errors:0 dropped:0 overruns:0 ca=
rrier:0
> > =A0 =A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
> > =A0 =A0 =A0 =A0 =A0 =A0 RX bytes:83958 (81.9 KiB) =A0TX bytes:55310 (54=
.0 KiB)
>
> > =A0 =A0<and so on for each subnet>
>
> > NMS Workstation:
>
> > =A0 Physical Address. . . . . . . . . : 00-19-21-13-FB-FD
> > =A0 DHCP Enabled. . . . . . . . . . . : Yes
> > =A0 Autoconfiguration Enabled . . . . : Yes
> > =A0 IPv4 Address. . . . . . . . . . . : 172.16.3.99(Preferred)
> > =A0 Subnet Mask . . . . . . . . . . . : 255.255.254.0
> > =A0 Default Gateway . . . . . . . . . : 172.16.2.1
> > =A0 DHCP Server . . . . . . . . . . . : 172.16.2.1
> > =A0 DNS Servers . . . . . . . . . . . : 172.16.2.1 172.16.2.2

Or ensure routing is enabled to/from that subnet. But yes, either
would work. Your solution bypasses the need for l3 routing since you
create a local interface with layer 2 access.

Similar ThreadsPosted
Getting router to talk to client subnet/VLAN August 23, 2008, 4:33 pm
NAT ~ when two computers with same IP talk? August 19, 2007, 4:38 pm
Two 3825s won't talk to each other July 10, 2008, 6:23 am
ubr924 modem does not want to talk through its ethernet0 port June 7, 2006, 8:32 am
VPN clients unable to talk to internal networks January 11, 2008, 2:22 pm
CSS 11503 Gig over Copper Ports - Talk to Fast Ethernet? August 15, 2006, 12:23 pm
Cisco IOS Router as VPN Client April 12, 2006, 10:17 pm
VPN Client ---> 1841 router September 23, 2007, 7:23 am
PPTP CLIENT ON ROUTER CISCO January 9, 2006, 7:20 am
Cisco Router as PPTP Client April 6, 2008, 10:16 am
Re: Cisco router as a PPTP Client September 27, 2008, 2:28 am
split tunneling for vpn client and spoke router December 7, 2006, 4:10 pm
Cisco Router as a VPN server and a Microsoft Client April 25, 2007, 2:59 pm
Re: Cisco Router problem routing for Remote Client December 7, 2005, 12:37 pm
How to force DHCP client router to renew its lease? February 4, 2006, 10:49 am