Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read YAML File Properly #29

Closed
aqsandy opened this issue Dec 27, 2023 · 0 comments
Closed

Cannot read YAML File Properly #29

aqsandy opened this issue Dec 27, 2023 · 0 comments

Comments

@aqsandy
Copy link

aqsandy commented Dec 27, 2023

Hi,

I've been tested the vnt-cli for couple days now. I realized that if I use the yaml file to configure the vnt client, the client does not read server address correctly.

Here is my yaml file:

token: $someTokenHere name: $HostnameHere password: $SomePasswordHere server: $ServerHostName:Port ip: $AssignedIPHere mtu: 1250 parallel: 16 no-proxy: true first-latency: true

When I use the yaml file above, the vnt-cli will give me invalid ip error. Once I removed the server, I will get successful message like
version 1.2.8 ====== Connect Successfully ====== virtual_gateway:10.26.0.1 virtual_ip:10.26.0.2 ====== Create Network Interface Successfully ====== name:vnt-tun version: ====== Start Successfully ======
However, the server I run does not on the 10.26.0.1/24 virtual ip CIDR.

If I run the client by using command arguments, it works correctly.

Here is the result with command line:
version 1.2.8 ====== Connect Successfully ====== virtual_gateway:100.x.x.x virtual_ip:100.x.x.x ====== Create Network Interface Successfully ====== name:vnt-tun version: ====== Start Successfully ======

@aqsandy aqsandy closed this as completed Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant