mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <simon.guinot@sequanux.org>, <amir.jer.levy@intel.com>
Cc: <gregkh@linuxfoundation.org>, <andreas.noever@gmail.com>,
	<bhelgaas@google.com>, <corbet@lwn.net>,
	<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<thunderbolt-linux@intel.com>, <mika.westerberg@intel.com>,
	<tomas.winkler@intel.com>, <xiong.y.zhang@intel.com>,
	<michael.jamet@intel.com>, <remi.rerolle@seagate.com>
Subject: RE: [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking
Date: Tue, 22 Nov 2016 17:36:15 +0000	[thread overview]
Message-ID: <f653e691805d41d190160409282ea450@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <20161122172828.GB31492@kw.sim.vm.gnt>

> Here are a couple of additional questions:
> 
> - When the network interface is created, there is no IP address
>   assigned (or negotiated ?) on the Linux side. But it is done on the
>   MacOS side. And in the Linux kernel logs I can also read the message:
>   "ready for ThunderboltIP negotiation". Is there something missing or
>   not working on the Linux side ? What is the correct way to configure
>   or negotiate the IP address. For my tests I did it manually...
> 
> - When the Linux machine is started with the Thunderbolt wire already
>   connected to a MacBook Pro, sometimes (but not every time) the
>   network interface is not created. The Thunderbolt wire needs to be
>   replugged.
> 
> FWIW you get my
> 
> Tested-by: Simon Guinot <simon.guinot@sequanux.org>
> 
> Simon

Simon,

Since I also performed testing on the previous patchset, I'll share what I did.

I configured Network Manager to use the TBT interface to share an internet
connection to another box.  This configures a static IP address on the local
Linux side and sets up routing.

Network manager remembers setup this in a configuration database.  
When the interface goes up it will then set up a DHCP server to hand
out an IP address to the other side.

  reply	other threads:[~2016-11-22 17:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 14:20 Amir Levy
2016-11-09 14:20 ` [PATCH v9 1/8] thunderbolt: Macro rename Amir Levy
2016-11-09 14:20 ` [PATCH v9 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-11-09 14:20 ` [PATCH v9 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-11-09 14:20 ` [PATCH v9 4/8] thunderbolt: Networking state machine Amir Levy
2016-11-09 14:20 ` [PATCH v9 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-11-09 14:20 ` [PATCH v9 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 7/8] thunderbolt: Networking doc Amir Levy
2016-11-09 16:00   ` Greg KH
2016-11-10 11:47     ` Levy, Amir (Jer)
2016-11-10 11:53       ` Greg KH
2016-11-10 14:24     ` Jonathan Corbet
2016-11-09 14:20 ` [PATCH v9 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-11-09 14:36 ` [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Simon Guinot
2016-11-09 15:42   ` Levy, Amir (Jer)
2016-11-15 10:59     ` Simon Guinot
2016-11-18  8:48       ` Levy, Amir (Jer)
2016-11-18 10:07         ` gregkh
2016-11-20  6:30           ` Levy, Amir (Jer)
2016-11-21 12:22             ` gregkh
2016-11-18 11:20         ` Simon Guinot
2016-11-22 17:28           ` Simon Guinot
2016-11-22 17:36             ` Mario.Limonciello [this message]
2016-11-24 20:35             ` Levy, Amir (Jer)
2016-11-09 16:02 ` Greg KH
2016-11-10 11:39   ` Levy, Amir (Jer)
2016-11-10 11:44     ` Greg KH
2016-11-10 11:48       ` Levy, Amir (Jer)

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=f653e691805d41d190160409282ea450@ausx13mpc120.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=amir.jer.levy@intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=remi.rerolle@seagate.com \
    --cc=simon.guinot@sequanux.org \
    --cc=thunderbolt-linux@intel.com \
    --cc=tomas.winkler@intel.com \
    --cc=xiong.y.zhang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®