Oh yes, you all have a holiday.  Happy 4TH of July (Everyone).
I shall wait to see if any CCIEs reply.  If not I think segmenting the 
wireless bridges is the way to go, I feel bridging is taking a step back.

Thanks
KM


>From: Priscilla Oppenheimer 
>To: "KM Reynolds" ,[EMAIL PROTECTED]
>Subject: Re: Directly connected ethernet interface [7:10998]
>Date: Wed, 04 Jul 2001 09:12:25 -0700
>
>Sitting here at Starbucks, using wireless, waiting for the 4th of July
>parade.... My brain isn't working too well. The latte wore off hours ago.
>
>But.... it occurs to me that Aironet is bridging, as you know. The routed
>network doesn't know when a bridged network goes down. Could you do this
>area of the network with all bridging? Could the ISDN link use bridging
>also, in other words? I know bridging over ISDN is supported.
>
>The convergence might be so slow, however, that you could pull the e1
>interface in about the same timeframe (if you knew to do it though.)
>
>I can't think of any other solution (besides the one you mentioned of
>adding a router). It's an interesting design question. Maybe one of the
>CCIEs on the list will answer.
>
>Priscilla
>
>At 11:35 AM 7/4/01, KM Reynolds wrote:
>>Hi Everyone,
>>
>>Need you help.
>>
>>I have a server that is on a remote LAN.  To ping the server, the traffic
>>goes in the local router(gateway) e0, out e1, to a local Aironet wireless
>>bridge, to the remote Aironet wireless bridge, to a switch, to server.
>>Works great.
>>
>>Currently, there is also a link to the remote site, an ISDN, from the 
>>local
>>router to a remote router.  We would like to use this ISDN as a backup to
>>wireless connection.
>>
>>The routers are configured to use EIGRP to route between the wireless, and
>>floating routes are set with higher administrative distance so when the
>>EIGRP disappears out of the routing table the floating routes route via 
>>the
>>ISDN.
>>
>>All works, when the ethernet (e1) is shutdown. When I disconnect the
>>wireless at the remote, the ISDN comes up.  The problem is, the route to 
>>the
>>directly connected ethernet LAN is still in the routing table (C
>>192.168.30.128 255.255.255.128 is directly connected, Ethernet1). So 
>>traffic
>>still flows out of e1, and I guess when it reaches the remote wireless
>>bridge, it is discarded, that where the connection is down.
>>
>>Is there anyway around this, is there a way for the e1 to detect the path 
>>is
>>down or is my only option to place a router and segment the wireless 
>>bridge
>>link.
>>
>>Any help would be great.
>>
>>Thanks
>>KM
>>_________________________________________________________________________
>>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>________________________
>
>Priscilla Oppenheimer
>http://www.priscilla.com
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=11020&t=10998
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to