interface with multiple IPs not working #197

zadm · 2021-08-20T13:20:30Z

zadm
Aug 20, 2021

Hello,

I'am configuring pimd in a linux box acting as a router, I have a vlan interface with 2 ips

ip add show bond1.2016
300295: bond1.2016@bond1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether a0:36:9f:d4:65:0a brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.169/29 brd 192.168.3.175 scope global bond1.2016
       valid_lft forever preferred_lft forever
    inet 10.200.75.161/27 brd 10.200.75.191 scope global bond1.2016
       valid_lft forever preferred_lft forever
    inet6 fe80::a236:9fff:fed4:650a/64 scope link 
       valid_lft forever preferred_lft forever

The receiver machine behind the interface bond1.2016 is configured with an ip in the network 10.200.75.161/27

bellow pimd config file

cat /etc/pimd.conf 

phyint tun10 enable igmpv2
phyint bond1.2016 enable igmpv2
#rp-candidate tun10 time 30 priority 1
#bsr-candidate tun10 priority 5

rp_address  X.X.X.X 224.0.28.89 masklen 32

cand_rp time 30 priority 20         # Smaller value means "higher" priority
cand_bootstrap_router priority 5    # Bigger value means  "higher" priority
spt-threshold                   rate 50000 interval 20  # 50kbps (approx.)

When I start pimd with this config, it create the bellow entry in the routing table

irtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.3.169/29    192.168.3.168/29         1  DR NO-NBR     ==> bond1.2016
  1  10.247.4.178     10.247.4.176/30          1  DR PIM     10.247.4.177   ==> tun10
  2  192.168.3.169     register_vif0            1 

 Vif  SSM Group        Sources

My question is how can I configure pimd to create an entry in the 10.200.75.161/27 network? Or how can make my setup working with 2 IPs ?

FY, I tried to add the ip instead of the interface in the config file but this is not working

Regards

ruckc · 2021-08-20T13:30:54Z

ruckc
Aug 20, 2021

If your trying to use VLANs then your network configuration is wrong. Normally, I only see multiple IP addresses on a NIC if they belong to the same subnet. When PIMD sends network traffic, it sends it out the device (bond1.2016) and the device chooses the source IP address.

I would recommend having those two subnets on separate VLANs so their broadcast traffic doesn't overlap.

0 replies

zadm · 2021-08-20T13:44:38Z

zadm
Aug 20, 2021
Author

Hello ruckc,

thank you for your quick response.

I think my network setup is not wrong because I can see the igmp report traffic in the interface bond1.2016 from the receiver machine

my concern is that when the receiver machine try to subscribe to the multicast groups, I can't see any entry in the Multicast Routing Table

sudo  tcpdump -nni bond1.2016  multicast
13:40:52.455788 IP 0.0.0.0 > 224.0.28.89: igmp v2 report 224.0.28.89
13:40:52.457113 IP 0.0.0.0 > 224.0.28.216: igmp v2 report 224.0.28.216
13:40:52.457457 IP 0.0.0.0 > 224.0.28.89: igmp v2 report 224.0.28.89
13:40:52.475328 IP 0.0.0.0 > 224.0.28.47: igmp v2 report 224.0.28.47
13:40:52.500397 IP 0.0.0.0 > 224.0.28.174: igmp v2 report 224.0.28.174
13:40:52.524270 IP 0.0.0.0 > 224.0.28.5: igmp v2 report 224.0.28.5
13:40:52.526819 IP 0.0.0.0 > 224.0.28.216: igmp v2 report 224.0.28.216
13:40:52.527020 IP 0.0.0.0 > 224.0.28.216: igmp v2 report 224.0.28.216
13:40:52.550986 IP 0.0.0.0 > 224.0.28.47: igmp v2 report 224.0.28.47
13:40:52.558145 IP 0.0.0.0 > 224.0.28.132: igmp v2 report 224.0.28.132
13:40:52.572077 IP 0.0.0.0 > 224.0.28.174: igmp v2 report 224.0.28.174
13:40:52.613778 IP 0.0.0.0 > 224.0.28.5: igmp v2 report 224.0.28.5
13:40:52.626448 IP 0.0.0.0 > 224.0.28.216: igmp v2 report 224.0.28.216
13:40:52.634399 IP 0.0.0.0 > 224.0.28.132: igmp v2 report 224.0.28.132
13:40:52.641213 IP 0.0.0.0 > 224.0.28.47: igmp v2 report 224.0.28.47
13:40:52.720979 IP 0.0.0.0 > 224.0.28.174: igmp v2 report 224.0.28.174
13:40:52.721593 IP 0.0.0.0 > 224.0.28.5: igmp v2 report 224.0.28.5
13:40:52.738742 IP 0.0.0.0 > 224.0.28.132: igmp v2 report 224.0.28.132
13:40:52.838502 IP 0.0.0.0 > 224.0.28.5: igmp v2 report 224.0.28.5
13:40:52.862502 IP 0.0.0.0 > 224.0.28.89: igmp v2 report 224.0.28.89
13:40:52.886524 IP 0.0.0.0 > 224.0.28.47: igmp v2 report 224.0.28.47
13:40:52.906789 IP 0.0.0.0 > 224.0.28.89: igmp v2 report 224.0.28.89
13:40:53.098556 IP 0.0.0.0 > 224.0.28.174: igmp v2 report 224.0.28.174
13:40:53.166288 IP 0.0.0.0 > 224.0.28.132: igmp v2 report 224.0.28.132

