Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   Cisco (http://www.velocityreviews.com/forums/f27-cisco.html)
-   -   Forwarding multicast packets. (http://www.velocityreviews.com/forums/t39332-forwarding-multicast-packets.html)

Robert Dohrenburg 05-21-2005 04:20 AM

Forwarding multicast packets.
 
Hi,

I hope someone can answer this simple question.

I have a cisco 2611XM with two fast enet interfaces connected to a
westell 6100 adsl modem set in bridge mode. My adsl service is SBC PPPoE
sticky statics /28 block. My outside interface is dialer0 connected to
FA0/1, my inside interface is FA0/0. My westell is at 192.168.1.254, my
FA0/1 at 192.168.1.1, my FA0/0 at 192.168.0.1.

What I want is to forward status multicast packets generated by the
westell 6100 to the local LAN where a monitoring program is processing
the information. The westell multicast group is 224.73.193.62 Mcast
Packets are generated 1 every 2 seconds and look like this

[START]
No. Time Source Destination Protocol
Info
9 2.000057 192.168.1.254 224.73.193.62 UDP
Source port:
Frame 9 (162 bytes on wire, 162 bytes captured)
Arrival Time: May 20, 2005 23:05:43.175368000
Time delta from previous packet: 0.133024000 seconds
Time since reference or first frame: 2.000057000 seconds
Frame Number: 9
Packet Length: 162 bytes
Capture Length: 162 bytes
Ethernet II, Src: 00:60:0f:7e:37:6c, Dst: 01:00:5e:49:c1:3e
Destination: 01:00:5e:49:c1:3e (01:00:5e:49:c1:3e)
Source: 00:60:0f:7e:37:6c (Westell_7e:37:6c)
Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.1.254 (192.168.1.254), Dst Addr:
224.73.193.62 (
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 148
Identification: 0x0123 (291)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 1
Protocol: UDP (0x11)
Header checksum: 0x5408 (correct)
Source: 192.168.1.254 (192.168.1.254)
Destination: 224.73.193.62 (224.73.193.62)
User Datagram Protocol, Src Port: 1875 (1875), Dst Port: 1875 (1875)
Source port: 1875 (1875)
Destination port: 1875 (1875)
Length: 128
Checksum: 0x0000 (none)
Data (120 bytes)
0000 01 00 5e 49 c1 3e 00 60 0f 7e 37 6c 08 00 45 00 ..^I.>.`.~7l..E.
0010 00 94 01 23 00 00 01 11 54 08 c0 a8 01 fe e0 49 ...#....T......I
0020 c1 3e 07 53 07 53 00 80 00 00 00 32 01 03 95 45 .>.S.S.....2...E
0030 01 00 a0 00 65 00 22 01 60 02 73 00 a6 00 e0 01 ....e.".`.s.....
0040 80 17 00 00 00 00 49 02 00 00 00 00 00 00 00 00 ......I.........
0050 00 00 00 00 00 00 ce 1c 08 00 1c 04 90 00 35 04 ..............5.
0060 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00 ................
0070 00 00 01 00 ff ff ff ff ff ff ff ff ff ff ff ff ................
0080 ff ff ff ff ff ff ff ff ff ff ff ff 12 8c 06 00 ................
0090 f5 3c 03 00 00 00 00 00 00 00 00 00 00 01 00 00 .<..............
00a0 00 00
[END] ..

I have tried PIM sparse, dense, sparse-dense modes and all the examples
in the cisco cookbook (chapter 23) without any success. Some real good
cisco CNXX guys have tried to help me without any success.

My questions are: Can the packets be forwarded to the LAN and how? Could
the dialer0 interface (PPPoE encapsulation) be causing the packets not
to reach the LAN?

My operational situation is not critical but my curiosity is. I've been
banging my head over this one for months, I leave it alone but I keep
coming back.

any ideas?

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Erik Tamminga 05-21-2005 09:55 AM

Re: Forwarding multicast packets.
 
Hi,

Is your pc joining the multicast group? does "show ip mroute" show the
multicast group? Do a debug for igmp traffic and make sure your pc joins the
group.

Erik

"Robert Dohrenburg" <NOSPAMtrifid_sagitarius@yahoo.com> wrote in message
news:428eb7ec$1_2@spool9-west.superfeed.net...
> Hi,
>
> I hope someone can answer this simple question.
>
> I have a cisco 2611XM with two fast enet interfaces connected to a westell
> 6100 adsl modem set in bridge mode. My adsl service is SBC PPPoE sticky
> statics /28 block. My outside interface is dialer0 connected to FA0/1, my
> inside interface is FA0/0. My westell is at 192.168.1.254, my FA0/1 at
> 192.168.1.1, my FA0/0 at 192.168.0.1.
>
> What I want is to forward status multicast packets generated by the
> westell 6100 to the local LAN where a monitoring program is processing the
> information. The westell multicast group is 224.73.193.62 Mcast Packets
> are generated 1 every 2 seconds and look like this
>
> [START]
> No. Time Source Destination Protocol
> Info
> 9 2.000057 192.168.1.254 224.73.193.62 UDP Source
> port:
> Frame 9 (162 bytes on wire, 162 bytes captured)
> Arrival Time: May 20, 2005 23:05:43.175368000
> Time delta from previous packet: 0.133024000 seconds
> Time since reference or first frame: 2.000057000 seconds
> Frame Number: 9
> Packet Length: 162 bytes
> Capture Length: 162 bytes
> Ethernet II, Src: 00:60:0f:7e:37:6c, Dst: 01:00:5e:49:c1:3e
> Destination: 01:00:5e:49:c1:3e (01:00:5e:49:c1:3e)
> Source: 00:60:0f:7e:37:6c (Westell_7e:37:6c)
> Type: IP (0x0800)
> Internet Protocol, Src Addr: 192.168.1.254 (192.168.1.254), Dst Addr:
> 224.73.193.62 (
> Version: 4
> Header length: 20 bytes
> Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
> 0000 00.. = Differentiated Services Codepoint: Default (0x00)
> .... ..0. = ECN-Capable Transport (ECT): 0
> .... ...0 = ECN-CE: 0
> Total Length: 148
> Identification: 0x0123 (291)
> Flags: 0x00
> 0... = Reserved bit: Not set
> .0.. = Don't fragment: Not set
> ..0. = More fragments: Not set
> Fragment offset: 0
> Time to live: 1
> Protocol: UDP (0x11)
> Header checksum: 0x5408 (correct)
> Source: 192.168.1.254 (192.168.1.254)
> Destination: 224.73.193.62 (224.73.193.62)
> User Datagram Protocol, Src Port: 1875 (1875), Dst Port: 1875 (1875)
> Source port: 1875 (1875)
> Destination port: 1875 (1875)
> Length: 128
> Checksum: 0x0000 (none)
> Data (120 bytes)
> 0000 01 00 5e 49 c1 3e 00 60 0f 7e 37 6c 08 00 45 00 ..^I.>.`.~7l..E.
> 0010 00 94 01 23 00 00 01 11 54 08 c0 a8 01 fe e0 49 ...#....T......I
> 0020 c1 3e 07 53 07 53 00 80 00 00 00 32 01 03 95 45 .>.S.S.....2...E
> 0030 01 00 a0 00 65 00 22 01 60 02 73 00 a6 00 e0 01 ....e.".`.s.....
> 0040 80 17 00 00 00 00 49 02 00 00 00 00 00 00 00 00 ......I.........
> 0050 00 00 00 00 00 00 ce 1c 08 00 1c 04 90 00 35 04 ..............5.
> 0060 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00 ................
> 0070 00 00 01 00 ff ff ff ff ff ff ff ff ff ff ff ff ................
> 0080 ff ff ff ff ff ff ff ff ff ff ff ff 12 8c 06 00 ................
> 0090 f5 3c 03 00 00 00 00 00 00 00 00 00 00 01 00 00 .<..............
> 00a0 00 00
> [END] ..
> I have tried PIM sparse, dense, sparse-dense modes and all the examples in
> the cisco cookbook (chapter 23) without any success. Some real good cisco
> CNXX guys have tried to help me without any success.
>
> My questions are: Can the packets be forwarded to the LAN and how? Could
> the dialer0 interface (PPPoE encapsulation) be causing the packets not to
> reach the LAN?
>
> My operational situation is not critical but my curiosity is. I've been
> banging my head over this one for months, I leave it alone but I keep
> coming back.
>
> any ideas?
>
> ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet
> News==----
> http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
> Newsgroups
> ----= East and West-Coast Server Farms - Total Privacy via Encryption
> =----




Robert Dohrenburg 05-21-2005 12:49 PM

Re: Forwarding multicast packets.
 
Erik,

First, thanks for reading my post.


With basic multicast routing enabled.
ip multicast-routing
ip pim dense-mode in all interfaces.

before running the monitor program:
cisco2611xm#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast
Tunnel
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.1), 00:00:16/00:02:51, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:00:10/00:00:00
FastEthernet0/0, Forward/Dense, 00:00:16/00:00:00

(*, 224.0.1.40), 00:00:17/00:02:52, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:00:10/00:00:00
FastEthernet0/0, Forward/Dense, 00:00:17/00:00:00

(*, 224.0.1.60), 00:00:14/00:02:57, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:00:10/00:00:00
FastEthernet0/0, Forward/Dense, 00:00:14/00:00:00

(*, 239.255.255.250), 00:00:16/00:02:51, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:00:10/00:00:00
FastEthernet0/0, Forward/Dense, 00:00:16/00:00:00

after the monitor program starts:
cisco2611xm#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast
Tunnel
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.1), 00:03:38/00:02:51, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:03:32/00:00:00
FastEthernet0/0, Forward/Dense, 00:03:38/00:00:00

(*, 224.0.1.40), 00:03:40/00:02:55, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:03:32/00:00:00
FastEthernet0/0, Forward/Dense, 00:03:40/00:00:00

(*, 224.0.1.60), 00:03:36/00:02:56, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:03:32/00:00:00
FastEthernet0/0, Forward/Dense, 00:03:36/00:00:00

(*, 224.73.193.62), 00:02:53/00:02:53, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:00:06/00:00:00

(*, 239.255.255.250), 00:03:38/00:02:55, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Dense, 00:03:32/00:00:00
FastEthernet0/0, Forward/Dense, 00:03:38/00:00:00

Debuging...
cisco2611xm#debug ip rout
IP routing debugging is on
cisco2611xm#debug ip mpacket 224.73.193.62
IP multicast packets debugging is on for group 224.73.193.62
cisco2611xm#debug ip igmp
IGMP debugging is on
cisco2611xm#sh log
Syslog logging: enabled (10 messages dropped, 1 messages rate-limited, 0
flushes, 0 overruns, xml disabled)
Console logging: disabled
Monitor logging: disabled
Buffer logging: level debugging, 79745 messages logged, xml disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: disabled
Trap logging: level debugging, 79650 message lines logged
Logging to 192.168.0.5, 79650 message lines logged, xml disabled

Log Buffer (52000 bytes):

RT: NET-RED 0.0.0.0/0
RT: NET-RED queued, Queue size 1
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.7 for
224.73.193.62
IGMP(0): Received Group record for group 224.73.193.62, mode 2 from
192.168.0.7 for 0 sources
IGMP(0): WAVL Insert group: 224.73.193.62 interface:
FastEthernet0/0Successful
IGMP(0): Switching to EXCLUDE mode for 224.73.193.62 on FastEthernet0/0
IGMP(0): Updating EXCLUDE group timer for 224.73.193.62
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.73.193.62) by 0

It is connecting to the group but I don't think it is joining the group.



Erik Tamminga wrote:
> Hi,
>
> Is your pc joining the multicast group? does "show ip mroute" show the
> multicast group? Do a debug for igmp traffic and make sure your pc joins the
> group.
>
> Erik
>
> "Robert Dohrenburg" <NOSPAMtrifid_sagitarius@yahoo.com> wrote in message
> news:428eb7ec$1_2@spool9-west.superfeed.net...
>
>>Hi,
>>
>>I hope someone can answer this simple question.
>>
>>I have a cisco 2611XM with two fast enet interfaces connected to a westell
>>6100 adsl modem set in bridge mode. My adsl service is SBC PPPoE sticky
>>statics /28 block. My outside interface is dialer0 connected to FA0/1, my
>>inside interface is FA0/0. My westell is at 192.168.1.254, my FA0/1 at
>>192.168.1.1, my FA0/0 at 192.168.0.1.
>>
>>What I want is to forward status multicast packets generated by the
>>westell 6100 to the local LAN where a monitoring program is processing the
>>information. The westell multicast group is 224.73.193.62 Mcast Packets
>>are generated 1 every 2 seconds and look like this
>>
>>[START]
>>No. Time Source Destination Protocol
>>Info
>> 9 2.000057 192.168.1.254 224.73.193.62 UDP Source
>>port:
>>Frame 9 (162 bytes on wire, 162 bytes captured)
>> Arrival Time: May 20, 2005 23:05:43.175368000
>> Time delta from previous packet: 0.133024000 seconds
>> Time since reference or first frame: 2.000057000 seconds
>> Frame Number: 9
>> Packet Length: 162 bytes
>> Capture Length: 162 bytes
>>Ethernet II, Src: 00:60:0f:7e:37:6c, Dst: 01:00:5e:49:c1:3e
>> Destination: 01:00:5e:49:c1:3e (01:00:5e:49:c1:3e)
>> Source: 00:60:0f:7e:37:6c (Westell_7e:37:6c)
>> Type: IP (0x0800)
>>Internet Protocol, Src Addr: 192.168.1.254 (192.168.1.254), Dst Addr:
>>224.73.193.62 (
>> Version: 4
>> Header length: 20 bytes
>> Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
>> 0000 00.. = Differentiated Services Codepoint: Default (0x00)
>> .... ..0. = ECN-Capable Transport (ECT): 0
>> .... ...0 = ECN-CE: 0
>> Total Length: 148
>> Identification: 0x0123 (291)
>> Flags: 0x00
>> 0... = Reserved bit: Not set
>> .0.. = Don't fragment: Not set
>> ..0. = More fragments: Not set
>> Fragment offset: 0
>> Time to live: 1
>> Protocol: UDP (0x11)
>> Header checksum: 0x5408 (correct)
>> Source: 192.168.1.254 (192.168.1.254)
>> Destination: 224.73.193.62 (224.73.193.62)
>>User Datagram Protocol, Src Port: 1875 (1875), Dst Port: 1875 (1875)
>> Source port: 1875 (1875)
>> Destination port: 1875 (1875)
>> Length: 128
>> Checksum: 0x0000 (none)
>>Data (120 bytes)
>>0000 01 00 5e 49 c1 3e 00 60 0f 7e 37 6c 08 00 45 00 ..^I.>.`.~7l..E.
>>0010 00 94 01 23 00 00 01 11 54 08 c0 a8 01 fe e0 49 ...#....T......I
>>0020 c1 3e 07 53 07 53 00 80 00 00 00 32 01 03 95 45 .>.S.S.....2...E
>>0030 01 00 a0 00 65 00 22 01 60 02 73 00 a6 00 e0 01 ....e.".`.s.....
>>0040 80 17 00 00 00 00 49 02 00 00 00 00 00 00 00 00 ......I.........
>>0050 00 00 00 00 00 00 ce 1c 08 00 1c 04 90 00 35 04 ..............5.
>>0060 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00 ................
>>0070 00 00 01 00 ff ff ff ff ff ff ff ff ff ff ff ff ................
>>0080 ff ff ff ff ff ff ff ff ff ff ff ff 12 8c 06 00 ................
>>0090 f5 3c 03 00 00 00 00 00 00 00 00 00 00 01 00 00 .<..............
>>00a0 00 00
>>[END] ..
>>I have tried PIM sparse, dense, sparse-dense modes and all the examples in
>>the cisco cookbook (chapter 23) without any success. Some real good cisco
>>CNXX guys have tried to help me without any success.
>>
>>My questions are: Can the packets be forwarded to the LAN and how? Could
>>the dialer0 interface (PPPoE encapsulation) be causing the packets not to
>>reach the LAN?
>>
>>My operational situation is not critical but my curiosity is. I've been
>>banging my head over this one for months, I leave it alone but I keep
>>coming back.
>>
>>any ideas?
>>
>>----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet
>>News==----
>>http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
>>Newsgroups
>>----= East and West-Coast Server Farms - Total Privacy via Encryption
>>=----

>
>
>



----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

Robert Dohrenburg 05-21-2005 01:35 PM

Re: Forwarding multicast packets.
 
Opps... here is the debug info:

cisco2611xm#sh ip igmp grou
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
224.0.1.1 FastEthernet0/0 01:04:18 00:02:23 192.168.0.5
224.0.1.40 FastEthernet0/0 01:04:19 00:02:20 192.168.0.1
224.0.1.60 FastEthernet0/0 01:04:15 00:02:20 192.168.0.128
239.255.255.250 FastEthernet0/0 01:04:18 00:02:15 192.168.0.20


cisco2611xm#sh log
Syslog logging: enabled (10 messages dropped, 1 messages rate-limited, 0
flushes, 0 overruns, xml disabled)
Console logging: disabled
Monitor logging: disabled
Buffer logging: level debugging, 81516 messages logged, xml disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: disabled
Trap logging: level debugging, 81307 message lines logged
Logging to 192.168.0.5, 81307 message lines logged, xml disabled

Log Buffer (52000 bytes):

IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.7 for
224.73.193.62
IGMP(0): Received Group record for group 224.73.193.62, mode 2 from
192.168.0.7 for 0 sources
IGMP(0): WAVL Insert group: 224.73.193.62 interface:
FastEthernet0/0Successful
IGMP(0): Switching to EXCLUDE mode for 224.73.193.62 on FastEthernet0/0
IGMP(0): Updating EXCLUDE group timer for 224.73.193.62
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.73.193.62) by 0
MRT(0): Update (*,224.73.193.62), RPF /0.0.0.0
MRT(0): Set the C-flag for (*, 224.73.193.62)
MRT(0): WAVL Insert interface: FastEthernet0/0 in (* ,224.73.193.62)
Successful
MRT(0): Add FastEthernet0/0/224.73.193.62 to the olist of (*,
224.73.193.62), Forward state - MAC built
IGMP(0): Send v2 general Query on FastEthernet0/0
IGMP(0): Set report delay time to 4.3 seconds for 224.0.1.40 on
FastEthernet0/0
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.20 for
239.255.255.250
IGMP(0): Received Group record for group 239.255.255.250, mode 2 from
192.168.0.20 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 239.255.255.250
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,239.255.255.250) by 0
MRT(0): Update (*,239.255.255.250), RPF /0.0.0.0
MRT(0): Update FastEthernet0/0/239.255.255.250 in the olist of (*,
239.255.255.250), Forward state - MAC built
IGMP(0): Send v2 general Query on FastEthernet0/1
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.7 for
224.73.193.62
IGMP(0): Received Group record for group 224.73.193.62, mode 2 from
192.168.0.7 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 224.73.193.62
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.73.193.62) by 0
MRT(0): Update (*,224.73.193.62), RPF /0.0.0.0
MRT(0): Update FastEthernet0/0/224.73.193.62 in the olist of (*,
224.73.193.62), Forward state - MAC built
IGMP(0): Received v1 Report on FastEthernet0/0 from 192.168.0.128 for
224.0.1.60
IGMP(0): Received Group record for group 224.0.1.60, mode 2 from
192.168.0.128 for 0 sources
IGMP(0): Setting v1 old host timer for 224.0.1.60 on FastEthernet0/0
IGMP(0): Updating EXCLUDE group timer for 224.0.1.60
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.0.1.60) by 0
MRT(0): Update (*,224.0.1.60), RPF /0.0.0.0
MRT(0): Update FastEthernet0/0/224.0.1.60 in the olist of (*,
224.0.1.60), Forward state - MAC built
IGMP(0): Send v2 Report for 224.0.1.40 on FastEthernet0/0
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.1 for
224.0.1.40
IGMP(0): Received Group record for group 224.0.1.40, mode 2 from
192.168.0.1 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 224.0.1.40
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.0.1.40) by 0
MRT(0): Update (*,224.0.1.40), RPF /0.0.0.0
MRT(0): Update FastEthernet0/0/224.0.1.40 in the olist of (*,
224.0.1.40), Forward state - MAC built
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.6 for
224.0.0.251
IGMP(0): Report has illegal group address 224.0.0.251
IGMP(0): Received v2 Report on FastEthernet0/0 from 192.168.0.5 for
224.0.1.1
IGMP(0): Received Group record for group 224.0.1.1, mode 2 from
192.168.0.5 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 224.0.1.1
IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.0.1.1) by 0
MRT(0): Update (*,224.0.1.1), RPF /0.0.0.0
MRT(0): Update FastEthernet0/0/224.0.1.1 in the olist of (*, 224.0.1.1),
Forward state - MAC built
IGMP(0): Received Leave from 192.168.0.7 (FastEthernet0/0) for 224.73.193.62
IGMP(0): Received Group record for group 224.73.193.62, mode 3 from
192.168.0.7 for 0 sources
IGMP(0): Lower expiration timer to 2000 msec for 224.73.193.62 on
FastEthernet0/0
IGMP(0): Send v2 Query on FastEthernet0/0 for group 224.73.193.62
IGMP(0): Send v2 Query on FastEthernet0/0 for group 224.73.193.62
IGMP(0): Switching to INCLUDE mode for 224.73.193.62 on FastEthernet0/0
IGMP(0): MRT delete FastEthernet0/0 for (*,224.73.193.62) by 0
MRT(0): Delete FastEthernet0/0/224.73.193.62 from the olist of (*,
224.73.193.62)
MRT(0): set min mtu for (0.0.0.0, 224.73.193.62) 1500->0
MRT(0): Reset the C-flag for (*, 224.73.193.62)

