[Bug] virtual part in local.conf not work?

[Catofes]

My zerotier version is 1.2.4 and I found that after I set virtual part in local.json like the manual said, the blacklist didn't work. Here is more info.

Node f79b86d760:

1. local.conf

 SSH:  xxx@ubuntu /v/l/zerotier-one  $ cat /var/lib//zerotier-one/local.json 
{
	"virtual": {
        	"7a23a23ff4": {
                	"try": ["2001:xxxx:xxxx:xxxx:0000:0000:0000:103/9993"],
			"blacklist": ["2xx.xx.47.0/24"]
        	}
	}
} 

2. zerotier-cli info -j

 SSH:  xxx@ubuntu /v/l/zerotier-one  $ sudo zerotier-cli info -j
{
 "address": "f79b86d760",
 "clock": 1506608090997,
 "cluster": null,
 "config": {
  "physical": null,
  "settings": {
   "portMappingEnabled": true,
   "primaryPort": 9993,
   "softwareUpdate": "disable",
   "softwareUpdateChannel": "release"
  }
 },
 "online": true,
 "planetWorldId": 149604618,
 "planetWorldTimestamp": 1452708876314,
 "publicIdentity": "f79b86d760:0:800b98b9581c7cab9cc83bdb3c9eea24a1c315241c3b55f93af2c5e4e2794d06a76a1c911386954a36da04167c0f8b3d36d1b7036efa92df28912784b0850f7b",
 "tcpFallbackActive": false,
 "version": "1.2.4",
 "versionBuild": 0,
 "versionMajor": 1,
 "versionMinor": 2,
 "versionRev": 4
}

3. zerotier-cli listpeers -j

 SSH:  xxx@ubuntu /v/l/zerotier-one  $ sudo zerotier-cli listpeers -j | grep 7a23 -A 20 -B 1
 {
  "address": "7a23a23ff4",
  "latency": 257,
  "paths": [
   {
    "active": true,
    "address": "2xx.xxx.47.196/31265",
    "expired": false,
    "lastReceive": 1506608505419,
    "lastSend": 1506608505419,
    "linkQuality": 0.976470588235294,
    "preferred": true,
    "trustedPathId": 0
   }
  ],
  "role": "LEAF",
  "version": "1.2.4",
  "versionMajor": 1,
  "versionMinor": 2,
  "versionRev": 4
 },
 {

I'm sorry that I hide the exactly address for privacy, but I'm sure the path's address fall in the blacklist.

By the way, can Zerotier support a function that Prefer a path which means after manual set a path in local.conf that path will always be perfered unless it's unreachable. Thank you

[joseph-henry]

Looks like it was a copy and paste error in the config file loading code. I've issued a patch on dev, go give it a shot.