I suspect your Eero wifi extender may be doing NAT itself which would explain why wired clients can't access wireless clients behind it.
If you do as I suggested in your other thread and run the...
Type: Posts; User: btindie; Keyword(s):
I suspect your Eero wifi extender may be doing NAT itself which would explain why wired clients can't access wireless clients behind it.
If you do as I suggested in your other thread and run the...
Your wired and wireless networks are on different subnets - 192.168.1.0/24 vs 192.168.4.0/22 - they are connected aren't they?
One simple test you can do is to run a simple http server on a...
Sorry, I had meant to say
ls -l /etc/apt/trusted.gpg.d
On a clean docker image of ubuntu:22.04 it contains just
root@6eed3a8b0a0f:~# ls -l /etc/apt/trusted.gpg.dtotal 8
-rw-r--r-- 1 root...
That's only true if the user you're running it as uses /bin/sh as their shell.
You haven't mentioned what you're doing in your dockerfile in terms of adding users etc so without additional detail...
That file you've downloaded is not a GPG key, hence the errors you're seeing. So please delete it.
sudo rm /etc/apt/trusted.gpg.d/jammy-security.asc
I'm not sure how you updated your system but...
It doesn't make any difference if you run
cd /tmp
./clean.sh
or simply
/tmp/clean.sh
they both do the same thing. The script is using absolute paths so it doesn't matter what directory...
Well spotted! I've fixed that in my original post.
All of the duplicate keys you have in /etc/apt/trusted.gpg.d/ appear to be backups — files ending in '~'. It should be fine to clean them up by...
Depending on what you've already done, it may be the case that you've got multiple keys in /etc/apt/trusted.gpg.d that are the same and would need cleaning up.
The below will give you a rough idea...
Another option to those suggested above is to bind mount the various directories. It's similar to mounting a partition on a directory but instead you mount a directory on another directory by using...
The file incorrectly has a *.jpg extension as it's actually a tiff.
$ file RP13922.jpg
RP13922.jpg: TIFF image data, little-endian, direntries=15, height=2478, bps=8, compression=none,...
Alternatively you can use the members command from the package with the same name.
Yes, by means of the setfacl command which applies ACLs to files and directories. It allows you to give...
$AddUnixListenSocket /var/sftp/uploads/dev/log
is incorrect. Your setup uses /var/sftp as the chroot base which means the sftp process expects to find the socket at /var/sftp/dev/log
I've got...
The hash (#) at the beginning of the command signifies that you need to run it as root. So prior to running them you first need to type
$ sudo -i
to become root. Once done, press Ctrl+d to exit...
You're using ssh and not scp
:~$: ssh -oHostKeyAlgorithms=+ssh-rsa root@192.168.1.138:/mnt/sda1/meter_E.txt /home/bill/Downloads/yundata.txt
which is why it doesn't work.
if you're logged...
It's because your device is using legacy hostkeys which have been disabled by the default SSH install on your client.
Additionally, you've already got the RSA hostkey stored in your known_hosts...
OK, so the ttyUSB's are available at that stage in the boot.
If you run
sudo systemd-analyze plot > /tmp/systemd.svg
and open the image, you'll need to zoom in towards the bottom. You'll see...
As mentioned previously, it may be because when that script is executed the USB device might not be available.
On my version of Ubuntu, that script is started by the systemd service called...
If you reboot, they then won't be loaded. modprobe just loads them into memory temporarily.
Take a look at the install docs https://docs.anbox.io/userguide/install.html#install-kernel-modules it...
You can just use the find command to find files based on the extension.
e.g. the below will copy all .jpg + .png files into the /absolute/path directory preserving timestamps, set that to the...
Take a look at https://linux.die.net/man/8/dmidecode that should do what you want for the motherboard/cpu
For the disks you can use https://linux.die.net/man/8/hdparm
e.g.
# hdparm -i...
If you've still got an issue you could try running _sshd_ in debug mode on the server
sudo /usr/sbin/sshd -ddd -p 2022
which will make it listen on port 2022 and make it show any connection...
Nope, it's a unix socket used to control the fail2ban process. That message will mean that either the logrotate script doesn't have permission to access it, unlikely, or the fail2ban process isn't...
It's failing because your public key isn't in the authorized_keys file for the user lardeployer or the permissions are in correct.
debug1: Authentications that can continue: publickey,password...
Have you added your public key (~/.ssh/id_rsa.pub) to .ssh/authorized_keys file on the remote server?
Make sure the permissions on the .ssh directory & authorized_keys file are correct or else...
I'm not aware of anything that does this directly.
You could though script something using tmux, the terminal multiplexer. You can get it to create new windows/panes and send commands to them....