Configuring jails

[Cédric Maunoury]

Hi Brandon,

Maybe you can give a try to the « -c » option of pkg command to chroot during the upgrade... the network should not be an issue anymore.

It’s more a workaround...

Regards,

Cedric

Envoyé de mon iPhone

> Le 4 mai 2020 à 18:05, Brandon helsley <brandon.helsley at hotmail.com> a écrit :
> 
> Could you guys still help me. Updating pkg In a jail not working after resolve.conf has been copied and did ping too ip from ifconfig and the default gateway. I did ping inside the jail and it works.
> 
> Sent from Outlook Mobile<https://aka.ms/blhgte>
> 
> ________________________________
> From: owner-freebsd-jail at freebsd.org <owner-freebsd-jail at freebsd.org> on behalf of Brandon helsley <brandon.helsley at hotmail.com>
> Sent: Monday, May 4, 2020 8:11:51 AM
> To: D'Arcy Cain <darcy at druid.net>; freebsd-jail at freebsd.org <freebsd-jail at freebsd.org>
> Subject: Re: Configuring jails
> 
> You said" If so then ping it. If that works then try to ping something
> outside of your network. Try an IP address first and then try by name."
> 
> I found an ip address in ifconfig. Then I netstat -rn and ping default gateway
> Ping gives me
> 64 bytes from 192.168.0.1: icmp_seq=71 ttl=64 time=2.628 ms
> 
> What is an ip address or name I can ping? What does this mean? Thanks.
> 
> Sent from Outlook Mobile<https://aka.ms/blhgte>
> 
> ________________________________
> From: owner-freebsd-jail at freebsd.org <owner-freebsd-jail at freebsd.org> on behalf of D'Arcy Cain <darcy at druid.net>
> Sent: Monday, May 4, 2020, 5:28 AM
> To: freebsd-jail at freebsd.org
> Subject: Re: Configuring jails
> 
>> On 2020-05-03 19:42, Brandon helsley wrote:
>> Doesn't work. I'm trying to update packages to see if networkings up. There must be a usual solution right?
> 
> You are jumping too far ahead.  While being able to update packages
> would prove that networking was up, not working does not prove anything
> except that something is not working.
> 
> Your first step is to run "ifconfig".  Make sure that you have an IP
> address.  If you do then run "netstat -rn" to see if you have a default
> route.  If so then ping it.  If that works then try to ping something
> outside of your network.  Try an IP address first and then try by name.
> The next step would be to update packages but we already know that that
> doesn't work.
> 
> If you do the above then report back here when you get to the step that
> failed.  Then we can help you investigate that.
> 
> --
> D'Arcy J.M. Cain <darcy at druid.net>         |  Democracy is three wolves
> http://www.druid.net/darcy/                |  and a sheep voting on
> +1 416 788 2246     (DoD#0082)    (eNTP)   |  what's for dinner.
> IM: darcy at VybeNetworks.com, VoIP: sip:darcy at druid.net
> 
> 
> _______________________________________________
> freebsd-jail at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-jail
> To unsubscribe, send any mail to "freebsd-jail-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-jail at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-jail
> To unsubscribe, send any mail to "freebsd-jail-unsubscribe at freebsd.org"