Problem: Some flac players refuse to play some flac files, and even tools like an old ffmpeg can’t handle some flac files
Solution: These flac files might have id3v2 tags which they realy should not, because flac uses vorbis style tags and not id3. Remove those id3v2 tags with this command:
> id3v2 --delete-all song.flac
This removes the id3v2 tags from the flac file in place
Discussion: Those flac files were made with EAC. In the encoder settings “Add ID3 Tags” was checked, and EAC added ID3 tags even though flac files don’t need and must not have ID3 tags. If you like to know, whether your flac files have these false ID3 tags your can run “id3v2 -l song.flac” or look into the files with hexdump.
Problem: current Chrome browsers cut URl parts and hide the correct URL. https://www.derstandard.at/ is shown as derstandard.at. This is simply wrong from the technical point of view. And it might even be dangerous for some URLs form a security standpoint.
Why does Google insist on breaking the URL scheme ? What’s behind this ?
Update 3: New method to work around the Chrome URL bug for version 83: Enable the setting: chrome://flags/#omnibox-context-menu-show-full-urls then right click in the location input field and activate “Alway show full URLs”
The line “wpa-scan-ssid 1” allows to use hidden WLAN that are not broadcasted. With “metric 4” you can make WLAN less preferred if there is a second LAN connection that should be preferred (default is “metric 1”).
Problem: Mikrotik allows only one ipsec policy per network-to-network pair. If you want to have redundant tunnels between two locations with two upstreams you cannot configure ipsec redundancy on Mikrotik because one ipsec policy is always marked as “invalid” by the OS.
Solution: I made a Mikrotik script that checks the status and reachabilty of the ipsec tunnel and endpoint, and switches between a primary and secondary tunnel policy and peer. You can add this script to the scheduler, for automatic failover. (Source: “/system script run 0” if this script is script “0”)
Problem: Two FortiGate firewall show “not synchonized” in the HA status.
Discussion: the problem with this is, that FortiGate does not show why it fails. I found no log file with a reasonable error message. So I tried to synchronize the config myself, which is exactly what should NOT be necessary when using HA synchronization.
Solution: When an ipsec-phase1 setting in the master is removed while the slave is not online, the ipsec-phase1 removal fails during synchronization. Why Fortinet, doesn’t your box log this? Removing the phase1-section by hand did not work ether:
FortiGate-Master # execute ha manage 1
FortiGate-Slave $ config vpn ipsec phase1-interface FortiGate-Slave (phase1-interface) $ delete VPN-PEER This phase1-interface is currently used command_cli_delete:5937 delete table entry VPN-PEER unset oper error ret=-23 Command fail. Return code -23
Like with most cheap software I had to reboot the slave, and then I could remove the phase1-interface section, and then the synchronization worked again.
I don’t remember if I ever had to reboot a Cisco or Linux box to fix a bug.