RE: Re: [magma] Re: [MBONED] multiple SSM sources behind a NAT

Hello,

 

A very simple solution:

 

Multicast senders can choose the multicast group from 224.0.0.0 to 239.255.255.255.

 

A simple solution is to recommend (ietf draft) multicast sender to use groups in the form: xxx.yyy.zzz.xxx where the user can choose x and

 

1)      yyy.zzz are the last two bytes of the internal IP address. (for example 192.168.yyy.zzz)

 

Or another solution (when using more than one NAPT):

 

2)      yyy is the last byte of the internal IP address and zzz is the public IP address.

 

note that SSM range is shorter than ASM.

 

Regards


Alvaro


________________________________

De: Beau Williamson [mailto:[email protected]]
Enviado el: mar 17/07/2007 15:27
Para: Stig Venaas; Bharat Joshi
CC: [email protected]; [email protected]; [email protected]
Asunto: [BEHAVE] Re: [magma] Re: [MBONED] multiple SSM sources behind a NAT



At 01:36 AM 7/17/2007, Stig Venaas wrote:
>This sounds rather ugly to me, and the behaviour may be hard to
>understand for users exposed to this. I would rather have both
>being forwarded and say that it's a user error to try to use the
>same group for the two. That is like Marshall said, use different
>groups. However, I don't think it's a good idea to modify the group
>in the NAT itself since that would also probably require the
>announcement of which S,G to be used to be modified, and this can be
>done through methods, e.g. SDP file through HTTP or email or whatever.
>
>In short, I don't think you should solve this. In this not so common
>situation, better let admins/users figure out that they should not
>use the same G. In fact, there may be other reasons for choosing
>different Gs as well (e.g. it may be good to use Gs that map to
>different MAC addresses due to snooping devices and NICs).

I agree with Stig on this.  I don't think we want to tackle this
problem.  If you have multiple SSM sources behind a NAT, there are
other ways to solve this such as above or the best way (IMHO) is to
get more global addresses from your SP so your SSM sources can each
have a unique global address.   I know this isn't always easily done
but I still don't think we want to solve this problem for
administrators by coming up with special NAT GW behaviors.

Beau Williamson 


_______________________________________________
Behave mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/behave