Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    IPtv multicast

    Scheduled Pinned Locked Moved
    Russian
    50
    270
    336.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Dda
      last edited by

      Имею тот же трабл. что и у большинства провайдер НАШНЕТ КИЕВ.
      Кто настраивал и получилось ? Что нужно прописать в upstream какую сеть ? Общался с провайдером - говорит не поступает запрос на соединение. У провайдера каналы вещаются с адресов 228.0.0.Х и тд. В лог кидается вот такой тред

      Feb 19 21:33:33  igmpproxy: Note: RECV Membership query from 172.16.25.1 to 224.0.0.1 (ip_hl 20, data 8)
      Feb 19 21:33:33 igmpproxy: Note: RECV V2 member report from 172.16.25.158 to 224.0.0.2 (ip_hl 20, data 8)
      Feb 19 21:33:33 igmpproxy: Note: Adding MFC: 172.16.25.52 -> 239.255.255.250, InpVIf: 0
      Feb 19 21:33:33 igmpproxy: Note: Adding MFC: 172.16.25.173 -> 239.255.255.250, InpVIf: 0
      Feb 19 21:42:07 igmpproxy: Note: The source address 172.16.25.35 for group 239.255.255.250, is valid DOWNSTREAM VIF #0.
      Feb 19 21:42:07 igmpproxy: Note: New origin for route 239.255.255.250 is 172.16.25.35, flood 0
      Feb 19 21:42:07 igmpproxy: Note: Adding MFC: 172.16.25.35 -> 239.255.255.250, InpVIf: 0
      Feb 19 21:51:36 igmpproxy: Warn: The source address 10.5.5.1 for group 228.0.0.103, is not in any valid net for upstream VIF.
      Feb 19 21:51:36 igmpproxy: Warn: The source address 10.5.5.1 for group 228.0.0.130, is not in any valid net for upstream VIF.
      Feb 19 21:51:36 igmpproxy: Warn: The source address 10.5.5.1 for group 228.0.0.57, is not in any valid net for upstream VIF.

      Настройки делал по статье, что упоминал killeo

      1 Reply Last reply Reply Quote 0
      • E
        Eugene
        last edited by

        10.5.5.0/24 на upstream интерфесе в Networks добавил?

        http://ru.doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • D
          Dda
          last edited by

          @Evgeny:

          10.5.5.0/24 на upstream интерфесе в Networks добавил?

          Пробовал и так тоже. Лог пишет:

          Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 224.0.1.60 on re1
Feb 20 10:40:14 	igmpproxy: Note: Removing MFC: 172.16.25.97 -> 239.192.152.143, InpVIf: 0
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 239.192.152.143 on re1
Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 224.0.1.178 on re1
Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 239.255.255.250 on re1
Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 224.0.0.251 on re1
Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.
Feb 20 10:40:14 	igmpproxy: Note: leaveMcGroup: 224.0.0.252 on re1
Feb 20 10:40:14 	igmpproxy: Note: Route is not active. No kernel updates done.

во время сканирования каналов IP-TV плеером :

Feb 20 10:45:26 	igmpproxy: Note: RECV Membership query from 172.16.25.1 to 224.0.0.1 (ip_hl 20, data 8)
Feb 20 10:45:26 	igmpproxy: Note: RECV V2 member report from 172.16.25.158 to 224.0.0.2 (ip_hl 20, data 8)
Feb 20 10:45:26 	igmpproxy: Note: RECV Membership query from 94.244.154.180 to 224.0.0.1 (ip_hl 20, data 8)
Feb 20 10:45:27 	igmpproxy: Note: RECV V2 member report from 172.16.25.91 to 224.0.0.252 (ip_hl 24, data 8)
Feb 20 10:45:27 	igmpproxy: Note: RECV V2 member report from 172.16.25.32 to 224.0.1.60 (ip_hl 24, data 8)
Feb 20 10:45:28 	igmpproxy: Note: RECV V2 member report from 172.16.25.172 to 239.255.255.250 (ip_hl 24, data 8)
Feb 20 10:45:28 	igmpproxy: Note: RECV V2 member report from 172.16.25.172 to 224.0.0.253 (ip_hl 24, data 8)
Feb 20 10:45:30 	igmpproxy: Note: RECV V2 member report from 172.16.25.173 to 224.0.0.251 (ip_hl 24, data 8)
Feb 20 10:45:30 	igmpproxy: Note: RECV V2 member report from 172.16.25.98 to 224.0.0.2 (ip_hl 24, data 8)

          Версия pfsense 1.2.3 Release
          igmpproxy 0.1

          Rules WAN  lan

          
