Customize the IPs and private keys

[KusakabeShi]

I want an option to customize the IPs and wireguard keys for em_proxy while initialization.

Add 4 new optional paramater for em_proxy:

Name	Default Value
em_proxy server_privatekey	UI+sCDEketXDq6vOAidLe0mYiHogMh1TA2zg3CqlxEA=
em_proxy client_publickey	ow01dGyrgRSrjln9bGb6fx0FwY5XKSVMTaoKQ2GDSkM=
em_proxy server_ip	10.0.7.1
em_proxy client_ip	10.0.7.10

make these value customizable instead of hardcoded in em_prixy

[KusakabeShi]

By the way, em_proxy client_ip seems automatic detected so we doesn't need to make it configureable.

[arthurmelton]

The only place I can even find the server ip is in a test

em_proxy/src/lib.rs

Line 329 in c8a280e

std::net::TcpStream::connect(SocketAddrV4::new(Ipv4Addr::new(10, 7, 0, 1), 3000))

[KusakabeShi]

The scenario of changeable IP is the IP used by em_proxy( 10.0.7.1 ) may conflict with the real VPN (if I want to use em_proxy with real wireguard vpn).
In most case it won't be an issue but make it changeable to give us a chance to avoid the conflict would be better I think.

[arthurmelton]

I believe the IP used for the user is set by one of the functions. Whenever you start the proxy you can set the IP to be whatever you want. If their is a program you are using that uses em_proxy, you would have to request that program to change the IP used. There fire I believe this issue can be closed.