diskdiddler
Wizard
- Joined
- Jul 9, 2014
- Messages
- 2,377
I had many issues with iocage initially, mostly my fault and VMWare.
However, my actual main server, using U5 and iocage CLI jails has definitely had a genuine bug occur to it which I don't know if I should be reporting?
(Networking for all 3 jails just "stopped" randomly, can shell into them, they can ping themselves, can't even ping the host)
Even a restart of the jail doesn't fix this.
I THINK the broadcast address has broken itself (I'm not a networking guru)
I assure you all, this was working for days, just randomly died.
So should I report it, or try BETA1 first?
However, my actual main server, using U5 and iocage CLI jails has definitely had a genuine bug occur to it which I don't know if I should be reporting?
(Networking for all 3 jails just "stopped" randomly, can shell into them, they can ping themselves, can't even ping the host)
Even a restart of the jail doesn't fix this.
I THINK the broadcast address has broken itself (I'm not a networking guru)
Code:
root@radarr:~ # ifconfig 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 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> groups: lo epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether 02:ff:60:c1:df:cb hwaddr 02:ed:e0:00:05:0b inet 192.168.0.198 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=1<PERFORMNUD> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active groups: epair root@radarr:~ #
I assure you all, this was working for days, just randomly died.
So should I report it, or try BETA1 first?