>
>
> Hi *,
>
> a short SUMMARY on what has been successfully tested:
>
> 1) conf t
> int tun 0
> bridge-group 1
>
> --> working
but not supported :(
>
> 2) dlsw (hint by Siva)
>
> --> Working
>
but this is supported :)
>
> That means it's possible to bridge *sort of any-traffic* into a
> tunnel interface as well as using dlsw as a kind of tunnel (even if
> its not SNA or NETBIOS). Dlsw works this way only if both "external"
yep
> interfaces are ethernet (there seems to be a bypass in the source
> around explorer frames, canureach msg etc.. if connected to eth).
no worries.
cheers
.siva
>
> Thx4hlp
> --- Maik
>
>
> On Tue, Jun 19, 2001 at 04:12:47PM -0700, Siva Valliappan wrote:
> > we don't support bridging over GRE tunnels (you can configure it) but
> > it's behavior is unpredictable. what kind of OSI traffic do you
> > plan to pass? you can configure clns/isis on GRE tunnels and enable
> > the router for clns routing. i have never done this myself, so don't
> > know if it will work. but looking around the stuff to support clns/isis
> > over GRE tunnels is there. if it's some traffic that you want
> > passed transparently trough the router, you may want to think about
> > running DLSW/RSRB between your 2 end points.
> >
> > regards
> > .siva
> >
> >
> > On Tue, 19 Jun 2001, Maik Bachmann wrote:
> >
> > >
> > > Hi *,
> > >
> > >
> > > is there a way to bridge some kind of traffic "into" a tunnel interface?
> > >
> > > The situation is as follows:
> > >
> > > ----eth-ROUTER_A-ser---------------------ser-ROUTER_B-eth---------
> > >
> > > Router_a and Router_B are 2621 with c2600-is-mz.120-7.T.bin.
> > > Traffic coming to A (thru eth if) is OSI traffic, which I want to
> > > tunnel to B. On B's eth there is another OSI device to connect to.
> > >
> > > The line between A and B is IP over SDH, so no way to bridge
> > > via FR or ATM VCs. Basic bridging is also not possible due to some issues
> > > by the carrier who filters that traffic (SDH managment data).
> > >
> > >
> > > The obvious solution would be:
> > > Router_A:
> > >
> > > interface eth0
> > > ip address 1.1.1.1 ....
> > > bridge group 1
> > > ....
> > >
> > > interface ser0
> > > ip address 2.1.1.1 ...
> > > ....
> > >
> > > interface tunnel0
> > > source 2.1.1.1
> > > destination 2.1.1.2
> > > bridge-group 1
> > >
> > > bridge protocol dec
> > >
> > > similar on Router_B......
> > >
> > > But .... no way to use bridge-group 1 on tunnel interfaces.
> > > In some way this sounds sensible since bridging doesn't touch the packet
> > > where tunnel touches (encaps in IP) it.
> > >
> > > On the other side - there must be some way to tunnel *any kind of junk*
> > > coming in.
> > >
> > > Start and endpoints of the tunnel interfaces may be the eth interfaces
> > > as well - but I found no way to tie the physical interface with the
> > > tunnel interface.
> > >
> > > Any ideas?
> > >
> > > TIA
> > > ---Maik
> > >
> > >
> > > --
> > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > > _/ Maik Bachmann ---------------- secnetix GmbH & Co KG
> > > _/ Oettingenstr. 2 -------------- D-80538 Muenchen
> > > _/ Tel(priv.): +49-8093-2962 ---- Mobil: +49-172-8305649
> > > _/ Email: bachmann@secnetix.de -- IRC: IronMaik
> > > _/ PGP KeyID: F7A67E11 ---------- PGP Fingerprint:
> > > _/ CA 3B AA EB 7F 6F 7D 7A 54 D4 AA 01 82 8E 32 9C
> > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > >
> >
> >
>
> --
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> _/ Maik Bachmann ---------------- secnetix GmbH & Co KG
> _/ Oettingenstr. 2 -------------- D-80538 Muenchen
> _/ Tel(priv.): +49-8093-2962 ---- Mobil: +49-172-8305649
> _/ Email: bachmann@secnetix.de -- IRC: IronMaik
> _/ PGP KeyID: F7A67E11 ---------- PGP Fingerprint:
> _/ CA 3B AA EB 7F 6F 7D 7A 54 D4 AA 01 82 8E 32 9C
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:42 EDT