Plugin install difficulty: "You must configure your network..."

[Antioch18]

I recently upgraded my 8.3.0 system to 9.1. All seems to have gone well: my ZFS pools are all intact, my user/groups still work, etc.

Next I went about trying to get the Jail working again. I realize that the old 8.x plugins won't work and that I'll need to re-install, so I decided to wipe my old jail (I only had 1 plugin with no settings to backup) and make a 9.x jail for the new plugins instead. I followed the docs and made a new jail, mounted some folders, and all seems to have gone well. I was also able to jexec into the jail without issue.

I then tried to install a plugin from the plugins menu (BitTorrent) but was told "You must configure your network interface and a default gateway". I've configured the jail with it's own static IP address, which I get a ping reply from - so the jail's network should be working.

What step have I missed? What do I need to do to get this working?

Thanks! :)

edit: when I made the jail mentioned above, it was automatically configured as type=standard. I then made another jail with type=plugins hoping that that would solve the issue, but it didn't. Trying to install plugins to the 2nd jail also fails with the same message.

 

[Antioch18]

More information:

Code:

netstat -rn
Routing tables
 
Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
0.0.0.0/8          link#13            U          0        0 epair0 =>
default            192.168.1.1        UGS        0      72    em0
127.0.0.1          link#11            UH          0    8018    lo0
192.168.1.0/24    link#5            U          0    1593    em0
192.168.1.194      link#5            UHS        0        0    lo0
 
Internet6:
Destination                      Gateway                      Flags      Netif Expire
::/96                            ::1                          UGRS        lo0
::1                              link#11                      UH          lo0
::ffff:0.0.0.0/96                ::1                          UGRS        lo0
fe80::/10                        ::1                          UGRS        lo0
fe80::%lo0/64                    link#11                      U          lo0
fe80::1%lo0                      link#11                      UHS        lo0
fe80::%epair0a/64                link#13                      U      epair0a
fe80::32:cdff:fe00:d0a%epair0a    link#13                      UHS        lo0
ff01::%lo0/32                    ::1                          U          lo0
ff01::%epair0a/32                fe80::32:cdff:fe00:d0a%epair0a U      epair0a
ff02::/16                        ::1                          UGRS        lo0
ff02::%lo0/32                    ::1                          U          lo0
 
ifconfig -a
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=42098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWTSO>
        ether 00:25:90:93:ea:90
        inet 192.168.1.194 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
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 0xb
        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:01:c8:3e:df:00
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        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 13 priority 128 path cost 2000
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:32:cd:00:0d:0a
        inet6 fe80::32:cdff:fe00:d0a%epair0a prefixlen 64 scopeid 0xd
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active

My jails config:
IPv4 Network 192.168.99.0/24
IPv4 Network Start Address 192.168.1.20
IPv4 Network End Address 192.168.1.25

I configured the start/end, but the IPV4 Network setting was auto configured and the documentation said it leave it as-is when in doubt.

The "plugins jail" settings:
Jail Name plugins
IPv4 address 192.168.1.20/24
IPv4 aliases
IPv4 bridge address
IPv4 bridge aliases
IPv4 default gateway 192.168.1.1

As mentioned before, I can ping 192.168.1.20 and get a reply - but the ifconfig shows that epair0a's ip is set to 0.0.0.0 so something must be wrong...

The GUI's network summary page shows this issue as well:
Name IPv4 Address
em0 192.168.1.194/24
epair0a 0.0.0.0/8
Nameserver 192.168.1.1
Default route 192.168.1.1

Thanks for your help!

 

[Antioch18]

I changed the Jail Config from IPv4 Network 192.168.99.0/24 to 192.168.1.0/24 and I was able to install a plugin without the network config error.

em0 still lists as 0.0.0.0/24 - but perhaps this is what it should be?

 

[Rob]

I had a similar issue when I upgrade from 8.3.2 to 9.1.1. I had to change my jail configuration to 192.168.0.0/24. This seems to have corrected my issue. I had to look at the results in the netstat -rn to get this correct value