Re: Private: Re: [vpp-dev] Queries regarding mfib and multicast support in VPP

2022-04-20 Thread Neale Ranns 

You need to add them both in the same command


DBGvpp# ip mroute add 1.1.1.1 239.1.1.1 via loop0 Accept Forward

DBGvpp# sh ip mfib 1.1.1.1 239.1.1.1

ipv4-VRF:0, fib_index:0 flags:none

(1.1.1.1, 239.1.1.1/32):

 fib:0 index:8 locks:1

  src:CLI flags:none locks:1:

path-list:[13] locks:2 flags:no-uRPF, uRPF-list: None

  path:[13] pl-index:13 ip4 weight=1 pref=0 attached:

 loop0

Extensions:

 path:13 flags:Accept,Forward,

Interface-Forwarding:

 loop0: Accept,Forward,   <<<<<



  Interfaces:

   loop0: Accept,Forward,

  multicast-ip4-chain

  [@0]: dpo-drop ip4

DBGvpp#


/neale

From: arunmitta...@gmail.com 
Date: Wednesday, 20 April 2022 at 05:47
To: Neale Ranns 
Subject: Private: Re: [vpp-dev] Queries regarding mfib and multicast support in 
VPP
Thanks Neale,

I think this information will help me a lot to understand multicast forwarding 
in VPP.

I am using "ip mroute add 1.1.1.1 239.1.1.1 via Eth0/2 Accept" to configure a 
mroute from VPP CLI. I have observed that, I can configure the interface as 
FORWARD or ACCEPT for the given S, G entry but not both.
With you input, I understand that we can configure an interface with both 
FORWARD as well as ACCEPT attributes. Am I missing something or still there is 
some gap in my understanding ?


root@cnfp:/# cnfp-dbg vpp ip mroute add 1.1.1.1 239.1.1.1 via 
TenGigabitEthernet3/0/1.205 Accept
root@cnfp:/# cnfp-dbg vpp show ip mfib
ipv4-VRF:0, fib_index:0 flags:none
(*, 0.0.0.0/0):  flags:Drop,
  Interfaces:
  multicast-ip4-chain
  [@0]: dpo-drop ip4
(*, 224.0.0.1/32):
  Interfaces:
  multicast-ip4-chain
  [@2]: dpo-replicate: [index:0 buckets:1 flags:[has-local ] to:[0:0]]
[0] [@1]: dpo-receive
(*, 224.0.0.2/32):
  Interfaces:
  multicast-ip4-chain
  [@2]: dpo-replicate: [index:1 buckets:1 flags:[has-local ] to:[0:0]]
[0] [@1]: dpo-receive
(1.1.1.1, 239.1.1.1/32):
  Interfaces:
   TenGigabitEthernet3/0/1.205: Accept,
  multicast-ip4-chain
  [@0]: dpo-drop ip4

root@cnfp:/# cnfp-dbg vpp ip mroute add 1.1.1.1 239.1.1.1 via 
TenGigabitEthernet3/0/1.205 Forward
root@cnfp:/# cnfp-dbg vpp show ip mfib
ipv4-VRF:0, fib_index:0 flags:none
(*, 0.0.0.0/0):  flags:Drop,
  Interfaces:
  multicast-ip4-chain
  [@0]: dpo-drop ip4
(*, 224.0.0.1/32):
  Interfaces:
  multicast-ip4-chain
  [@2]: dpo-replicate: [index:0 buckets:1 flags:[has-local ] to:[0:0]]
[0] [@1]: dpo-receive
(*, 224.0.0.2/32):
  Interfaces:
  multicast-ip4-chain
  [@2]: dpo-replicate: [index:1 buckets:1 flags:[has-local ] to:[0:0]]
[0] [@1]: dpo-receive
(1.1.1.1, 239.1.1.1/32):
  Interfaces:
   TenGigabitEthernet3/0/1.205: Forward,
  multicast-ip4-chain
  [@2]: dpo-replicate: [index:6 buckets:1 flags:[none] to:[0:0]]
[0] [@2]: ipv4-mcast: TenGigabitEthernet3/0/1.205: mtu:9000 next:4 
01005e003cecef457f4b81640800



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21273): https://lists.fd.io/g/vpp-dev/message/21273
Mute This Topic: https://lists.fd.io/mt/90579491/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Queries regarding mfib and multicast support in VPP

2022-04-13 Thread Neale Ranns 
Hi Arun,

From: vpp-dev@lists.fd.io  on behalf of arunmittal88 via 
lists.fd.io 
Date: Tuesday, 12 April 2022 at 15:24
To: vpp-dev@lists.fd.io 
Subject: [vpp-dev] Queries regarding mfib and multicast support in VPP
Hi,

Just want to know if the mfib-lookup node is attached to the default packet 
processing node graph or do we need to explicitly enable this.
It’s enabled by default.
Also wanted to understand if the following things are achievable with mfib in 
VPP (To understand the mfib in VPP I am following 
"https://wiki.fd.io/view/VPP/MFIB; page).

Lets assume I have 3 interfaces Eth0/1 Eth0/2 and Eth0/3 and I want to 
configure the multicast rule for Group G (236.1.2.3) as follow:
1.) The group G stream is acceptable on interface Eth0/1 and Eth0/2 and it is 
blocked on interface Eth0/3.
2.) If group G stream is received on Eth0/1, it is forwarded to Eth0/2 and if 
Eth0/2 receives it then, it should be forwarded to Eth0/1 as well.
If eth0/1 and eth0/2 are both ACCEPT and FROWARDING, that is the behaviour you 
will get. But N.B, multicast will never forward back out the interface on which 
the packet was received (I think that’s what you want but it’s not entirely 
clear).
/neale


Thanks,
Arun

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21249): https://lists.fd.io/g/vpp-dev/message/21249
Mute This Topic: https://lists.fd.io/mt/90417743/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Queries regarding mfib and multicast support in VPP

2022-04-12 Thread arunmittal88 
Hi,

Just want to know if the mfib-lookup node is attached to the default packet 
processing node graph or do we need to explicitly enable this.

Also wanted to understand if the following things are achievable with mfib in 
VPP (To understand the mfib in VPP I am following 
"https://wiki.fd.io/view/VPP/MFIB; page).

Lets assume I have 3 interfaces Eth0/1 Eth0/2 and Eth0/3 and I want to 
configure the multicast rule for Group G (236.1.2.3) as follow:
1.) The group G stream is acceptable on interface Eth0/1 and Eth0/2 and it is 
blocked on interface Eth0/3.
2.) If group G stream is received on Eth0/1, it is forwarded to Eth0/2 and if 
Eth0/2 receives it then, it should be forwarded to Eth0/1 as well.

Thanks,
Arun

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21238): https://lists.fd.io/g/vpp-dev/message/21238
Mute This Topic: https://lists.fd.io/mt/90417743/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-