On Sat 29 Mar 2025 at 16:37:39 (+0100), Hans wrote: > > You need to make one PC an access point. I think most guides are > > designed to then connect that AP to the rest of the network, so > > that the AP is useful to wifi-only devices, but you can just > > ignore that. > > > > Example at: > > > > http://souktha.github.io/misc/create-ap-linuxpc/ > > yes, I already am aware of this, but this I wanted to avoid. It will be then > again a new hop, which causes delay (and I suppose, a software router is > sklower than a hardware device).
What new hop? You said you had the setup: hostA≡E----------cat5/6--cable----------∃≡hostB where E and ∃ are ethernet sockets. (You don't normally need a crossover cable nowadays.) Assuming that hostA can configure its wifi as an access point, then you replace the cable with: hostAP≡∈ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ∋≡hostB where ∈ and ∋ are antennae, and hostB connects to the AP as it would to a router's AP. My point with respect to your OP was that the wifi link is not symmetrical: hostB doesn't need to be an AP. 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. Cheers, David.
