no port needed ?
Yes, a port is needed, choose something like 5555, so to send or receive the url is:
rtp://[ff08::abc:123]:5555/
Let's please stick to this so we can be sure we are not confusing each other
how can I check if any traffic is received on WAN ? just to make sure the stream is routed through the switch to the WAN port
also do I have to setup the LAN for IPv6 on the GUI or something ?
I believe that with what we have set up so far, if the switch is smart about ipv6, it will not be sending the traffic.
To confirm you can do on the router:
tcpdump -i WANGOESHERE ip6 and udp
insert your wan interface it's sometimes eth0.2 for example
19:04:38.464224 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.479215 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.489247 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.504259 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.514262 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.529260 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.539287 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.554303 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.564313 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.579301 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.589327 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.604331 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.612373 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.625442 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.637511 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.650561 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.663630 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.678614 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.689690 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.704677 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.714750 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.726798 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.739849 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.752896 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.765932 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
19:04:38.778002 IP6 fe80::d199:66cb:7489:2353.56846 > ff08::abc:123.5004: UDP, length 1328
^\Quit
Ok, so your switch is flooding the multicast traffic. It may have IGMP snooping but it doesn't have MLDv2 snooping, I suspect.
If you listen on your br-lan interface does this same udp appear? Does it appear after you start up your VLC listener? Does the VLC listener get the stream?
Also notice that you seem to have selected the default port, which is ok, but let's keep it consistent. To listen for this stream you'll need the URL:
rtp://[ff08::abc:123]:5004
not getting anything on lan
it's helpful if you give more details, as in:
"I listened on br-lan and wasn't getting anything, and then I started up VLC listener and I still wasn't getting anything"
is that correct?
ok
yes thats correct
Can you, for testing purposes, force VLC broadcaster to use TTL=2, if you don't know how, please google for it, I remember seeing it somewhere but don't remember how to do it.
EDIT: if you use the VLC streaming wizard, it will give you a thing like:
:sout=#rtp{dst=ff08::abc:123,port=5004,mux=ts,sap,name=test} :no-sout-all :sout-keep
if you add "ttl=2" as follows:
:sout=#rtp{dst=ff08::abc:123,port=5004,mux=ts,sap,name=test,ttl=2} :no-sout-all :sout-keep
You will get ttl = 2 in the packets (confirmed for my VLC at least)
1 Like
still doesn't work
you're still not being very helpful in terms of informative feedback. what did you actually do? What did you verify about the TTL on the packets? were you able to set the TTL and see it was set on the WAN packet capture? etc
ttl=2 crashes VLC instantly
what version of VLC? I have 3.0.3 on linux and it works fine and I see the TTL set correctly on packet capture.
i have version 3.0.4
you can see the stream ?
in openwrt mld traffic rules it says allow source address fe80::/10
that important ?
I don't have the setup you have. I have just a single linux machine so I can't test whether I can receive the stream, only send it 
I really don't uderstand why it doesn't work. We managed to get it to work in IPv4.
IPv6 should be easier I thought.
It will be easier, but you're going to need to get TTL=2 onto those packets or they won't route from WAN to LAN. Of course, you can adjust the TTL in ip6tables, but it would be good to send an appropriate ttl in the first place for testing.
1 Like
in ipv6 it's called the Hop Limit, and you can use a rule that does ... -j HL --hl-set 2 in the mangle table. You may need some packages to get the HL target.
so it's just the hop limit ?
I have set the Hop LImit to 2 in the VLC settings.