Forums

[songinno]

hi, i need help.

[server]

windows 11
all firewall are closed
installed wiresock and wireguard
using telecom router
extenal IP – 115.140.xxx.xxx
internal IP – 192.xxx.219.102

[ situation ]

1. router setting
NAT configuration – port forwarding
port : 51820
ip : {internal IP}
protocol : TCP/IP, UDP

2. open powershell and execute command
wg-quick-config -add
– Configure the Wireguard Server endpoint
ㄴ {external IP}:51820
– Configure the Wireguard IPv4 subnet
ㄴ 192.xxx.219.50/32

3. result

wiresock.conf

[Interface]
PrivateKey = cD2zxxxxxxxxxxxxxxxxxxxxx=
Address = 192.xxx.219.51/32
ListenPort = 51820

[Peer]
PublicKey = qnexxxxxxxxxxxxxxxxxxx=
AllowedIPs = 192.xxx.219.52/32

wsclient_1.conf

[Interface]
PrivateKey = YNBxxxxxxxxxxxxxxxxxxxxxxA=
Address = 192.xxx.219.52/32
DNS = 8.8.8.8, 1.1.1.1
MTU = 1420

[Peer]
PublicKey = Z8Qxxxxxxxxxxxxxxxxxxxxxxxxxxx=
AllowedIPs = 0.0.0.0/0
Endpoint = 115.140.xxx.xxx:51820
PersistentKeepalive = 25

4. go to client computer(my notebook, using another network(cell phone hotstpot) and open wireguard, add tunnel

5. copy wsclient_1.conf file`s content and paste it

6. log
Keypair 1 created for peer 1
Receiving keepalive packet from peer 1 (115.140.xxx.xxx:51820)
(repeat)
Keypair 2 created for peer 1
Sending keepalive packet to peer 1
Receiving keepalive packet from peer 1 (115.140.xxx.xxx:51820)
(repeat)
Keypair 1 destroyed for peer 1
Keypair 3 created for peer 1
Sending keepalive packet to peer 1
Receiving keepalive packet from peer 1 (115.140.xxx.xxx:51820)

(repeat)
ping test
server to client
ping 192.168.xxx.52 (OK)

client to server and external IP
ping 192.xxx.219.51(OK)
ping 192.xxx.219.102(FAIL)
ping 155.140.xxx.xx(FAIL)

===========================================

i want to use my server network in outside by using wireguard VPN

but, i can`t use internet on my client computer

please help me, what`s the problem

thank you

• This topic was modified 3 years, 1 month ago by songinno.

[Vadim Smirnov]

The WireSock VPN Gateway is capable of functioning in two distinct modes: NAT and Proxy. It is imperative to understand that the PING command is operational exclusively in NAT mode, given that Proxy mode is restricted to supporting only the TCP and UDP protocols. Nonetheless, any protocols that are based on UDP and TCP are expected to perform seamlessly in either mode.

[Vadim Smirnov]

To switch from default PROXY mode to NAT mode. Start a command prompt as Administrator and run the following commands:

wiresock-service uninstall
wiresock-service install -start-type 2 -mode nat -interface wiresock -log-level none
sc start wiresock-service

[songinno]

thanks to reply me

I tried as you suggested, but the same problem still occurred.
————————————————————-

[server – power shell]

Trying to make Wireguard tunnel network private…
PS C:\WINDOWS\system32> wg-quick-config -stop
Existing configuration loaded successfully.
Stopping Wireguard tunnel…
PS C:\WINDOWS\system32> wiresock-service uninstall
wiresock-service is removed.
PS C:\WINDOWS\system32> wiresock-service install -start-type 2 -mode nat -interface wiresock -log-level none
>>
wiresock-service is installed.
PS C:\WINDOWS\system32> sc start wiresock-service
PS C:\WINDOWS\system32> wg-quick-config -start
Existing configuration loaded successfully.

Starting Wireguard tunnel…

Trying to make Wireguard tunnel network private…

————————————————————-

[client – wireguard log]

Receiving keepalive packet from peer 1(115.140.xxx.xxx:51820)
Receiving keepalive packet from peer 1(115.140.xxx.xxx:51820)
Receiving keepalive packet from peer 1(115.140.xxx.xxx:51820)
….

• This reply was modified 3 years, 1 month ago by songinno.

[Author]

Posts