yes tony thats it :) On Wed, 22 Aug 2001, Tony Medeiros wrote: > Sounds like Spanning tree is screwing it up. Since this is a multipoint > interface. It think spanning tree will consider it as one port. Any packet > that comes in the router and is destined for the same subnet doesn't hit > the BVI and is bridged. > > 1st rule of bridge forwarding : > If the destination MAC address is unknown, forward out all ports except the > ingress port. Since all the packets come in the same port as far a spanning > tree is concerned, unknown or ANY packets for that matter, will not be set > out the same port. Packets on different subnets hit the BVI and are routed > and so will bypass the bridging rule. > > A bridge will NEVER forward a frame out the same port in came it. > > Solution: > Set up P to P subinterfaces. These should be treated by bridge as different > ports and frames will get forwarded. > > IGRP and split horizon have nothing to do with it. > > At least I think this is the problem :) > > Tony M > #6172 > > ----- Original Message ----- > From: "suaveguru" > To: > Sent: Tuesday, August 21, 2001 7:55 PM > Subject: RE: CHALLENGE PROBLEM (was Re: For FR Grus.... [7:16635]) [7:16755] > > > > is it something to do with using classless rather than > > classful routing protocols? > > > > > > regards, > > suaveguru > > --- Patrick Ramsey > > wrote: > > > How about get rid of igrp and configure ospf in nbma > > > mode? :) > > > > > > -Patrick > > > > > > >>> "Brian" 08/21/01 02:10PM >>> > > > No one has gotten this problem yet. Remeber, making > > > it so the clients are > > > on differnt layer 3 networks works, but when they > > > are on the same it > > > doesn't. What mechanics are involved in how the > > > packet will be treated > > > different if on the same network vs. different > > > networks. > > > > > > I'll still leave the answer open, someone will get > > > this. > > > > > > Brian > > > > > > > > > On Tue, 21 Aug 2001, Wayne Wenthin wrote: > > > > > > > To me this looks very similar to bridging with > > > DSL. Since you cannot > > > > receive the ARP the router must proxy this. > > > > > > > > At 09:52 AM 8/21/2001, McCallum, Robert wrote: > > > > >you can correct me here if I am wrong but split > > > horizon is only used in > > > > >distance vector protocols???? NO??? > > > > > > > > > >The problem here without giving the answer is > > > that a router is expected to > > > > >pass a packet out of an interface which is on its > > > own subnet !! Doesn't > > > > >compute! What is the routing protocol being used > > > to route ip?? This is > > > > >where the answer will lye > > > > > > > > > >-----Original Message----- > > > > >From: Donald B Johnson jr > > > [mailto:[EMAIL PROTECTED]] > > > > >Sent: 21 August 2001 17:06 > > > > >To: [EMAIL PROTECTED] > > > > >Subject: Re: CHALLENGE PROBLEM (was Re: For FR > > > Grus.... [7:16635]) > > > > >[7:16681] > > > > > > > > > > > > > > >I don't think bridge will work on this network > > > because of split horizon. > > > > > > > > > > > > > > > > > > > > > > > > >----- Original Message ----- > > > > >From: "Brian" > > > > >To: > > > > >Sent: Tuesday, August 21, 2001 7:51 AM > > > > >Subject: CHALLENGE PROBLEM (was Re: For FR > > > Grus.... [7:16635]) [7:16659] > > > > > > > > > > > > > > > > On Tue, 21 Aug 2001, Cisco Lover wrote: > > > > > > > > > > > > > Hi Guys.. > > > > > > > > > > > > > > Come with some New Queston.. > > > > > > > > > > > > hmm, ok, so your looking for some challenging > > > questions? Ok, I will > > > post > > > > > > one, its got FR in it. First I'll post the > > > problem, followed by the > > > > > > config: > > > > > > > > > > > > THE PROBLEM > > > > > > =========== > > > > > > Users on DLCI's 200, 224, 201, 225 cannot > > > communicate to eachother. > > > They > > > > > > can talk just fine to the rest of the network, > > > but no packets can pass > > > > > > between them. Later discovery reveals that so > > > long as they are on > > > > > > different layer 3 network addressing, > > > communcation can occur, but if > > > they > > > > > > are on the same network, such as 192.168.3.0, > > > then they cannot > > > > communicate > > > > > > > > > > > > What is the problem? I will reply to let > > > everyone know who got the > > > > > > correct answer. > > > > > > > > > > > > Below is the configuration: > > > > > > > > > > > > ! > > > > > > version 11.3 > > > > > > ! > > > > > > interface Ethernet2/0 > > > > > > ip address 192.168.1.242 255.255.255.0 > > > > > > ! > > > > > > interface Serial4/0 > > > > > > no ip address > > > > > > encapsulation frame-relay IETF > > > > > > keepalive 15 > > > > > > frame-relay map bridge 200 broadcast IETF > > > > > > frame-relay map bridge 224 broadcast IETF > > > > > > frame-relay map bridge 201 broadcast IETF > > > > > > frame-relay map bridge 225 broadcast IETF > > > > > > frame-relay lmi-type ansi > > > > > > bridge-group 1 > > > > > > ! > > > > > > interface BVI1 > > > > > > ip address 192.168.3.242 255.255.255.0 > > > secondary > > > > > > ip address 192.168.2.242 255.255.255.0 > > > > > > > > > > > > ! > > > > > > router igrp 1 > > > > > > network 192.1.0.0 > > > > > > network 192.2.0.0 > > > > > > network 193.3.0.0 > > > > > > ! > > > > > > ip classless > > > > > > ! > > > > > > bridge irb > > > > > > bridge 1 protocol ieee > > > > > > bridge 1 route ip > > > > > > ! > > > > > > > > > > > > > > > > > > > > > > > > > > For eg, > > > > > > > our FR switch is setup for Full mesh,But out > > > network is setup as Hub > > > & > > > > > > Spoke > > > > > > > FAQ, list archives, and subscription info: > > > > > > http://www.groupstudy.com/list/cisco.html > > > > > > > Report misconduct and Nondisclosure > > > violations to > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----------------------------------------------- > > > > > > I'm buying / selling used CISCO gear!! > > > > > > email me for a quote > > > > > > > > > > > > Brian Feeny, CCIE #8036 Scarlett Parria > > > > > > [EMAIL PROTECTED] [EMAIL PROTECTED] > > > > > > 318-213-4709 318-213-4701 > > > > > > > > > > > > Netjam, LLC http://www.netjam.net > > > > > > 333 Texas St. VISA/MC/AMEX/COD > > > > > > Suite 1401 30 day warranty > > > > > > Shreveport, LA 71101 Cisco Channel Partner > > > > > > toll free: 866-2NETJAM > > > > > > phone: 318-212-0245 > > > > > > fax: 318-212-0246 > > > I'm buying / selling used CISCO gear!! > > > email me for a quote > > > > > > Brian Feeny, CCIE #8036 Scarlett Parria > > > [EMAIL PROTECTED] [EMAIL PROTECTED] > > > 318-213-4709 318-213-4701 > > > > > > Netjam, LLC http://www.netjam.net > > > 333 Texas St. VISA/MC/AMEX/COD > > > Suite 1401 30 day warranty > > > Shreveport, LA 71101 Cisco Channel Partner > > > toll free: 866-2NETJAM > > > phone: 318-212-0245 > > > fax: 318-212-0246 > > [EMAIL PROTECTED] > > > > > > __________________________________________________ > > Do You Yahoo!? > > Make international calls for as low as $.04/minute with Yahoo! Messenger > > http://phonecard.yahoo.com/ I'm buying / selling used CISCO gear!! email me for a quote Brian Feeny, CCIE #8036 Scarlett Parria [EMAIL PROTECTED] [EMAIL PROTECTED] 318-213-4709 318-213-4701 Netjam, LLC http://www.netjam.net 333 Texas St. VISA/MC/AMEX/COD Suite 1401 30 day warranty Shreveport, LA 71101 Cisco Channel Partner toll free: 866-2NETJAM phone: 318-212-0245 fax: 318-212-0246 Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=16771&t=16771 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
