RE: confusion on bridging

From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Fri Nov 03 2000 - 11:38:13 GMT-3


   
First of all, there is no law that says a bridge CANT have an IP address.
How else do you telnet in or SNMP manage them? But if al you are doing is
bridge, no, the two interface addresses are on different subnets and you may
not be able to get into one or the other.

You spent a lot of time covering the OSI model in the lower level
certifications. So let's use it and see how it helps.

Bridges operate at which layer? Routing operates at which layer?

What does the bridging layer use for addressing? What about the routing
layer?

What is the relationship between the layers? What happens at each layer as
data moves from here to there.

Host---R1----R2-----Host ( surely you recognize this :-> )

In your proposed example, based upon your thinking through the OSI model,
what do you think?

Chuck

-----Original Message-----
From: David T. Absalom [mailto:dabsalom@lucent.com]
Sent: Friday, November 03, 2000 3:27 AM
To: Chuck Larrieu; Ccielab; Paulo Mendes De Oliveira
Subject: Re: confusion on bridging

Thanks Chuck and Paulo, good answers. I'm almost there...

Then let's assume this config of two routers, back to back via s1. Only the
serial interfaces are in a bridge group. As is, the e0 interfaces should
not see each other since they are on different subnets. If I add the e0 on
each device into the same bridge group as the s0 interfaces and disable ip
routing, should the e0 then see each other on the same subnet?

hostname R1
!
interface Ethernet0
 ip address 192.168.10.1 255.255.255.0
!
interface Serial1
 no ip address
 no ip route-cache
 clockrate 500000
 bridge-group 1
!
no ip classless
!
bridge 1 protocol ieee

------------------
hostname R2
!
interface Ethernet0
 ip address 192.168.10.1 255.255.255.0
!
interface Serial1
 no ip address
 no ip route-cache
 clockrate 500000
 bridge-group 1
!
no ip classless
!
bridge 1 protocol ieee



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:41 GMT-3