Proto 	Source 	Port 	Destination 	Port 	Gateway 	Schedule
UDP 	* 	* 	224.0.0.0/4 	* 	* 	  
	Proto 	Source 	Port 	Destination 	Port 	Gateway 	Schedule 	Description 		
	IGMP 	LAN net 	* 	224.0.0.0/4 	* 	* 	  

          Кажись пакет  igmpproxy  у меня старый… можешь выслать работающий пакетик ?

          $ ls -l /usr/local/sbin/igmpproxy
-rwxr-xr-x  1 root  wheel  31060 Feb 19 22:23 /usr/local/sbin/igmpproxy
          1 Reply Last reply Reply Quote 0
          • E
            Eugene
            last edited by

            отсюда

            Feb 20 10:45:26 igmpproxy: Note: RECV Membership query from 172.16.25.1 to 224.0.0.1 (ip_hl 20, data 8)
            Feb 20 10:45:26 igmpproxy: Note: RECV V2 member report from 172.16.25.158 to 224.0.0.2 (ip_hl 20, data 8)
            Feb 20 10:45:26 igmpproxy: Note: RECV Membership query from 94.244.154.180 to 224.0.0.1 (ip_hl 20, data 8)
            Feb 20 10:45:27 igmpproxy: Note: RECV V2 member report from 172.16.25.91 to 224.0.0.252 (ip_hl 24, data 8)
            Feb 20 10:45:27 igmpproxy: Note: RECV V2 member report from 172.16.25.32 to 224.0.1.60 (ip_hl 24, data 8)
            Feb 20 10:45:28 igmpproxy: Note: RECV V2 member report from 172.16.25.172 to 239.255.255.250 (ip_hl 24, data 8)
            Feb 20 10:45:28 igmpproxy: Note: RECV V2 member report from 172.16.25.172 to 224.0.0.253 (ip_hl 24, data 8)
            Feb 20 10:45:30 igmpproxy: Note: RECV V2 member report from 172.16.25.173 to 224.0.0.251 (ip_hl 24, data 8)
            Feb 20 10:45:30 igmpproxy: Note: RECV V2 member report from 172.16.25.98 to 224.0.0.2 (ip_hl 24, data 8)

            что-то вырезано или так и есть в логе?

            http://ru.doc.pfsense.org

            1 Reply Last reply Reply Quote 0
            • D
              Dda
              last edited by

              !!!!! Заработало, блокировалось WAN 10.10.5.1 в firewall.
              Еще вопрос - как лучше настроить балансировку UDP трафика, если у меня 2 входящих интерфейса от провайдера? WAN и OPT1 работают в режиме loadballancing. Но я так понимаю это только для TCP\IP….
              В настройках igmpproxy говорится, что upstream поток может быть только один и он у меня на wan. Downstream смотрит в lan. Как пристроить opt1 ?

              1 Reply Last reply Reply Quote 0
              • E
                Eugene
                last edited by

                @Dda:

                !!!!! Заработало, блокировалось WAN 10.10.5.1 в firewall.
                Еще вопрос - как лучше настроить балансировку UDP трафика, если у меня 2 входящих интерфейса от провайдера? WAN и OPT1 работают в режиме loadballancing. Но я так понимаю это только для TCP\IP….
                В настройках igmpproxy говорится, что upstream поток может быть только один и он у меня на wan. Downstream смотрит в lan. Как пристроить opt1 ?

                Что в данном случае имеется ввиду под балансировкой трафика?

                http://ru.doc.pfsense.org

                1 Reply Last reply Reply Quote 0
                • D
                  Dda
                  last edited by

                  Что в данном случае имеется ввиду под балансировкой трафика?

                  Имееся в виду возможность получать UDP пакеты  на свой хост с распределением по интерфейсам OPT1 и WAN, а не только через WAN как сейчас.  Или это невозможно в принципе для IPTV?

                  1 Reply Last reply Reply Quote 0
                  • E
                    Eugene
                    last edited by

                    Не думаю, что это возможно.

                    http://ru.doc.pfsense.org

                    1 Reply Last reply Reply Quote 0
                    • P
                      Philosof
                      last edited by

                      Прочитал всю ветку. Спасибо всем кто помог прояснить этот вопрос.
                      Помогите.
                      После всех мучений) так и не заработало. Но трафик UDP потока на upstream появляется и что самое интересное он появляется и на downstream интерфейсе но как (in) входящий. Хотя на LAN трафик долженбыть исходящим. Через udpxy все работает как надо. Но нужен мультикаст для приставки. Где может быть косяк?

                      системный лог сразу после запуска (плеер запускается на 172.30.0.100 )

                      Mar 4 00:43:21 igmpproxy: Note: RECV Membership query from 172.30.0.254 to 224.0.0.1 (ip_hl 24, data 12)
                      Mar 4 00:43:21 igmpproxy: Note: RECV V2 member report from 172.30.0.100 to 233.3.2.1 (ip_hl 24, data 8)
                      Mar 4 00:43:21 igmpproxy: Note: joinMcGroup: 233.3.2.1 on em1_vlan2
                      Mar 4 00:43:21 igmpproxy: Note: New origin for route 233.3.2.1 is 213.140.243.98, flood -1
                      Mar 4 00:43:21 igmpproxy: Note: Adding MFC: 213.140.243.98 -> 233.3.2.1, InpVIf: 1
                      Mar 4 00:43:22 igmpproxy: Note: RECV V2 member report from 172.30.0.100 to 233.3.2.1 (ip_hl 24, data 8)
                      Mar 4 00:43:22 igmpproxy: Note: Adding MFC: 213.140.243.98 -> 233.3.2.1, InpVIf: 1
                      Mar 4 00:43:23 igmpproxy: Note: RECV V2 member report from 172.30.0.100 to 233.3.2.1 (ip_hl 24, data 8)
                      Mar 4 00:43:23 igmpproxy: Note: Adding MFC: 213.140.243.98 -> 233.3.2.1, InpVIf: 1
                      Mar 4 00:43:25 igmpproxy: Note: RECV Membership query from 172.30.0.254 to 224.0.0.252 (ip_hl 24, data 8)
                      Mar 4 00:43:25 igmpproxy: Note: RECV Membership query from 172.30.0.254 to 224.0.0.1 (ip_hl 24, data 12)
                      Mar 4 00:43:27 igmpproxy: Note: RECV V2 member report from 172.30.0.113 to 224.0.0.252 (ip_hl 24, data 8)
                      Mar 4 00:43:31 igmpproxy: Note: RECV Membership query from 172.30.0.254 to 224.0.0.252 (ip_hl 24, data 8)
                      Mar 4 00:43:31 igmpproxy: Note: RECV Membership query from 172.30.0.254 to 224.0.0.1 (ip_hl 24, data 12)

                      1 Reply Last reply Reply Quote 0
                      • E
                        Eugene
                        last edited by

                        @Philosof:

                        Но трафик UDP потока на upstream появляется и что самое интересное он появляется и на downstream интерфейсе но как (in) входящий.

                        Как определил, что входящий? -)

                        http://ru.doc.pfsense.org

                        1 Reply Last reply Reply Quote 0
                        • P
                          Philosof
                          last edited by

                          @Evgeny:

                          @Philosof:

                          Но трафик UDP потока на upstream появляется и что самое интересное он появляется и на downstream интерфейсе но как (in) входящий.

                          Как определил, что входящий? -)

                          Красная полоска на графике Traffic Graph. На upstream и downstream интерфейсе.

                          Все настроил !! ) Пришлось под мультикаст отдельный интерфейс выделить. Надеюсь некому не придется повторять мой заморочки).
                          PfSense рулит!

                          1 Reply Last reply Reply Quote 0
                          • V
                            vagiff
                            last edited by

                            всё таки udpxy легче настроить….

                            1 Reply Last reply Reply Quote 0
                            • V
                              vagiff
                              last edited by

                              собираю пакет udpxy
                              как соберу выложу

                              1 Reply Last reply Reply Quote 0
                              • K
                                killeo
                                last edited by

                                IGMP proxi работает, но мусорит в логах

                                Apr 9 18:58:29 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:29 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)
                                Apr 9 18:58:29 igmpproxy: Note: RECV V2 member report from 192.168.11.8 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:30 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.253 (ip_hl 24, data 8 )
                                Apr 9 18:58:30 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)
                                Apr 9 18:58:35 igmpproxy: Note: RECV V2 member report from 192.168.11.8 to 224.0.0.253 (ip_hl 24, data 8 )
                                Apr 9 18:58:38 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:38 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)
                                Apr 9 18:58:38 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:38 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)
                                Apr 9 18:58:39 igmpproxy: Note: RECV V2 member report from 192.168.11.29 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:40 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.253 (ip_hl 24, data 8 )
                                Apr 9 18:58:40 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)
                                Apr 9 18:58:48 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 239.255.255.250 (ip_hl 24, data 8 )
                                Apr 9 18:58:48 igmpproxy: Note: RECV Membership query from 192.168.11.1 to 224.0.0.1 (ip_hl 24, data 12)

                                Подскажите, пожалуйста, как выключить логи в IGMP

                                DuckDuckGo is a search engine does not collect or share personal information.

                                1 Reply Last reply Reply Quote 0
                                • A
                                  Al2108
                                  last edited by

                                  Добрый лень - помогите разобраться в логах - не понимаю ошибки - все по инструкции делал !!!

                                  TCP dump

                                  
