From: Bill Hill (bhill@xxxxxxxxxx)
Date: Sun Jan 06 2002 - 00:10:26 GMT-3
Until you add the bridge-group commands, even though ip routing is disabled, th
e interface doesn't belong to a specific bridge-group. If you remove the bridg
e group from the interface and do a show spanning-tree, you will see that the i
nterface is not particiapting and in effect on a separate network than the rest
of your bridged network.
-----Original Message-----
From: Wayne Lewis [mailto:lewisway@hcc.hawaii.edu]
Sent: Saturday, January 05, 2002 9:41 PM
To: ccielab@groupstudy.com
Subject: baby bridging
I have a basic transparent bridging question. Here's the setup:
R1 (E0) -- Cat -- (E0) R2 (S0) --HDLC-- (S0) R3
R1 has an IP configured on E0, ip routing is disabled (R1's acting like a
host).
Cat has the default configuration (nothing configured)
R2 has bridging configured on E0 and S0 (bridge-group 1) with ieee STP and
no ip routing.
R3 has ip routing disabled, R3's S0 has an IP on the same network as R1's.
R3 cannot ping R1 with this setup, but if I add bridge-group 1 on R3's S0
and ieee STP on R3, it can ping. Why is this?
What is the rule about configuring bridging on an interface with IP
configured? It automatically bridges IP? Why does R3 require the bridging
commands, but not R1?
Thanks,
Wayne
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:17 GMT-3