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 10:54:22 +0000 [thread overview]
Message-ID: <87y3nixstd.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <efdd1725-f2c0-e3aa-0e6f-871106ad3d2e@siemens.com> (Daniel Wagner's message of "Tue, 7 Nov 2017 09:47:58 +0100")
Daniel,
Daniel Wagner <daniel.wagner@siemens.com> writes:
> Hi Daniel,
>
> On 11/07/2017 03:40 AM, Daniel Sangorrin wrote:
>>> So my question is, couldn't we add additional network interface, e.g.
>>> USB Ethernet adapter, and attach the device under test to this
>>> interface? I don't know if Vagrant is offering such an option. In the
>>> past I've done this with Qemu.
>>
>> If your network is using the MAC address for authentication you could also
>> put the MAC address of your USB ethernet adapter into the Virtualbox
>> ethernet interface (adapter 2).
>
> Unfortunately, we do have proper security in place :) The device needs
> to do EAP and I don't think u-boot is able to this.
>
> Having a dedicated network interface (maybe attached to a standalone
> switch) has also the beauty that you have it complete under control what
> is happening on the test network.
>
We've opened a ticket for this
https://gitlab.com/cip-project/cip-testing/testing/issues/169
so that we can investigate and you can keep track!
Robert
next prev parent reply other threads:[~2017-11-07 10:54 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 [this message]
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
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=87y3nixstd.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.