pkg and jail network [Version 9.10 Stable Official Release]

Status
Not open for further replies.

NASDenny

Cadet
Joined
May 31, 2016
Messages
7
Hello -
I'm new in using FreeNAS and I'm disappointed in using it because nothing work for me I'm expected for.

First - If I want to instsall pkg I get the following message:

  • Updating FreeBSD repository catalogue...
  • FreeBSD repository is up-to-date.
  • Updating local repository catalogue...
  • pkg: file:///usr/ports/packages/meta.txz: No such file or directory
  • repository local has no meta file, using default settings
  • pkg: file:///usr/ports/packages/packagesite.txz: No such file or directory

Second - If I create a jail I'am not able to connect to the internet it doesn't matter if I'm use DCHP or static

I hope someone can help me and exlpain me what I've forgott?

Thanks :)
 

pirateghost

Unintelligible Geek
Joined
Feb 29, 2012
Messages
4,219
Well for starters, you can't install things on the base OS. You need to use jails.

Without any valid information you can't be expected to receive help on a networking issue that we have no visibility on.

We need to understand what's not working and what you've actually tried. "It doesn't work" is a pretty bad generalization.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,466
I'am not able to connect to the internet it doesn't matter if I'm use DCHP or static
That's going to be a problem. To install a jail, your FreeNAS server will need Internet access. What happens from the shell if you type 'ping google.com'? What about 'ping 8.8.8.8'?
 

NASDenny

Cadet
Joined
May 31, 2016
Messages
7
Thanks for quick reply :)

I'm not working on the "BaseSystem" I've created a jail (virtualbox) if I open the shell from jail and do ping on such like google or DNS (8.8.8.8) I don't get any repsonse.

I only able ping my "BaseSystem".

My "BaseSystem" have an active internet connection an can ping google.de or 8.8.8.8 (sure because I've downloaded the VirtualBox).
 

Attachments

  • VMTEST.png
    VMTEST.png
    105.9 KB · Views: 257

NASDenny

Cadet
Joined
May 31, 2016
Messages
7
BaseSystem:
Code:
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=98<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
        ether 08:00:27:63:00:53
        inet 192.168.31.125 netmask 0xffffff00 broadcast 192.168.31.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
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 0x2
        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:90:be:4e:75:00
        nd6 options=9<PERFORMNUD,IFDISABLED>
        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: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 2000
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 4 priority 128 path cost 2000
        member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:20:00:04:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:20:00:05:0a
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active


Jail
Code:
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>
epair1b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:70:00:06:0b
        inet 192.168.31.201 netmask 0xffffff00 broadcast 192.168.31.255
        nd6 options=9<PERFORMNUD,IFDISABLED>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
 

Attachments

  • JailSettings.png
    JailSettings.png
    34.2 KB · Views: 264

pirateghost

Unintelligible Geek
Joined
Feb 29, 2012
Messages
4,219
What are your settings for the jails?

I feel like I am trying to pull teeth here.
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
Try unchecking the VIMAGE box and restart the jail. I had a similar issue testing 9.10 and this resolved the problem.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
ehh unchecking vimage isn't fixing the problem. Can you ping 192.168.31.1 when vimage is checked?
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Why? If I uncheck it all works fine for me... and I can't ping 192.168.31.1 if VIMAGE is checked...
Because when you unchecked it you lost the entire networking stack for that jail. It just changed how the jail works it doesn't fix the fact that you have a configuration or network problem. Who knows what else is broken or just works by accident. I tried to reproduce your problem and couldn't so I'm not even sure what is wrong.
 

mjk79

Explorer
Joined
Nov 4, 2014
Messages
67
Just to put it out there, I'm having the same issue, but unchecking VIMAGE fixed it.

root@TS3_Jail:/ # ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 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
^C
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
root@TS3_Jail:/ # ping 192.168.1.37
PING 192.168.1.37 (192.168.1.37): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
ping: sendto: No route to host
 
Status
Not open for further replies.
Top