znailnetem / znail Goto Github PK

requirements.txt currently has flask==1.1.2, which is no longer supported and has started to cause issues due to transitive dependencies

I would like to see a demonstration video of how to setup Znail and interact with it.

Hi. I've been tested a nanoPi R2S. eth0 was connected WAN, eth1 was connected LAN port of R2S. All impairments were adopted on downlink(eth0 > eth1). Can I adopt the impairment on an uplink(eth1 > eth0) direction?

For Raspberry Pi builds, wifi and bluetooth should be disabled at build time to minimize possible external data interference.

They can be disabled by adding the following to config.txt:

dtoverlay=pi3-disable-wifi
dtoverlay=pi3-disable-bt

I think the NanoPi R2S could potentially be a good hardware platform for the znail:

https://www.friendlyarm.com/index.php?route=product/product&product_id=282

It has 2 GBit interfaces, TF-card slot for OS and a USB port that potentially could be used for a USB-storage device.
The USB-storage could be used for saving TCP-dump, user settings that should be "portable" between devices and a text file with current IP-addresses of the interfaces written on boot to make it simpler to find on the network.
It also supports a USB2LCD that can be used to display the IP-address.

Ubuntu core and FriendlyWRT are among the many OSes available.

DevConSoft is willing to sponsor this feature by paying for 1 set of the hardware (NanoPi R2S, case, MicroSD card, USB2LCD, shipping, VAT) up to 1000 SEK. Sponsorship require prior agreement between DevConSoft and the implementor and valid receipt of the purchase.

Original maintainers has first dibs on the sponsoring.

Clicking on "Network Disconnect" button indeed shuts down the device-facing network adapter (eth1). However, clicking on the "Network Reconnect" button does not bring it back up despite the message that the changes were applied successfully. ifconfig does not show eth1 anymore, packets are not going through, and it cannot be fixed by anything other than reboot.

Have not checked that feature on Armbian, maybe it works there.

As discussed in #3, it would be great to have releases built from a build server instead of locally.