sudo pimd -r 
Virtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.3.169    192.168.3.168/29          1  DR NO-NBR
  1  10.247.4.178     10.247.4.176/30          1  DR PIM     10.247.4.177   
  2  192.168.3.169     register_vif0            1 

 Vif  SSM Group        Sources             

Multicast Routing Table ======================================================
--------------------------------- (*,*,G) ------------------------------------
Number of Groups: 0
Number of Cache MIRRORs: 0
------------------------------------------------------------------------------

0 replies

troglobit · 2021-08-21T05:54:38Z

troglobit
Aug 21, 2021
Maintainer

If I understood your setup, I think you may be able to solve your problem by using the altnet 10.200.75.161/27 argument to phyint.

In pimd versions < 3.x, the first interface address found is the only address pimd considers. As of pimd 3.0 (still unreleased), the first address found enumerates the VIF and any other addresses found for the same interface adds altnets automatically.

2 replies

zadm Aug 23, 2021
Author

Hello troglobit
thank you so much for your reply

I have added the altnet 10.200.75.161/27 to phyint

phyint bond1.2016 enable igmpv2 altnet 10.200.75.160/27

When I start pimd in debug mode I see the bellow output related to this interface

12:21:15.352 Installing bond1.2016 ( 192.168.3.169 on subnet  192.168.3.168/29) VIF #0 (ifindex: 300295), rate 0                                                                                  
12:21:15.352 Ignoring bond1.2016 (10.200.75.161 on subnet 10.200.75.160/29) (alias for vif#0?)
12:23:50.471 ALTNET: 10.200.75.160/27

And the virtual interfacae table

Virtual Interface Table ======================================================                 
Vif  Local Address    Subnet              Thresh  Flags      Neighbors                         
---  ---------------  ------------------  ------  ---------  -----------------                 
  0  192.168.3.169     192.168.3.168/29          1  DR NO-NBR                                    
  1  10.247.4.178     10.247.4.176/30          1  DR NO-NBR                                    
  2  192.168.3.169     register_vif0            1                                                                                                                                              
                                                                                                                                                                                              
 Vif  SSM Group        Sources

And nothing in the Multicast Routing Table

Multicast Routing Table ======================================================
--------------------------------- (*,*,G) ------------------------------------
Number of Groups: 0
Number of Cache MIRRORs: 0
------------------------------------------------------------------------------

Is it expected to not see the network 10.200.75.160/27 in the Virtual Interface Table ?

Best regards

troglobit Sep 23, 2021
Maintainer

Hi again, and sorry for coming back to this so late. The altnet option is described in the man page:

altnet <network/len>
       Alternative host(s)/network(s) to accept as locally attached multicast sources on a given
       interface. If a phyint is attached to multiple IP subnets, describe each additional subnet
       with the altnet keyword.

I.e., it is used to identify incoming multicast from a given source with an inbound multicast VIF.
You cannot peer with another PIM router using these secondary IP addresses. Only prevent
inbound multicast on a multinetted network from being dropped.

troglobit · 2021-08-21T17:58:39Z

troglobit
Aug 21, 2021
Maintainer

Converted to discussion, since this doesn't seem to be a bug report, but more of a support request.

3 replies

eduarmen Jul 20, 2023

Does PIMD supports data forwarding between same subnets?, I mean if I have the following subnet:

PC1(192.168.1.10) connected to Device1(192.168.1.251 and 169.254.2.58), Device1 is connected to Device2 (169.254.3.24 and 192.168.1.252), Device2 is connected to PC2 (192.168.1.11)
---------------------------------- ---------------------------------
192.168.1.10 <--> | 192.168.1.251 | | 192.168.1.252 | <--> 192.168.1.11
| 169.254.2.58 | <--> | 169.254.3.24 |
---------------------------------- ----------------------------------

I'm not able to forward multicast traffic from PC1 to PC2 using above IPs.

But if I change the IP of PC2 and Device2 like this:

PC1(192.168.1.10) connected to Device1(192.168.1.251 and 169.254.2.58), Device1 is connected to Device2 (169.254.3.24 and 192.168.2.252), Device2 is connected to PC2 (192.168.2.11)

                            ----------------------------------            ---------------------------------

192.168.1.10 <--> | 192.168.1.251 | | 192.168.2.252 | <--> 192.168.2.11
| 169.254.2.58 | <--> | 169.254.3.24 |
---------------------------------- ----------------------------------

This is working. I can send data from PC1 to PC2 using PIMD.

I'm running PIMD on Device1 and Device2, my PIMD.conf file for both is this:

default-route-distance 2
default-route-metric 2

phyint eth0 enable
phyint eth1 enable

igmp-query-interval 1
igmp-querier-timeout 8

bsr-candidate priority 5

rp-candidate time 30 priority 20

rp-address 192.168.1.10 224.0.0.0/4

spt-threshold packets 0 interval 5

Thanks,
Eduardo

troglobit Jul 20, 2023
Maintainer

Depends more on your IP and interface setup than pimd. Overlapping subnets is not supported.

eduarmen Sep 12, 2023

Hi,

Thanks I got it!, now I want to forward data from PC2 to PC1, but I can't. I'm only able to forward data from PC1 to PC2, this is my network setup:

PC1 <----> NWC1 <---> NWC2 <---> PC2

I'm running the pimd daemon on the Network Card 1 (NWC1) and on the Network Card 2 (NWC2).

the pimd.conf for NWC1 is the following:

phyint eth0 disable
phyint eth1 enable

bsr-candidate 169.254.15.45

rp-candidate 169.254.15.45 time 100
group-prefix 224.0.0.0 masklen 4

spt-threshold packets 0 interval 100

the pimd.conf for NWC2 is the following:

phyint eth0 disable
phyint eth1 enable

bsr-candidate 169.254.11.252

rp-candidate 169.254.11.252 time 100
group-prefix 224.0.0.0 masklen 4

spt-threshold packets 0 interval 100

I have joined a multicast group on PC1 (225.0.21.0) and on PC2(225.0.17.0). The routing tables are as follow:

NWC1:

Virtual Interface Table ======================================================                  
Vif  Local Address    Subnet              Thresh  Flags      Neighbors                          
---  ---------------  ------------------  ------  ---------  -----------------                  
  0  169.254.15.45    169.254                  1  DR PIM     169.254.11.252                     
  1  192.168.2.250    192.168.2                1  DR NO-NBR                                     
  2  169.254.15.45    register_vif0            1                                                
                                                                                                
 Vif  SSM Group        Sources                                                                  
                                                                                                
12:58:03.674 Send PIM JOIN/PRUNE from 169.254.15.45 on eth0:avahi                               
12:58:03.674 SENT    74 bytes PIM v2 Join/Prune         from 169.254.15.45   to 224.0.0.13      
                                                                                                
Multicast Routing Table ======================================================                  
----------------------------------- (*,G) ------------------------------------                  
Source           Group            RP Address       Flags                                        
---------------  ---------------  ---------------  ---------------------------                  
INADDR_ANY       225.0.21.0       169.254.11.252   WC RP                                        
Joined   oifs: ...                                                                              
Pruned   oifs: ...                                                                              
Leaves   oifs: .l.                                                                              
Asserted oifs: ...                                                                              
Outgoing oifs: .o.                                                                              
Incoming     : I..                                                                              
                                                                                                
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                               
             0    60     0       0        0  0  0                                               
----------------------------------- (S,G) ------------------------------------                  
----------------------------------- (*,G) ------------------------------------                  
Source           Group            RP Address       Flags                                        
---------------  ---------------  ---------------  ---------------------------                  
INADDR_ANY       239.0.0.2        169.254.11.252   WC RP                                        
Joined   oifs: ...                                                                              
Pruned   oifs: ...                                                                              
Leaves   oifs: l..                                                                              
Asserted oifs: ...                                                                              
Outgoing oifs: o..                                                                              
Incoming     : I..                                                                              
                                                                                                
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                               
             0    60     0       0        0  0  0                                               
----------------------------------- (S,G) ------------------------------------                  
--------------------------------- (*,*,G) ------------------------------------                  
Number of Groups: 2                                                                             
Number of Cache MIRRORs: 0                                                                      
------------------------------------------------------------------------------                  
                                                                                                
Candidate Rendezvous-Point Set ===============================================                  
RP address       Incoming  Group Prefix        Priority  Holdtime                               
---------------  --------  ------------------  --------  ---------------------                  
169.254.15.45    2         224/4               0         185                                    
169.254.11.252   0         224/4               0         225                                    
169.254.0.1      0         232/8               1         65535                                  
------------------------------------------------------------------------------                  
Current BSR address: 169.254.15.45

NWC2:

Virtual Interface Table ======================================================            
Vif  Local Address    Subnet              Thresh  Flags      Neighbors                    
---  ---------------  ------------------  ------  ---------  -----------------            
  0  169.254.11.252   169.254                  1  PIM        169.254.15.45                
  1  192.168.3.250    192.168.3                1  DR NO-NBR                               
  2  169.254.11.252   register_vif0            1                                          
                                                                                          
 Vif  SSM Group        Sources                                                            
                                                                                          
                                                                                          
Multicast Routing Table ======================================================            
----------------------------------- (*,G) ------------------------------------            
Source           Group            RP Address       Flags                                  
---------------  ---------------  ---------------  ---------------------------            
INADDR_ANY       225.0.17.0       169.254.11.252   WC RP                                  
Joined   oifs: ...                                                                        
Pruned   oifs: ...                                                                        
Leaves   oifs: .l.                                                                        
Asserted oifs: ...                                                                        
Outgoing oifs: .o.                                                                        
Incoming     : .I                                                                        
                                                                                          
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                         
             0    55     0       0        0  0  0                                         
----------------------------------- (S,G) ------------------------------------            
----------------------------------- (*,G) ------------------------------------            
Source           Group            RP Address       Flags                                  
---------------  ---------------  ---------------  ---------------------------            
INADDR_ANY       225.0.21.0       169.254.11.252   WC RP                                  
Joined   oifs: j..                                                                        
Pruned   oifs: ...                                                                        
Leaves   oifs: ...                                                                        
Asserted oifs: ...                                                                        
Outgoing oifs: o..                                                                        
Incoming     : ..I                                                                        
                                                                                          
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                         
           205    60     0       0       205  0  0                                        
----------------------------------- (S,G) ------------------------------------            
----------------------------------- (*,G) ------------------------------------            
Source           Group            RP Address       Flags                                  
---------------  ---------------  ---------------  ---------------------------            
INADDR_ANY       239.0.0.2        169.254.11.252   WC RP                                  
Joined   oifs: j..                                                                        
Pruned   oifs: ...                                                                        
Leaves   oifs: l..                                                                        
Asserted oifs: ...                                                                        
Outgoing oifs: o..                                                                        
Incoming     : ..I                                                                        
                                                                                          
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                         
           205    60     0       0       205  0  0                                        
----------------------------------- (S,G) ------------------------------------            
----------------------------------- (S,G) ------------------------------------            
Source           Group            RP Address       Flags                                  
---------------  ---------------  ---------------  ---------------------------            
169.254.52.16    239.255.255.250  169.254.15.45    SG                                     
Joined   oifs: ...                                                                        
Pruned   oifs: ...                                                                        
Leaves   oifs: ...                                                                        
Asserted oifs: ...                                                                        
Outgoing oifs: ...                                                                        
Incoming     : I..                                                                        
                                                                                          
TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2                                         
           180    35     0       0        0  0  0                                         
--------------------------------- (*,*,G) ------------------------------------            
Number of Groups: 4                                                                       
Number of Cache MIRRORs: 0                                                                         
                                                                                          
Candidate Rendezvous-Point Set ===============================================            
RP address       Incoming  Group Prefix        Priority  Holdtime                         
---------------  --------  ------------------  --------  ---------------------            
169.254.15.45    0         224/4               0         180                              
169.254.11.252   2         224/4               0         220                              
169.254.0.1      0         232/8               1         65535                            
        
Current BSR address: 169.254.15.45

I noticed in NWC1 tables the group 225.0.17.0 (PC2 has joined) is not present, I suspect here is the problem.

Do you notice something wrong in the pimd.conf files? Any ide why data are forwarded only from PC1 and PC2 and not vice versa?.

As an experiment I left only rp-candidate in NWC2 and only bsr-candidate in NWC1 and I'm able to send data from PC2 to PC1, but I need bidirectional traffic.

Thanks.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

interface with multiple IPs not working #197

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

interface with multiple IPs not working #197

zadm Aug 20, 2021

Replies: 4 comments · 5 replies

ruckc Aug 20, 2021

zadm Aug 20, 2021 Author

troglobit Aug 21, 2021 Maintainer

zadm Aug 23, 2021 Author

troglobit Sep 23, 2021 Maintainer

troglobit Aug 21, 2021 Maintainer

eduarmen Jul 20, 2023

troglobit Jul 20, 2023 Maintainer

eduarmen Sep 12, 2023

zadm
Aug 20, 2021

Replies: 4 comments 5 replies

ruckc
Aug 20, 2021

zadm
Aug 20, 2021
Author

troglobit
Aug 21, 2021
Maintainer

zadm Aug 23, 2021
Author

troglobit Sep 23, 2021
Maintainer

troglobit
Aug 21, 2021
Maintainer

troglobit Jul 20, 2023
Maintainer