Asus WRT Merlin version 3006.102.5
I have TAPO cameras that send videos via RTSP ONVIF to my NVR server.
Of course I am not here to speak about Tp-Link Tapo Camera bug, but this helped me to identify something interesting on my asus router.
There are knows and never fixed bug on all TAPO cameras that (don't but this scam guys)
Digging here and there on my router (with I.A. helps) I found this about IGMP Snooping . 192.168.119.50 is the arp binded (not only DHCP reservation but arp binded by ssh) ip of the tplink camera.
On my asus router i have IGMP snooping enabled for both wifi, as well as undert LAN->IPTV.
IGMP was not replied (NVR server is running and working with other cameras)
looking for kernel modules i found this
Question 1) Is IGMP and EMS working on this router ?
So i tried the following and suddenly the TpLink camera connected again to NVR
A.I. suggests that maybe something wrong with broadcom hardware switch BCM4912 at L2/CAM table, as packets from TpLink camere where dropped at L2 layer not L3
A.I. deduced this as those commands suddenly fixed the problem
and probably this dmsg log underly something wrong at kernel driver loading of the hardware switch
emf: Unknown symbol osl_malloc (err -2)
igs: Unknown symbol emfc_igmp_snooper_register (err -2)
Question 2) are there Broadcom hardware switch documented trubles ?
I have TAPO cameras that send videos via RTSP ONVIF to my NVR server.
Of course I am not here to speak about Tp-Link Tapo Camera bug, but this helped me to identify something interesting on my asus router.
There are knows and never fixed bug on all TAPO cameras that (don't but this scam guys)
- Wrong RTSP closing: TCP FIN and RST unproperly formatted when the stream is closed
- Keep-alive buggy: keep-alive packets wrongly send
- Aggressive Port reuse : Try to reuse old opened ports without waiting timeouts
Digging here and there on my router (with I.A. helps) I found this about IGMP Snooping . 192.168.119.50 is the arp binded (not only DHCP reservation but arp binded by ssh) ip of the tplink camera.
On my asus router i have IGMP snooping enabled for both wifi, as well as undert LAN->IPTV.
Bash:
conntrack -L | grep 192.168.119.50
Bash:
unknown 2 586 src=192.168.119.50 dst=224.0.0.22 [UNREPLIED] src=224.0.0.22 dst=192.168.119.50 mark=4239808 use=1
IGMP was not replied (NVR server is running and working with other cameras)
looking for kernel modules i found this
Bash:
lsmod | grep emf
emf 28672 3 dhd,wl,igs
hnd 380928 4 dhd,wl,igs,emf
bcmmcast 110592 5 dhd,igs,emf,wfd
@GT-AX6000-C0C0:/tmp/home/root# dmesg | grep -i emf
emf: Unknown symbol osl_malloc (err -2)
emf: Unknown symbol osl_pktdup_cpy (err -2)
emf: Unknown symbol osl_mfree (err -2)
emf: Unknown symbol linux_pktfree (err -2)
emf: Unknown symbol osl_pktdup (err -2)
igs: Unknown symbol emfc_wmf_scbfind (err -2)
igs: Unknown symbol emfc_mfdb_ipv6_membership_add (err -2)
igs: Unknown symbol emfc_rtport_del (err -2)
igs: Unknown symbol emfc_igmp_snooper_register (err -2)
igs: Unknown symbol emfc_mfdb_ipv6_membership_del (err -2)
igs: Unknown symbol emfc_wmf_get_igsc (err -2)
igs: Unknown symbol emfc_rtport_add (err -2)
igs: Unknown symbol emfc_igmp_snooper_unregister (err -2)
igs: Unknown symbol emfc_mfdb_membership_del (err -2)
igs: Unknown symbol emfc_mfdb_membership_add (err -2)
Question 1) Is IGMP and EMS working on this router ?
So i tried the following and suddenly the TpLink camera connected again to NVR
Bash:
echo "=== active Tplink camera 192.168.119.50 connections ==="
conntrack -L | grep 192.168.119.50
echo "=== Flushing conntrack entries ==="
conntrack -D -s 192.168.119.50
conntrack -D -d 192.168.119.50
echo "=== Connections after flush ==="
conntrack -L | grep 192.168.119.50
echo "=== Flushing routing cache ==="
ip route flush cache
echo "=== Current ARP entry ==="
arp | grep 192.168.119.50
echo "=== Deleting ARP entry ==="
arp -d 192.168.119.50
echo "=== Rebuilding ARP ==="
ping -c 2 192.168.119.50
echo "=== New ARP entry ==="
arp | grep 192.168.119.50
echo "=== Final check - all connections for camera ==="
conntrack -L | grep 192.168.119.50
A.I. suggests that maybe something wrong with broadcom hardware switch BCM4912 at L2/CAM table, as packets from TpLink camere where dropped at L2 layer not L3
A.I. deduced this as those commands suddenly fixed the problem
Bash:
arp -d 192.168.119.50
ping -c 2 192.168.119.50
and probably this dmsg log underly something wrong at kernel driver loading of the hardware switch
emf: Unknown symbol osl_malloc (err -2)
igs: Unknown symbol emfc_igmp_snooper_register (err -2)
Question 2) are there Broadcom hardware switch documented trubles ?
Last edited: