nadoo

Hi @mzz2017 , I really appreciate your effort on improving glider! glider intends to be simple so I use the command line flag name as key in config file, and...

Hi @laincat , thanks for you suggestion, I'm very busy these days and hope to add it soon.

Haven't support QUIC yet, although it's quite easy to support it by using 3rd party package, but it'll make glider binary much bigger. and what is hysteria? any protocol spec...

> Such feature would be great to have ! > > something like: > > ``` > forward=tun-interface://tun0 > ``` Hi @nil0x42 , I guess you just want to forward...

> > > Such feature would be great to have ! > > > > something like: > > > > ``` > > > > forward=tun-interface://tun0 > > >...

Hi @nil0x42 , actually the following config is working start from the version v0.15.0: ``` verbose listen=:8443 strategy=rr forward=direct://#interface=tun0 forward=direct://#interface=tun1 forward=direct://#interface=tun2 ```

> Hi ! I've tried this technique with vlan interfaces (secondary ips), and it doesn't work: `$ cat glider.conf` > > ``` > listen=:8444 > strategy=rr > forward=direct://#interface=eth0:0 > forward=direct://#interface=eth0:1...

Then why not use the round robin mode?

Maybe the `checktimeout` config will meet your requirement?

Is there any reason to use haproxy but not glider's built in scheduling algorithm?