☰

VPN이 작동하지 않아 혼란스러워요

tag-icon • tag-icon linux ubuntu vpn
VPN이 작동하지 않아 혼란스러워요

VPN을 사용하려고 합니다. F5 VPN 소프트웨어를 사용해야 하는데, 이 소프트웨어는 전송 및 수신된 바이트에 대한 정보와 함께 "연결됨"이라는 팝업 창을 표시합니다.

여기에 이미지 설명을 입력하세요.

실행하면 ifconfig다음이 표시됩니다.

enp9s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.53  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 fe80::88b4:8386:46b2:b870  prefixlen 64  scopeid 0x20<link>
        ether 18:c0:4d:20:ba:e3  txqueuelen 1000  (Ethernet)
        RX packets 2614623  bytes 1488386639 (1.4 GB)
        RX errors 0  dropped 203768  overruns 0  frame 0
        TX packets 1591444  bytes 424169212 (424.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[...]

tun0: flags=81<UP,POINTOPOINT,RUNNING>  mtu 1384
        inet 172.21.181.120  netmask 255.255.255.255  destination 1.1.1.1
        inet6 2001:630:e4:4280::1582  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::e3a6:ca39:2dd9:c23e  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 1544  bytes 416098 (416.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1690  bytes 126644 (126.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

실행하면 ip route list다음과 같은 결과를 얻습니다.

default via 192.168.178.1 dev enp9s0 proto dhcp metric 100 
1.1.1.1 dev tun0 proto kernel scope link src 172.21.181.120 
4.234.210.7 via 172.21.181.120 dev tun0 metric 1 
10.0.0.0/8 via 172.21.181.120 dev tun0 metric 1 
10.42.0.0/24 dev wlp1s0 proto kernel scope link src 10.42.0.1 metric 600 
20.49.140.221 via 172.21.181.120 dev tun0 metric 1 
20.49.230.123 via 172.21.181.120 dev tun0 metric 1 
34.242.90.168 via 172.21.181.120 dev tun0 metric 1 
34.243.28.11 via 172.21.181.120 dev tun0 metric 1 
34.248.57.236 via 172.21.181.120 dev tun0 metric 1 
51.140.73.190 via 172.21.181.120 dev tun0 metric 1 
51.140.80.148 via 172.21.181.120 dev tun0 metric 1 
51.143.224.92 via 172.21.181.120 dev tun0 metric 1 
51.179.223.115 via 172.21.181.120 dev tun0 metric 1 
52.50.187.38 via 172.21.181.120 dev tun0 metric 1 
54.72.152.131 via 172.21.181.120 dev tun0 metric 1 
54.72.239.170 via 172.21.181.120 dev tun0 metric 1 
54.73.203.23 via 172.21.181.120 dev tun0 metric 1 
54.229.195.216 via 172.21.181.120 dev tun0 metric 1 
78.25.196.229 via 172.21.181.120 dev tun0 metric 1 
104.16.117.12 via 172.21.181.120 dev tun0 metric 1 
104.16.118.12 via 172.21.181.120 dev tun0 metric 1 
104.16.119.12 via 172.21.181.120 dev tun0 metric 1 
104.16.120.12 via 172.21.181.120 dev tun0 metric 1 
104.16.121.12 via 172.21.181.120 dev tun0 metric 1 
104.18.0.20 via 172.21.181.120 dev tun0 metric 1 
104.18.1.20 via 172.21.181.120 dev tun0 metric 1 
116.203.77.235 via 172.21.181.120 dev tun0 metric 1 
130.14.29.110 via 172.21.181.120 dev tun0 metric 1 
130.246.130.28 via 172.21.181.120 dev tun0 metric 1 
130.246.130.29 via 172.21.181.120 dev tun0 metric 1 
130.246.130.121 via 172.21.181.120 dev tun0 metric 1 
130.246.130.164 via 172.21.181.120 dev tun0 metric 1 
130.246.130.165 via 172.21.181.120 dev tun0 metric 1 
130.246.130.166 via 172.21.181.120 dev tun0 metric 1 
130.246.130.167 via 172.21.181.120 dev tun0 metric 1 
130.246.130.171 via 172.21.181.120 dev tun0 metric 1 
130.246.130.172 via 172.21.181.120 dev tun0 metric 1 
130.246.130.173 via 172.21.181.120 dev tun0 metric 1 
137.222.0.0/16 via 172.21.181.120 dev tun0 metric 1 
137.222.251.108 via 192.168.178.1 dev enp9s0 metric 1 
151.101.16.95 via 172.21.181.120 dev tun0 metric 1 
151.101.16.152 via 172.21.181.120 dev tun0 metric 1 
160.109.109.97 via 172.21.181.120 dev tun0 metric 1 
162.159.129.81 via 172.21.181.120 dev tun0 metric 1 
162.159.129.87 via 172.21.181.120 dev tun0 metric 1 
162.159.130.81 via 172.21.181.120 dev tun0 metric 1 
162.159.130.87 via 172.21.181.120 dev tun0 metric 1 
169.254.0.0/16 dev enp9s0 scope link metric 1000 
172.16.0.0/12 via 172.21.181.120 dev tun0 metric 1 
173.254.190.144 via 172.21.181.120 dev tun0 metric 1 
185.249.69.250 via 172.21.181.120 dev tun0 metric 1 
192.168.0.0/16 via 172.21.181.120 dev tun0 metric 1 
192.168.178.0/24 dev enp9s0 proto kernel scope link src 192.168.178.53 metric 100 
192.168.178.1 via 192.168.178.53 dev enp9s0 proto unspec metric 1 
194.34.213.28 via 172.21.181.120 dev tun0 metric 1

하지만 "내 IP는 무엇입니까?"라고 Google에 검색하면 마치 VPN이 실행되지 않는 것처럼 여전히 일반 IP 주소가 표시됩니다.

내가 뭘 잘못했나요?

답변1

VPN은 "분할 터널링" 모드에서 사용되므로 VPN 대상으로 향하는 트래픽만 VPN을 통해 전송되고 다른 모든 트래픽은 일반 라우팅을 사용하여 전송됩니다.

특정 IP 주소에 대한 특정 경로를 찾을 수 있습니다.

ip route get 8.8.8.8          # Your usual route
ip route get 20.49.230.123    # VPN

내 시스템의 첫 번째 보고서는 다음과 같습니다.

8.8.8.8 via 192.168.1.1 dev enxb827eb315364 src 192.168.1.18
^target     ^gateway    ^interface              ^my IP address

관련 정보