RE: ipv6 multicast testing

That is addres on r1 (server)

From: garry baker [mailto:baker.garry_at_gmail.com]
Sent: Wednesday, December 01, 2010 4:41 PM
To: gp
Cc: ccielab_at_groupstudy.com
Subject: Re: ipv6 multicast testing

cool so now my question is what and where did that Source Address:
FD11:2222:3333:4444::15 come from?

i have the same thing on my single router, loopback0 testing now that i have
turned on ipv6 multicast-routing

--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
2010/12/1 gp <gs4me2me_at_gmail.com>
Mldv2 is turned by default, when you apply ipv multicast-routing.
 
This is output from r4 on which is directly connected r5 (host):
 
sh ipv mld groups detail 
Interface:      FastEthernet0/0
Group:          FF33:1111::10
Uptime:         06:08:29
Router mode:    INCLUDE
Host mode:      INCLUDE
Last reporter:  FE80::219:6FF:FE52:A148
Group source list:
Source Address                          Uptime    Expires   Fwd  Flags
FD11:2222:3333:4444::15                 06:08:29  00:02:56  Yes  Remote 4
 
sh ipv mld int f0/0
FastEthernet0/0 is up, line protocol is up
  Internet address is FE80::215:F9FF:FE8C:D514/10
  MLD is enabled on interface
  Current MLD version is 2
  MLD query interval is 125 seconds
  MLD querier timeout is 255 seconds
  MLD max query response time is 10 seconds
  Last member query response interval is 1 seconds
  Inbound MLD access group is: 
  MLD activity: 14 joins, 3 leaves
  MLD querying router is FE80::215:F9FF:FE8C:D514 (this system)
 
I didnt try with "regular" multicast because ssm for v4 works fine, and as i
can see from output works for v6 too, except i cannot test it with ping like
with v4, 
on net i find that can be test with ssmping but that require additinal pc-s.
 
Thank you for help
 
 
 
From: garry baker [mailto:baker.garry_at_gmail.com] 
Sent: Wednesday, December 01, 2010 4:09 PM
To: gp
Cc: ccielab_at_groupstudy.com
Subject: Re: ipv6 multicast testing
 
ok ipv6 ssm, sort of out of my scope, but the doccd says this about it:
"MLD version 2 is required for SSM to operate. MLD allows the host to
provide source information. Before SSM will run with MLD, SSM must be
supported in the Cisco IOS IPv6 router, the host where the application is
running, and the application itself."
so now i am trying to figure out how to determine and then turn on MLDv2?
and for a test what happens if you just use pim-sm and use "regular" ipv6
multicast does it work? meaning this is a SSM specific issue?
--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
2010/12/1 gp <gs4me2me_at_gmail.com>
Configuration is preaty simple, i have unicast v6 connectivity form r1 to r5
with static routes (there is no redudant links). 
 
For multicast configuration what i post before; all routers have ipv6
unicast routing, ipv6 multicast routing, and on r1 i try to emulate server
with ping FF33:1111::10, on r5 try to emulate host with ipv6 mld join-group
FF33:1111::10 FD11:2222:3333:4444::15
On every router int he path i have PIM neighborsheep, mroute that looks
ok.just cannot ping:)
 
i use SSM.
This scenario works for v4 SSM multicast.
 
Thank you!
Regards,
Gp
 
 
 
 
 
From: garry baker [mailto:baker.garry_at_gmail.com] 
Sent: Wednesday, December 01, 2010 3:00 PM
To: gp
Cc: ccielab_at_groupstudy.com
Subject: Re: ipv6 multicast testing
 
i am not sure what this error means, (% No valid source address for
destination) have never seen it before...
can you show some of the configs?
--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
2010/12/1 gp <gs4me2me_at_gmail.com>
Thank you garry for your answer!
 
You show ping from the same router on which is join made. I have situation
like this:
 
