Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: Linux Distributed Switch Architecture with Local Option82
ISC DHCP server/DHCP relay (Simon Hobson)
2. Re: Linux Distributed Switch Architecture with Local Option82
ISC DHCP server/DHCP relay (Simon Hobson)
----------------------------------------------------------------------
Message: 1
Date: Tue, 10 Nov 2020 15:03:58 +0000
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Linux Distributed Switch Architecture with Local Option82
ISC DHCP server/DHCP relay
Message-ID: <6943bb91-7de4-4fb6-b89b-ece758790...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii
I wrote:
> Performance wise it would be best to use the hardware bridge as a single
> interface IFF you can access port status and attached devices list/port
> (MAC-Port mappings).
Thinking a bit more about this, the switch (bridge) ship can't be completely
"dumb". There's obviously a way to configure VLANs on it, so it would be worth
investing a bit of effort to find out if that same interface also supports
reading port status and forwarding tables - it could remove the need to run a
software bridge altogether.
Simon
------------------------------
Message: 2
Date: Tue, 10 Nov 2020 16:10:18 +0000
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Linux Distributed Switch Architecture with Local Option82
ISC DHCP server/DHCP relay
Message-ID: <9883446a-425c-4af7-be43-e7e2619b6...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii
Well, as they say, every day is a learning day. I'd not come across Distributed
Switch Architecture (DSA) before - now I've read up on it, interesting.
https://docplayer.net/50750816-Distributed-switch-architecture-a-k-a-dsa.html
As a refinement to the monitoring suggestion I made earlier, there's scope for
switching ports between modes.
So when a port becomes inactive, switch it from packet switching within the
bridge to forwarding packets direct to the processor. This will mean that when
something is plugged in, the Linux network stack will be able to see the
association between MAC address and port. Once that's been collected, the port
can be switched back to using the in-chip switch and (potentially) offload from
the processor.
I say potentially because the actual traffic flows haven't really been
described by the OP. If the application basically takes streams from cameras,
pipes them through the host processor and stores them on local storage - then
it makes little difference.
But if there are streams between devices, using the in-chip switch would
offload the handling of this from the host CPU.
As an alternative, there's scope for switching an inactive port to a different
VLAN to make it appear on a different Linux network port. Then when the MAC
address has been captured, change the port back to the normal VLAN.
Simon
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 145, Issue 6
******************************************
