Für mein Archiv: Zur Amazon chat geht via AmazonSmile – Kontaktieren Sie uns.
–jeroen
https://smile.amazon.de/gp/help/contact-us/general-questions.html/
Posted by jpluimers on 2019/01/07
Für mein Archiv: Zur Amazon chat geht via AmazonSmile – Kontaktieren Sie uns.
–jeroen
https://smile.amazon.de/gp/help/contact-us/general-questions.html/
Posted in LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2019/01/07
A while ago, I write about Locally Administered Addresses: a few series of MAC addresses you can use on your local network: MAC address ranges safe for testing purposes (Locally Administered Address).
A while ago, I found ones in my network and ones in my WiFi SSID survey starting with FA:8F:CA
. They did not show up in the Wireshark · OUI Lookup Tool nor their manufacturer database.
But with bit 7 turned off they start with F8:8F:CA
which does show up as “F8:8F:CA Google, Inc.”
They appear to be Google devices, in my case Google ChromeCast ones, though they can also be Google Home ones.
Google does “magic” with networks, just look at a few of the links here:
–jeroen
Posted in Ethernet, Google, Internet, Network-and-equipment, Power User, Ubiquiti, WiFi | Leave a Comment »
Posted by jpluimers on 2019/01/07
A few notes on Zabbix triggers and web scenarios:
For now I’ve set these kinds of triggers on response times:
Warning
: 2 minute of response time > averageAverage
: 5 minutes of response time > 2*averageHigh
: 10 minutes of response time > 4*avarageDisaster
: 30 minutes of response time > 10*averageThese are the colours by default used for the trigger levels: at http://example.org/zabbix/adm.triggerseverities.php
–jeroen
Posted in *nix, Monitoring, Power User, Zabbix | Leave a Comment »
Posted by jpluimers on 2019/01/07
After an outrage about AdWare mid last year on the Windows side of things, a new outrage on the Mac side of things at the end of last year caused FileZilla to be removed from the homebrew cask repository.
They do not care that there is a non-bundle version that (right now) does not have adware, as FileZilla could put AdWare in that version at any moment in time.
After trying to update, it will disappear, and you might get an error like this (a full log is below the fold):
"Error: Cask 'filezilla' is unavailable: No Cask with this name exists."
Too bad, as FileZilla was fun while it lasted.
For the dare devils, you might want to try the non-bundled version at fosshub, but please run it through at least VirusTotal before installing, and remember: you have to trust yet another man-in-the-middle!
Uninstalling now that the cask has been removed is described in:
Delete
Filezilla.app
in/Applications
, as well as the"$(brew --prefix)/Caskroom/filezilla
directory. If you also want to delete its config files, see them on the deleted cask [Wayback].
cask 'filezilla' do version '3.38.1' sha256 '250dfd5e8f4c97bf0baf762251cc328f60b2da4a0dd1c316d67a45c1f1349cf7' url "https://download.filezilla-project.org/client/FileZilla_#{version}_macosx-x86.app.tar.bz2" appcast 'https://filezilla-project.org/versions.php?type=client' name 'FileZilla' homepage 'https://filezilla-project.org/' depends_on macos: '>= :mavericks' app 'FileZilla.app' zap trash: [ '~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/de.filezilla.sfl*', '~/Library/Saved Application State/de.filezilla.savedState', '~/Library/Preferences/de.filezilla.plist', '~/.config/filezilla', ] end
Related:
–jeroen
Posted in Apple, Power User, Windows | Leave a Comment »