16:22:16.409770 IP 109.206.47.191.1900 > 239.255.255.250.1900: UDP, length 437
16:22:16.410868 IP 109.206.47.191.1900 > 239.255.255.250.1900: UDP, length 446
16:22:16.411367 IP 109.206.47.191.1900 > 239.255.255.250.1900: UDP, length 493
16:22:16.411667 IP 109.206.47.191.1900 > 239.255.255.250.1900: UDP, length 501
16:22:16.585025 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.594413 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.600914 IP 109.206.47.159 > 239.255.255.250: igmp
16:22:16.632858 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.652431 IP 109.206.47.191 > 239.255.255.250: igmp
16:22:16.792636 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.808414 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.815304 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:16.978377 IP 109.206.47.130 > 239.255.255.250: igmp
16:22:17.036396 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:17.046283 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:17.101006 IP 109.206.47.159 > 239.255.255.250: igmp
16:22:18.757296 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:18.810422 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:18.975192 IP 109.206.47.130 > 239.255.255.250: igmp
16:22:23.986304 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:23.994093 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:24.018758 IP 109.206.47.143 > 239.255.255.250: igmp
16:22:24.453987 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:24.456649 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:24.482211 IP 109.206.47.130 > 239.255.255.250: igmp
16:22:31.025787 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:31.102680 IP 109.206.47.159 > 239.255.255.250: igmp
16:22:40.065703 IP 10.20.183.15.47856 > 239.192.152.143.6771: UDP, length 119
16:22:40.065718 IP 10.20.183.15.47856 > 239.192.152.143.6771: UDP, length 119
16:22:40.065728 IP 10.20.183.15.47856 > 239.192.152.143.6771: UDP, length 119
16:22:40.065736 IP 10.20.183.15.47856 > 239.192.152.143.6771: UDP, length 119
16:22:40.065745 IP 10.20.183.15.47856 > 239.192.152.143.6771: UDP, length 119
16:22:41.247448 IP 109.206.47.130.62549 > 224.0.0.253.3544: UDP, length 40
16:22:41.248644 IP 109.206.47.159.51871 > 224.0.0.253.3544: UDP, length 40
16:22:41.252024 IP 109.206.47.159.51871 > 224.0.0.253.3544: UDP, length 40
16:22:41.261711 IP 109.206.47.159.51871 > 224.0.0.253.3544: UDP, length 40
16:22:41.263509 IP 109.206.47.159.51871 > 224.0.0.253.3544: UDP, length 40
16:22:41.700899 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:41.700947 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:41.700958 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:42.700505 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:42.700521 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:42.700616 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:42.700633 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:42.700643 IP 109.206.47.182.6771 > 239.192.152.143.6771: UDP, length 119
16:22:45.226383 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:45.480728 IP 109.206.47.130 > 239.255.255.250: igmp
16:22:51.848249 IP 10.20.183.15.62198 > 239.192.152.143.6771: UDP, length 119
16:22:56.910887 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:56.978393 IP 109.206.47.130 > 239.255.255.250: igmp
16:22:57.103918 IP 172.21.36.250 > 239.255.255.250: igmp
16:22:57.105818 IP 109.206.47.159 > 239.255.255.250: igmp
16:22:57.347179 IP 109.206.47.182.1052 > 239.255.255.250.1900: UDP, length 133
16:22:58.717767 IP 109.206.47.182.1056 > 239.255.255.250.1900: UDP, length 98
16:23:00.357880 IP 109.206.47.182.1052 > 239.255.255.250.1900: UDP, length 133
16:23:03.358096 IP 109.206.47.182.1052 > 239.255.255.250.1900: UDP, length 133
16:23:09.190862 IP 172.21.36.250 > 224.0.0.1: igmp
16:23:09.794919 IP 109.206.47.181 > 239.255.255.250: igmp
16:23:10.472974 IP 109.206.47.130 > 224.0.0.253: igmp
16:23:11.655525 IP 109.206.47.191 > 224.0.0.252: igmp
16:23:11.855948 IP 10.20.183.15.62198 > 239.192.152.143.6771: UDP, length 119
16:23:11.962435 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.962447 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.962707 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.963065 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.963418 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.963773 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.964261 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.964519 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.964771 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.965027 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.965282 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.965534 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.966050 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.966320 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.966582 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.966842 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.967103 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.967367 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.967888 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.968160 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.968415 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.968684 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.968928 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.969185 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.969565 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.969827 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.970094 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.970458 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.970725 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.971009 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.971748 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.972017 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.972267 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.972598 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.973335 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.973607 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.973875 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.974132 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.974392 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.974893 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.975156 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.975416 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.975670 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.975922 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.976175 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:11.976684 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.946707 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.946905 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.947269 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.947624 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.947986 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:12.948524 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:13.958454 IP 10.20.183.15.33592 > 239.192.152.143.6771: UDP, length 119
16:23:14.534709 IP 109.206.47.143 > 224.0.0.251: igmp
16:23:15.795351 IP 109.206.47.181 > 239.192.152.143: igmp

                                  Log

                                  May 23 16:21:47 	syslogd: kernel boot file is /boot/kernel/kernel
