From: Wes Stevens (ccie_miami@xxxxxxxxxxx)
Date: Mon May 27 2002 - 00:16:52 GMT-3
Tunnels and bridges are not exactly what I would call unsupported. The
reason you do not see people using them instead of dlsw is that they will
not work very well. Most dlsw is for sna traffic. Sna is an old an very time
critical beast. It also puts a lot of useless traffic accross the link. It
will flood your tunnel with local acks and then the sna sessions will
timeout and die.
Another sounds good in theory but does not work in real life.
>From: "Michael Snyder" <msnyder@ldd.net>
>Reply-To: "Michael Snyder" <msnyder@ldd.net>
>To: <ccielab@groupstudy.com>
>Subject: This command is an unreleased and unsupported feature
>Date: Sun, 26 May 2002 20:23:16 -0500
>
>Anybody ever use this one? I love finding new stuff (new to me). I
>don't need any stinking dlsw. Just give me a bridged tunnel interface.
>
>Testing from workstation to workstation, Workstation 192.168.200.100 is
>plugged into router b and Workstation 192.168.200.200 is plugged into
>router f.
>
>C:\>ping 192.168.200.200
>
>
>Reply from 192.168.200.200: bytes=32 time=141ms TTL=128
>Reply from 192.168.200.200: bytes=32 time=63ms TTL=128
>Reply from 192.168.200.200: bytes=32 time=63ms TTL=128
>Reply from 192.168.200.200: bytes=32 time=63ms TTL=128
>
>Ping statistics for 192.168.200.200:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 63ms, Maximum = 141ms, Average = 82ms
>
>C:\>ping 192.168.200.100
>
>Pinging 192.168.200.100 with 32 bytes of data:
>
>Reply from 192.168.200.100: bytes=32 time<10ms TTL=128
>Reply from 192.168.200.100: bytes=32 time<10ms TTL=128
>Reply from 192.168.200.100: bytes=32 time<10ms TTL=128
>Reply from 192.168.200.100: bytes=32 time<10ms TTL=128
>
>Ping statistics for 192.168.200.100:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>C:\>
>
>
>------------------------------------------------------------------------
>-----------------
>
>
>Router B
>
>bridge crb
>bridge 1 protocol ieee
>
>!
>interface Loopback0
> ip address 2.2.2.2 255.255.255.0
>!
>interface Tunnel0
> no ip address
> tunnel source Loopback0
> tunnel destination 6.6.6.6
> bridge-group 1
>!
>interface Ethernet0
> no ip address
> bridge-group 1
>
>
>Router F
>
>bridge crb
>bridge 1 protocol ieee
>
>
>interface Loopback0
> ip address 6.6.6.6 255.255.255.0
>!
>interface Tunnel0
> no ip address
> tunnel source Loopback0
> tunnel destination 2.2.2.2
> bridge-group 1
>!
>interface Ethernet0
> no ip address
> bridge-group 1
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:09 GMT-3