Nie można wyświetlić tego widżeta.
Nie można wyświetlić tego widżeta.
Nie można wyświetlić tego widżeta.

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

ROZWIĄZANE
Idź do rozwiązania
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Przeglądałem forum i znalazłem wątek w którym jest informacja o tym, żeby w igmpproxy ustawić grupę adresów 10.0.0.0/8.
https://nasz.orange.pl/t5/Modemy-i-routery/Dzia%C5%82anie-dekodera-IPTV-w-podsieci/td-p/257752/page/...

 

phyint <interface podpięty do FB> upstream ratelimit 0 threshold 1

 altnet 10.0.0.0/8

phyint <interface LAN> downstream ratelimit 0 threshold 1


Skonfigurowałem "Bridge relay" na podstawie dokumentu który już był wcześniej przytaczany, żeby przydzielać adresy pomiędzy FunBox DHCP a klienatami za OpenWRT.

https://openwrt.org/docs/guide-user/network/wifi/wifiextenders/relay_configuratio

 

Zainstalowałem również pakiet igmpproxy którego domyślna konfiguracja wygląda następująco:

config igmpproxy
        option quickleave 1
#       option verbose [0-3](none, minimal[default], more, maximum)

config phyint
        option network wan
        option zone wan
        option direction upstream
        list altnet 192.168.1.0/24

config phyint
        option network lan
        option zone lan
        option direction downstream

 

Poniżej umieszczam wyniki 'ifconfig -a' dla wypisania urządzeń oraz zawartość pliku konfiguracyjnego do nich z /etc/config/network. Sieć bridge utworzona przez relayD, jest nazwana "config interface 'Bridge'",

 

W których połaczenie przez WiFi jest "parowane" przez urządzenie phy1-sta0. A konfiguracja do niego zawiera się w pliku /etc/config/networks w bloku "config interface 'FunBox_Connetion'"

 

 

root@OpenWrt:~# ifconfig -a
br-lan    Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9329 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10620 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1111069 (1.0 MiB)  TX bytes:14550707 (13.8 MiB)

eth0      Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          inet6 addr: fe80::6283:e7ff:fec6:dae8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1504  Metric:1
          RX packets:9405 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16516 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1283464 (1.2 MiB)  TX bytes:15034124 (14.3 MiB)
          Interrupt:21

