On Tue, Aug 15, 2023 at 5:33 PM, Gert Doering<g...@greenie.muc.de> wrote:   Hi,

On Tue, Aug 15, 2023 at 12:54:45PM +0000, Jason Long via Openvpn-users wrote:
> I did a tcpdump:
> 
> # tcpdump --interface any udp port 2000 -n -v
> tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture 
> size 262144 bytes
> 08:50:47.761991 IP (tos 0x0, ttl 128, id 892, offset 0, flags [DF], proto UDP 
> (17), length 82)
>     192.168.1.21.60461 > 192.168.1.20.2000: UDP, length 54

Client is sending to ip A.

> 08:50:47.762524 IP (tos 0x0, ttl 64, id 24726, offset 0, flags [DF], proto 
> UDP (17), length 94)
>     10.10.0.1.2000 > 192.168.1.21.60461: UDP, length 66

... and server is replying from IP B.

Not sure how you ended there, but if you want the server on 10.10.0.1,
then the client needs to connect to *that* IP.

>(I said it before: if a machine has multiple IP >addresses and you use
>UDP, you *must* use --multihome on the server)

>gert
Hello,Gert, I used the multihome statement and when the client tries to connect 
to the server, the connection is repeatedly reset.I will show you the log 
tomorrow.
-- 
"If was one thing all people took for granted, was conviction that if you 
 feed honest figures into a computer, honest figures come out. Never doubted 
 it myself till I met a computer with a sense of humor."
                            Robert A. Heinlein, The Moon is a Harsh Mistress

Gert Doering - Munich, Germany                            g...@greenie.muc.de
  
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to