Sonos speakers and applications on different subnets (VLAN's)

jimp · Jan 27, 2020, 1:24 PM

@Qinn said in Sonos speakers and applications on different subnets (VLAN's):

The moment I start PIMD from the CLI using my old config file the Sonos devices and Sonos apps (both on different VLAN's) find one another in a few seconds.

What is in your old config exactly?

@Qinn said in Sonos speakers and applications on different subnets (VLAN's):

BTW is there a way to set the GUI interface to the debug settings like

No, not currently.

@Qinn said in Sonos speakers and applications on different subnets (VLAN's):

I tried to set the log level in the General tab, but it doesn't change anything in the Status tab.

That affects what gets put into the system logs by pimd, it doesn't change anything in the status output.

stephenw10 · Jan 27, 2020, 1:29 PM

You should see more logs from pimd in the system log though.

You can try stopping pimd in the gui and start it from the CLI using the generated config file. The conf file is pretty much identical to your initial post here if you have only set the interfaces. It can only be how it's started that is different, which by default is:

/usr/local/sbin/pimd -c /var/etc/pimd/pimd.conf --disable-vifs -s notice

Steve

Qinn · Jan 27, 2020, 2:14 PM

phyint pppoe0 disable
phyint igb1.1002 disable
phyint igb1.1003 disable
phyint igb1.1004 disable
phyint igb0 disable
phyint igb1.1007 disable
phyint igb1.1008 disable

Above the only thing I added/changed to the default pimd.conf file, this means that PIMD is running on 1010 and 1005, as there are no 1006 and 1009. Running PIMD with the debug option confirms this.

jimp · Jan 27, 2020, 2:16 PM

Your config doesn't contain any enable interfaces, so you need to change the default bind to Bind to All. The GUI package defaults to Bind to None, which with your config means "bind to nothing", so it won't start.

You are better off leaving the default behavior and then making interface entries for the ones you do want, set to always bind.

Qinn · Jan 27, 2020, 3:27 PM

pimd -d -c /var/etc/pimd.conf.del

That's the old conf file and it still works 'when loading it in the PIMD daemon on the command line, the file the GUI makes eg uses is in

[2.4.4-RELEASE][root@pfSense.localdomain]/: find / -name 'pimd.*'
/var/etc/pimd/pimd.conf
/var/etc/pimd.conf.del
/var/run/pimd/pimd.dump
/etc/inc/priv/pimd.priv.inc
/usr/local/etc/pimd.conf
/usr/local/etc/rc.d/pimd.sh
/usr/local/etc/pimd.conf.sample
/usr/local/pkg/pimd.inc
/usr/local/pkg/shortcuts/pimd.sc.inc
/usr/local/pkg/pimd.xml
/usr/local/man/man8/pimd.8.gz
[2.4.4-RELEASE][root@pfSense.localdomain]/: cat /var/etc/pimd/pimd.conf
##################### DO NOT EDIT THIS FILE! ######################
###################################################################
# This file was created by an automatic configuration generator.  #
# The contents of this file will be overwritten without warning!  #
###################################################################
phyint igb1.1005 enable
phyint igb1.1001 enable
[2.4.4-RELEASE][root@pfSense.localdomain]/:

stephenw10 · Jan 27, 2020, 3:36 PM

Yes it starts with the --disable-vifs switch so the conf file is the inverse of yours but both ways should result in it using igb1.1001 and igb1.1005. By default at least.

You can set the pfSense package to 'Bind to all' by default and then set those interfaces to 'Do not bind' and the resulting conf file should be exactly the same as yours was.

Steve

Qinn · Jan 27, 2020, 3:41 PM

When I start PIMD using the commandline and with option -d I can see what happens and I see that it works

[2.4.4-RELEASE][root@pfSense.localdomain]/root: pimd -d -c /var/etc/pimd.conf.del
debug level 0xffffffff (dvmrp_detail,dvmrp_prunes,dvmrp_routes,dvmrp_neighbors,dvmrp_timers,igmp_proto,igmp_timers,igmp_members,trace,timeout,packets,interfaces,kernel,cache,rsrr,pimdetail,pim_hello,pim_register,pim_join_prune,pim_bootstrap,pim_asserts,pim_cand_rp,pim_routes,pim_timers,pim_rpf)
13:19:09.017 pimd version 2.3.2 starting ...
13:19:09.019 Got 262144 byte send buffer size in 0 iterations
13:19:09.019 Got 262144 byte recv buffer size in 0 iterations
13:19:09.019 Got 262144 byte send buffer size in 0 iterations
13:19:09.019 Got 262144 byte recv buffer size in 0 iterations
13:19:09.019 Getting vifs from kernel
13:19:09.019 Installing igb0 (192.168.100.2 on subnet 192.168.100) as vif #0 - rate 0
13:19:09.019 Installing igb1.1002 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0
13:19:09.020 Installing igb1.1005 (192.168.5.1 on subnet 192.168.5) as vif #2 - rate 0
13:19:09.020 Installing igb1.1003 (10.0.0.1 on subnet 10/24) as vif #3 - rate 0
13:19:09.020 Installing igb1.1004 (172.16.0.1 on subnet 172.16/24) as vif #4 - rate 0
13:19:09.020 Installing igb1.1010 (172.16.10.1 on subnet 172.16.10/24) as vif #5 - rate 0
13:19:09.020 Installing igb1.1007 (172.16.20.1 on subnet 172.16.20/24) as vif #6 - rate 0
13:19:09.020 Installing igb1.1001 (192.168.1.1 on subnet 192.168.1) as vif #7 - rate 0
13:19:09.020 Ignoring igb1.1001 (10.10.10.1 on subnet 10.10.10/24) (alias for vif#7?)
13:19:09.020 Installing igb1.1008 (192.168.8.1 on subnet 192.168.8) as vif #8 - rate 0
13:19:09.020 Installing pppoe0 (194.xxx.xxx.xxx -> 194.xxx.xxx.xxx) as vif #9 - rate=0
13:19:09.020 Getting vifs from /var/etc/pimd.conf.del
13:19:09.020 Local Cand-BSR address 192.168.5.1, priority 5
13:19:09.020 Local Cand-RP address 192.168.5.1, priority 20, interval 30 sec
13:19:09.020 spt-threshold packets 0 interval 100
13:19:09.020 Local static RP: 169.254.0.1, group 232.0.0.0/8
13:19:09.020 IGMP query interval  : 12 sec
13:19:09.020 IGMP querier timeout : 41 sec
13:19:09.021 Interface igb0 is DISABLED; vif #0 out of service
13:19:09.021 Interface igb1.1002 is DISABLED; vif #1 out of service
13:19:09.021 Interface igb1.1005 comes up; vif #2 now in service
13:19:09.022 query_groups(): Sending IGMP v3 query on igb1.1005
13:19:09.022 Send IGMP Membership Query     from 192.168.5.1 to 224.0.0.1
13:19:09.022 SENT    36 bytes IGMP Membership Query     from 192.168.5.1     to 224.0.0.1
13:19:09.022 SENT    46 bytes PIM v2 Hello              from 192.168.5.1     to 224.0.0.13
13:19:09.022 Interface igb1.1003 is DISABLED; vif #3 out of service
13:19:09.022 Interface igb1.1004 is DISABLED; vif #4 out of service
13:19:09.022 Interface igb1.1010 comes up; vif #5 now in service
13:19:09.022 query_groups(): Sending IGMP v3 query on igb1.1010
13:19:09.023 Send IGMP Membership Query     from 172.16.10.1 to 224.0.0.1
13:19:09.023 SENT    36 bytes IGMP Membership Query     from 172.16.10.1     to 224.0.0.1
13:19:09.023 SENT    46 bytes PIM v2 Hello              from 172.16.10.1     to 224.0.0.13
13:19:09.023 Interface igb1.1007 is DISABLED; vif #6 out of service
13:19:09.023 Interface igb1.1001 comes up; vif #7 now in service
13:19:09.023 query_groups(): Sending IGMP v3 query on igb1.1001
13:19:09.023 Send IGMP Membership Query     from 192.168.1.1 to 224.0.0.1
13:19:09.023 SENT    36 bytes IGMP Membership Query     from 192.168.1.1     to 224.0.0.1
13:19:09.023 SENT    46 bytes PIM v2 Hello              from 192.168.1.1     to 224.0.0.13
13:19:09.023 Interface igb1.1008 is DISABLED; vif #8 out of service
13:19:09.023 Interface pppoe0 is DISABLED; vif #9 out of service
13:19:09.023 Interface register_vif0 comes up; vif #10 now in service
Virtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.100.2    192.168.100              1  DISABLED
  1  192.168.2.1      192.168.2                1  DISABLED
  2  192.168.5.1      192.168.5                1  DR NO-NBR
  3  10.0.0.1         10/24                    1  DISABLED
  4  172.16.0.1       172.16/24                1  DISABLED
  5  172.16.10.1      172.16.10/24             1  DR NO-NBR
  6  172.16.20.1      172.16.20/24             1  DISABLED
  7  192.168.1.1      192.168.1                1  DR NO-NBR
  8  192.168.8.1      192.168.8                1  DISABLED
  9  194.xxx.xxx.xxx   194.xxx.xxx.xxx/32        1  DISABLED
 10  192.168.5.1      register_vif0            1

 Vif  SSM Group        Sources

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

13:19:09.024 Received IGMP Membership Query     from 172.16.10.1 to 224.0.0.1
13:19:09.024 RECV    46 bytes PIM v2 Hello              from 192.168.5.1     to 224.0.0.13
13:19:09.025 Received IGMP Membership Query     from 192.168.1.1 to 224.0.0.1
13:19:09.025 RECV    46 bytes PIM v2 Hello              from 172.16.10.1     to 224.0.0.13
13:19:09.025 RECV    46 bytes PIM v2 Hello              from 192.168.1.1     to 224.0.0.13
13:19:09.029 Received IGMP v3 Membership Report from 192.168.1.1 to 224.0.0.22
13:19:09.029 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.1.1 to 224.0.0.22 with 3 group records.
13:19:09.029 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:09.029 Set delete timer for group: 224.0.0.22
13:19:09.029 SM group order from  192.168.1.1 (*,224.0.0.22)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:09.030 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.2
13:19:09.030 SM group order from  192.168.1.1 (*,224.0.0.2)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:09.030 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.13
13:19:09.030 SM group order from  192.168.1.1 (*,224.0.0.13)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:09.030 Received IGMP v3 Membership Report from 172.16.10.1 to 224.0.0.22
13:19:09.030 accept_membership_report(): IGMP v3 report, 32 bytes, from 172.16.10.1 to 224.0.0.22 with 3 group records.
13:19:09.030 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.22
13:19:09.030 SM group order from  172.16.10.1 (*,224.0.0.22)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:09.030 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.2
13:19:09.030 SM group order from  172.16.10.1 (*,224.0.0.2)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:09.030 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.13
13:19:09.030 SM group order from  172.16.10.1 (*,224.0.0.13)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:09.030 Received IGMP v3 Membership Report from 192.168.5.1 to 224.0.0.22
13:19:09.030 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.5.1 to 224.0.0.22 with 3 group records.
13:19:09.030 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.22
13:19:09.030 SM group order from  192.168.5.1 (*,224.0.0.22)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:09.030 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.2
13:19:09.030 SM group order from  192.168.5.1 (*,224.0.0.2)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:09.030 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:09.030 Set delete timer for group: 224.0.0.13
13:19:09.030 SM group order from  192.168.5.1 (*,224.0.0.13)
13:19:09.030 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:09.229 Received IGMP v3 Membership Report from 172.16.10.1 to 224.0.0.22
13:19:09.229 accept_membership_report(): IGMP v3 report, 32 bytes, from 172.16.10.1 to 224.0.0.22 with 3 group records.
13:19:09.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:09.229 Set delete timer for group: 224.0.0.22
13:19:09.229 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:09.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:09.229 Set delete timer for group: 224.0.0.2
13:19:09.229 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:09.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:09.229 Set delete timer for group: 224.0.0.13
13:19:09.229 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:09.234 Received IGMP Leave message        from 172.16.10.20 to 224.0.0.2
13:19:09.234 accept_leave_message(): src 172.16.10.20 dst 224.0.0.2 group 224.0.0.251
13:19:09.234 Received IGMP v2 Membership Report from 172.16.10.20 to 224.0.0.251
13:19:09.234 accept_group_report(): igmp_src 172.16.10.20 ssm_src 224.0.0.251 group 224.0.0.251 report_type 22
13:19:09.234 Change IGMP compatibility mode to v2 for group 224.0.0.251
13:19:09.234 Set delete timer for group: 224.0.0.251
13:19:09.234 SM group order from  172.16.10.20 (*,224.0.0.251)
13:19:09.234 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:10.029 Received IGMP v3 Membership Report from 192.168.1.1 to 224.0.0.22
13:19:10.029 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.1.1 to 224.0.0.22 with 3 group records.
13:19:10.029 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:10.029 Set delete timer for group: 224.0.0.22
13:19:10.029 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:10.029 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:10.029 Set delete timer for group: 224.0.0.2
13:19:10.029 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:10.030 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:10.030 Set delete timer for group: 224.0.0.13
13:19:10.030 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:10.600 Received IGMP v2 Membership Report from 192.168.1.100 to 224.0.0.252
13:19:10.600 accept_group_report(): igmp_src 192.168.1.100 ssm_src 224.0.0.252 group 224.0.0.252 report_type 22
13:19:10.600 Change IGMP compatibility mode to v2 for group 224.0.0.252
13:19:10.600 Set delete timer for group: 224.0.0.252
13:19:10.600 SM group order from  192.168.1.100 (*,224.0.0.252)
13:19:10.600 Not creating routing entry for LAN scoped group 224.0.0.252
13:19:11.229 Received IGMP v3 Membership Report from 172.16.10.1 to 224.0.0.22
13:19:11.229 accept_membership_report(): IGMP v3 report, 32 bytes, from 172.16.10.1 to 224.0.0.22 with 3 group records.
13:19:11.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:11.229 Set delete timer for group: 224.0.0.22
13:19:11.229 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:11.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:11.229 Set delete timer for group: 224.0.0.2
13:19:11.229 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:11.229 accept_group_report(): igmp_src 172.16.10.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:11.229 Set delete timer for group: 224.0.0.13
13:19:11.229 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:11.829 Received IGMP v3 Membership Report from 192.168.5.1 to 224.0.0.22
13:19:11.829 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.5.1 to 224.0.0.22 with 3 group records.
13:19:11.829 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:11.829 Set delete timer for group: 224.0.0.22
13:19:11.829 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:11.829 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:11.829 Set delete timer for group: 224.0.0.2
13:19:11.830 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:11.830 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:11.830 Set delete timer for group: 224.0.0.13
13:19:11.830 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:12.260 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:12.260 create group entry, group 239.255.255.250
13:19:12.829 Received IGMP v3 Membership Report from 192.168.1.1 to 224.0.0.22
13:19:12.829 accept_membership_report(): IGMP v3 report, 40 bytes, from 192.168.1.1 to 224.0.0.22 with 4 group records.
13:19:12.829 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:12.829 Set delete timer for group: 224.0.0.22
13:19:12.830 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:12.830 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:12.830 Set delete timer for group: 224.0.0.2
13:19:12.830 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:12.830 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:12.830 Set delete timer for group: 224.0.0.13
13:19:12.830 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:12.830 accept_group_report(): igmp_src 192.168.1.1 ssm_src 0.0.0.0 group 224.0.0.251 report_type 34
13:19:12.830 Set delete timer for group: 224.0.0.251
13:19:12.830 SM group order from  192.168.1.1 (*,224.0.0.251)
13:19:12.830 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:13.092 Received IGMP v2 Membership Report from 192.168.1.4 to 224.0.0.251
13:19:13.092 accept_group_report(): igmp_src 192.168.1.4 ssm_src 224.0.0.251 group 224.0.0.251 report_type 22
13:19:13.092 accept_group_report(): al_pv=3
13:19:13.092 Change IGMP compatibility mode to v2 for group 224.0.0.251
13:19:13.092 Set delete timer for group: 224.0.0.251
13:19:13.092 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:13.780 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:13.780 create group entry, group 239.255.255.250

Virtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.100.2    192.168.100              1  DISABLED
  1  192.168.2.1      192.168.2                1  DISABLED
  2  192.168.5.1      192.168.5                1  DR NO-NBR
  3  10.0.0.1         10/24                    1  DISABLED
  4  172.16.0.1       172.16/24                1  DISABLED
  5  172.16.10.1      172.16.10/24             1  DR NO-NBR
  6  172.16.20.1      172.16.20/24             1  DISABLED
  7  192.168.1.1      192.168.1                1  DR NO-NBR
  8  192.168.8.1      192.168.8                1  DISABLED
  9  194.xxx.xxx.xxx   194.xxx.xxx.xxx/32        1  DISABLED
 10  192.168.5.1      register_vif0            1

 Vif  SSM Group        Sources


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

13:19:14.782 SENT    34 bytes PIM v2 Bootstrap          from 192.168.5.1     to 224.0.0.13
13:19:14.782 SENT    34 bytes PIM v2 Bootstrap          from 172.16.10.1     to 224.0.0.13
13:19:14.782 SENT    34 bytes PIM v2 Bootstrap          from 192.168.1.1     to 224.0.0.13
Candidate Rendezvous-Point Set ===============================================
RP address       Incoming  Group Prefix        Priority  Holdtime
---------------  --------  ------------------  --------  ---------------------
------------------------------------------------------------------------------
Current BSR address: 192.168.5.1

13:19:14.782 RECV    34 bytes PIM v2 Bootstrap          from 192.168.5.1     to 224.0.0.13
13:19:14.782 RECV    34 bytes PIM v2 Bootstrap          from 172.16.10.1     to 224.0.0.13
13:19:14.782 RECV    34 bytes PIM v2 Bootstrap          from 192.168.1.1     to 224.0.0.13
13:19:15.840 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:15.840 create group entry, group 239.255.255.250
13:19:16.100 Received IGMP v2 Membership Report from 192.168.1.100 to 239.255.255.250
13:19:16.100 accept_group_report(): igmp_src 192.168.1.100 ssm_src 239.255.255.250 group 239.255.255.250 report_type 22
13:19:16.100 Change IGMP compatibility mode to v2 for group 239.255.255.250
13:19:16.100 Set delete timer for group: 239.255.255.250
13:19:16.100 SM group order from  192.168.1.100 (*,239.255.255.250)
13:19:16.100 create group entry, group 239.255.255.250
13:19:17.384 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:17.384 create group entry, group 239.255.255.250

Virtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.100.2    192.168.100              1  DISABLED
  1  192.168.2.1      192.168.2                1  DISABLED
  2  192.168.5.1      192.168.5                1  DR NO-NBR
  3  10.0.0.1         10/24                    1  DISABLED
  4  172.16.0.1       172.16/24                1  DISABLED
  5  172.16.10.1      172.16.10/24             1  DR NO-NBR
  6  172.16.20.1      172.16.20/24             1  DISABLED
  7  192.168.1.1      192.168.1                1  DR NO-NBR
  8  192.168.8.1      192.168.8                1  DISABLED
  9  194.xxx.xxx.xxx   194.xxx.xxx.xxx/32        1  DISABLED
 10  192.168.5.1      register_vif0            1

 Vif  SSM Group        Sources


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

Candidate Rendezvous-Point Set ===============================================
RP address       Incoming  Group Prefix        Priority  Holdtime
---------------  --------  ------------------  --------  ---------------------
------------------------------------------------------------------------------
Current BSR address: 192.168.5.1

13:19:22.340 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:22.340 create group entry, group 239.255.255.250
13:19:23.871 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:23.871 create group entry, group 239.255.255.250
13:19:24.873 query_groups(): Sending IGMP v3 query on igb1.1005
13:19:24.873 Send IGMP Membership Query     from 192.168.5.1 to 224.0.0.1
13:19:24.873 SENT    36 bytes IGMP Membership Query     from 192.168.5.1     to 224.0.0.1
13:19:24.873 query_groups(): Sending IGMP v3 query on igb1.1010
13:19:24.873 Send IGMP Membership Query     from 172.16.10.1 to 224.0.0.1
13:19:24.873 SENT    36 bytes IGMP Membership Query     from 172.16.10.1     to 224.0.0.1
13:19:24.873 query_groups(): Sending IGMP v3 query on igb1.1001
13:19:24.873 Send IGMP Membership Query     from 192.168.1.1 to 224.0.0.1
13:19:24.874 SENT    36 bytes IGMP Membership Query     from 192.168.1.1     to 224.0.0.1

Virtual Interface Table ======================================================
Vif  Local Address    Subnet              Thresh  Flags      Neighbors
---  ---------------  ------------------  ------  ---------  -----------------
  0  192.168.100.2    192.168.100              1  DISABLED
  1  192.168.2.1      192.168.2                1  DISABLED
  2  192.168.5.1      192.168.5                1  DR NO-NBR
  3  10.0.0.1         10/24                    1  DISABLED
  4  172.16.0.1       172.16/24                1  DISABLED
  5  172.16.10.1      172.16.10/24             1  DR NO-NBR
  6  172.16.20.1      172.16.20/24             1  DISABLED
  7  192.168.1.1      192.168.1                1  DR NO-NBR
  8  192.168.8.1      192.168.8                1  DISABLED
  9  194.xxx.xxx.xxx   194.xxx.xxx.xxx/32        1  DISABLED
 10  192.168.5.1      register_vif0            1

 Vif  SSM Group        Sources


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

Candidate Rendezvous-Point Set ===============================================
RP address       Incoming  Group Prefix        Priority  Holdtime
---------------  --------  ------------------  --------  ---------------------
------------------------------------------------------------------------------
Current BSR address: 192.168.5.1

13:19:24.874 Received IGMP Membership Query     from 192.168.5.1 to 224.0.0.1
13:19:24.874 Received IGMP Membership Query     from 172.16.10.1 to 224.0.0.1
13:19:24.874 Received IGMP Membership Query     from 192.168.1.1 to 224.0.0.1
13:19:25.110 Received IGMP v2 Membership Report from 192.168.1.100 to 239.255.255.250
13:19:25.110 accept_group_report(): igmp_src 192.168.1.100 ssm_src 239.255.255.250 group 239.255.255.250 report_type 22
13:19:25.110 accept_group_report(): al_pv=2
13:19:25.110 Set delete timer for group: 239.255.255.250
13:19:25.110 create group entry, group 239.255.255.250
13:19:25.110 route to: 169.254.0.1
13:19:25.110  destination is: 0.0.0.0
13:19:25.110  gateway is: 194.xxx.xxx.xxx
13:19:25.110  iif is 9
13:19:25.110 For src 169.254.0.1, iif is 9, next hop router is 194.xxx.xxx.xxx: NOT A PIM ROUTER
13:19:25.911 Cache miss, src 192.168.1.100, dst 239.255.255.250, iif 7
13:19:25.911 create group entry, group 239.255.255.250
13:19:26.107 Received IGMP v3 Membership Report from 192.168.5.58 to 224.0.0.22
13:19:26.107 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.5.58 to 224.0.0.22 with 3 group records.
13:19:26.107 accept_group_report(): igmp_src 192.168.5.58 ssm_src 0.0.0.0 group 230.199.198.133 report_type 34
13:19:26.107 Set delete timer for group: 230.199.198.133
13:19:26.107 SM group order from  192.168.5.58 (*,230.199.198.133)
13:19:26.107 create group entry, group 230.199.198.133
13:19:26.107 accept_group_report(): igmp_src 192.168.5.58 ssm_src 0.0.0.0 group 239.255.255.250 report_type 34
13:19:26.107 Set delete timer for group: 239.255.255.250
13:19:26.107 SM group order from  192.168.5.58 (*,239.255.255.250)
13:19:26.107 create group entry, group 239.255.255.250
13:19:26.107 accept_group_report(): igmp_src 192.168.5.58 ssm_src 0.0.0.0 group 224.0.0.251 report_type 34
13:19:26.107 Set delete timer for group: 224.0.0.251
13:19:26.107 SM group order from  192.168.5.58 (*,224.0.0.251)
13:19:26.107 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:26.228 Received IGMP v3 Membership Report from 192.168.5.1 to 224.0.0.22
13:19:26.228 accept_membership_report(): IGMP v3 report, 40 bytes, from 192.168.5.1 to 224.0.0.22 with 4 group records.
13:19:26.228 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.22 report_type 34
13:19:26.228 Set delete timer for group: 224.0.0.22
13:19:26.228 Not creating routing entry for LAN scoped group 224.0.0.22
13:19:26.228 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.2 report_type 34
13:19:26.228 Set delete timer for group: 224.0.0.2
13:19:26.228 Not creating routing entry for LAN scoped group 224.0.0.2
13:19:26.228 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.13 report_type 34
13:19:26.228 Set delete timer for group: 224.0.0.13
13:19:26.228 Not creating routing entry for LAN scoped group 224.0.0.13
13:19:26.229 accept_group_report(): igmp_src 192.168.5.1 ssm_src 0.0.0.0 group 224.0.0.251 report_type 34
13:19:26.229 Set delete timer for group: 224.0.0.251
13:19:26.229 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:27.014 Received IGMP v2 Membership Report from 192.168.5.68 to 239.255.255.250
13:19:27.014 accept_group_report(): igmp_src 192.168.5.68 ssm_src 239.255.255.250 group 239.255.255.250 report_type 22
13:19:27.014 accept_group_report(): al_pv=3
13:19:27.014 Change IGMP compatibility mode to v2 for group 239.255.255.250
13:19:27.014 Set delete timer for group: 239.255.255.250
13:19:27.014 create group entry, group 239.255.255.250
13:19:27.192 Received IGMP v2 Membership Report from 192.168.1.4 to 224.0.0.251
13:19:27.192 accept_group_report(): igmp_src 192.168.1.4 ssm_src 224.0.0.251 group 224.0.0.251 report_type 22
13:19:27.192 accept_group_report(): al_pv=2
13:19:27.192 Set delete timer for group: 224.0.0.251
13:19:27.192 Not creating routing entry for LAN scoped group 224.0.0.251
13:19:27.371 Received IGMP v3 Membership Report from 192.168.5.60 to 224.0.0.22
13:19:27.371 accept_membership_report(): IGMP v3 report, 32 bytes, from 192.168.5.60 to 224.0.0.22 with 3 group records.
13:19:27.371 accept_group_report(): igmp_src 192.168.5.60 ssm_src 0.0.0.0 group 230.199.198.133 report_type 34
13:19:27.371 Set delete timer for group: 230.199.198.133
13:19:27.371 create group entry, group 230.199.198.133
13:19:27.372 accept_group_report(): igmp_src 192.168.5.60 ssm_src 0.0.0.0 group 239.255.255.250 report_type 34
13:19:27.372 Set delete timer for group: 239.255.255.250
13:19:27.372 create group entry, group 239.255.255.250
13:19:27.372 accept_group_report(): igmp_src 192.168.5.60 ssm_src 0.0.0.0 group 224.0.0.251 report_type 34
13:19:27.372 Set delete timer for group: 224.0.0.251

With the GUI it doesn't work/ do it's job and I cannot see the output, well just a few lines in the system.log, although it set log level in the GUI to debug.

jimp · Jan 27, 2020, 3:54 PM

Read our last few replies again. You are not comparing apples to apples. We have already explained what is happening.

Qinn · Jan 27, 2020, 4:10 PM

Sorry @jimp that I don't get it. When I use the GUI and set it as shown below the Sonos devices are not accessible.
login-to-view login-to-view login-to-view login-to-view login-to-view login-to-view

The moment I load the "old"config file manually it works.

jimp · Jan 27, 2020, 4:11 PM

Read our replies again. We explained exactly what to change. No need to repeat yourself.

Qinn · Jan 27, 2020, 4:37 PM

Thanks for your patience. I just tested what I think you both suggested;

Default bind "Bind to All" and then added every interface I dont want to use in the interfaces tab to "Never Bind", then enabled PIMD in the General tab, alas I cannot connect to the Sonos interfaces.

wanabe · Jan 27, 2020, 5:58 PM

@Qinn said in Sonos speakers and applications on different subnets (VLAN's):

Thanks for your patience. I just tested what I think you both suggested;

Default bind "Bind to All" and then added every interface I dont want to use in the interfaces tab to "Never Bind", then enabled PIMD in the General tab, alas I cannot connect to the Sonos interfaces.

As I described above, I am having the exact same experience. I have not been successful in getting the pfSense package working for me. I have tried both “Bind to All” and deselecting the interfaces I don’t want to bind, as well as “Bind to None” and selecting the the interfaces that I do want to bind in the interfaces tab without success. When I deleted the pfSense package and manually reinstalled pimd, everything works! BTW, I made sure I uninstalled pimd and rebooted before I installed the pfSense package. I confirmed that the service was enabled and running. Is it possible that the manual installation configures something that is not configured by default in the pfSense package?

jimp · Jan 27, 2020, 6:22 PM

If it works differently then there is either a difference in your configuration or a difference in the command line the package is running. Check the config you are using with the FreeBSD package compared to the GUI, and look at the ps uxaww | grep pimd output for both as well.

The version of pimd is the same, and there shouldn't be anything different about how it operates.

Deviant0ne · Jan 27, 2020, 8:14 PM

@Qinn

I was able to get this working by adding an RP address, specifying the IP address of one of my Sonos speakers and 239.255.255.250 for the multicast group. All of my other settings are identical to your screenshots above.

Update: I was able to confirm using the GUI method is working after configuring all of my Sonos devices in the RP address section with nothing configured for multicast group.

Qinn · Jan 27, 2020, 7:11 PM

I can confirm, that did the trick, strange that you have to add this, when using the GUI and it seems adding the ip of a Sonos device does the trick, but it should not be that way as the ip address of a multicast device should not be needed to make it work and it will not work when using DHCP and not static or reserved addresses.

Deviant0ne · Jan 27, 2020, 8:10 PM

This post is deleted!

stephenw10 · Jan 27, 2020, 8:54 PM

The difference between your working output and the package, at least when you were using default 'do not bind' appears to be that you were enabled on 172.16.10.1 in the manual method but disabled in the package status.

Hard to see how it could be any different otherwise though.

Maybe post the command lines and config files for comparison here from each method. There must be some difference.

Steve

edz · Jan 27, 2020, 9:12 PM

@stephenw10

@stephenw10 said in Sonos speakers and applications on different subnets (VLAN's):

That can sort of error can often be Snort blocking the traffic.

Steve

hmm, ok I'm not using snort but I am using pfblockerNG. Could this be the cause?

JeGr · Jan 27, 2020, 9:45 PM

@Deviant0ne said in Sonos speakers and applications on different subnets (VLAN's):

@Qinn

I was able to get this working by adding an RP address, specifying the IP address of one of my Sonos speakers and 239.255.255.250 for the multicast group. All of my other settings are identical to your screenshots above.

Update: I was able to confirm using the GUI method is working after configuring all of my Sonos devices in the RP address section with nothing configured for multicast group.

Strange, neither one of those options is working for me. Tried out the PIMd package, configured it extremely basic:

VLAN with media devices (Sonos et al)
VLAN LAN
VLAN Guest/Wifi
allowed all VLANs access to each other

set up pimd with

bind none
added the three vlans as "allowed"
default anywhere else

-> no function

under "RP addresses" added my Sonos Beam IP with 239... as group address

-> still nope

removed group address and added other Sonos devices

-> still nope (and many more errors like:)

	For src 172.27.3.30, iif is 5, next hop router is 172.27.3.30: NOT A PIM ROUTER

got entries in status like

Source           Group            RP Address       Flags
---------------  ---------------  ---------------  ---------------------------
172.27.1.128     239.255.255.250  172.27.3.30      CACHE SG
Joined   oifs: ..........j         
Pruned   oifs: ...........         
Leaves   oifs: ...........         
Asserted oifs: ...........         
Outgoing oifs: ..........o         
Incoming     : .I.........         

TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2  3  4  5  6  7  8  9  10
           210    45     0       0        0  0  0  0  0  0  0  0  0  0  0
Source           Group            RP Address       Flags
---------------  ---------------  ---------------  ---------------------------
172.27.3.1       239.255.255.250  172.27.3.30      CACHE SG
Joined   oifs: ..........j         
Pruned   oifs: ...........         
Leaves   oifs: ...........         
Asserted oifs: ...........         
Outgoing oifs: ..........o         
Incoming     : .....I.....         

TIMERS:  Entry    JP    RS  Assert VIFS:  0  1  2  3  4  5  6  7  8  9  10
           185    10     0       0        0  0  0  0  0  0  0  0  0  0  0

but still the android app on the phone won't find the sonos devices/network at all.

Deviant0ne · Jan 27, 2020, 9:58 PM

@JeGr

I was using an iOS device for testing and found that I was experiencing the same issue as some of the other users where my Sonos system could not be located at first - after disabling and re-enabling WiFi on my iOS device, I was able to access my Sonos system without issue. Otherwise, my configuration is nearly identical to what you're describing.