https://oneeyedman.net/wiki/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0One-Eyed Man Wiki - New pages [en]2024-03-29T13:10:00ZFrom One-Eyed Man WikiMediaWiki 1.37.1https://oneeyedman.net/wiki/index.php/Resetting_the_Foris_passwordResetting the Foris password2023-12-12T22:26:09Z<p>Dwrob: the usual</p>
<hr />
<div>Ridiculously obscure, here is how you do it, at the command line:<br />
uci delete foris.auth<br />
<br />
uci commit<br />
After that, Foris (or reForis) is listed as the default management tool and it has no protection at all.<br />
<br />
https://forum.turris.cz/t/how-to-create-new-foris-password-from-scratch/18190/6</div>Dwrobhttps://oneeyedman.net/wiki/index.php/Resolve_WAN_as_LAN_on_TurrisResolve WAN as LAN on Turris2023-08-10T22:09:28Z<p>Dwrob: </p>
<hr />
<div>Making hairpin/loopback/reflection requests on public URLs is not complicated but the information is well hidden from Turris users. (None of this is accessible from the Luci GUI.)<br />
<br />
In '''/etc/config/resolver''', you need this stanza:<br />
config resolver 'kresd'<br />
option rundir '/tmp/kresd'<br />
option log_stderr '1'<br />
option log_stdout '1'<br />
option keep_cache '1'<br />
option include_config '/etc/kresd/custom.conf'<br />
<br />
Create the '''/etc/kresd/custom.conf''' file.<br />
<br />
Fill up '''custom.conf''' with "hints":<br />
hints['mon.sous.domaine.fr'] = '192.0.2.118'<br />
Restart the kresd daemon.<br />
<br />
Sources:<br />
<br />
Sort of useful -- https://wiki.turris.cz/doc/en/public/dns_knot_misc<br />
<br />
Totally useless -- https://knot-resolver.readthedocs.io/en/stable/modules-hints.html<br />
<br />
Other confused people -- https://forum.turris.cz/t/configure-kresd-to-resolve-a-wan-address-to-a-lan-ip/13597/15</div>Dwrobhttps://oneeyedman.net/wiki/index.php/Git_remote_setup:_ObservationsGit remote setup: Observations2023-07-19T06:03:15Z<p>Dwrob: Created page with "Cloning a private repo: git clone ssh://git@nnn.nnn.nnn.nnn/home/git/widgets"</p>
<hr />
<div>Cloning a private repo:<br />
<br />
git clone ssh://git@nnn.nnn.nnn.nnn/home/git/widgets</div>Dwrobhttps://oneeyedman.net/wiki/index.php/ADS-B_Exchange_and_local_setupADS-B Exchange and local setup2023-03-12T20:17:01Z<p>Dwrob: Added content</p>
<hr />
<div>I did this in the following order and it all worked in the end:<br />
<br />
<br />
For needed information a coordinates finder:<br />
<br />
* https://www.freemaptools.com/elevation-finder.htm<br />
<br />
<br />
https://www.adsbexchange.com/how-to-feed/:<br />
<br />
* curl -L -o /tmp/axfeed.sh <nowiki>https://adsbexchange.com/feed.sh</nowiki> sudo bash /tmp/axfeed.sh<br />
<br />
<br />
https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb:<br />
<br />
* sudo bash -c "$(wget -O - <nowiki>https://github.com/wiedehopf/adsb-scripts/raw/master/readsb-install.sh</nowiki>)"<br />
<br />
<br />
Also this, so as not to burn out the SD-card:<br />
<br />
* <code>sudo apt remove rsyslog -y</code><br />
<br />
<br />
Resulting local website with live map:<br />
<br />
* <nowiki>http://x.x.x.x/tar1090</nowiki><br />
<br />
<br />
Check with ADS-B Exchange that the feed to them is working:<br />
<br />
* https://www.adsbexchange.com/myip/<br />
<br />
<br />
Search for my own station here:<br />
<br />
https://map.adsbexchange.com/mlat-map/#</div>Dwrobhttps://oneeyedman.net/wiki/index.php/Git_--_new_repository_setupGit -- new repository setup2023-03-06T18:42:27Z<p>Dwrob: Adding clone info</p>
<hr />
<div>== Set up new repository ==<br />
Note that the URL in my case is defined via ~/.ssh/config. I write it directly into .../[repo]/.git/config.<br />
<br />
On server, as user git:<br />
<pre><br />
mkdir project.git<br />
cd project.git<br />
git --bare init</pre><br />
On client:<br />
<pre><br />
mkdir project<br />
cd project<br />
touch .gitignore<br />
git init<br />
git add .<br />
git commit -m "Initial commit"<br />
git remote add origin youruser@yourserver.com:/path/to/project.git<br />
git push origin master</pre><br />
<br />
<code>[https://stackoverflow.com/questions/2337281/how-do-i-do-an-initial-push-to-a-remote-repository-with-git<nowiki>]</nowiki></code><br />
<br />
== Clone existing repository ==<br />
On client, as regular user:<br />
<pre><br />
cd ~/git<br />
git clone git:/home/git/project.git</pre></div>Dwrobhttps://oneeyedman.net/wiki/index.php/Asus_Zenbook_UX325EA-XH74_notesAsus Zenbook UX325EA-XH74 notes2023-02-16T03:12:33Z<p>Dwrob: </p>
<hr />
<div>== Notes on setup and whatever follows ==<br />
<br />
=== Audio ===<br />
The audio adapter is not detected, and all input is directed to "dummy" output.<br />
<br />
The adapter in question:<blockquote>dwrob@skamander:~$ inxi -A<br />
<br />
Audio:<br />
<br />
Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel <br />
<br />
Sound Server: ALSA v: k5.10.0-21-amd64 </blockquote>First encountered after initial Debian 12 installation, and apparently fixed by downgrading to Debian 11. However, it recurred there after a couple of days.<br />
<br />
The following configuration tweaks resulted in working audio:<br />
<code>echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf</code><br />
<br />
<code>echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf</code><br />
An additional tweak didn't have any effect by itself, but in combination with these other two caused a more or less continuous rushing sound, so don't do this:<br />
<code>echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf</code><br />
Source: https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output-issue-in.html<br />
<br />
<br />
'''Follow-up:''' This is probably an Intel audio adapter issue, and not specific to Asus. See among others https://askubuntu.com/questions/1454347/dummy-ouput-no-sound-ubuntu-22-04-and-22-10. The solution is to install firmware-sof-signed (Bullseye, i.e., Debian 11), but I haven't tried this yet since the system is working correctly this moment.</div>Dwrobhttps://oneeyedman.net/wiki/index.php/Quick_SSH_key_creationQuick SSH key creation2023-01-18T14:42:22Z<p>Dwrob: New topic</p>
<hr />
<div>ssh-keygen -t ed25519 -f $HOME/.ssh/id_ed25519 -C "$(whoami)@$(hostname)-$(date +'%y%m%d')"<br />
<br />
<br />
The <code>ssh-keygen</code> command will create a new key and the most common options are below:<br />
<br />
* <code>-t {rsa,ed25519}</code> Key type: RSA or ED25519<br />
* <code>-b [number]</code> Number of bits, only needed for RSA keys<br />
* <code>-C "Comment"</code> Comment for the key<br />
* <code>-f filename</code> The filename for the key<br />
<br />
By default new SSH keys will go into the <code>.ssh</code> folder in the current users home folder. The default RSA keys will have the filenames <code>id_rsa</code> for the private key and <code>id_rsa.pub</code> for the public key while Ed25519 keys will use the similar filename <code>id_ed25519</code> for the private key and <code>id_ed25519.pub</code> for the public key.<br />
<br />
<br />
[https://www.mebmc.uk/posts/creating_ed25519_ssh_keys.html (https://www.mebmc.uk/posts/creating_ed25519_ssh_keys.html])</div>Dwrob