On Sun 30 Mar 2025 at 15:40:07 (+0200), Hans wrote: > > What new hop? You said you had the setup: > > > > hostA≡E----------cat5/6--cable----------∃≡hostB > > no, I have no cable setup, I just said, I know, how to setup when using a > cable. Maybe I did not use the correct English idiom...
Yes, I obviously misunderstood your statement "it is working with ethernet cable and crossover-cable." > > Assuming that hostA can configure its wifi as an access point, > > then you replace the cable with: > > > > hostAP≡∈ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ∋≡hostB > > That is, what I wanted to do. > Then use NGINX with RTMP-module listening on its standard port and streaming > with RTMP from Computer A to Computer B to the standard port. > > Everything without any AP or router between. > > The stream can then be made visible with VLC or OBS on Computer B. > > That is the plan, and as litle as possible between the two computers. > > If you can do it via ad-hoc networking, that's fine by me. > > The benefit of the method above is that you only have to > > reconfigure one host, A, and leave B untouched: B knows how > > to connect to an AP, so you can focus all your attention > > on getting hostA to work, and test it with any normal wifi > > device that happens to be on hand. > > I do not know, if that is possible with wlan at all. However, it looks like I > am always have to use an AP on one of the computers (as other users told). I didn't say you couldn't do it with ad-hoc networking—I just said that I couldn't see any benefit because, as I see it, you effectively have a base station in hostA. (I'm obviously guessing that hostB might be the drone.) So you configure hostB to find and connect to a fixed AP, just as most hosts do in a home network: in this case, it's hostA rather than a router. And hostA just waits for hostB to connect to it. > I intend to build a full preconfigurated livefile system based on debian, so > that people with Windows-computers can boot it in the fields and can use it. > > But - this will be a long way. Cheers, David.