lan1      Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan2      Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan3      Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan4      Link encap:Ethernet  HWaddr 60:83:XX:XX:XX:XX
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9405 errors:0 dropped:5 overruns:0 frame:0
          TX packets:10619 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1114174 (1.0 MiB)  TX bytes:14550665 (13.8 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1186 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1186 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:97611 (95.3 KiB)  TX bytes:97611 (95.3 KiB)

phy1-sta0 Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6283:e7ff:fec6:dae7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16400 errors:0 dropped:88 overruns:0 frame:0
          TX packets:9957 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14517939 (13.8 MiB)  TX bytes:2717087 (2.5 MiB)

wan       Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21

wlan0     Link encap:Ethernet  HWaddr 60:83:E7:XX:XX:XX
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
root@OpenWrt:~# nano /etc/config/network
  GNU nano 8.2                                                                                                 /etc/config/network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd69:2a91:51df::/48'
        option packet_steering '1'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'
        option ipv6 '0'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'FunBox_Connetion'
        option proto 'static'
        option device 'phy1-sta0'
        option ipaddr '192.168.1.3'
        option netmask '255.255.255.0'
        option gateway '192.168.1.1'
        option broadcast '192.168.1.255'
        list dns '8.8.8.8'

config interface 'Bridge'
        option proto 'relay'
        list network 'FunBox_Connetion'
        list network 'lan'
        option ipaddr '192.168.1.3'

 

 

Jak teraz należy poprawnie skonfigurować plik /etc/config/igmpproxy, aby uwzględnić nazwy urządzeń, interfejsów a także "altnet 10.0.0.0/8", na którym "nadaje" multicast?

Jak rozumiem igmpproxy pobiera konfiguracje z pliku /etc/config/network? Czy jak rozwiązuje nazwy?

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Generalnie ustawiłem w ten sposób igmpproxy:

 

 

config igmpproxy
    option quickleave 0

config phyint
    option network 'phy1-sta0'
    option zone 'lan'
    option direction 'upstream'
    option ratelimit 0
    option threshold 1
    list altnet '10.0.0.0/8'

config phyint
    option network 'lan'
    option zone 'lan'
    option direction 'downstream'
    option ratelimit 0
    option threshold

 

 

I dalej nie działa.

Nie działa też wtedy kiedy w upstream ustawię option network 'FunBox_Connetion'  jako nazwę sieci.

Aczkolwiek downstream ustawiony jako option network 'lan' w obu przypadkach powoduje wygenerowanie logów. Wydaje się że nie ma logów gdy downstream jest ustawiony na br-lan. Adres dekodera to 192.168.1.25.

 

 

root@OpenWrt:~# tcpdump -i phy1-sta0 igmp
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on phy1-sta0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
16:02:38.929295 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
16:02:38.931383 IP 192.168.1.1 > 232.0.20.59: igmp query v2 [max resp time 1] [gaddr 232.0.20.59]
16:02:39.027326 IP 192.168.1.1 > 232.0.20.59: igmp query v2 [max resp time 1] [gaddr 232.0.20.59]
16:02:39.504785 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
16:02:41.884766 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
16:02:44.932672 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
16:02:44.936257 IP 192.168.1.1 > 232.0.20.59: igmp query v2 [max resp time 1] [gaddr 232.0.20.59]
16:02:45.027351 IP 192.168.1.1 > 232.0.20.59: igmp query v2 [max resp time 1] [gaddr 232.0.20.59]
16:02:45.473083 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
^C
9 packets captured
10 packets received by filter
0 packets dropped by kernel

 

 

Znalazłem jeszcze reguły firewalla:

https://openwrt.org/docs/guide-user/network/wan/udp_multicast

 

Aczkolwiek ja mam puszczony cały ruch, więc nie wiem z czego to może wynikać ten problem.

 

root@OpenWrt:~# nano /etc/config/firewall
  GNU nano 8.2                                                                                                /etc/config/firewall

config defaults
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        option synflood_protect '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'
        list network 'FunBox_Connetion'
        list network 'briddge'
        list network 'Bridge'

 

Odpowiedz
Samotnick

Poziom 31, Pasjonat Galaktyczny
  • 2217
  • 10615
  • 89
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

@P7CagdPBe8mwHy7 Moim skromnym zdaniem musisz zdecydować się na tandem  igmpproxy i różna adresacja po obu stronach (i NAT) lub tryb brigde i relayd.

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Spróbuję jeszcze bridge i udpxy, ale to w późniejszym terminie.

Poza tym nie ma iptables, tylko jest fw3, i reguły w /etc/firewall.user nie działają nawet po instalacji pakietów.

 

root@OpenWrt:~# tail /etc/firewall.user
iptables -t mangle -A PREROUTING -d 224.0.0.0/4 -p udp -j TTL --ttl-set 2
iptables -t mangle -A PREROUTING -i phy1-sta0 -d 224.0.0.0/4 -p udp -j TTL --ttl-set 2
iptables -A INPUT -i phy1-sta0 -j DROP
iptables -A OUTPUT -o phy1-sta0 -j DROP
root@OpenWrt:~# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

A do fw3 nie za bardzo są manuale. Chociaż wątpię aby blokował to firewall bo jest puszczony cały ruch, jako accept.

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Witam ponownie. 

 

Dalej reparter nie działa poprawnie. 

Próbowałem ustawić VLAN 839 i jako WAN podać mu kartę WiFi na której jest połączenie z FunBoxem. 

Następnie ustawić mostek z konfguracją zaadaptowaną stąd:

https://nasz.orange.pl/t5/Modemy-i-routery/Konfiguracja-IPTV-na-OpenWRT-LuCI-z-dekoderem-4K-Multi/td...

 

Po podłaczeniu do dekodera, dekoder przerywa połączenie jest stop-klatka i nie ma logów w ogóle w TCPdump. 

Odpowiedz
Samotnick

Poziom 31, Pasjonat Galaktyczny
  • 2217
  • 10615
  • 89
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

@P7CagdPBe8mwHy7 Nie ma żadnych VLANów po stronie LAN, nie tędy droga. Zobacz https://www.gargoyle-router.com/phpbb/viewtopic.php?t=5115

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Dziękuję za odpowiedź. 

 

Zrobiłem tą konfigurację jeszcze raz w trybie mostka. Pakiet udpxy jest generalnie do vlc media player, albo kodi. Więc go odpuszczam. 

Musze mieć relayD ponieważ inaczej nie przydziela adresu IP dekoderowi. 

 

Konfiguracja /etc/config/network oraz struktura ifconfig generalnie się nie różni od tego co już wklejałem. 

ifconfig -a 

 

root@OpenWrt:~# ifconfig -a
br-lan    Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:936 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:120702 (117.8 KiB)  TX bytes:109324 (106.7 KiB)
 
eth0      Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          inet6 addr: fe80::6283:e7ff:fec6:dae8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1504  Metric:1
          RX packets:866 errors:0 dropped:0 overruns:0 frame:0
          TX packets:944 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:136943 (133.7 KiB)  TX bytes:124327 (121.4 KiB)
          Interrupt:21
 
lan1      Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
lan2      Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
lan3      Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
lan4      Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:866 errors:0 dropped:3 overruns:0 frame:0
          TX packets:928 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:121355 (118.5 KiB)  TX bytes:108830 (106.2 KiB)
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4594 (4.4 KiB)  TX bytes:4594 (4.4 KiB)
 
phy1-sta0 Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6283:e7ff:fec6:dae7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:469 errors:0 dropped:29 overruns:0 frame:0
          TX packets:326 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:63220 (61.7 KiB)  TX bytes:22639 (22.1 KiB)
 
wan       Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:21
 
wlan0     Link encap:Ethernet  HWaddr 60:83:E7:xx:xx:xx
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

 

 

/etc/config/network 

 

onfig interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'
 
config globals 'globals'
        option ula_prefix 'fd69:2a91:51df::/48'
        option packet_steering '1'
 
config device
        option igmp_snooping '1'
        option name 'br-lan'
        option type 'bridge'
        list ports 'lan1'
        list ports 'lan2'
        list ports 'lan3'
        list ports 'lan4'
        option ipv6 '0'
 
config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
 
config interface 'FunBox_Connetion'
        option proto 'static'
        option device 'phy1-sta0'
        option ipaddr '192.168.1.3'
        option netmask '255.255.255.0'
        option gateway '192.168.1.1'
        option broadcast '192.168.1.255'
        list dns '8.8.8.8'
 
config interface 'Bridge'
        option proto 'relay'
        option ipaddr '192.168.1.3'
        list network 'FunBox_Connetion'
        list network 'lan'

 

 

 

Odbiega troche konfiguracja igmpproxy oraz firewalla do niego:

 

config igmpproxy
        option quickleave 1
#       option verbose [0-3](none, minimal[default], more, maximum)

config phyint
        option network 'phy1-sta0'
        option zone 'iptv'
        option direction 'upstream'
        list altnet '0.0.0.0/0'

config phyint
        option zone 'lan'
        option network 'lan'
        option direction 'downstream'

 

/etc/config/firewall

 

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'
        list network 'Bridge'

config zone
        option name 'iptv'
        list network 'FunBox_Connetion'
        option input 'DROP'
        option output 'ACCEPT'
        option forward 'DROP'

config rule
        option target 'ACCEPT'
        option proto 'igmp'
        option src 'FunBox_Connetion'

config rule
        option target 'ACCEPT'
        option proto 'udp'
        option src 'FunBox_Connetion'
        option dest 'lan'
        option dest_ip '224.0.0.0/4'

config forwarding
        option src 'FunBox_Connetion'
        option dest 'lan'

 

 

 

.

.

.

 

Taka knfiguracja powoduje generowanie logów. 

 

Ale problem jest z Firewallem. 

Nie działają opcje option src 'FunBox_Connetion' lub też option src 'phy1-sta0'

root@OpenWrt:~# /etc/init.d/firewall restart
Section @rule[0] option 'src' specifies invalid value 'FunBox_Connetion'
Section @rule[0] skipped due to invalid options
Section @rule[1] option 'src' specifies invalid value 'FunBox_Connetion'
Section @rule[1] skipped due to invalid options
Section @forwarding[0] option 'src' specifies invalid value 'FunBox_Connetion'
Section @forwarding[0] skipped due to invalid options
root@OpenWrt:~# nano /etc/config/firewall

root@OpenWrt:~# /etc/init.d/firewall restart
Section @rule[0] option 'src' specifies invalid value 'phy1-sta0'
Section @rule[0] skipped due to invalid options
Section @rule[1] option 'src' specifies invalid value 'phy1-sta0'
Section @rule[1] skipped due to invalid options
Section @forwarding[0] option 'src' specifies invalid value 'phy1-sta0'
Section @forwarding[0] skipped due to invalid options

1. Co należy wpisać w option src '' żeby firewall się uruchomił?

 

Poniżej są logi z tcpdump, 

root@OpenWrt:~# tcpdump -i phy1-sta0 | grep 192.168.1.25
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on phy1-sta0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:35:06.969633 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:09.237849 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:14.966629 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.18.36
14:35:17.069723 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.18.36
14:35:22.470589 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.19.78
14:35:28.469490 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.19.78
14:35:29.411236 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.18.36
14:35:29.904797 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:31.206669 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.18.102
14:35:33.895445 ARP, Request who-has 192.168.1.25 tell 192.168.1.3, length 28
14:35:33.896559 ARP, Request who-has 192.168.1.25 (Broadcast) tell 192.168.1.25, length 28
14:35:33.896655 ARP, Reply 192.168.1.25 is-at 60:83:e7:c6:da:e7 (oui Unknown), length 28
14:35:36.970306 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:42.972262 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:48.976487 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:35:54.970931 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
14:36:00.970588 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
^C407 packets captured
413 packets received by filter
0 packets dropped by kernel

2. Dlaczego jest napisane igmp leave 232.0.20.59

14:35:06.969633 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59

Innymi słowy dlaczego dekoder z opuszcza grupę? 

 

Odpowiedz
Samotnick

Poziom 31, Pasjonat Galaktyczny
  • 2217
  • 10615
  • 89
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

@P7CagdPBe8mwHy7 Ruch IGMP wychodzi. Zmień grepa tak aby pokazywał ruch z docelowym adresem z klasy multicastowej lub https://stackoverflow.com/questions/7931746/how-can-i-use-tcpdump-on-unix-to-view-messages-sent-to-a...

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

Zmieniłem "src" na iptv które było zdefiniowane w "config zone" w którym już jest sieć FunBox_Connetion i uruchomiła się bez błędów ale pomieszałem coś w GUI i odcięło internet w routerze. Generalnie jestem przyzwyczajony do jakichś normalnych firewalli typu ipfw albo pf, które posiadają logi a tu są jakieś dziwne rzeczy utworzone typu np. zony.

 

config defaults
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option synflood_protect '1'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        list network 'lan'
        list network 'Bridge'

config zone
        option name 'iptv'
        list network 'FunBox_Connetion'
        option input 'DROP'
        option output 'ACCEPT'
        option forward 'DROP'

config rule
        option target 'ACCEPT'
        option proto 'igmp'
        option src 'iptv'

config rule
        option target 'ACCEPT'
        option proto 'udp'
        option src 'iptv'
        option dest 'lan'
        option dest_ip '224.0.0.0/4'

config forwarding
        option src 'iptv'
        option dest 'lan'

 

 

Co do komend z linku sprawdzę jak tylko będę mieć dostęp do TV. 

tcpdump -i eth0 -s0 -vv host 239.255.255.250
tcpdump -i eth0 -s0 -vv net 224.0.0.0/4

 

Odpowiedz
P7CagdPBe8mwHy7

Poziom 19, Odkrywca Przestworzy
  • 21
  • 54
  • 1
wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

wrzesień

TP-LINK Archer AX23 w trybie bridge - czarny ekran na IPTV

 

 

Poniżej zapis logów z tcpdump. 

 

1. końcowy fragment loga od włączenia dekodera do uruchomienia strimingu kanału. 

17:35:12.370518 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:13.013745 IP 212.244.39.202.443 > 192.168.1.25.58609: Flags [F.], seq 2784, ack 2336, win 16935, options [nop,nop,TS val 363260014 ecr 5152757], length 0
17:35:13.017776 IP 212.244.39.200.443 > 192.168.1.25.39696: Flags [F.], seq 30915, ack 3996, win 18595, length 0
17:35:13.054471 IP 192.168.1.25.58609 > 212.244.39.202.443: Flags [.], ack 2785, win 4748, options [nop,nop,TS val 5157132 ecr 363260014], length 0
17:35:13.058310 IP 192.168.1.25.39696 > 212.244.39.200.443: Flags [.], ack 30916, win 18980, length 0
17:35:14.008666 IP 212.244.39.200.443 > 192.168.1.25.39698: Flags [F.], seq 28885, ack 2396, win 16995, options [nop,nop,TS val 363261010 ecr 5153508], length 0
17:35:14.010638 IP 212.244.39.200.443 > 192.168.1.25.39700: Flags [F.], seq 19856, ack 2396, win 16995, options [nop,nop,TS val 363261012 ecr 5153573], length 0
17:35:14.017288 IP 212.244.39.200.443 > 192.168.1.25.39699: Flags [F.], seq 36076, ack 2396, win 16995, options [nop,nop,TS val 363261018 ecr 5153516], length 0
17:35:14.049461 IP 192.168.1.25.39698 > 212.244.39.200.443: Flags [.], ack 28886, win 4672, options [nop,nop,TS val 5158127 ecr 363261010], length 0
17:35:14.051386 IP 192.168.1.25.39700 > 212.244.39.200.443: Flags [.], ack 19857, win 4672, options [nop,nop,TS val 5158129 ecr 363261012], length 0
17:35:14.057352 IP 192.168.1.25.39699 > 212.244.39.200.443: Flags [.], ack 36077, win 4672, options [nop,nop,TS val 5158135 ecr 363261018], length 0
17:35:14.303260 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
17:35:14.835678 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:18.658784 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:20.306542 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
17:35:20.818005 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:21.524911 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:24.563870 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
17:35:24.622046 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
17:35:26.304936 ARP, Request who-has 192.168.1.25 tell 192.168.1.1, length 38
17:35:26.306204 ARP, Request who-has 192.168.1.25 (Broadcast) tell 192.168.1.25, length 28
17:35:26.306411 ARP, Reply 192.168.1.25 is-at 60:83:e7:XX:XX:XX (oui Unknown), length 28
17:35:26.306488 ARP, Reply 192.168.1.25 is-at 60:83:e7:XX:XX:XX (oui Unknown), length 28
17:35:26.347557 ARP, Request who-has 192.168.1.25 tell 192.168.1.1, length 38
17:35:26.348730 ARP, Request who-has 192.168.1.25 (Broadcast) tell 192.168.1.25, length 28
17:35:26.348884 ARP, Reply 192.168.1.25 is-at 60:83:e7:XX:XX:XX (oui Unknown), length 28
17:35:26.348960 ARP, Reply 192.168.1.25 is-at 60:83:e7:XX:XX:XX (oui Unknown), length 28
17:35:26.705441 IP 212.244.39.200.443 > 192.168.1.25.39698: Flags [R.], seq 28886, ack 2396, win 0, length 0
17:35:27.219960 IP 212.244.39.200.443 > 192.168.1.25.39700: Flags [R.], seq 19857, ack 2396, win 0, length 0
17:35:28.359404 IP 212.244.39.200.443 > 192.168.1.25.39696: Flags [R.], seq 30916, ack 3996, win 0, length 0
17:35:29.290027 IP 212.244.39.200.443 > 192.168.1.25.39699: Flags [R.], seq 36077, ack 2396, win 0, length 0
17:35:29.802934 IP 192.168.1.25 > all-routers.mcast.net: igmp leave 232.0.20.59
17:35:30.326392 IP 192.168.1.25 > 232.0.20.59: igmp v2 report 232.0.20.59
^C20311 packets captured
20418 packets received by filter
0 packets dropped by kernel

 

2. Fragment wyniku logów z komendy tcpdump -i phy1-sta0 -s0 -vv net 224.0.0.0/4 dużo powtarzających się wpisów. 

17:39:59.045585 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.045630 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.047602 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.049574 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.051574 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.051616 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.053620 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.056359 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.057581 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.059598 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.059642 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.061574 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.063597 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.065586 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.067606 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
17:39:59.067648 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328
^C17:39:59.070835 IP (tos 0x90, ttl 49, id 0, offset 0, flags [DF], proto UDP (17), length 1356)
    10.1.61.8.4352 > 232.0.20.59.5500: [no cksum] UDP, length 1328

3. Wynik tcpdump -i phy1-sta0 -s0 -vv host 239.255.255.250

root@OpenWrt:~# tcpdump -i phy1-sta0 -s0 -vv host 239.255.255.250
tcpdump: listening on phy1-sta0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
17:54:39.550974 IP (tos 0x0, ttl 4, id 4707, offset 0, flags [DF], proto UDP (17), length 304)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 276
17:54:39.551521 IP (tos 0x0, ttl 4, id 4708, offset 0, flags [DF], proto UDP (17), length 304)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 276
17:54:39.552055 IP (tos 0x0, ttl 4, id 4709, offset 0, flags [DF], proto UDP (17), length 313)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 285
17:54:39.857737 IP (tos 0x0, ttl 4, id 4710, offset 0, flags [DF], proto UDP (17), length 313)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 285
17:54:39.858348 IP (tos 0x0, ttl 4, id 4711, offset 0, flags [DF], proto UDP (17), length 368)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 340
17:54:39.858959 IP (tos 0x0, ttl 4, id 4712, offset 0, flags [DF], proto UDP (17), length 368)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 340
17:54:39.859592 IP (tos 0x0, ttl 4, id 4713, offset 0, flags [DF], proto UDP (17), length 378)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 350
17:54:39.860226 IP (tos 0x0, ttl 4, id 4714, offset 0, flags [DF], proto UDP (17), length 378)
    192.168.1.1.1900 > 239.255.255.250.1900: [udp sum ok] UDP, length 350
17:54:41.393677 IP (tos 0x80, ttl 4, id 31808, offset 0, flags [DF], proto UDP (17), length 165)
    192.168.1.23.51048 > 239.255.255.250.1900: [udp sum ok] UDP, length 137
17:54:42.314992 IP (tos 0x80, ttl 1, id 0, offset 0, flags [DF], proto IGMP (2), length 32, options (RA))
    192.168.1.23 > 239.255.255.250: igmp v2 report 239.255.255.250
17:55:06.177592 IP (tos 0x80, ttl 4, id 49849, offset 0, flags [DF], proto UDP (17), length 165)
    192.168.1.23.51048 > 239.255.255.250.1900: [udp sum ok] UDP, length 137
17:55:11.372730 IP (tos 0x0, ttl 1, id 45846, offset 0, flags [DF], proto UDP (17), length 153)
    192.168.1.13.43878 > 239.255.255.250.1900: [udp sum ok] UDP, length 125
17:55:14.878598 IP (tos 0x80, ttl 4, id 52125, offset 0, flags [DF], proto UDP (17), length 313)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 285
17:55:14.879198 IP (tos 0x80, ttl 4, id 52145, offset 0, flags [DF], proto UDP (17), length 370)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 342
17:55:15.185845 IP (tos 0x80, ttl 4, id 52316, offset 0, flags [DF], proto UDP (17), length 358)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 330
17:55:15.493125 IP (tos 0x80, ttl 4, id 52360, offset 0, flags [DF], proto UDP (17), length 304)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 276
17:55:15.800299 IP (tos 0x80, ttl 4, id 52391, offset 0, flags [DF], proto UDP (17), length 350)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 322
17:55:15.800967 IP (tos 0x80, ttl 4, id 52476, offset 0, flags [DF], proto UDP (17), length 360)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 332
17:55:15.801648 IP (tos 0x80, ttl 4, id 52483, offset 0, flags [DF], proto UDP (17), length 368)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 340
17:55:18.565045 IP (tos 0x80, ttl 4, id 54651, offset 0, flags [DF], proto UDP (17), length 368)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 340
17:55:18.565573 IP (tos 0x80, ttl 4, id 54658, offset 0, flags [DF], proto UDP (17), length 313)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 285
17:55:18.566672 IP (tos 0x80, ttl 4, id 54699, offset 0, flags [DF], proto UDP (17), length 350)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 322
17:55:18.872269 IP (tos 0x80, ttl 4, id 54743, offset 0, flags [DF], proto UDP (17), length 360)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 332
17:55:19.486685 IP (tos 0x80, ttl 4, id 54887, offset 0, flags [DF], proto UDP (17), length 358)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 330
17:55:19.487295 IP (tos 0x80, ttl 4, id 54994, offset 0, flags [DF], proto UDP (17), length 304)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 276
17:55:21.549581 IP (tos 0x80, ttl 4, id 55910, offset 0, flags [DF], proto UDP (17), length 368)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 340
17:55:21.557029 IP (tos 0x80, ttl 4, id 55911, offset 0, flags [DF], proto UDP (17), length 360)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 332
17:55:22.229650 IP (tos 0x80, ttl 4, id 55962, offset 0, flags [DF], proto UDP (17), length 313)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 285
17:55:22.261699 IP (tos 0x80, ttl 4, id 55981, offset 0, flags [DF], proto UDP (17), length 350)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 322
17:55:22.559018 IP (tos 0x80, ttl 4, id 56049, offset 0, flags [DF], proto UDP (17), length 358)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 330
17:55:22.865693 IP (tos 0x80, ttl 4, id 56139, offset 0, flags [DF], proto UDP (17), length 304)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 276
17:55:22.866308 IP (tos 0x80, ttl 4, id 56287, offset 0, flags [DF], proto UDP (17), length 370)
    192.168.1.23.51027 > 239.255.255.250.1900: [udp sum ok] UDP, length 342
17:55:31.466994 IP (tos 0x80, ttl 4, id 58753, offset 0, flags [DF], proto UDP (17), length 165)
    192.168.1.23.51048 > 239.255.255.250.1900: [udp sum ok] UDP, length 137
17:55:56.349963 IP (tos 0x80, ttl 4, id 61394, offset 0, flags [DF], proto UDP (17), length 165)
    192.168.1.23.51048 > 239.255.255.250.1900: [udp sum ok] UDP, length 137
17:56:11.709507 IP (tos 0x0, ttl 1, id 48481, offset 0, flags [DF], proto UDP (17), length 153)
    192.168.1.13.43878 > 239.255.255.250.1900: [udp sum ok] UDP, length 125
17:56:21.195468 IP (tos 0x80, ttl 4, id 8906, offset 0, flags [DF], proto UDP (17), length 165)
    192.168.1.23.51048 > 239.255.255.250.1900: [udp sum ok] UDP, length 137
^C
36 packets captured
78 packets received by filter
0 packets dropped by kernel


Wynika z tego, że dekoder najpierw się dołącza IGMP v2 report do grupy multicast 232.0.20.59  a potem się rozłącza Ponieważ wysyła IGMP leave. 

Odpowiedz