Possible problems installing with latest Debian (Buster) and Ubuntu 20.04

[Chaskel]

Hello, this is by far the cleanest looking UI front end for this stuff I've come across (really nice work) and I'm trying to get everything up and running. I've tried on both Debian (Buster) and Ubuntu 20.04 (and it's very possible I'm doing something wrong), but do you know if the latest versions of the dependencies listed and your code can be successfully utilized under either of these environments? (e.g. throughout the process I get lots of warnings about optional dependencies being skipped, unsupported engines, and not compatible messages).

In addition to the clean UI you provide, I'm hoping to be able to switch over to this from WANem so I may run a current OS that I can keep up-to-date.

Thank you

[codekoala]

Hi there! I'm happy to hear that you like this UI!

I'll be brutally honest here--I haven't personally used (or maintained) this tool for several years, so it will take me some time to actually answer your questions in a satisfactory fashion. I'll take some time to get a build working with current tooling and post about my progress!

[Chaskel]

Many thanks - I greatly appreciate it!

[codekoala]

Unsurprisingly, the polymer (and every other) ecosystem has progressed a lot since I built this. I am considering just rebuilding the whole UI with the current LitElement magic I just learned about. I can't promise it will be a quick migration, but it will result in a tool that actually builds!

[Chaskel]

I greatly appreciate your efforts. In case this helps as far as what I am envisioning on my end, I essentially would like to spin up a dedicated VM (minimal OS) with 2 bridged interfaces to be able to control both the outgoing and incoming conditions.

[codekoala]

That's precisely the use case I had when I built this tool! Hopefully it works as well for you as it did for me!

One slight difference in the "appliance" I used: it had a third "management" interface, which was used to access the UI. You might consider adding one to your VM as well, so you can interact with the UI without the network shaping rules affecting your experience ;)

[Chaskel]

Thanks for sharing. I had primarily envisioned just using the web browser locally on the OS (which I'd probably still want to do) but having this option could also be helpful.

[Chaskel]

Hi @codekoala , I just thought I'd check in to see if you've had any luck or potential ETA?

Thanks!

[codekoala]

Hi @Chaskel! The guy working on the UI revamp has been making great progress, but we don't have an ETA just yet. Hopefully we won't be too much longer :)

Are you able to use the pre-built binary?

[Chaskel]

@codekoala thanks for the quick response and glad to hear of the great progress! Where is the pre-built binary are you referring to (and associated readme so that I can look to attempt)?

Thanks again!

[codekoala]

You should be able to download the current pre-built binary at https://github.com/codekoala/network-shaper/releases/tag/0.0.5. Please let me know if you have any issues with that!

[Chaskel]

@codekoala ok thanks. Will be giving it a shot on a CentOS box that is currently available and will get back to you.

[codekoala]

I suppose I should try reading an entire response before responding. The configuration and usage for this tool is described in the README at the repo root. The good stuff starts around here: https://github.com/codekoala/network-shaper#using-this-tool

[Chaskel]

No worries. That's the one I had been using previously but wasn't sure if there was something different for the pre-compiled binary you were referencing. Will keep you posted.

[Chaskel]

Hi @codekoala . Quick update. Both the CentOS test as well as an Ubuntu 20.04 test appear to work in initial tests. I have however run into an issue and I'm not sure how widespread is.

Please note that in my setup I have it where:

• eth0 is LAN/mgmt connection (IPv4 and IPv6 via DHCP)
• eth1 and eth2 are members of br0 interface I created and none of these interfaces are configured to have IPv4 or IPv6 addresses. One plugs into router and the other plugs into client to be tested.
• In the network-shaper web interface I select eth1 as the incoming and eth2 as the outgoing (but I also have to check the checkbox to show interfaces without IPs since they don't show up (which btw after checking that box I have to first apply a bogus selection in order to have them show up on a refresh <unless I've missed something obvious>)

The issue I've been able to reproduce (not configuring anything else except for selecting the interfaces) is that if I enable delay on the outbound interface, put in 50ms for Time and 150ms for Jitter, apply the change, then change just the Jitter back to 0ms, it appears to deselect the previously selected interfaces. Again, I'm not sure how widespread (e.g. if it possibly alters other settings as well or if it is reproducible with other settings)

One other comment in case this helps is that I like the sliders however as I'm tending to want to use the lower range of the scale, I find that they are too delicate to pick low numbers so I end up typing them in. (which is fine for my use but for those that like sliders it could be problematic)

[Chaskel]

...just adding really quick (in case it relates to what I mention above) that when I tried to select the interfaces again just now, it took me saving about 5 times for it to actually stick. Each time it said it was successfully applied but when the page refreshed they would not be selected.