marklnz
Cadet
- Joined
- Oct 21, 2012
- Messages
- 3
Righto, I've followed this guide to get the MiniDLNA plugin installed - which seems to have gone fine.
However when I try to start the plugins service I simply get "The service could not be started"
On the console I get three new lines of text:
"bridge0: Ethernet address: 16:46:ce:64:30:1b
epair0a: Ethernet Address: 02:80:c4:00:04:0a
epair0b: Ethernet Address: 02:80:c4:00:05:0b"
Each time I try to start the plugin service bridge & epair#a/b increments by one (bridge1, epair1a, ab, etc)
None of these MAC addresses matches the physical MAC address - though I see these appear when I do an ifconfig (virtual adapters I'm guessing?)
Are there logs I can check to see why the plugin service failed to start?
I am running FreeNAS-8.2.0-RELEASE-p1-x86 (r11950), booting FreeNAS off a USB key, but storing both the jail and archive path's on the internal SATA HDD. (/mnt/muckabout/jail and /mnt/muckabout/software)
I have searched the forums, came up with a couple of threads, but neither seemed to be related to what I'm experiencing (and neither had any mention of logs to check to see what's wrong)
Thanks for any help you can provide!
However when I try to start the plugins service I simply get "The service could not be started"
On the console I get three new lines of text:
"bridge0: Ethernet address: 16:46:ce:64:30:1b
epair0a: Ethernet Address: 02:80:c4:00:04:0a
epair0b: Ethernet Address: 02:80:c4:00:05:0b"
Each time I try to start the plugin service bridge & epair#a/b increments by one (bridge1, epair1a, ab, etc)
None of these MAC addresses matches the physical MAC address - though I see these appear when I do an ifconfig (virtual adapters I'm guessing?)
Are there logs I can check to see why the plugin service failed to start?
I am running FreeNAS-8.2.0-RELEASE-p1-x86 (r11950), booting FreeNAS off a USB key, but storing both the jail and archive path's on the internal SATA HDD. (/mnt/muckabout/jail and /mnt/muckabout/software)
I have searched the forums, came up with a couple of threads, but neither seemed to be related to what I'm experiencing (and neither had any mention of logs to check to see what's wrong)
Thanks for any help you can provide!