Erik Tamminga wrote:
> Hi,
>
> Is your pc joining the multicast group? does "show ip mroute" show the
> multicast group? Do a debug for igmp traffic and make sure your pc joins the
> group.
>
> Erik
>
> "Robert Dohrenburg" <NOSPAMtrifid_sagitarius@yahoo.com> wrote in message
> news:428eb7ec$1_2@spool9-west.superfeed.net...
>
>>Hi,
>>
>>I hope someone can answer this simple question.
>>
>>I have a cisco 2611XM with two fast enet interfaces connected to a westell
>>6100 adsl modem set in bridge mode. My adsl service is SBC PPPoE sticky
>>statics /28 block. My outside interface is dialer0 connected to FA0/1, my
>>inside interface is FA0/0. My westell is at 192.168.1.254, my FA0/1 at
>>192.168.1.1, my FA0/0 at 192.168.0.1.
>>
>>What I want is to forward status multicast packets generated by the
>>westell 6100 to the local LAN where a monitoring program is processing the
>>information. The westell multicast group is 224.73.193.62 Mcast Packets
>>are generated 1 every 2 seconds and look like this
>>
>>[START]
>>No. Time Source Destination Protocol
>>Info
>> 9 2.000057 192.168.1.254 224.73.193.62 UDP Source
>>port:
>>Frame 9 (162 bytes on wire, 162 bytes captured)
>> Arrival Time: May 20, 2005 23:05:43.175368000
>> Time delta from previous packet: 0.133024000 seconds
>> Time since reference or first frame: 2.000057000 seconds
>> Frame Number: 9
>> Packet Length: 162 bytes
>> Capture Length: 162 bytes
>>Ethernet II, Src: 00:60:0f:7e:37:6c, Dst: 01:00:5e:49:c1:3e
>> Destination: 01:00:5e:49:c1:3e (01:00:5e:49:c1:3e)
>> Source: 00:60:0f:7e:37:6c (Westell_7e:37:6c)
>> Type: IP (0x0800)
>>Internet Protocol, Src Addr: 192.168.1.254 (192.168.1.254), Dst Addr:
>>224.73.193.62 (
>> Version: 4
>> Header length: 20 bytes
>> Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
>> 0000 00.. = Differentiated Services Codepoint: Default (0x00)
>> .... ..0. = ECN-Capable Transport (ECT): 0
>> .... ...0 = ECN-CE: 0
>> Total Length: 148
>> Identification: 0x0123 (291)
>> Flags: 0x00
>> 0... = Reserved bit: Not set
>> .0.. = Don't fragment: Not set
>> ..0. = More fragments: Not set
>> Fragment offset: 0
>> Time to live: 1
>> Protocol: UDP (0x11)
>> Header checksum: 0x5408 (correct)
>> Source: 192.168.1.254 (192.168.1.254)
>> Destination: 224.73.193.62 (224.73.193.62)
>>User Datagram Protocol, Src Port: 1875 (1875), Dst Port: 1875 (1875)
>> Source port: 1875 (1875)
>> Destination port: 1875 (1875)
>> Length: 128
>> Checksum: 0x0000 (none)
>>Data (120 bytes)
>>0000 01 00 5e 49 c1 3e 00 60 0f 7e 37 6c 08 00 45 00 ..^I.>.`.~7l..E.
>>0010 00 94 01 23 00 00 01 11 54 08 c0 a8 01 fe e0 49 ...#....T......I
>>0020 c1 3e 07 53 07 53 00 80 00 00 00 32 01 03 95 45 .>.S.S.....2...E
>>0030 01 00 a0 00 65 00 22 01 60 02 73 00 a6 00 e0 01 ....e.".`.s.....
>>0040 80 17 00 00 00 00 49 02 00 00 00 00 00 00 00 00 ......I.........
>>0050 00 00 00 00 00 00 ce 1c 08 00 1c 04 90 00 35 04 ..............5.
>>0060 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 00 00 ................
>>0070 00 00 01 00 ff ff ff ff ff ff ff ff ff ff ff ff ................
>>0080 ff ff ff ff ff ff ff ff ff ff ff ff 12 8c 06 00 ................
>>0090 f5 3c 03 00 00 00 00 00 00 00 00 00 00 01 00 00 .<..............
>>00a0 00 00
>>[END] ..
>>I have tried PIM sparse, dense, sparse-dense modes and all the examples in
>>the cisco cookbook (chapter 23) without any success. Some real good cisco
>>CNXX guys have tried to help me without any success.
>>
>>My questions are: Can the packets be forwarded to the LAN and how? Could
>>the dialer0 interface (PPPoE encapsulation) be causing the packets not to
>>reach the LAN?
>>
>>My operational situation is not critical but my curiosity is. I've been
>>banging my head over this one for months, I leave it alone but I keep
>>coming back.
>>
>>any ideas?
>>
>>----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet
>>News==----
>>http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+
>>Newsgroups
>>----= East and West-Coast Server Farms - Total Privacy via Encryption
>>=----

>
>
>


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----


All times are GMT. The time now is 06:02 AM.

Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.