R1(f0/0) -------- r2 --------- r3 ---------- r4 ---------- (f0/0) r5
 
On every router i configured:
Ipv6 unicast-routing
Ipv6 multicast-routing
 
On r5 int f0/0:
ipv6 mld join-group FF33:1111::10 FD11:2222:3333:4444::15
 
on r1 i try to ping ff33:1111::10 and get this:
ping ipv6 ff33:1111::10 so f0/1.10
Output Interface: fastethernet0/1.10
% No valid source address for destination
 
On every router on the path i have the following:
sh ipv6 mroute 
Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, 
       C - Connected, L - Local, I - Received Source Specific Host Report,
       P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,
       J - Join SPT 
Timers: Uptime/Expires
Interface state: Interface, State
 
 (FD11:2222:3333:4444::15, FF33:1111::10), 00:00:02/00:03:27, flags: ST
  Incoming interface: FastEthernet0/0.10
  RPF nbr: FE80::218:18FF:FEC5:2957
  Immediate Outgoing interface list:
    FastEthernet0/1.50, Forward, 00:00:02/00:03:27
 
And that is correct output, i think. Now i want to know why ping doesn't
work? For ipv4 works:)
 
 
 
From: garry baker [mailto:baker.garry_at_gmail.com] 
Sent: Tuesday, November 30, 2010 6:10 PM
To: gp
Cc: ccielab_at_groupstudy.com
Subject: Re: ipv6 multicast testing
 
R4(config-if)#ipv6 mld join-group FF02::224:1:1:1
R4(config-if)#do sh ipv6 int
Loopback0 is up, line protocol is up
  IPv6 is enabled, link-local address is FE80::C606:24FF:FE44:0
  No Virtual link-local address(es):
  Global unicast address(es):
    2001::C606:24FF:FE44:0, subnet is 2001::/64 [EUI]
  Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF44:0
    FF02::224:1:1:1
  MTU is 1514 bytes
  ICMP error messages limited to one every 100 milliseconds
  ICMP redirects are enabled
  ICMP unreachables are sent
  ND DAD is not supported
  ND reachable time is 30000 milliseconds
  Hosts use stateless autoconfig for addresses.
R4#sh ipv6 mld interface loopback 0
Loopback0 is up, line protocol is up
  Internet address is FE80::C606:24FF:FE44:0/10
  MLD is disabled on interface
R4#ping FF02::224:1:1:1
Output Interface: Loopback0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FF02::224:1:1:1, timeout is 2 seconds:
Packet sent with a source address of FE80::C606:24FF:FE44:0
Reply to request 0 received from FE80::C606:24FF:FE44:0, 4 ms
Reply to request 1 received from FE80::C606:24FF:FE44:0, 4 ms
Reply to request 2 received from FE80::C606:24FF:FE44:0, 4 ms
Reply to request 3 received from FE80::C606:24FF:FE44:0, 4 ms
Reply to request 4 received from FE80::C606:24FF:FE44:0, 0 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/4 ms
5 multicast replies and 0 errors.
--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
2010/11/30 gp <gs4me2me_at_gmail.com>
That is for emulate host, but how to emulate server?
 
 
From: garry baker [mailto:baker.garry_at_gmail.com] 
Sent: Tuesday, November 30, 2010 5:46 PM
To: gp
Cc: ccielab_at_groupstudy.com
Subject: Re: ipv6 multicast testing
 
'ipv6 mld join-group'
mld "is" igmp for ipv6
--
Garry L. Baker
"There is no 'patch' for stupidity." - www.sqlsecurity.com
On Tue, Nov 30, 2010 at 10:22 AM, gp <gs4me2me_at_gmail.com> wrote:
Hi all,
How to test ipv6 multicast on routers, like for ipv4 on router to emulate
server with ping 224.1.1.1 and to emulate the host with ip igmp join group
224.1.1.1.
Is it possible something like this for ipv6?
Thanks
Blogs and organic groups at http://www.ccie.net