Web GUI not accessible when miniDLNA jail started

[bppeters]

Summary: When I start the miniDLNA jail on FreeNAS, the web GUI becomes inaccessible and I have to reboot the system to regain access to the web GUI. I feel like I'm missing something basic here like that I'm not supposed to be configuring the jails network to be on the main network, idk.

Repro Steps:
1. Log in to FreeNas
2. Click on "jails"
3. Click on miniDLNA jail that was created when the plugin was installed

Expected Behaviour: miniDLNA jail will start, plugin will be available and WebGUI will remain stable
Actual Behaviour: miniDLNA jail starts, webGUI becomes inaccessible within 2 minutes

Configuration Information:
BuildFreeNAS-9.2.1.5-RELEASE-x64 (80c1d35)
PlatformIntel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz
Memory16300MB

Jails (global) Network Configuration:
ipv4 network: 192.168.99.204 // (note: this is the same as my home network)
ipv4 net start address: 192.168.99.201
ipv4 net end address : 192.168.99.215

miniDLNA Jail Network Configuration:
ipv4 address: 192.168.99.205
ipv4 netmask: /24
ipv4 default gateway 192.168.99.1
vimage: [x] (is checked)

NOTE: My network has DHCP on 192.168.99.0/24

Other Notes:
I've tried modifying almost all of the settings, I can get the Jail to come online, the plugin to appear and to still have the web GUI accessible with the following settings:
ipv4 addr: 192.168.99.205
ipv4 netmask : /24
ipv4 bridge netmask: /24
ipv4 bridge alias: 192.168.99.8
ipv4 default gateway: 192.168.99.1

With these settings I experience another issue:

Step 1: start miniDLNA jail
Step 2: wait less than 2 minutes

Expected behaviour: everything will be up and online in the web GUI
Actual behaviour: "You must configure a default route (Network->IPv4 Default Gateway) "
This shows on the following screens:
"Jails", "Plugins"

 

[Yatti420]

You mean the actual freenas webgui becomes inaccessible? Is minidlna running when after the GUI becomes inaccessible? if you access the minidlna jail then watch the log aswell.. Did you upgrade freenas or is this a clean setup? Maybe just remove minidlna/jail and restart.. Reinstall..

 

[bppeters]

Thanks for the reply!

• Yes, the freenas gui (192.168.99.8) becomes inaccessible
• When the GUI becomes inaccessible, the freeNAS box / ip for the GUI (99.8) cannot be pinged
• Where is the minidlna jail log? where does it persist / how do I read it?
• This is a clean setup of FreeNAS
• How do I remove jails - there isn't an option in the "jails" configuration screen...?
  • I only have "edit jail", "add storage" and "start" when i select the minidlna_1 jail

For scenario 2 I'm adding the ifconfig output when I'm getting the default gateway error:
igb0:

flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO> ether d0:50:99:1a:06:d1 inet 192.168.99.8 netmask 0xffffff00 broadcast 192.168.99.255 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect (1000baseT <full-duplex>) status: active ​

igb1:

flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO> ether d0:50:99:1a:06:d2 nd6 options=9<PERFORMNUD,IFDISABLED> media: Ethernet autoselect status: no carrier ​

ipfw0:

flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536 nd6 options=9<PERFORMNUD,IFDISABLED>​

lo0:

flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> ​

bridge0:

flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 02:fe:4a:c8:9c:00 inet 192.168.99.8 netmask 0xffffff00 broadcast 192.168.99.255 nd6 options=1<PERFORMNUD> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member:epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 8 priority 128 path cost 2000 member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 2 priority 128 path cost 20000 ​

epair0a:

flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether 02:c4:1c:00:08:0a nd6 options=1<PERFORMNUD> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active​

 

[bppeters]

Other notes:
When I go into the Settings --> General (after starting the jail)

• The webGUI ipv4 address says "0.0.0.0"
• on the drop-down menu I can see two options "0.0.0.0" and "192.168.99.8"
• when I select the .99.8 I get the following message:
  • " Select a valid choice. 192.168.99.8 is not one of the available choices."
• after I do this - if I browse away from the "General" tab and go back, the .99.8 will no long show up in the list of webGUI ipv4 addresses (drop-down)

 

[solarisguy]

I do not know the cause of your problems, I am guessing something about network/DHCP. However, given your latest error, please try
* delete the plugin
* make sure that you have a working GUI and the IP address of the GUI (one selectable in General tab) is operational; try clean install if unable to get control
* before installing a plugin, go to Jails → Configuration
modify
→ IPv4 Network Start Address, and
→ IPv4 Network End Address
in such a way, that the range of possible addresses the plugin would accept is for sure not allocated to any network device and (of course) within your DHCP server range

And only now try to install the plugin.

