[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed05bbff-2f87-4196-8f76-38bd501c3a35@gmail.com>
Date: Mon, 19 Aug 2024 07:16:45 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Vladimir Oltean <olteanv@...il.com>, Pieter <vtpieter@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Woojung Huh <woojung.huh@...rochip.com>,
UNGLinuxDriver@...rochip.com, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Russell King <linux@...linux.org.uk>,
Pieter Van Trappen <pieter.van.trappen@...n.ch>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 2/2] net: dsa: microchip: add KSZ8
change_tag_protocol support
On 8/19/2024 7:05 AM, Vladimir Oltean wrote:
> On Mon, Aug 19, 2024 at 03:43:42PM +0200, Pieter wrote:
>> Right so I'm managing it but I don't care from which port the packets
>> originate, so I could disable the tagging in my case.
>>
>> My problem is that with tagging enabled, I cannot use the DSA conduit
>> interface as a regular one to open sockets etc.
>
> Open the socket on the bridge interface then?
+1
--
Florian
Powered by blists - more mailing lists