[SOLUCIONADO] PfSense e Imagenio
-
Pues tengo un problema, esta mañana la tabla de rutas estaba bien, al comprobarlo a mediodia otra vez estaba la ruta estática.
¿Que puede estar modificando la ruta?
-
Yo tengo el mismo problema que tu, tampoco me carga la guia y no puedo ver las series del videoclub , yomvi o como se llame.
a mí me aparece lo siguiente
default 192.168.144.1 UGS 61862 1492 pppoe0
10.64.0.0/10 link#9 U 14909 1492 re0_vlan2
80.58.61.250 192.168.144.1 UGHS 1318 1492 pppoe0
80.58.61.254 192.168.144.1 UGHS 0 1492 pppoe0
172.26.22.0/26 10.64.0.1 UG 449 1492 re0_vlan2
172.26.22.23 10.64.0.1 UGH 121 1492 re0_vlan2
172.26.22.56/29 10.64.0.1 UG 0 1492 re0_vlan2
172.26.23.0/27 10.64.0.1 UG 48 1492 re0_vlan2
172.26.23.4 10.64.0.1 UGH 10 1492 re0_vlan2
172.26.23.5 10.64.0.1 UGH 0 1492 re0_vlan2
172.26.23.23 10.64.0.1 UGH 13 1492 re0_vlan2
172.26.23.24 10.64.0.1 UGH 15 1492 re0_vlan2
172.26.23.30 10.64.0.1 UGH 8 1492 re0_vlan2
172.26.80.0/21 10.64.0.1 UG 22 1492 re0_vlan2
192.168.144.1 link#10 UH 16383 1492 pppoe0 -
No dije nada, ya carga la guia. Supongo que habrá que esperar. Lo dejé asi sin cargar la guia y despues de unos minutos veo que la guia la carga.
Lo que no puedo ver son las series o peliculas del yomvi, se queda cargando el anuncio previo antes de ver del capitulo o pelicula.
-
Otra vez se ha modificado la ruta, esta vez estaba viendo la tele cuando paso, estoy mirando los logs y veo que a las 22:00 se inicio un proceso de renovación de DHCP en el interfaz de VOIP.
Esto es lo que he sacado de log pero no se interpretarlo, he resaltado una linea que me llama la atención sobre el interfaz de TV (ImagenioWAN en mi config).
Por el momento he añadido una ruta estatica para 172.26.23.3 y espero que no se modifique, pero me gustaría saber que esta pasando.Nov 15 22:00:19 firewall dhclient: EXPIRE
Nov 15 22:00:19 firewall dhclient: Deleting old routes
Nov 15 22:00:19 firewall dhclient: PREINIT
Nov 15 22:00:19 firewall dhclient: ARPSEND
Nov 15 22:00:19 firewall kernel: arpresolve: can't allocate llinfo for 10.26.x.x on em0_vlan3
Nov 15 22:00:21 firewall dhclient: ARPCHECK
Nov 15 22:00:21 firewall dhclient: BOUND
Nov 15 22:00:21 firewall kernel: arpresolve: can't allocate llinfo for 10.26.x.x on em0_vlan3
Nov 15 22:00:21 firewall dhclient: Starting add_new_address()
Nov 15 22:00:21 firewall dhclient: ifconfig em0_vlan3 inet 10.26.x.x netmask 255.255.224.0 broadcast 10.26.31.255
Nov 15 22:00:21 firewall dhclient: New IP Address (em0_vlan3): 10.26.x.x
Nov 15 22:00:21 firewall dhclient: New Subnet Mask (em0_vlan3): 255.255.224.0
Nov 15 22:00:21 firewall dhclient: New Broadcast Address (em0_vlan3): 10.26.31.255
Nov 15 22:00:21 firewall dhclient: New Routers (em0_vlan3): 10.26.x.x
Nov 15 22:00:21 firewall dhclient: Adding new routes to interface: em0_vlan3
Nov 15 22:00:21 firewall dhclient: Creating resolv.conf
Nov 15 22:00:21 firewall check_reload_status: rc.newwanip starting em0_vlan3
Nov 15 22:00:22 firewall php-fpm[6377]: /rc.newwanip: rc.newwanip: Info: starting on em0_vlan3.
Nov 15 22:00:22 firewall php-fpm[6377]: /rc.newwanip: rc.newwanip: on (IP address: 10.26.x.x) (interface: VOIPWAN[opt3]) (real interface: em0_vlan3).
Nov 15 22:00:23 firewall xinetd[25854]: Starting reconfiguration
Nov 15 22:00:23 firewall xinetd[25854]: Swapping defaults
Nov 15 22:00:23 firewall xinetd[25854]: readjusting service 6969-udp
Nov 15 22:00:23 firewall xinetd[25854]: Reconfigured: new=0 old=1 dropped=0 (services)
Nov 15 22:00:26 firewall dpinger: send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 10.64.y.y bind_addr
10.64.e.e identifier "ImagenioGW "
Nov 15 22:00:26 firewall dpinger: send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.144.1 bind_
addr 80.39.51.77 identifier "WAN_PPPOE "
Nov 15 22:00:26 firewall dpinger: send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 10.26.x.x bind_addr
10.26.8.44 identifier "VOIPWAN_DHCP "
Nov 15 22:00:27 firewall dhcpd: Internet Systems Consortium DHCP Server 4.3.4
Nov 15 22:00:27 firewall dhcpd: Copyright 2004-2016 Internet Systems Consortium.
Nov 15 22:00:27 firewall dhcpd: All rights reserved.
Nov 15 22:00:27 firewall dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 15 22:00:27 firewall dhcpd: Config file: /etc/dhcpd.conf
Nov 15 22:00:27 firewall dhcpd: Database file: /var/db/dhcpd.leases
Nov 15 22:00:27 firewall dhcpd: Internet Systems Consortium DHCP Server 4.3.4
Nov 15 22:00:27 firewall dhcpd: PID file: /var/run/dhcpd.pid
Nov 15 22:00:27 firewall dhcpd: Copyright 2004-2016 Internet Systems Consortium.
Nov 15 22:00:27 firewall dhcpd: All rights reserved.
Nov 15 22:00:27 firewall dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 15 22:00:27 firewall dhcpd: Wrote 0 deleted host decls to leases file.
Nov 15 22:00:27 firewall dhcpd: Wrote 0 new dynamic host decls to leases file.
Nov 15 22:00:27 firewall dhcpd: Wrote 64 leases to leases file.
Nov 15 22:00:27 firewall dhcpd: Listening on BPF/re1_vlan104/
Nov 15 22:00:27 firewall dhcpd: Sending on BPF/re1_vlan104/
Nov 15 22:00:27 firewall dhcpd: Listening on BPF/re0/
Nov 15 22:00:27 firewall dhcpd: Sending on BPF/re0/
Nov 15 22:00:27 firewall dhcpd: Listening on BPF/em1/
Nov 15 22:00:27 firewall dhcpd: Sending on BPF/em1/
Nov 15 22:00:27 firewall dhcpd: Sending on Socket/fallback/fallback-net
Nov 15 22:00:27 firewall dhcpd: Server starting service.
Nov 15 22:00:28 firewall php-fpm[6377]: /rc.newwanip: Resyncing OpenVPN instances for interface VOIPWAN.
Nov 15 22:00:28 firewall php-fpm[6377]: /rc.newwanip: Creating rrd update script
Nov 15 22:00:28 firewall igmpproxy[46120]: select() failure; Errno(4): Interrupted system call
Nov 15 22:00:28 firewall php-fpm[6377]: /rc.newwanip: Started IGMP proxy service.
Nov 15 22:00:29 firewall dpinger: ImagenioGW 10.64.0.1: Alarm latency 0us stddev 0us loss 100%
Nov 15 22:00:29 firewall check_reload_status: updating dyndns ImagenioGW
Nov 15 22:00:29 firewall check_reload_status: Restarting ipsec tunnels
Nov 15 22:00:29 firewall check_reload_status: Restarting OpenVPN tunnels/interfaces
Nov 15 22:00:29 firewall check_reload_status: Reloading filter
Nov 15 22:00:29 firewall dpinger: VOIPWAN_DHCP 10.26.x.x: Alarm latency 0us stddev 0us loss 100%
Nov 15 22:00:29 firewall dpinger: WAN_PPPOE 192.168.144.1: Alarm latency 0us stddev 0us loss 100%
Nov 15 22:00:29 firewall check_reload_status: updating dyndns WAN_PPPOE
Nov 15 22:00:29 firewall check_reload_status: Restarting ipsec tunnels
Nov 15 22:00:29 firewall check_reload_status: Restarting OpenVPN tunnels/interfaces
Nov 15 22:00:29 firewall check_reload_status: Reloading filter
Nov 15 22:00:30 firewall php-fpm[23634]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use ImagenioGW.
Nov 15 22:00:30 firewall xinetd[25854]: Starting reconfiguration
Nov 15 22:00:30 firewall xinetd[25854]: Swapping defaults
Nov 15 22:00:30 firewall xinetd[25854]: readjusting service 6969-udp
Nov 15 22:00:30 firewall xinetd[25854]: Reconfigured: new=0 old=1 dropped=0 (services)
Nov 15 22:00:30 firewall php-fpm[6377]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 10.26.y.y -> 10.26.y.y - Restarting packages.
Nov 15 22:00:30 firewall check_reload_status: Starting packages
Nov 15 22:00:30 firewall php-fpm[6377]: /rc.dyndns.update: phpDynDNS (asterix.mydomain.net): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Nov 15 22:00:30 firewall snmpd[10820]: disk_OS_get_disks: adding device 'ada0' to device list
Nov 15 22:00:31 firewall php-fpm[12394]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_PPPOE.
Nov 15 22:00:34 firewall xinetd[25854]: Starting reconfiguration
Nov 15 22:00:34 firewall xinetd[25854]: Swapping defaults
Nov 15 22:00:34 firewall xinetd[25854]: readjusting service 6969-udp
Nov 15 22:00:34 firewall xinetd[25854]: Reconfigured: new=0 old=1 dropped=0 (services)
Nov 15 22:00:35 firewall php-fpm[12461]: [pfBlockerNG] Starting cron process.esto es mi crontab:
minute hour mday month wday who command Add
1,31 0-5 * * * root /usr/bin/nice -n20 adjkerntz -a
1 3 1 * * root /usr/bin/nice -n20 /etc/rc.update_bogons.sh
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 webConfiguratorlockout
1 1 * * * root /usr/bin/nice -n20 /etc/rc.dyndns.update
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot
30 12 * * * root /usr/bin/nice -n20 /etc/rc.update_urltables
*/5 * * * * root /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_cron_misc.inc
*/5 * * * * root /usr/bin/nice -n20 /sbin/pfctl -q -t snort2c -T expire 3600
39 0,12 * * * root /usr/bin/nice -n20 /usr/local/bin/php -f /usr/local/pkg/snort/snort_check_for_rule_updates.php
15 0 * * * root /usr/local/pkg/swapstate_check.php
0 * * * * root /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php cron >> /var/log/pfblockerng/pfblockerng.log 2>&1
0 8 1-7 * * root /usr/local/bin/php /usr/local/www/pfblockerng/pfblockerng.php dcc >> /var/log/pfblockerng/extras.log 2>&1 -
Mediante DHCP se puede poner una ruta estatica con la opcion 121. ¿Que mediante el interface de voip te este forzando la ruta? Es posible pero me aprece muy heavy. Mete un wireshak hay filtrando los paquetes dhcp a ver que encuntras. No conozco a nadie que le pase esto pero todo es posible.
Si tu pones una ruta estatica manual en principio tiene preferencia sobre las otras. Pero desconozco si las staticas tienen preferencia sobrea las de la opcion 121. Prueba lode wireshark a ver si localizas algo y salimos de dudas
-
vuelvo a tener problemas con la guia. Salen todos los canales "Sin información" pero todas la funciones de MovistarTV estan disponobles, puedo ver mis grabaciones, series, etc.
La tabla de rutas esta bien.¿Alguna sugerencia?
-
Buenas tardes :
Después de leer el hilo varias veces durante varios días, no soy capaz de hacer funcionar IPTV de movistar a través de mi pfSense. La conexión WAN me funciona sin problemas, la VOIP no la he probado todavía, pero el IPTV no hay manera.
Tengo configurado el RIP (en los interfaces de VOIP y IPTV).
También tengo configurado el udpxy:
Server Process ID Accepting clients on Multicast address Active clients
25352 192.168.20.1:4000 10.64.122.110 0Os pego a continuación información de mi config :
*** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense ***
WAN (wan) -> pppoe0 -> v4/PPPoE: 80.xx.xx.xx/32
LAN (lan) -> vtnet0 -> v4: 192.168.20.1/24
VOIP (opt1) -> vtnet1_vlan3 -> v4/DHCP4: 10.26.167.138/19
IPTV (opt2) -> vtnet1_vlan2 -> v4: 10.64.122.110/10–-- IPv4 Routes ----
Destination Gateway Flags Use Mtu Netif Expire
default 80.xx.xx.xx UGS 1703314 1492 pppoe0
10.0.10.1 link#11 UH 0 1500 ovpnc1
10.0.10.2 127.0.0.1 UH 0 16384 lo0
10.26.160.0/19 link#8 U 66031 1500 vtnet1_vlan3
10.26.167.138 link#8 UHS 0 16384 lo0
10.64.0.0/10 link#9 U 66031 1500 vtnet1_vlan2
10.64.122.110 link#9 UHS 0 16384 lo0
80.xx.xx.xx 127.0.0.1 UH 0 16384 lo0
80.xx.xx.xx 80.xx.xx.xx UGHS 6556 1492 pppoe0
80.xx.xx.xx 80.xx.xx.xx UGHS 6578 1492 pppoe0
80.xx.xx.xx link#10 UH 66024 1492 pppoe0
127.0.0.1 link#6 UH 2572 16384 lo0
172.26.22.0/26 10.64.0.1 UG 0 1500 vtnet1_vlan2
172.26.22.56/29 10.64.0.1 UG 0 1500 vtnet1_vlan2
172.26.23.0/27 10.64.0.1 UG 4 1500 vtnet1_vlan2
172.26.23.4 10.64.0.1 UGH 0 1500 vtnet1_vlan2
172.26.23.5 10.64.0.1 UGH 0 1500 vtnet1_vlan2
172.26.23.23 10.64.0.1 UGH 0 1500 vtnet1_vlan2
172.26.23.24 10.64.0.1 UGH 0 1500 vtnet1_vlan2
172.26.23.30 10.64.0.1 UGH 0 1500 vtnet1_vlan2
172.26.80.0/21 10.64.0.1 UG 0 1500 vtnet1_vlan2
192.168.0.0/24 192.168.20.2 UGS 15 1500 vtnet0
192.168.1.0/24 10.0.10.1 UGS 1695835 1500 ovpnc1
192.168.20.0/24 link#1 U 4481213 1500 vtnet0
192.168.20.1 link#1 UHS 0 16384 lo0---- IGMP Proxy
Name Type Values Description
IPTV upstream 172.26.0.0/16, 239.0.0.0/8, 10.0.0.0/8, 239.0.0.0/16, 172.0.0.0/8, 192.168.20.0/24, 224.0.0.0/4 Multicast IMAGENIO
LAN downstream 192.168.20.0/24 Multicast TVTengo una única LAN (192.168.20.0/24) donde están los PC's, el Deco de Movistar y una RPI con KODI y el addon de movistar. Con el router de movistar me funciona todo (RPI/KODI y Deco), Con el pfSense no me funciona ninguna de las dos opciones de TV. Internet va de lujo con 300/300 y la VOIP no la he probado aún.
Alguna pista por donde pueda empezar a buscar ? estoy un poco desesperado, he probado también con el pfSense 2.2 y tengo los mismos síntomas.
Muchas gracias !!
-
Has configurado las reglas avanzadas del firewall?
-
Hola donizt, gracias por contestar.
Si, las reglas las tengo configuradas según el PDF de ayuda. Desconozco si hay alguna versión actualizada del PDF para la pfSense 2.3, aunque lo más seguro es que estoy haciendo algo mal…
Te adjunto pantallazos de las configuraciónes de las reglas de firewall para los interfaces LAN y IPTV.
Gracias y saludos.
-
No parece que tengas trafico de video por la inerface iptv… a ver si haviendo algunas pruebas nos da mas pistas de pasa:
Ejecuta en igmprocy en modo debug en consola e intenta ver video, deberias ver como los join del igmp de lan pasan a iptv o incluso ver si en al propia ejecucion del servicio ves algo raro
Ttambien en paralelo haz un tcpdump del interface iptv a ver que trafico tenemos por alli.
Por otro lado revisa primero si tienes un switch de capa2 que no este bloqueado el trafico igmp que algunos lo tienen bloqueados de fabrica
-
Hola Donitz :
Te pego info del tcpdump :
[2.3.2-RELEASE][root@pfSense.localdomain]/root: tcpdump -i vtnet1_vlan2 udp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vtnet1_vlan2, link-type EN10MB (Ethernet), capture size 65535 bytes
17:49:50.597525 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:50:19.637006 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:50:45.634217 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:51:14.631415 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:51:49.619338 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:52:14.587789 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:52:39.625520 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:53:11.604725 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:53:42.621564 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:54:17.629887 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:54:45.630872 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:55:15.614802 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:55:43.612760 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:56:12.621687 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:56:40.600827 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:57:06.619058 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:57:33.578170 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:58:06.636669 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
17:58:39.631676 IP 10.64.0.1.router > rip2-routers.mcast.net.router: RIPv2, Response, length: 184
^C
19 packets captured
1181 packets received by filter
0 packets dropped by kernelAqui la información del igmpproxy
[2.3.2-RELEASE][root@pfSense.localdomain]/root: igmpproxy -d -vv /tmp/igmpproxy.conf
Searching for config file at '/tmp/igmpproxy.conf'
Config: Quick leave mode enabled.
Config: Got a phyint token.
Config: IF: Config for interface vtnet1_vlan2.
Config: IF: Got upstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 172.26.0.0/16.
Config: IF: Altnet: Parsed altnet to 172.26/16.
Config: IF: Got altnet token 239.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 239/8.
Config: IF: Got altnet token 10.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 10/8.
Config: IF: Got altnet token 239.0.0.0/16.
Config: IF: Altnet: Parsed altnet to 239.0/16.
Config: IF: Got altnet token 172.0.0.0/8.
Config: IF: Altnet: Parsed altnet to 172/8.
Config: IF: Got altnet token 192.168.20.0/24.
Config: IF: Altnet: Parsed altnet to 192.168.20/24.
Config: IF: Got altnet token 224.0.0.0/4.
Config: IF: Altnet: Parsed altnet to 224/4.
IF name : vtnet1_vlan2
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 1
Allowednet ptr : 1017050
Config: Got a phyint token.
Config: IF: Config for interface vtnet0.
Config: IF: Got downstream token.
Config: IF: Got ratelimit token '0'.
Config: IF: Got threshold token '1'.
Config: IF: Got altnet token 192.168.20.0/24.
Config: IF: Altnet: Parsed altnet to 192.168.20/24.
IF name : vtnet0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 2
Allowednet ptr : 10170c0
Config: Got a phyint token.
Config: IF: Config for interface pppoe0.
Config: IF: Got disabled token.
IF name : pppoe0
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
Config: Got a phyint token.
Config: IF: Config for interface vtnet1_vlan3.
Config: IF: Got disabled token.
IF name : vtnet1_vlan3
Next ptr : 0
Ratelimit : 0
Threshold : 1
State : 0
Allowednet ptr : 0
buildIfVc: Interface vtnet0 Addr: 192.168.20.1, Flags: 0xffff8843, Network: 192.168.20/24
buildIfVc: Interface lo0 Addr: 127.0.0.1, Flags: 0xffff8049, Network: 127/8
buildIfVc: Interface vtnet1_vlan3 Addr: 10.26.167.138, Flags: 0xffff8843, Network: 10.26.160/19
buildIfVc: Interface vtnet1_vlan2 Addr: 10.64.122.110, Flags: 0xffff8843, Network: 10.64/10
buildIfVc: Interface pppoe0 Addr: 80.xx.xx.xx, Flags: 0xffff88d1, Network: 80.xx.xx.xx/32
Found config for vtnet0
Found config for vtnet1_vlan3
Found config for vtnet1_vlan2
Found config for pppoe0
adding VIF, Ix 0 Fl 0x0 IP 0x0114a8c0 vtnet0, Threshold: 1, Ratelimit: 0
Network for [vtnet0] : 192.168.20/24
Network for [vtnet0] : 192.168.20/24
adding VIF, Ix 1 Fl 0x0 IP 0x8aa71a0a vtnet1_vlan3, Threshold: 1, Ratelimit: 0
Network for [vtnet1_vlan3] : 10.26.160/19
adding VIF, Ix 2 Fl 0x0 IP 0x6e7a400a vtnet1_vlan2, Threshold: 1, Ratelimit: 0
Network for [vtnet1_vlan2] : 10.64/10
Network for [vtnet1_vlan2] : 172.26/16
Network for [vtnet1_vlan2] : 239/8
Network for [vtnet1_vlan2] : 10/8
Network for [vtnet1_vlan2] : 239.0/16
Network for [vtnet1_vlan2] : 172/8
Network for [vtnet1_vlan2] : 192.168.20/24
Network for [vtnet1_vlan2] : 224/4
adding VIF, Ix 3 Fl 0x0 IP 0xaefc1c50 pppoe0, Threshold: 1, Ratelimit: 0
Network for [pppoe0] : 80.xx.xx.xx/32
Got 262144 byte buffer size in 0 iterations
Joining all-routers group 224.0.0.2 on vif 192.168.20.1
joinMcGroup: 224.0.0.2 on vtnet0
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 1 (#0) - delay 10 secs
(Id:1, Time:10)
Created timeout 2 (#1) - delay 21 secs
(Id:1, Time:10)
(Id:2, Time:21)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 1 (#0)
Aging routes in table.Current routing table (Age active routes):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 2 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 3 (#0) - delay 10 secs
(Id:3, Time:10)
Created timeout 4 (#1) - delay 21 secs
(Id:3, Time:10)
(Id:4, Time:21)
RECV Membership query from 192.168.20.1 to 224.0.0.1
About to call timeout 3 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.20.3 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested addressCurrent routing table (Remove route):
No routes in table...
Current routing table (Age active routes):
No routes in table...
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 4 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 5 (#0) - delay 10 secs
(Id:5, Time:10)
Created timeout 6 (#1) - delay 115 secs
(Id:5, Time:10)
(Id:6, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 5 (#0)
Aging routes in table.Current routing table (Age active routes):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 6 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 7 (#0) - delay 10 secs
(Id:7, Time:10)
Created timeout 8 (#1) - delay 115 secs
(Id:7, Time:10)
(Id:8, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 7 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.20.3 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested addressCurrent routing table (Remove route):
No routes in table...
Current routing table (Age active routes):
No routes in table...
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 8 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 9 (#0) - delay 10 secs
(Id:9, Time:10)
Created timeout 10 (#1) - delay 115 secs
(Id:9, Time:10)
(Id:10, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 9 (#0)
Aging routes in table.Current routing table (Age active routes):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.5 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.20.3 to 192.168.20.5Current routing table (Activate Route):
#0: Src: 192.168.20.5, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.20.5 to 192.168.20.3Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 10 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 11 (#0) - delay 10 secs
(Id:11, Time:10)
Created timeout 12 (#1) - delay 115 secs
(Id:11, Time:10)
(Id:12, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 11 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.20.3 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested addressCurrent routing table (Remove route):
No routes in table...
Current routing table (Age active routes):
No routes in table...
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 12 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 13 (#0) - delay 10 secs
(Id:13, Time:10)
Created timeout 14 (#1) - delay 115 secs
(Id:13, Time:10)
(Id:14, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 13 (#0)
Aging routes in table.Current routing table (Age active routes):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.5 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.20.3 to 192.168.20.5Current routing table (Activate Route):
#0: Src: 192.168.20.5, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.20.5 to 192.168.20.3Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 14 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 15 (#0) - delay 10 secs
(Id:15, Time:10)
Created timeout 16 (#1) - delay 115 secs
(Id:15, Time:10)
(Id:16, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 15 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.20.3 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested addressCurrent routing table (Remove route):
No routes in table...
Current routing table (Age active routes):
No routes in table...
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 16 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 17 (#0) - delay 10 secs
(Id:17, Time:10)
Created timeout 18 (#1) - delay 115 secs
(Id:17, Time:10)
(Id:18, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
About to call timeout 17 (#0)
Aging routes in table.Current routing table (Age active routes):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 18 (#0)
SENT Membership query from 192.168.20.1 to 224.0.0.1
Sent membership query from 192.168.20.1 to 224.0.0.1. Delay: 10
Created timeout 19 (#0) - delay 10 secs
(Id:19, Time:10)
Created timeout 20 (#1) - delay 115 secs
(Id:19, Time:10)
(Id:20, Time:115)
RECV Membership query from 192.168.20.1 to 224.0.0.1
Route activate request from 192.168.20.3 to 239.255.255.250Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:1, St: A, OutVifs: 0x00000000
About to call timeout 19 (#0)
Aging routes in table.
Removing group 239.255.255.250. Died of old age.
Removed route entry for 239.255.255.250 from table.
Vif bits : 0x00000000
Removing MFC: 192.168.20.3 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested addressCurrent routing table (Remove route):
No routes in table...
Current routing table (Age active routes):
No routes in table...
Route activate request from 192.168.20.3 to 239.255.255.250
No table entry for 239.255.255.250 [From: 192.168.20.3]. Inserting route.
No existing route for 239.255.255.250. Create new.
No routes in table. Insert at beginning.
Inserted route table entry for 239.255.255.250 on VIF #-1
No downstream listeners for group 239.255.255.250. No join sent.Current routing table (Insert Route):
–---------------------------------------------------
#0: Src: 0.0.0.0, Dst: 239.255.255.250, Age:2, St: I, OutVifs: 0x00000000Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.3 to 239.255.255.250
Current routing table (Activate Route):
#0: Src: 192.168.20.3, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
Route activate request from 192.168.20.5 to 239.255.255.250
The origin for route 239.255.255.250 changed from 192.168.20.3 to 192.168.20.5Current routing table (Activate Route):
#0: Src: 192.168.20.5, Dst: 239.255.255.250, Age:2, St: A, OutVifs: 0x00000000
^Cselect() failure; Errno(4): Interrupted system call
Got a interupt signal. Exiting.
clean handler called
Removing route entry for 239.255.255.250
Vif bits : 0x00000000
Removing MFC: 192.168.20.5 -> 239.255.255.250, InpVIf: 2
MRT_DEL_MFC; Errno(49): Can't assign requested address
All routes removed. Routing table is empty.
Shutdown complete.... -
Pues no veo anda raro que explique por que no te funciona… el pfsense corre en un host fisico o virtualizado? tienes la ont directa al nic del pfsense?
-
Hola donizt :
El pfSense corre en un host virtualizado (KVM, proxmox) y la ont está directamente conectada con un cable a uno de los interfaces físicos del servidor proxmox, que a su vez está dedicado como interfaz externo (virtio) al pfsense.
De todas formas, me parece rarisimo que internet me funcione de maravilla, sin embargo la IPTV no hay manera…
Gracias !!
-
No conozco promox pero revisa en la configuración de los servidores de virtualizacion que no se este filtrando el trafico multicast en vmware hay una opcion para permitir trafico multicast que por defecto viene activada. Revisa que no tengas algo parecido por que lo que parece es que en la vlan de imagenio no hay nada de trafico multicast.
-
mirando en google veo que hay que hacer algunas cosas para que el multicast funcione
http://pve.proxmox.com/wiki/Multicast_notes
https://forum.proxmox.com/threads/multicast-is-there-a-test-to-check.8165/
https://forum.proxmox.com/threads/multicast-problem-solved-enabling-promisc-mode.27082/Al configuración del pfsense aparentemente esta bien. Mínimo deberias tener trafico multicast en la interfave iptv me parece que el problema es externo al pfsense
-
Hola que tal?
Ante todo agradecer a todo la gente del foro la ayuda que están prestando a la comunidad.
Reabro este hilo en vez de crear uno nuevo, porque todos los enlaces de google vienen aquí y tengo un poco de confusión…
¿alguien tiene todo configurado y que le funcione correctamente?
ya que el manual elaborado por donizt en pdf tiene unas pautas a seguir, pero luego él mismo comenta que hay un fallo con el igm-prozy, ¿se actualizó el manual o es la priemra versión?
yo actualmente tengo:
ONT --- pfsense con las 3vlan creadas pero no logro hacer que funcione ni voip ni iptv.
Miento, iptv me llegó a funcionar por vlc, pero el deco arris se queda en negro (leí que hay que conectarlo directamente sin pasar por swtiches para evitar el multicast en todos los puntos de red, pero me pierdo un poco.
si añado una segunda interface conectada directamente al deco... con qué parametros? ip fija? puerta de enlace específica? ¿que reglas le meto en el firewall para asignarla al decodificador?Y luego está el tema de voip... en el manual sólo dice que configures la vlan, y nada más. ¿Es necesario alguna otra configuración?
Estoy haciendo capturas de pantalla de todo, para que una vez vaya todo, poder ampliar el manual.saludos
-
Hola elhits :
Yo sigo sin conseguir hacer funcionar IPTV y VOIP. El resto me funciona perfecto y sin problemas. Lo único es que lo tengo virtualizado con KVM y el problema puede estar en el multicast, pero no he dado con ello.
En cualquier caso, puedo disponer de una máquina dedicada con dos intergaces GBit, para instalar desde cero y realizar pruebas. Me encantaría tener todo funcionando con pfSense.
Cualquier cosa, me comentas.
-
Muy buenas, comento un poco la situación actual:
Actualmente el sistema funciona completamente, tanto la voip, el imagenio y demás. La guia en pdf no esta actualizada pero básicamente por lo único que hay que cambiar son las ips de upstream del interface imageneio en el igmpproxy -172.26.0.0/16, 239.0.0.0/8, 10.0.0.0/8, 239.0.0.0/16, 172.0.0.0/8-
En cuanto a tener el pfsense virtualizado, en mi caso tengo 4 sistemas distintos para familiares y amigos todos virtualizados con vmware esxi y corriendo sin problemas. Pero no he sido capaz de hacerlo funcionar con promox, el trafico multicast no llega a las maquinas virtuales y cuando busque información vi que había muchos casos parecido y decidí volver al vmware.
Mas cosillas, la Voip funciona perfectamente y es una gozada montar una centralita ip y y el telefono conectado al pfsense por openvpn y que las llamadas movil->fijo salgan por el el teléfono de casa via vpn y con la linea de 200MB esa que dan extra que no vale de nada meterla en la centralita y que las fijo->movil salgan por esa tarjeta…. :-)
Todo este sistema en principio solo funciona si la ONT esta por separa del router, por lo visto movistar lleva un tiempo montando un sistema que es todo junto, en ese caso creo que no se puede hacer nada al estar todo integrado, pero no conozco a nadie que se lo pusieran todo integrado y no he podido meterle mano.
-Esta parte es opcional y no afecta al funcionamiento standart-
Si alguien quiere montar un servidor como tvheanded (lo cual recomiendo) se puede montar en otra maquina y recomiendo mirar la pagina de http://www.luispa.com/ que aunque no use pfsense (lo monta todo con gentoo) si da mucha informacion para afinarlo mucho sobre todo en cuanto a la dns de imagenio para el epg. (Nota: olvidaros de hacer un ping a la dns de imagenio 172.26.23.3 que no responde)
Para comprobar que las dns las esta resolviendo correctamente el dominio svc.imagenio.telefonica.net y tv.movistar.es deben apuntar a 172.26.23.3 De no ser asi se meten en la seccion Domain Overrrides dentro del DNS Forwader
-Fin de la parte opcional-Mi recomendación para gente que lo monte de 0 siguiendo los pasos de la guia es que primero monte bien todas las interfaces y el dhcp de voip le de ip y despues seguir con l aparte de imagenio comprobar que el igmpproxy esta haciendo su trabajo haciendo un tcpdump al interface imganeio cuando alguien pida video por molticast (el vlc por ejemplo) si todo ba bien deben empezar a aparecer trafico multicast en el tcpdump. Si eso es asi la cosa tiene buena pinta.
Si no se ve trafico multicast parar y revisar bien las cosas antes de continuar. -
Gracias por tus comentarios, donizt.
Hace una semana, me armé de paciencia y monté en un servidor físico con dos puertos gbit, con pfsense 2.3.4. Seguí los pasos y después de varias pruebas y algunas modificaciones, lo tuve funcionando, con imagenio incluido. Todo fenomenal. Después volví a crear una nueva máquina virtual desde cero en proxmox, seguí los mismos pasos realizados en el servidor físico y… FUNCIONANDO !!! Todavía me queda configurar la parte de VoIP, en breve me podré con ello y te iré comentando.
Saludos.
-
Genial eres el primero que conozco que le funciona con promox, lo mismo al version que hay ahora soluciona lo del multicast de la version anterior, la verdad es que no lo he mirado, pero lo mirare por que promox tiene algunas cosas muy chulas que con vmware son de pago
enhorabuena