Conversation
-LO will follow redirects -L in case the page has moved (3xx response) curl will redirect the request to the new address -o output to a file instead of stdout (usually the screen). In your case the o flag is redundant since the output is piped to bash (for execution) - not to a file.
|
upvoting... |
|
The main fork is pretty much dead, however, check out this comment: #220 (comment) |
|
Upvoting. only change was that each line now uses -LO. sudo curl $1 -# -LO http://standards-oui.ieee.org/iab/iab.csv
sudo curl $1 -# -LO http://standards-oui.ieee.org/oui28/mam.csv
sudo curl $1 -# -LO http://standards-oui.ieee.org/oui36/oui36.csv
sudo curl $1 -# -LO http://standards-oui.ieee.org/oui/oui.csv
|
|
FYI the original report wasn't updated for 2 years. Check out the latest comment here #221 |
|
Thank you, yes this latest comment #221 gave me the info to modify BY ADDING “O” to flag -LO. I landed into this from an old Reddit Post and subsequently installed, trouble shot, then uninstalled after seeing the forks. That led to a lot more troubleshooting too. :) for the server direct install on Raspberrian leiweibau fork which needed tweaks for python3 and for python libraries I was missing. Then log files are missing for php and the symlinks step fails too. So far my install is running and I just need to prune down the hundred+ legacy devices imported from past years of PiHole. I suspect that dynamic IP addressing plays a part but I have a mess to untangle for PiAlert and PiHole to align logical common names to MAC addresses, and the moving IP addresses. Example: my smart Tv is labeled as a MacBook but vendor is Vizio. And there are a hundred+ untitled entries. Thanks so much for the incredible improvements and contributions!!! |
|
I think we active maintainers only do this because we think the "tool" "pucherot/Pi.Alert" is great and that this software deserves to be maintained to stay great. |
-LO will follow redirects
-L in case the page has moved (3xx response) curl will redirect the request to the new address -o output to a file instead of stdout (usually the screen). In your case the o flag is redundant since the output is piped to bash (for execution) - not to a file.