Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
AlbumArtist and multiple tag values
28-06-2014, 18:22
Post: #11
RE: AlbumArtist and multiple tag values
(28-06-2014 17:34)simoncn Wrote:  Editing the configuration file isn't recommended. It is very easy to make a mistake (for example, by deleting lines that are needed).

The problem here is that I can only access the Qnap MinimServer is installed onto by VPN. The NAS itself acts as a VPN server using OpenVPN.
For a reason I am not aware of, Kinsky works on this VPN channel while minimwatch does not. I spent some hours on it. I do point it to the VPN addresses by using the "network" property, but it still cannot find the remote MinimServer installation. I'd love to use Minimwatch instead of vi.

Quote:Trying to do this using a text editor is not supported and is likely to cause problems and unexpected results.

I am aware of it, but right now it is the only option. The Qnap NAS is 500km away.

Quote:have you installed the latest update (update 31) on your QNAP? Without this, you will get the problem you have described.

What I did was download the latest version from minimserver.com and install it along with java8, as per your instructions. I thought it included the latest update, but apparently it did not. I'll look for a way to perform the update.
Thanks!

Bye,
Roberto
Find all posts by this user
Quote this message in a reply
28-06-2014, 20:39
Post: #12
RE: AlbumArtist and multiple tag values
(28-06-2014 18:22)rpatriarca Wrote:  The problem here is that I can only access the Qnap MinimServer is installed onto by VPN. The NAS itself acts as a VPN server using OpenVPN.
For a reason I am not aware of, Kinsky works on this VPN channel while minimwatch does not. I spent some hours on it. I do point it to the VPN addresses by using the "network" property, but it still cannot find the remote MinimServer installation. I'd love to use Minimwatch instead of vi.

What I did was download the latest version from minimserver.com and install it along with java8, as per your instructions. I thought it included the latest update, but apparently it did not. I'll look for a way to perform the update.
Thanks!

Bye,
Roberto

You will need to use MinimWatch to perform the update.

If Kinsky can discover the remote MinimServer, MinimWatch should be able to discover it as well. Perhaps you don't have the correct setting for the ohnet.subnet property of MinimWatch. What value are you using for this setting? Can you post the output from the Windows "ipconfig /all" command?
Find all posts by this user
Quote this message in a reply
28-06-2014, 23:16
Post: #13
RE: AlbumArtist and multiple tag values
(28-06-2014 20:39)simoncn Wrote:  You will need to use MinimWatch to perform the update.

If Kinsky can discover the remote MinimServer, MinimWatch should be able to discover it as well. Perhaps you don't have the correct setting for the ohnet.subnet property of MinimWatch. What value are you using for this setting? Can you post the output from the Windows "ipconfig /all" command?

Sure. Apparently, OpenVPN allocates a /30 subnet for my connection, and thus I set ohnet.subnet address in Minimwatch to 192.168.2.4, .6 being my pc's address.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Seppiapc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter OAS
Physical Address. . . . . . . . . : 00-FF-F7-12-DC-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b0e4:178b:355a:e7d2%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.252

