#3 IPv6 support

[Pedro Lopez-Cabanillas]

For your information, latest desktop VMPK has IPv6 enabled, in addition to IPv4. I've used the address ff12::37 by default.

Why is it important for me? Because my new router Orange Livebox Fibra refuses to route UDP IPv4 frames. No problem with IPv6.

And also ... https://www.google.com/intl/es/ipv6/statistics.html

[Rui Nuno Capela]

hi Pedro,

i'm sure you know that UDP/IP multicast is not--never was--meant to fly over the internet.
eventually, it might get through in some (naive? promiscuous?) networks but it is not, nerver been, the use case for qmidinet in particular and UDP/IP multicast in general whatsoever.

that said, it 's all mean to run on a LAN segment and probably static switches only; never meant to go through a router, no matter if it's set to IPv4/6 or else.

however, if you think you can contribute with some IPv6 code, I'm all ears and open and sure will welcome that stuff :)

thanks && cheers

[Pedro Lopez-Cabanillas]

Hi,

And I'm sure that you know that if you want your UDP IP multicast packets to travel from Wifi connected devices to Ethernet connected ones (and vice-versa) within your LAN, you need a router capable of that.

I don't have any problems with TCP/IPv4 services between Wifi and Ethernet connected devices with this router, but looks like UDP IPv4 multicast is not supported, even among two devices directly connected to Ethernet ports of the router (and of course, configured to belong to the same LAN segment).

The link to the IPv6 adoption statistics is relevant because I expect that in the future more and more netwoork equipment will be deprecating IPv4 support. Or that IPv6-only equipment become dominant in the market.

About the IPv6 code, you can take it yourself from the drumstick-rt plugins at your convenience.
https://sourceforge.net/p/drumstick/code/HEAD/tree/trunk/library/rt-backends/net-in/netmidiinput_p.cpp
https://sourceforge.net/p/drumstick/code/HEAD/tree/trunk/library/rt-backends/net-out/netmidioutput.cpp

Regards,
Pedro

[Pedro Lopez-Cabanillas]

By the way: this request also applies to QmidiCtl

[Rui Nuno Capela]

will get up to this eventually, though not high a priority atm. :)
many thanks for the heads-up anyway!
cheers

[Pedro Lopez-Cabanillas]

Most modern Internet domestic routers installed by telcos provide both Ethernet and Wireless. My Linux desktop computer is connected via Ethernet, and my Android phone and my laptops (an Apple MacBook and an Asus transformer book t101ha with Windows 10) are usually connected via Wireless. Of course the main network usage is for Internet navigation, but the router also allows local network communications. I've used in the past some different routers configured by default to offer a single logical network segment encompassing the Wireless and Ethernet connections. In fact, some routers have a configuration option called "Client isolation" or "Wireless isolation" that, when enabled, configures Wireless and Ethernet ports as different local network segments, all with Internet access but without routing among them. I've never used this isolated mode except for specific testing purposes. The single segment scenario would be easy to emulate in a computer with two network interfaces configured in "bridge" mode.

What I've used extensively is to connect a MIDI program in my mobile devices with MIDI soft synths and DAWs in my desktop computer using ipMIDI. It always worked like a charm with IPv4 until Orange changed my home router to this Livebox Fibra model, which is fully IPv6 with limited IPv4 compatibility. UDP IPv4 multicast doesn't work with this router, even when using two Ethernet connected computers (without an additional Ethernet switch), but at least VMPK works now using my IPv6 implementation.

[Rui Nuno Capela]

hi Pedro,

there are good news already: as of todays git head master [a16936] there's anew hope! ;)
though, due to its extreme experimental status, could you please test on your particular LAN, provided you should build it from source with ./configure --enable-ipv6 ... ?

note that you probably have to set IP address into a IPv6 multicast one, to make it switch operation mode. eg. in Options, set UDP Address to "ff12::37" explicitly !

thanks a lot && cheers, saludos!

[Pedro Lopez-Cabanillas]

I've built it with CMake, because I try to avoid the autotools. Minor changes where needed (you have a merge request pending). Works OK here.

Muito obrigado!

[Rui Nuno Capela]

you're welcome

meanwhile please keep testing the new code as build from cmake -DCONFIG_IPV6=1 .. as much as you can.

the new build option (CONFIG_IPV6) will be turned on by default upstream probably in the next days, assuming you provide positive feedback--it's working for me, though I have no rigged up IPv6 network here still:)

muchas gracias && saludos!