From: Szenci A. [senszey] <sen...@fr...> - 2004-10-04 07:43:06
|
thx for tha answer, we'll try it soon. we had a problem, and i dont know if this answer will solve it. so, A connected to B (the server), and they could ping each other. and then when C connected to B, A and B couldnt ping each other any more. just B and C saw each other. thx A. Tim írta: > On Sun, 03 Oct 2004 23:50:56 +0200 > "Szenci Andras [senszey]" <sen...@fr...> wrote: > > >>hello all, >> >>im sorry, but i didnt find a good manual, a sample for my problem. i >>want to make a virtual lan between 3 computers. each of them has cable >>connection, almost static ip, windows xp. we want to use the network for >>games. at first with tcp/ip protokoll, but we would be glad if it could >>work with ipx. >> >>we chossed a comp. from the 3, to be the server. call this comp. B.. we >>could join to B form A and C, but the one who has connected earier >>couldnt commuicate with B or C. C couldnt see A. >> >>i try to test with ping, but A never see C. >>so, can you tell me what should i set to make it work? >> >>A. > > > This may be what you're looking for: > > --client-to-client > Because the OpenVPN server mode handles multiple clients through > a single tun or tap interface, it is effectively a router. The > --client-to-client flag tells OpenVPN to internally route > client-to-client traffic rather than pushing all client-origi- > nating traffic to the TUN/TAP interface. > > When this option is used, each client will "see" the other > clients which are currently connected. Otherwise, each client > will only see the server. Don't use this option if you want to > firewall tunnel traffic using custom, per-client rules. > > |