Confirm BETA1 for AMD HP Microserver N54L, iocage jails networking not ideal

[diskdiddler]

Figured I'd be the guinea pig.
As per all updates, I've noticed, BE PATIENT, just update and wait wait wait wait as long as you can, it will eventually come back.


As for BETA1, 2 issues so far.
1, I have a jail with autostart ticked. I choose to stop the jail, it continues to start itself over and over. (stop via CLI or GUI) - bug has been reported.
2, a little worse, also seen in U5, many others may have this?
Networking for iocage jails just outright, randomly broken. Wouldn't have thought much of it but they did work for 4 days, now they simply don't work, can't ping the host from within the jail, or vice versa, was working fine, unsure how the heck this occurred.
Rebooted U5, didn't fix, updated to BETA1, didn't fix - all 3 jails, just out of the blue. Luckily not too important right now, but a bit of a shame. Probably an easy fix - but be wary.
(Anyone else seen this?)

 

[diskdiddler]

I have now bit the bullet, switched to BETA1, this has not fixed the problem, obviously a reboot has occurred and I've even created a brand new jail from scratch, continues to be an issue.

Code:

root@freenas:~ # iocage create -n "testfixedip" -r 11.1-RELEASE ip4_addr="vnet0|192.168.0.180/24" vnet="on" allow_raw_sockets="1" defaultrouter="192.168.0.254" boot="on"
testfixedip successfully created!
* Starting testfixedip
  + Started OK
  + Configuring VNET OK
  + Starting services OK
root@freenas:~ # iocage list
+-----+-------------+-------+--------------+---------------+
| JID |	NAME	 | STATE |   RELEASE	|	  IP4	  |
+=====+=============+=======+==============+===============+
| 2   | jackett	 | up	| 11.1-RELEASE | 192.168.0.199 |
+-----+-------------+-------+--------------+---------------+
| 3   | qbittorrent | up	| 11.1-RELEASE | 192.168.0.197 |
+-----+-------------+-------+--------------+---------------+
| 1   | radarr	  | up	| 11.1-RELEASE | 192.168.0.198 |
+-----+-------------+-------+--------------+---------------+
| 7   | test		| up	| 11.1-RELEASE | DHCP		  |
+-----+-------------+-------+--------------+---------------+
| 9   | testfixedip | up	| 11.1-RELEASE | 192.168.0.180 |
+-----+-------------+-------+--------------+---------------+
root@freenas:~ # ping 192.168.0.180
PING 192.168.0.180 (192.168.0.180): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 192.168.0.180 ping statistics ---
11 packets transmitted, 0 packets received, 100.0% packet loss
root@freenas:~ #

 

[diskdiddler]

I have fixed this problem with the tunables command listed in other posts. I'm kind of shocked they shipped BETA1 with this known bug in it.
(For a change, this wasn't my fault)

Information here:
https://forums.freenas.org/index.php?threads/iocage-vnet0-and-bridge0.59964/#post-425631

Variable : cloned_interfaces ; Value : bridge0
Variable : ifconfig_bridge0 ; Value : addm igb0 up
Type rc.conf

In my case, the adapter name was bge0 NOT igb0.

 

[KrisBee]

I'm kind of shocked they shipped BETA1 with this known bug in it.

No surprise, considering recent track record. I expected BETA1 to be buggy and it is. VMs not looking too good either.