All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D network setup
Date: Tue, 07 Nov 2017 14:19:52 +0000	[thread overview]
Message-ID: <87lgjixjav.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <f8f9a13d-9711-5601-1266-5637b1dcb0ec@siemens.com> (Daniel Wagner's message of "Tue, 7 Nov 2017 15:13:57 +0100")

Daniel Wagner <daniel.wagner@siemens.com> writes:

> On 11/07/2017 01:09 PM, Robert Marshall wrote:
>>> Robert, what is your take on this approach?
>>>
>> 
>> I think that first step sounds reasonable - all the network config IIRC
>> happens in the Vagrantfile apart from the suggested workthrough on the
>> wiki.
>
> When I tried to build my own VM from scratch I failed at the config part
> inside the VM. Though this is a while ago. Maybe I should just retry to
> build the VM, though I would prefer not to do it. I workaround could be
> to asign the VM my USB Ethernet interface... Need to check the docs :)
>

>From my experience with network issues at ELCE I'd be inclined to just
comment out the

  config.vm.network "public_network", use_dhcp_assigned_default_route: true

line. And the VM should build without problems, it only needs that line
for running a test on the beaglebone black

Robert

      reply	other threads:[~2017-11-07 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06  9:49 [cip-dev] B@D network setup Daniel Wagner
2017-11-07  2:40 ` Daniel Sangorrin
2017-11-07  8:47   ` Daniel Wagner
2017-11-07 10:54     ` Robert Marshall
2017-11-07 11:42       ` Daniel Wagner
2017-11-07 11:58     ` Agustin Benito Bethencourt
2017-11-07 12:09       ` Robert Marshall
2017-11-07 14:13         ` Daniel Wagner
2017-11-07 14:19           ` Robert Marshall [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgjixjav.fsf@ctlt579.codethink.co.uk \
    --to=robert.marshall@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.