Jamulus
Mac jamulus client using -6 option doesn't list directory servers in any genres #2224
Replies: 3 comments 18 replies
-
|
Directories do not support IPv6 addressing. Try running with |
Beta Was this translation helpful? Give feedback.
-
|
BTW, I understand that IPv6 support is experimental, hence my testing. Seems to work as expected under Linux, can see and reach servers on both protocols when using Thanks for responding, I wanted to report what I'd found. |
Beta Was this translation helpful? Give feedback.
-
That's intentional. It's for debugging situations like this, only.
Hm. OK. Interesting. Unfortunately, my ISP doesn't support IPv6, so I can't do any testing. @softins can you confirm whether the fallback from IPv6 to IPv4 caters for querying a directory? The directory should only be listening on IPv4, so there should be no IPv6 route. (I know none of mine have an IPv6 route.) |
Beta Was this translation helpful? Give feedback.
-
|
OK, I'll do some experiments. I have IPv6 connectivity here. |
Beta Was this translation helpful? Give feedback.
-
|
I will note that my Windows and Linux boxes both have IPv6 addresses and, when I run the client with |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I have just done:
Note that on my Mac I have the Firewall switched off (System Preferences > Security & Privacy > Firewall). @rdica We will need more specific information (OS, Jamulus version, etc.), to try and understand what's happening for you. But unless it's an incompatibility with a more recent MacOS, I don't think it's a Jamulus bug. |
Beta Was this translation helpful? Give feedback.
-
MacOS Catalina 10.15.7 fully updated. I disabled the firewall, but that had same results. Running tcpdump on the interface: This continues to scroll until I close the Connection dialog box. I tried a direct connect to an IPv4 IP address of my server (daw2.diix.org), I see the connect attempt in that servers log, but it appears the connection cannot be completed. Rerunning tcpdump with which drew my attention to the packet size, and Looks to me like MTU issues? If there's any additional info I can provide, please let me know. |
Beta Was this translation helpful? Give feedback.
-
|
Could you do a capture to a file using |
Beta Was this translation helpful? Give feedback.
-
|
If you use Wireshark, you might find https://github.com/softins/jamulus-wireshark of interest too. |
Beta Was this translation helpful? Give feedback.
-
|
@softins thanks, I already installed that when I was testing some non-related things. I will work on testing with hardwired connection, and also do captures on both WIFI and hardwired. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't change anything, but I found I had another running jamulus process during all my testing, I killed it, restarted with I also found, much to my chagrine, that my ethernet adapter for Macbook was for an older version, it uses thunderbolt connector and my current macbook doesnt have that. sigh. I'm closing this as user error, sorry for wasting everyones time that looked at this. |
Beta Was this translation helpful? Give feedback.
-
|
@rdica thanks for the update. No problem, and it's still useful to know that this can occur. I have a hypothesis, which I have not tested: I suspect that the operating system may have allowed the second instance, when opening an |
Beta Was this translation helpful? Give feedback.
-
|
Hi, there! |
Beta Was this translation helpful? Give feedback.
-
|
You need the "legacy version" for MacOS. Visit https://github.com/jamulussoftware/jamulus/releases/tag/r3_11_0 and scroll down to the list of Assets. You'll see "jamulus_3.11.0_mac_legacy.dmg", which is the build you want. Download the DMG file, then double-click to run the installer. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks ever so much!!!! |
Beta Was this translation helpful? Give feedback.
-
|
Damn! When I try to open it I get the following message: “Jamulus” can’t be opened because Apple cannot check it for malicious software. What do I do? |
Beta Was this translation helpful? Give feedback.
-
You need to go to Finder, into Applications, and do Open on the Jamulus application. It will most likely give you that message, with no Open button, but a "Show in Finder" button. Click on "Show in Finder", and it will display the Applications folder again. This time, do Open again, and it should offer you an additional button for "Open". Click on "Open" and it will start the application. It will also remember that now, and allow you to open it normally each time without the warning. You will need to repeat this procedure each time you install a new version. |
Beta Was this translation helpful? Give feedback.
-
|
Hurrah!!! It is working now |
Beta Was this translation helpful? Give feedback.
-
In testing IPv6 connectivity from a Mac client, I found I could direct connect to an IPv6 enabled server but I could not see any servers listed in the Connect dialog for any genre, nor could I direct connect to a server via IPv4.
It appears connectivity is IPv6-only when using
-6option.Running jamulus without
-6option re-enables IPv4 connectivity for directory server listings for each genre, and direct IPv4 connectivity to servers.I'm starting jamulus from iTerm2 using this commandline:
/Applications/Jamulus.app/Contents/MacOS/Jamulus -6Under Linux, using
-6option does not disable IPv4 connectivity.Beta Was this translation helpful? Give feedback.
All reactions