Chimowicz Hillel

I'm the exact same audience (security researcher with little DSP background), I'm using squelch / power squelch to shunt data before and after a burst, I guess it could work...

So what about an option to enable, disable? (disable by default) UI Can be totally(maybe?) ignored; You already collect a "burst level" information in the form of RSSI; What about...

I would like to preserve original rssi, so total demodulation and remodulation might be possible. Im using both grc and urh on windows, any reference on how to use grc...

  I Should open a bug for that? o_O

Fix (for me): Comment out this next line in ` /lib/systemd/system/nginx.service` ```# ConditionPathExists=/etc/octopi_streamer/hls``` Then start NginX ```sudo service nginx start```

I Wonder myself where this is coming from, Haven't inspected Nginx installation script thoroughly though. Looks like when NginX is installed/configured something along the pipeline requires a specific "thing" that...

I Also spent some time trying to "composify" the project with no success; I ended up running this first on boot; and executing my compose with other services after this...

Look at how he adds the interfaces to the container before starting the container. There might be an issue though, since the order of the NICs might change, I found...

I Did it a while back, for me, something like that worked for me for a "virtual" dmz network inside the rpi & between openwrt & other containers. ``` docker...

Are you making sure you are removing everything on each attempt? Docket network, linux bridge if existing, container etc?