bparli/convey

Layer 4 load balancer with dynamic configuration loading

convey's Issues

1 INSECURE dependency and a few outdated dependencies

Check it out at https://deps.rs/crate/convey/0.2.0

Dependencies

Crate	Required	Latest	Status
crossbeam-channel	^0.3.4	0.5.0	out of date
failure	^0.1.2	0.1.8	insecure

Dev-ependencies

Crate	Required	Latest	Status
assert_fs	^0.10.0	1.0.0	out of date
proptest	^0.8.7	0.10.1	out of date
rand	^0.6.1	0.7.3	out of date
structopt	^0.2	0.3.21	out of date

http://127.0.0.1:7000/stats does not update.

http://127.0.0.1:7000/stats does not update untill backend disconnected
I tried this with proxy and one backend server.

is this production ready?

1. is this production ready?

2. what use case / case scenario is this used?

3. i havent try it yet but hope to see the cross-datacenter feature work too if possible

4. was wondering if it will work if i get 1 fixed ip line (for the load balancer) + multiple dhcp ip from same ISP connected as backend, will it work?

DSR Mode

Does DSR work across servers in different datacentres?

I have got the standard proxy working but cant get the config working for DSR and cant see where I'm going wrong from the instructions. Is there a log anywhere I could check?

The interface is listening with no errors, but I cant complete a TCP connection with the server behind it.

I set up the balancers as per the instructions below, is there anythign I could be missing?

Thank You for any help

` sudo tc qdisc add dev enp0s8 root handle 10: htb

sudo tc filter add dev enp0s8 parent 10: protocol ip prio 1 u32 match ip src <LOCAL_SERVER_IP> match ip sport <LISTEN_PORT> 0xffff match ip dst <LOAD_BALANCER_IP> action ok

sudo tc filter add dev enp0s8 parent 10: protocol ip prio 10 u32 match ip src <LOCAL_SERVER_IP> match ip sport <LISTEN_PORT> 0xffff action nat egress 192.168.1.117 <LOAD_BALANCER_IP> `

Possible to show some benchmark against haproxy etc?

Possible to show some benchmark against haproxy etc? Nice software btw