On Sun, Jun 05, 2016 at 12:35:29PM -0700, Don Lewis wrote:
> On 4 Jun, To: mm...@nextbsd.org wrote:
> > On 4 Jun, Matthew Macy wrote:
> >>
> >>
> >>
> >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund
> >> wrote
> >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
On 4 Jun, To: mm...@nextbsd.org wrote:
> On 4 Jun, Matthew Macy wrote:
>>
>>
>>
>> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund
>> wrote
>> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
>> > > It looks like something changed in -CURRENT to break network
>>
On 5 Jun, Otacílio wrote:
> Em 04/06/2016 23:04, Randy Westlund escreveu:
>> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
>>> It looks like something changed in -CURRENT to break network
>>> connectivity to VirtualBox guests. This was last known to work with
>>> r299139 (May 6th) an
On 4 Jun, Matthew Macy wrote:
>
>
>
> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund
> wrote
> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
> > > It looks like something changed in -CURRENT to break network
> > > connectivity to VirtualBox guests. This was
Em 04/06/2016 23:04, Randy Westlund escreveu:
On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
It looks like something changed in -CURRENT to break network
connectivity to VirtualBox guests. This was last known to work with
r299139 (May 6th) and is definitely broken with r301229.
I'v
On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund
wrote
> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
> > It looks like something changed in -CURRENT to break network
> > connectivity to VirtualBox guests. This was last known to work with
> > r299139 (May 6th
On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote:
> It looks like something changed in -CURRENT to break network
> connectivity to VirtualBox guests. This was last known to work with
> r299139 (May 6th) and is definitely broken with r301229.
I've been having VirtualBox networking problem
On 4 Jun, Alan Somers wrote:
> On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote:
>> On 3 Jun, Don Lewis wrote:
>>> It looks like something changed in -CURRENT to break network
>>> connectivity to VirtualBox guests. This was last known to work with
>>> r299139 (May 6th) and is definitely broken w
On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis wrote:
> On 3 Jun, Don Lewis wrote:
>> It looks like something changed in -CURRENT to break network
>> connectivity to VirtualBox guests. This was last known to work with
>> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox
>> port
On 3 Jun, Don Lewis wrote:
> It looks like something changed in -CURRENT to break network
> connectivity to VirtualBox guests. This was last known to work with
> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox
> port revisions are:
> virtualbox-ose-4.3.38_1
>
It looks like something changed in -CURRENT to break network
connectivity to VirtualBox guests. This was last known to work with
r299139 (May 6th) and is definitely broken with r301229. The VirtualBox
port revisions are:
virtualbox-ose-4.3.38_1
virtualbox-ose-kmod-4.3.38
It looks
11 matches
Mail list logo