lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHvy4AqRbsjvU4mtRXHuu6dvPCgGfvZUUiDc3OPbk_PtdNBpPg@mail.gmail.com>
Date: Mon, 19 Aug 2024 16:20:31 +0200
From: Pieter <vtpieter@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, Woojung Huh <woojung.huh@...rochip.com>, 
	UNGLinuxDriver@...rochip.com, Florian Fainelli <f.fainelli@...il.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

Hi Vladimir,

> 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?

Assuming this works, how to tell all user space programs to use br0 instead
of eth0? Both interfaces are up and I can't do `ifdown eth0` without losing
all connectivity. I'm using busybox's ifup BTW and it says:
$ ifup br0
ifup: ignoring unknown interface br0

Thanks, Pieter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