May 23 16:21:49 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:49 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:49 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:21:50 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:02 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:02 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:03 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:03 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:05 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:05 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:05 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:06 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:06 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:06 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:12 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:12 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:12 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:13 	kernel: sk0: promiscuous mode enabled
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:16 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:17 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:17 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:18 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:18 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:23 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:23 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:24 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:24 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:31 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:40 	igmpproxy: Note: The source address 192.168.1.164 for group 239.192.152.143, is valid DOWNSTREAM VIF #0.
May 23 16:22:40 	igmpproxy: Note: New origin for route 239.192.152.143 is 192.168.1.164, flood 0
May 23 16:22:40 	igmpproxy: Note: Adding MFC: 192.168.1.164 -> 239.192.152.143, InpVIf: 0
May 23 16:22:41 	igmpproxy: Note: New origin for route 239.192.152.143 is 109.206.47.182, flood -1
May 23 16:22:45 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:56 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:57 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:22:58 	igmpproxy: Note: New origin for route 239.255.255.250 is 109.206.47.182, flood -1
May 23 16:23:09 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 224.0.0.1 (ip_hl 20, data 8)
May 23 16:23:11 	igmpproxy: Note: The source address 192.168.1.100 for group 239.192.152.143, is valid DOWNSTREAM VIF #0.
May 23 16:23:11 	igmpproxy: Note: New origin for route 239.192.152.143 is 192.168.1.100, flood 0
May 23 16:23:11 	igmpproxy: Note: Adding MFC: 192.168.1.100 -> 239.192.152.143, InpVIf: 0
May 23 16:23:21 	igmpproxy: Note: RECV Membership query from 192.168.1.1 to 224.0.0.1 (ip_hl 24, data 8)
May 23 16:23:21 	igmpproxy: Note: RECV Membership query from 192.168.1.1 to 224.0.0.1 (ip_hl 24, data 12)
May 23 16:23:26 	kernel: sk0: promiscuous mode disabled
May 23 16:23:27 	igmpproxy: Note: RECV V2 member report from 192.168.1.1 to 224.0.0.2 (ip_hl 24, data 8)
May 23 16:23:27 	igmpproxy: Note: The IGMP message was from myself. Ignoring.
May 23 16:23:30 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
May 23 16:23:31 	igmpproxy: Warn: age_table_entry: SIOCGETSGCNT failing for (109.206.47.181 239.192.152.143); Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Note: Removing MFC: 109.206.47.181 -> 239.192.152.143, InpVIf: 1
May 23 16:23:31 	igmpproxy: Warn: MRT_DEL_MFC; Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Warn: age_table_entry: SIOCGETSGCNT failing for (109.206.47.182 239.192.152.143); Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Note: Removing MFC: 109.206.47.182 -> 239.192.152.143, InpVIf: 1
May 23 16:23:31 	igmpproxy: Warn: MRT_DEL_MFC; Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Warn: age_table_entry: SIOCGETSGCNT failing for (109.206.47.176 239.255.255.250); Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Note: Removing MFC: 109.206.47.176 -> 239.255.255.250, InpVIf: 1
May 23 16:23:31 	igmpproxy: Warn: MRT_DEL_MFC; Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Warn: age_table_entry: SIOCGETSGCNT failing for (109.206.47.182 239.255.255.250); Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Note: Removing MFC: 109.206.47.182 -> 239.255.255.250, InpVIf: 1
May 23 16:23:31 	igmpproxy: Warn: MRT_DEL_MFC; Errno(49): Can't assign requested address
May 23 16:23:31 	igmpproxy: Note: Route is not active. No kernel updates done.
May 23 16:23:31 	igmpproxy: Note: RECV V2 member report from 192.168.1.1 to 239.255.255.250 (ip_hl 24, data 8)
May 23 16:23:31 	igmpproxy: Note: The IGMP message was from myself. Ignoring.
May 23 16:23:35 	igmpproxy: Note: RECV Membership query from 172.21.36.250 to 239.255.255.250 (ip_hl 20, data 8)
                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    paveksam
                                    last edited by

                                    edit: Вопрос с igmpproxy снят. С LAN-интерфейса pfsense уходят нормальные udp пакеты с данными.
                                    Загвоздка в том, что на интерфейс внутреннего компа эти пакеты приходят с другими данными. Свитч, собака, безобразие какое-то учиняет чтоли.

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      dark_viking
                                      last edited by

                                      Подскажите в чем может быть проблема настроил все по инструкции

                                      pfSense-1.2.3-RELEASE
                                      IGMP установлен из System: Package Manager
                                      lan rules
                                      Proto Source Port Destination Port Gateway
                                      IGMP * * 224.0.0.0/4 * *  
                                      Advanced Options галочка не стоит

                                      wan rules
                                      Proto Source Port Destination Port Gateway
                                      UDP * * 224.0.0.0/4 * *

                                      Services: IGMP proxy
                                      wan upstream
                                      234.5.2.0/24

                                      lan downstream
                                      192.168.1.0/24

                                      lan интерфейс

                                      tcpdump -ni vr0 igmp

                                      tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
                                      listening on vr0, link-type EN10MB (Ethernet), capture size 96 bytes
                                      11:40:38.686984 IP 192.168.1.27 > 224.0.0.2: igmp leave 234.5.2.3
                                      11:40:39.292874 IP 192.168.1.27 > 234.5.2.1: igmp v2 report 234.5.2.1
                                      11:40:40.107654 IP 192.168.1.27 > 234.5.2.1: igmp v2 report 234.5.2.1
                                      11:40:41.107608 IP 192.168.1.27 > 234.5.2.1: igmp v2 report 234.5.2.1

                                      и все дальше ничего не происходит.
                                      провайдер fryazino.net  ип канала имеют адрес вида 234.5.2.ххх

                                      1 Reply Last reply Reply Quote 0
                                      • G
                                        gig
                                        last edited by

                                        Большое спасибо Evgeny и всем отписавшимся. Настроил у себя IPTV, хоть и не с первого раза :)

                                        pfSens 2.0-RC3 \ Интернет провайдер Butovo.com \ Интернет по DHCP

                                        Мои настройки:

                                        Firewall>Rules>Lan
                                        добавил правило
                                        Action=Pass
                                        Interface=Lan
                                        Protocol=IGMP
                                        Source=Lan subnet
                                        Destination=Network 224.0.0.0/4
                                        Advanced Options>поставил галочку "This allows packets with IP options to pass…"
                                        Правило поместил выше остальных.

                                        Firewall>Rules>Wan
                                        добавил правило
                                        Action=Pass
                                        Interface=Wan
                                        Protocol=UDP
                                        Source=any
                                        Destination=Network 224.0.0.0/4

                                        Применил правила Apply.

                                        Services>IGMP Proxy
                                        добавил upstream
                                        interface=Wan
                                        Type=Upstream Interfece
                                        Threshold=1
                                        Network(s)=77.94.170.0/24 192.168.1.2/32

                                        добавил downstream
                                        Interface=Lan
                                        Type=Downstream Interface
                                        Threshold=1
                                        Network(s)=192.168.0.0/24

                                        System>Advanced>Firewall/Nat
                                        поставил галочку Disable Firewall Scrub

                                        После этого перезапустил pfSense и насладился IPTV :)

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          art13
                                          last edited by

                                          Настроил по инструкции, но не получилось запустить.
                                          pfsense 2.0-RELEASE (i386)
                                          built on Tue Sep 13 17:00:00 EDT 2011

                                          От провайдера выделенный IP. Destination=Network 224.0.0.0/4. На компе файрвол отключен.
                                          Есть предположение что у меня "Сложный случай раз - провайдер вещает из какой-то сети, отличной от той, что прописана на Upstream (от 1.1.1.0/24 на моей диаграмме), например с адреса 3.4.5.42. Необходимо в конфигурации igmpproxy на Upstream интерфейсе добавить эту сеть в Networks - 3.4.5.0/24 (можно 3.4.5.42/32 для пущего страха)." Но я не знаю как это вычислить.

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            technomaq
                                            last edited by

                                            Возможно, что по умолчанию, включена опция Block private networks в секции Private networks во вкладке Interfaces: WAN. Она блокирует адреса вида 192.168. чтобы по WAN не было доступа к роутеру, но с этих адресов иногда провайдеры вещают IPTV.
                                            Галка должна быть снята. Пока её не снял, тоже не мог получить IPTV ни через IGMPProxy, ни через udpxy.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post