Interesting product: [WayBack] RugGear RG100: RugGear
The RugGear RG100 is the solid basic mobile phone for outdoor use. Tough and waterproof! The RG100 is equipped with a 1.3 megapixels camera and allows you to take pictures under water.
–jeroen
Archive for June 29th, 2020
RugGear RG100: RugGear
Posted by jpluimers on 2020/06/29
Posted in LifeHacker, Power User | Leave a Comment »
shell – List open SSH tunnels – via: Super User
Posted by jpluimers on 2020/06/29
I put an lsof example and output in Reverse ssh tunnel between two linux boxes to allow RDP traffic over port 3389, but forgot to explain it.
Note that if you are bumping into remote tunneling issues selecting the wrong network interface, then checkout the
GatewayPortssetting in the above post first!
Inactive local tunnels on the client: find the first word ssh on lsof output.
$ lsof -i -n | grep -w '^\<ssh\>' ssh 93548 jeroenp 3u IPv4 0x298985ab430c8aa9 0t0 TCP 192.168.71.77:50257->80.101.239.92:30022 (ESTABLISHED) ssh 93548 jeroenp 5u IPv6 0x298985ab22e02df9 0t0 TCP [::1]:59124 (LISTEN) ssh 93548 jeroenp 6u IPv4 0x298985ab272543a1 0t0 TCP 127.0.0.1:59124 (LISTEN) ssh 93548 jeroenp 7u IPv6 0x298985ab22e03339 0t0 TCP [::1]:ms-wbt-server (LISTEN) ssh 93548 jeroenp 8u IPv4 0x298985ab4306eaa9 0t0 TCP 127.0.0.1:ms-wbt-server (LISTEN) ssh 93548 jeroenp 9u IPv6 0x298985ab28049339 0t0 TCP [::1]:5925 (LISTEN) ssh 93548 jeroenp 10u IPv4 0x298985ab25cefe89 0t0 TCP 127.0.0.1:5925 (LISTEN)
The above listens two tunnels listening to ports 59124, 3389 (ms-wbt-server) and 5925.
Remote tunnels on the server: find the first word sshd on lsof output. Needs sudo if sshd runs as daemon or to listen active connections:
$ sudo lsof -i -n | grep -w '^\<sshd\>' sshd 1664 root 3u IPv4 21299 0t0 TCP *:ssh (LISTEN) sshd 1664 root 4u IPv6 21301 0t0 TCP *:ssh (LISTEN) sshd 5026 root 3u IPv4 350758 0t0 TCP 192.168.124.32:ssh->192.168.171.24:52417 (ESTABLISHED) sshd 5029 jeroenp 3u IPv4 350758 0t0 TCP 192.168.124.32:ssh->192.168.171.24:52417 (ESTABLISHED) sshd 5120 root 3u IPv4 6693665 0t0 TCP 192.168.124.32:ssh->80.100.143.119:11585 (ESTABLISHED) sshd 5123 jeroenp 3u IPv4 6693665 0t0 TCP 192.168.124.32:ssh->80.100.143.119:11585 (ESTABLISHED) sshd 13320 root 3u IPv4 6319692 0t0 TCP 192.168.124.32:ssh->192.168.171.24:56801 (ESTABLISHED) sshd 13323 jeroenp 3u IPv4 6319692 0t0 TCP 192.168.124.32:ssh->192.168.171.24:56801 (ESTABLISHED) sshd 16505 root 3u IPv4 6374150 0t0 TCP 192.168.124.32:ssh->192.168.171.24:21505 (ESTABLISHED) sshd 16508 jeroenp 3u IPv4 6374150 0t0 TCP 192.168.124.32:ssh->192.168.171.24:21505 (ESTABLISHED)
The above does not list any tunnels, just regular connections as there were no local tunnels from the client active, which lists the server side of tunnel -L 59124:192.168.124.32:5900 (which is service rfb):
$ sudo lsof -i -n | grep -w '^\<sshd\>' sshd 1664 root 3u IPv4 21299 0t0 TCP *:ssh (LISTEN) sshd 1664 root 4u IPv6 21301 0t0 TCP *:ssh (LISTEN) sshd 5026 root 3u IPv4 350758 0t0 TCP 192.168.124.32:ssh->192.168.171.24:52417 (ESTABLISHED) sshd 5029 jeroenp 3u IPv4 350758 0t0 TCP 192.168.124.32:ssh->192.168.171.24:52417 (ESTABLISHED) sshd 5120 root 3u IPv4 6693665 0t0 TCP 192.168.124.32:ssh->80.100.143.119:11585 (ESTABLISHED) sshd 5123 jeroenp 3u IPv4 6693665 0t0 TCP 192.168.124.32:ssh->80.100.143.119:11585 (ESTABLISHED) sshd 5123 jeroenp 13u IPv4 6698066 0t0 TCP 192.168.124.32:51494->192.168.124.32:rfb (ESTABLISHED) sshd 13320 root 3u IPv4 6319692 0t0 TCP 192.168.124.32:ssh->192.168.171.24:56801 (ESTABLISHED) sshd 13323 jeroenp 3u IPv4 6319692 0t0 TCP 192.168.124.32:ssh->192.168.171.24:56801 (ESTABLISHED) sshd 16505 root 3u IPv4 6374150 0t0 TCP 192.168.124.32:ssh->192.168.171.24:21505 (ESTABLISHED) sshd 16508 jeroenp 3u IPv4 6374150 0t0 TCP 192.168.124.32:ssh->192.168.171.24:21505 (ESTABLISHED)
For the client side of active connections you need sudo too:
$ sudo lsof -i -n | grep -w '^\<ssh\>' Password: ssh 93548 jeroenp 3u IPv4 0x298985ab430c8aa9 0t0 TCP 192.168.71.77:50257->80.101.239.92:30022 (ESTABLISHED) ssh 93548 jeroenp 5u IPv6 0x298985ab22e02df9 0t0 TCP [::1]:59124 (LISTEN) ssh 93548 jeroenp 6u IPv4 0x298985ab272543a1 0t0 TCP 127.0.0.1:59124 (LISTEN) ssh 93548 jeroenp 7u IPv6 0x298985ab22e03339 0t0 TCP [::1]:ms-wbt-server (LISTEN) ssh 93548 jeroenp 8u IPv4 0x298985ab4306eaa9 0t0 TCP 127.0.0.1:ms-wbt-server (LISTEN) ssh 93548 jeroenp 9u IPv6 0x298985ab28049339 0t0 TCP [::1]:5925 (LISTEN) ssh 93548 jeroenp 10u IPv4 0x298985ab25cefe89 0t0 TCP 127.0.0.1:5925 (LISTEN) ssh 93548 jeroenp 15u IPv4 0x298985ab2998de89 0t0 TCP 127.0.0.1:59124->127.0.0.1:52580 (ESTABLISHED)
Based on [WayBack] shell – List open SSH tunnels – Super User.
–jeroen
Share this:
Posted in *nix, *nix-tools, Power User, ssh/sshd | Leave a Comment »
Audacity error when starting “The application “Audacity.app” can’t be opened.”
Posted by jpluimers on 2020/06/29
For quite a while, I had the error “The application “Audacity.app” can’t be opened.” and Audacity still opening. Clicking the OK button often enough made me hunt for the solution:
This is what I did:
$ cd ~/Library/Application\ Support/audacity
$ grep Temp audacity.cfg
TempDir=/Users/jeroenp/Library/Application Support/audacity/SessionData
Then I checked if the directory existed:
$ find ~/Library/Application\ Support/audacity -type d
/Users/jeroenp/Library/Application Support/audacity
/Users/jeroenp/Library/Application Support/audacity/AutoSave
/Users/jeroenp/Library/Application Support/audacity/Plug-Ins
/Users/jeroenp/Library/Application Support/audacity/SessionData
The odd thing is the directory already existed, so I decided to delete the line, but first needed sed -n (the -n is important: it list only non-matching lines to stdout, see [WayBack] regex – What actually the meaning of “-n” in sed? – Stack Overflow):
$ sed -n '/^TempDir=/p' ~/Library/Application\ Support/audacity/audacity.cfg
TempDir=/Users/jeroenp/Library/Application Support/audacity/SessionData
Since this is Mac OS/Mac OS X/OS X, the -i parameter requires a string even if it is an empty [WayBack] shell – Delete lines in a text file that contain a specific string – Stack Overflow so we get:
$ sed -i '' -n '/^TempDir=/d' ~/Library/Application\ Support/audacity/audacity.cfg
After that, starting audacity still gave the same error and the TempDir entry was re-added.
So I did this:
- renamed the
audacitydirectory toaudacity.bad, - recreated an empty
audacitydirectory - created empty subdirectories
AutoSave,Plug-Ins,SessionData - looped this loop
- Start
Audacity - On success copy a missing file in the
audacitydirectory tree from theaudacity.baddirectory tree
- Start
In the end, these files were the cause:
pluginregistry.cfgpluginsettings.cfg
Since I wasn’t using any plugins, I removed them. Now audacity starts fine.
Now that I had the files pinpointed, I could refine the search and this seems to be a common problem [WayBack] FAQ:Installation, Startup and Plug-ins – Audacity Development Manual: How can I solve Audacity not appearing or crashing on launch, or crashing after I add a plug-in?.
Too bad that page didn’t show up in the original search results.
–jeroen
Share this:
Posted in *nix, *nix-tools, Apple, Mac, Mac OS X / OS X / MacOS, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, Power User, sed | Leave a Comment »
The Wiert Corner - irregular stream of stuff 