P.S. Upon reading just your summary, I was guessing that you have too many of audio/video files for your grossly underpowered CPU. However, your Xeon is perfectly fine :)

 

[bppeters]

Thanks a lot for the response!

I believe that the cause of my problems has to do with DHCP and the bridge configuration.

• I cannot delete the plugin because I cannot delete the plugin while the jail isn't running and when it is running, I can't get to the plugins page
• The GUI is on a working IP address when I boot the system, it's only when I bring up the jail that the IP address / gateway stuff gets wonky
• the ipv4 start and end addresses are well outside of the range of anything else on the network

Will the "factory restore" option let me do a "clean install"? Will I lose my ZFS / storage configurations when I reinstall?
Thanks again for the help!

 

[solarisguy]

Read pages 126-127 about exporting ZFS volumes, and 109-111 about importing ZFS volumes, from
http://web.freenas.org/images/resources/freenas9.2.1/freenas9.2.1_guide.pdf

The above is about your data and ZFS pool(s). I would start with a new USB memory and clean re-installation, documenting step by step what you had done, especially with anything related to the network.

P.S. Check the logs on your DHCP server and double check your DHCP server reservation list. Using some other system, ping the IP addresses you think your FreeNAS and miniDLNA might obtain, while your FreeNAS system is down (you will take it down before re-installation...)

 

[bppeters]

Okay - so I went back to my default scenario and here's what I found:

1. I uninstalled and reinstalled the plugin - did not help - had the same behavior
2. I started the jail and then look at the ifconfig output from the console
   1. ibg0 doesn't have an ip address anymore
   2. there's no default route configured
3. when I do the following, everything is working:
   1. ifconfig igb0 "192.168.99.8 255.255.255.0"
   2. route add default 192.168.99.1
   3. (all of the screens work and the web interface is once again online)

I would really like to not have to re-install my entire setup, does anyone have ideas for how to fix the issue that's happening where my IP config and route information is disappearing?
Thanks!

 

[Yatti420]

Delete the minidnla setup and try again.. Do ou nwed the bridge I suspect it is this...

Sent from my SGH-I257M using Tapatalk 2

 

[Hyperion]

turn offDHCP

 

[bppeters]

I did delete the MiniDLNA setup and try again - it just demonstrates the same behavior. The bridge settings are by-default with FreeNAS and I believe are how connections to the jails themselves are handled.

Hyperion - it would be helpful if you could please clarify and help me understand what DHCP would have to do with the issue here? The interface is not pulling any / the right information and there is a routing issue?

Thanks!

 

[joeschmuck]

It sounds like your DHCP is causing all the problems. The plugins use an incremental address based on the FreeNAS IP address and as far as I know the plugins could care less about if there is a DHCP conflict. In my opinion no one should leave their FreeNAS configured as DHCP as you are always asking for trouble. You should assign a static IP for your FreeNAS machine. This would keep everything the same and help you avoid conflicts. My advice is to change your DHCP server to only service a certain number of addresses and leave some room for static IPs, then assign FreeNAS a static IP and then remove and reinstall your plugins.

 

[bppeters]

Hi folks - again - I really appreciate the help here.

Maybe I haven't been clear about the setup that I have - the FreeNAS host 99.8 is on a static DHCP record (for its MAC address it will always pull the same IP). The DHCP server only addresses out 99.25-99.100 and so .100-.254 are not part of the DHCP block.

This means that the DLNA server never interacts with DHCP and that the address to the web gui is not dynamically assigned.

Thanks!

 

[joeschmuck]

So do you have any other statically assigned IPs, specifically directly after the FreeNAS IP?

After you have installed your plugin open up the GUI and click the Jails icon. This will list the IPs for your jails. Cut and paste that image for us. While doing that do you see an IP address conflict?

Now highlight (click on) the minidlna jail and at the bottom of the screen click the left icon for Edit Jail. Post that screen. You should have entered the IPv4 gateway address, if not you need to do that. It's part of the basic configuration, it's not automatic.

 

[GolDenis]

get it when trying to install MiniDLNA after update U6 ->U7

root@MiniDLNA:~ # pkg install minidlna
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly, please wait...
pkg: Error fetching http://pkg.FreeBSD.org/FreeBSD:11:amd64/quarterly/Latest/pkg.txz: Non-recoverable resolver failure
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

OS Version:
FreeNAS-11.2-U7

will appreciate any suggestions

 

[sretalla]

Is the jail using VNET?

 

[GolDenis]

Yeap...

 

[Fredda]

Unfortunately you cut away the default router setting in your screenshot ...

 

[sretalla]

I have seen many folks having big problems when assigning static IP addresses in iocage jails on the current versions.

Can you use DHCP. I reserve my jails IP addresses by MAC address and have no issues.

 

[GolDenis]

guys! You are a genius...
Change to DHCP & I'm in!
thanks a lot!