From: Don (seadon@attbi.com)
Date: Wed Dec 18 2002 - 13:17:19 GMT-3
That is because the tunnels enclose the multicast packet (and everything
else that uses the tunnel) inside of a unicast packet and send it out as a
unicast. That's why they can cross a unicast only network segment. So each
tunnel has to duplicate the multicast stream and so 5 tunnels means 5
unicast encoded multicast streams, not just one multicast stream.
Don
----- Original Message -----
From: "Adarsh Singh" <adarshs@hclinfinet.net>
To: "Don" <seadon@attbi.com>; "Sean Garrett" <SGarrett@cnitech.com>
Cc: <ccielab@groupstudy.com>
Sent: Monday, December 16, 2002 9:40 PM
Subject: Multicast ISSUE
> Hi Don,
>
> I have this typical problem with multicast :
>
> Multicast Server(router)----LL(64Kbps)----Router 1-----tunne1 ----R2(each
> tunnel traffic is 20 Kbps)
>
> ------tunnel2 ---R3
>
>
> Now as the number of tunnels(gre) increases at the router 1 , the traffic
> increases propotinally for the 64 Kbps leased line .
> So the mulicast is not taking place in real sense .
>
>
>
> The commands used at tunnel are as follows :
>
> interface Tunnel2
> ip address 172.168.12.1 255.255.255.252
> ip directed-broadcast
> ip pim sparse-dense-mode
> ip igmp join-group 239.255.255.255
> load-interval 30
> tunnel source 10.65.12.233
> tunnel destination 10.74.5.9
>
> interface FastEthernet0
> description connected to EthernetLAN
> ip address 192.168.10.85 255.255.255.0 secondary
> ip directed-broadcast
> ip pim sparse-dense-mode
> ip igmp join-group 239.255.255.255
> load-interval 30
> speed auto
> half-duplex
>
>
> interface Serial1
> description connected to infinet for VPN
> ip address 10.65.7.82 255.255.255.252
> ip accounting output-packets
> ip pim sparse-dense-mode
> ip igmp join-group 239.255.255.255
> load-interval 30
>
>
> Do let me know if someone has ideas of where i an making a mistake.
>
>
> Rgds
> Adarsh Singh
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:48 GMT-3