Short answer; no.
To add to what's already been said, the zero has only one port. It has two connectors but only one of those has the data lines.
That's a good idea. So the configuration it would be like this:hippy wrote: ↑Tue Mar 26, 2019 9:54 amShort answer; no.
But you could use a Zero as an OTG gadget and another Pi as a USB host and link the two through GPIO UART using PPP or some other means.
Not necessarily true.
thagrol wrote: ↑Sat May 18, 2019 3:42 pmNot necessarily true.
If the slave Pi are zero/zeroW/A/A+ running as ethernet gadgets (or as serial gadgets witth PPP/SLIP) you can ru a software bridge on the host Pi and add all the slave Pi to that.
Of course, the more slave Pi you have the less bandwidth available to each but that will apply however they're connected.
For some values of "better" perhaps. And that wasn't my point, I was clarifying your misleading statement that " the slaves can't talk to each other"
You say it's misleading, but your answer is not that slaves can talk to each other but that they have to communicate via a host, which confirms my point. That difference may or may not be important in some use cases, but the term "mesh" is inconsistent with USB topology. So I think your statement is the misleading one.thagrol wrote: ↑Sun May 19, 2019 10:14 amFor some values of "better" perhaps. And that wasn't my point, I was clarifying your misleading statement that " the slaves can't talk to each other"
What you propose lacks the central features of a mesh network.A mesh network is a network in which the devices -- or nodes -- are connected so that at least some, and sometimes all, have multiple paths to other nodes. This creates multiple routes for information between pairs of users, increasing the resilience of the network in case of a failure of a node or connection. In a full mesh topology, each network node is connected directly to each of the others.
https://internetofthingsagenda.techtarg ... sh-network
Then is what sense is that a mesh network?
LAN or WLAN allows for multiple reduncant connections, USB does not. There are other options of course, amany of which might use a USB connected interface.treefella wrote: I'm thinking of creating a device with the Compute Module and using the USB as a way to bridge a network connection between multiple Pis in a sort of mesh network.
lepass7 wrote: ↑Tue Mar 26, 2019 5:14 amHi guys,
I was wondering if it's possible to use one port of my raspberry pi as slave usb (otg mode) and the other port as master.
For example let's say on one port I will connect a USB keyboard (RPI as master) and on the other port I will connect my RPI to my pc (otg).
I would like to manipulate the input from the user that is coming from the keyboard and then send it to my pc.
I know it's possible to do this directly on my pc, but I would like to prepare this configuration just for research.
The configuration it should be like this:
I did my research and I have found that RPI zero can be set up as slave device but I am not sure if this configuration could only be just for one port.
I am looking forward to read your opinion on this.
As You read it that way I'll accept I could have been clearer, but of course, if any slave can communicate with the host and the host can communicate with any slave then any slave can get the host to relay a message to any other slave. It's just not a mesh network.thagrol wrote: ↑Sun May 19, 2019 11:39 am
I found you statement " If you connect many RPi slaves to a host RPi through USB hubs the slaves can't talk to each other, only to the host." to be inaccurate (and therefore misleading) as it gave the impression that slaves connected via USB ethernet gadget can communicate only with the host and never with other devices. It implied that routing and bridging on the USB host could not be used.
Ethernet emerged from ARPANET that was designed for multiple redundancy. It is a highly redundant network that transparently routes messages over available connections.
Ethernet LANs or WiFi WLANs are examples of the first and USB is an example of the second.A mesh network (or simply meshnet) is a local network topology in which the infrastructure nodes (i.e. bridges, switches and other infrastructure devices) connect directly, dynamically and non-hierarchically to as many other nodes as possible and cooperate with one another to efficiently route data from/to clients. This lack of dependency on one node allows for every node to participate in the relay of information. Mesh networks dynamically self-organize and self-configure, which can reduce installation overhead. The ability to self-configure enables dynamic distribution of workloads, particularly in the event that a few nodes should fail. This in turn contributes to fault-tolerance and reduced maintenance costs.
Mesh topology may be contrasted with conventional star/tree local network topologies in which the bridges/switches are directly linked to only a small subset of other bridges/switches, and the links between these infrastructure neighbours are hierarchical. While star-and-tree topologies are very well established, highly standardized and vendor-neutral, vendors of mesh network devices have not yet all agreed on common standards, and interoperability between devices from different vendors is not yet assured.
Of course that is possible, but "mesh network" was the term used and that was the basis of my reply and not the basis of yours so we gave different answers. Granted, if they didn't mean that then your answer is a good answer for getting USB devices to communicate over USB hierarchical topology.thagrol wrote: ↑Sun May 19, 2019 11:39 amAs for "What you propose lacks the central features of a mesh network.". Sure, but I'm not convinced that the person who asked the question fully understands what a mesh network is, as their question was somewhat vague: "bridge a network connection between multiple Pis in a sort of mesh network"
In contrast standard USB hubs can't be connected to provide automatic redundancy.If a hub fails every device connected downstream of it loses connectivity.Examples of network topologies are found in local area networks (LAN), a common computer network installation. Any given node in the LAN has one or more physical links to other devices in the network; graphically mapping these links results in a geometric shape that can be used to describe the physical topology of the network. A wide variety of physical topologies have been used in LANs, including ring, bus, mesh and star.
https://en.wikipedia.org/wiki/Network_t ... chnologies
I am trying to help folks by clearing up some incorrect information.PiGraham wrote: ↑Sun May 19, 2019 7:44 pm
You are obviously in a very argumentative mood. Aren't we all trying to help others?
Sure but that isn't what you suggested or what we were talking about (a bunch of Pi connected via USB to a server/host vs a bunch of Pi connected to a server/host via a single switch). Pi connected "to router by both WiFi and Ethernet" is not a mesh network. Please stop moving the goalposts.The hardware provides multiple redundant connections, if it is connected that way. You can have multiple switches and routers and the IP stack on top of that hardware can use those redundant connections to deliver data even if multiple switches, routers, servers or backbones fail. IP can't do better than the hardware is capable of. If you run a bridge on your one USB host IP has no way to route round faults. Ethernet hardware can be connected as a mesh rather than a star / tree.
You can connect a RPi to router by both WiFi and Ethernet so that if one interface fails the other still works. You can connect WiFi to a router and Ethernet to a separate Ethernet switch.
I'm not entirely sure how that's relevant. And again, if every node does not have a physical connection (I include point to point WiFi as a physical connection but not WiFi via an AP) to every other node it's not a full/true mesh network.Examples of network topologies are found in local area networks (LAN), a common computer network installation. Any given node in the LAN has one or more physical links to other devices in the network; graphically mapping these links results in a geometric shape that can be used to describe the physical topology of the network. A wide variety of physical topologies have been used in LANs, including ring, bus, mesh and star.
https://en.wikipedia.org/wiki/Network_t ... chnologies
Same thing with an ethernet switch. Especially an unmanaged one.In contrast standard USB hubs can't be connected to provide automatic redundancy.If a hub fails every device connected downstream of it loses connectivity.
Not gonna go there
Firstly, I would advise against using a daisy chain approach. For two main reasons (using A - B - C - D as an example config):Some details on my use case:
I was wondering if it is possible to just have 2 USB ports on each pi in a system (lets say 2-4 devices) and send around these NDI packets over a network connection. I have this working with ethernet on a switch on my PI3s and it works well. However the LAN controller takes a bunch of current and when I found out its implemented through the USB channels anyway I figured there must be some way to just pass the network along via USB.
So my question is:
Hardware wise, how do I have 2 devices connected to a given pi, sharing a network and passing it along a larger chain of pis? Is it possible to have this be "effectively" de-centralized as far as the end user is concerned?
Two devices? Is that all you need, one host and two slaves?