o-jasper commented 6 years ago

21 bothered me myself, as sometimes wireless is awful and wired is convenient.

44 might be a better option yet. Perhaps allow the use the output of a command, like `ip route show |grep default | cut -f 5 -d ' '` (not sure if that's reliable)

To be honest, i could feel more certain about bug-freeness of this code.... It is not very well tested at this point. Could separate out the "split-iterator" and test it better... Kindah wonder if it is better to use luajit or python(maybe a lightweight version is less than 100MB) and then just use C for the inner bits...

Edit: if you pull, probably better add a develop branch and dogfood it/test it more before putting it in master..

o-jasper commented 6 years ago

I was right about doubting the bug-freeness, it doesn't work.

o-jasper commented 6 years ago

It is no good right now, would suggest this solution instead.

jvinet / knock

Iterate over comma-separated potential interfaces #58

21 bothered me myself, as sometimes wireless is awful and wired is convenient.

44 might be a better option yet. Perhaps allow the use the output of a command, like `ip route show |grep default | cut -f 5 -d ' '` (not sure if that's reliable)

jvinet / knock

Iterate over comma-separated potential interfaces #58

21 bothered me myself, as sometimes wireless is awful and wired is convenient.

44 might be a better option yet. Perhaps allow the use the output of a command, like ip route show |grep default | cut -f 5 -d ' ' (not sure if that's reliable)

44 might be a better option yet. Perhaps allow the use the output of a command, like `ip route show |grep default | cut -f 5 -d ' '` (not sure if that's reliable)