Does not workNo setup just install it and you should be good to go.
No setup just install it and you should be good to go.
make distclean install -C /usr/ports/net/pecl-smbclient
ping 8.8.8.8
No worries, helping others helps me understand this stuff a lot more! Especially if I need to recreate it.
Go into your jail and run ifconfig and make sure it has the proper IP and also try to ping google and something on your internal LAN. This is to try and to see if you have connectivity issues.
Code:ping 8.8.8.8
If you have no issues then try service apache24 start
For smbclient for others, for future reference install this :
pkg install phpXX-pecl-smbclient
Replace XX with your php version.
root@nextcloud:/ # 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:ba:b5:82 hwaddr 02:53:e0:00:05:0b inet 192.168.1.27 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=1<PERFORMNUD> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active groups: epair root@nextcloud:/ # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ^C --- 8.8.8.8 ping statistics --- 24 packets transmitted, 0 packets received, 100.0% packet loss
??Ok, something strange here, (all the tests inside the jail) outside the jail ping works.
Code:root@nextcloud:/ # 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:ba:b5:82 hwaddr 02:53:e0:00:05:0b inet 192.168.1.27 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=1<PERFORMNUD> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active groups: epair root@nextcloud:/ # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ping: sendto: No route to host ^C --- 8.8.8.8 ping statistics --- 24 packets transmitted, 0 packets received, 100.0% packet loss
/usr/local/etc/apache24/httpd.conf, not /etc/make.conf. But putting "DEFAULT_VERSIONS+=php7.0" as the second line in that file (also weird - there's a giant block comment at the start of that file) results in syntax error.
My question is: what is the deal with this step of the guide? What's it for? "
Everything was already marked and filled.Hmm thats happened to me before, if I restart the iocage jail the network breaks. The only way to fix it was to restart FreeNAS completely. Obviously thats super irritating, The permanent fix was to enable vnet.
Whats odd its that you got a ping of 56 bytes then 100% loss. Strange.
Got to you freenas IP /ui
From there you should see the NEW freenas ui. Go to jails and chnage the network of your jail to vnet, tick the enable vnet and make sure "allow raw sockets" is also ticked. Also in the default router setting, make sure thats filled in otherwise vnet won't work.(I read that somewhere) Then restart the freenas os. NOT just the jail, restart freenas completely.
It is in the range of DHCP router and it really is really weird everything worked perfectly until restarting the systemStrange.. Im really not sure then, sorry ..No idea why the network just decided to break. Maybe try changing the IP ? Is that IP outside your dhcp range of your router ?
It is in the range of DHCP router and it really is really weird everything worked perfectly until restarting the system
Strange I have two more jail and everyone in the DHCP router I tried to add this MAC address but eventually it's IP of the FreeNAS and it's already there so it does not let you add two from the same MAC address but I do not have IP on the network that crashes even I did REST to Router and also hooked up Just system and still not working so I do not think this is the problemIt should NOT be in the DHCP range of your router. When we created the jail we assigned the IP NOT your router. So either create a static link with the mac address on your router or change the IP to something outside your dhcp server.
I'm afraid I'll have to reinstall all the jail and it's going to be a nightmare and I'll reinstall it It might be back after restart / power off Then what I will do is a problem I need to find what caused itIt should NOT be in the DHCP range of your router. When we created the jail we assigned the IP NOT your router. So either create a static link with the mac address on your router or change the IP to something outside your dhcp server.
It should NOT be in the DHCP range of your router. When we created the jail we assigned the IP NOT your router. So either create a static link with the mac address on your router or change the IP to something outside your dhcp server.
Strange I have two more jail and everyone in the DHCP router I tried to add this MAC address but eventually it's IP of the FreeNAS and it's already there so it does not let you add two from the same MAC address but I do not have IP on the network that crashes even I did REST to Router and also hooked up Just system and still not working so I do not think this is the problem
So you have an idea what I'm doing from here?I'm afraid I'll have to reinstall all the jail and it's going to be a nightmare and I'll reinstall it It might be back after restart / power off Then what I will do is a problem I need to find what caused it
Ok thanks for everything I'll let you know if I've found a solutionSorry, I don't know...
@sretalla Help me fix the problem just need to type the commandSorry, I don't know...
ifconfig bridge0 addm em0 up