Lease Obtained. . . . . . . . . . : sabato 28 giugno 2014 09:38:16
Lease Expires . . . . . . . . . . : domenica 28 giugno 2015 09:38:16
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.2.5
DHCPv6 IAID . . . . . . . . . . . : 436273143
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-F1-7F-C5-00-1F-C6-73-7F-E6
DNS Servers . . . . . . . . . . . : 62.101.93.101
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1F-C6-73-7F-E6
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4ccd:9169:2b1b:85cd%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.200
DHCPv6 IAID . . . . . . . . . . . : 301998022
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-F1-7F-C5-00-1F-C6-73-7F-E6
DNS Servers . . . . . . . . . . . : 85.37.17.16
85.38.28.68
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::dcc2:565b:2904:16fc%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.247.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 352342102
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-F1-7F-C5-00-1F-C6-73-7F-E6
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c476:4d7a:fdfb:4059%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.131.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 369119318
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-F1-7F-C5-00-1F-C6-73-7F-E6
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{B96A9189-86B9-4B38-88C7-CEB879A511D2}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{1B520662-0FFB-41DC-8E8A-F30E51DEC7C6}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{BE69BAD3-04E5-4A52-A0B1-FDACF5B8924F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{F712DCB8-361C-426E-8F4D-F010B59DD1F2}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


My routing table forwards the whole /24 subnet to the tunnel endpoint:

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.200 192.168.1.2 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.2 266
192.168.1.2 255.255.255.255 On-link 192.168.1.2 266
192.168.1.255 255.255.255.255 On-link 192.168.1.2 266
192.168.2.0 255.255.255.0 192.168.2.5 192.168.2.6 30


on the Qnap nas, OpenVPN allocates a point-to-point subnet:

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.2.1 P-t-P:192.168.2.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:12556 errors:0 dropped:0 overruns:0 frame:0
TX packets:24319 errors:0 dropped:25 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1122669 (1.0 MiB) TX bytes:14367404 (13.7 MiB)


and routing is set up accordingly:

# route
+ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
255.255.255.255 * 255.255.255.255 UH 0 0 0 eth0
192.168.2.2 * 255.255.255.255 UH 0 0 0 tun0
192.168.1.10 * 255.255.255.255 UH 0 0 0 eth0
192.168.2.0 192.168.2.2 255.255.255.0 UG 0 0 0 tun0


So basically everything should work fine. And I can indeed reach minimserver's http interface. But minimwatch simply doesn't like this network setup.
I even tried forwarding ports 9790 and 9791 over an ssh connection, but minimwatch ignores them, too.

I'll keep on trying, but any help is of course welcome.

Bye!

Roberto
Find all posts by this user
Quote this message in a reply
29-06-2014, 07:03 (This post was last modified: 29-06-2014 07:08 by simoncn.)
Post: #14
RE: AlbumArtist and multiple tag values
(28-06-2014 23:16)rpatriarca Wrote:  Sure. Apparently, OpenVPN allocates a /30 subnet for my connection, and thus I set ohnet.subnet address in Minimwatch to 192.168.2.4, .6 being my pc's address.

This looks like the correct setting. You can confirm that the subnet setting is active from the MinimWatch log, This should include a message

Using single subnet 192.168.2.4

Do you see this message in the log?

It's possible that MinimWatch is being blocked by the Windows firewall. As a test, please try disabling the firewall completely to see if this helps.

If this doesn't work, I will send you instructions for producing a low-level trace of the UPnP discovery messages sent and received by MinimWatch. There might be something about OpenVPN that is causing a problem with MinimWatch discovery.
Find all posts by this user
Quote this message in a reply
29-06-2014, 08:23
Post: #15
RE: AlbumArtist and multiple tag values
(29-06-2014 07:03)simoncn Wrote:  This looks like the correct setting. You can confirm that the subnet setting is active from the MinimWatch log, This should include a message

Using single subnet 192.168.2.4

Do you see this message in the log?

It's possible that MinimWatch is being blocked by the Windows firewall. As a test, please try disabling the firewall completely to see if this helps.

I do see the message. As per Windows firewall, I had the same thought while writing, and tried disabling it. Unfortunately without success.
Oddly enough, minimwatch seems also unable to detect the instance of minimserver running on the same PC (of course after changing the ohnet.subnet parameter). Unless it is an intentional behaviour, there is something wrong here.

I used Wireshark to sniff network traffic and see what is happening. For simplicity I used one of vmWare subnets where there is no traffic. I can see minimwatch query packets being sent to a multicast address:

1 0.000000000 192.168.131.1 239.255.255.250 SSDP 159 M-SEARCH * HTTP/1.1
2 0.000151000 192.168.131.1 239.255.255.250 SSDP 160 M-SEARCH * HTTP/1.1
3 0.000268000 192.168.131.1 239.255.255.250 SSDP 156 M-SEARCH * HTTP/1.1


but nothing replies to them.
I'll continue looking into this issue.
Bye,

Roberto
Find all posts by this user
Quote this message in a reply
29-06-2014, 10:58
Post: #16
RE: AlbumArtist and multiple tag values
Update: I managed to update Minim on the remote NAS by launching it manually via ssh and specifying the --set watch.view=console option. The console allowed me to perform the update as I'd have done from Minimwatch.

Still no clue as to why minimwatch cannnot find the remote server, though.

Anyway, the main issue is solved: update 31 fixed it all.

Thank you very much!!

Bye,
Roberto
Find all posts by this user
Quote this message in a reply
29-06-2014, 20:00
Post: #17
RE: AlbumArtist and multiple tag values
(29-06-2014 08:23)rpatriarca Wrote:  I do see the message. As per Windows firewall, I had the same thought while writing, and tried disabling it. Unfortunately without success.
Oddly enough, minimwatch seems also unable to detect the instance of minimserver running on the same PC (of course after changing the ohnet.subnet parameter). Unless it is an intentional behaviour, there is something wrong here.

This is intentional behaviour. It would be confusing to have both a MinimWatch icon and a MinimServer icon for the same local instance of MinimServer.

Quote:I used Wireshark to sniff network traffic and see what is happening. For simplicity I used one of vmWare subnets where there is no traffic. I can see minimwatch query packets being sent to a multicast address:

1 0.000000000 192.168.131.1 239.255.255.250 SSDP 159 M-SEARCH * HTTP/1.1
2 0.000151000 192.168.131.1 239.255.255.250 SSDP 160 M-SEARCH * HTTP/1.1
3 0.000268000 192.168.131.1 239.255.255.250 SSDP 156 M-SEARCH * HTTP/1.1


but nothing replies to them.

The source IP address should be 192.168.2.6, not 192.168.131.1. These packets are being sent by multicast to the 192.168.131.0 subnet and there are no UPnP devices on this subnet to respond to the packets.

If you set the ohnet.subnet property to 192.168.2.4 and restart MinimWatch, what do you see in Wireshark? Are any M-SEARCH packets sent from the 192.168.2.6 address? If so, are there any responses to these packets?
Find all posts by this user
Quote this message in a reply
29-06-2014, 20:06
Post: #18
RE: AlbumArtist and multiple tag values
(29-06-2014 10:58)rpatriarca Wrote:  Update: I managed to update Minim on the remote NAS by launching it manually via ssh and specifying the --set watch.view=console option. The console allowed me to perform the update as I'd have done from Minimwatch.

Still no clue as to why minimwatch cannnot find the remote server, though.

Anyway, the main issue is solved: update 31 fixed it all.

Thank you very much!!

Bye,
Roberto

This is a good solution. You can use the same approach to change configuration settings instead of editing the minimserver.config file. The only thing you can't do from the console interface is display the log.
Find all posts by this user
Quote this message in a reply
30-06-2014, 10:26
Post: #19
RE: AlbumArtist and multiple tag values
(29-06-2014 20:00)simoncn Wrote:  If you set the ohnet.subnet property to 192.168.2.4 and restart MinimWatch, what do you see in Wireshark? Are any M-SEARCH packets sent from the 192.168.2.6 address? If so, are there any responses to these packets?

It is one of the tests I did. I saw both M-SEARCH packets sent from 192.168.2.6 address, and announce (NOTIFY) packets sent by the remote Minimserver, 192.168.2.1. But somehow the two pieces of software didn't hear of each other.
My sensation is that it has more to do with OpenVPN than with minimserver/minimwatch, but of course I cannot be sure.

Anyway, my main issue is now solved. Thanks again!


Roberto
Find all posts by this user
Quote this message in a reply
30-06-2014, 16:43
Post: #20
RE: AlbumArtist and multiple tag values
(29-06-2014 10:58)rpatriarca Wrote:  Update: I managed to update Minim on the remote NAS by launching it manually via ssh and specifying the --set watch.view=console option. The console allowed me to perform the update as I'd have done from Minimwatch.

FYI, you shouldn't need to specify this option. If you're running MinimServer from SSH on a platform without a native desktop GUI, a console prompt will be shown automatically.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)