Scenario - ssh into a linux system from Windows using windows terminal/powershell, edit a file in nano and try and paste something.
Sometimes the terminal then freezes, and rings the bell on every keystroke or paste attempt. You can free it up by killing nano from another login session.
The problem is described in this thread:
This problem has been fixed in the latest versions of nano, but it will take a while to get into the distributions. The workaround in the meantime is to use something like PuTTY.
Scenario: Debian installed with nothing selected in the tasksel stage (not even the standard system utilities) - i.e. the most minimal install you can get with the standard installer. Once installed you then install the ssh server
This pulls in a bunch of dependencies, including dbus. You then can ssh into the system as normal. When trying to shutdown or reboot the system you get an error:
Read more...
The situation:
- Main network and private network (physically separate in this case)
- Main network has dhcp server
- Private network has dhcp server (server A, OPNsense in this case), which also acts as a router to main network
- Want to set up a separate system (server B) that we can ssh, rdp etc. into from main network to access private network
- Desire to use dhcp addressing for both interfaces on server B
A problem can arise with this setup if the server B uses server A as its default gateway for whatever reason. The outside network only sees the route to server B via server A, and when you try to remote access server B from the main network (using the appropriate IP address for the main network interface) it fails, as it routes via server A and doesn’t go anywhere.
Read more...
We have a setup where various systems export scratch directories to each other for convenience. An export is set up like:
/etc/exports
/local/scratch -rw,root_squash,no_subtree_check,sync 192.168.2.0/24
Autofs maps come from LDAP - the autofs configuration is:
/etc/autofs.conf
[autofs]
timeout = 300
browse_mode = no
mount_nfs_default_protocol = 4
ldap_uri = ldap:///dc%3Dldap%2Cdc%3Dyour%2Cdc%3Dserver%2Cdc%3Ddns%2Cdc%3Dname
search_base = ou=maps,ou=subsubunit,ou=subunit,o=organisation
map_object_class = nisMap
entry_object_class = nisObject
map_attribute = nisMapName
entry_attribute = cn
value_attribute = nisMapEntry
[ amd ]
dismount_interval = 300
If server A (ip address 192.168.2.101) exports the directory, server B (ip address 192.168.2.102) that also gets the autofs maps automounts this as expected when accessing the desired directory. The findmnt command shows:
Read more...
System – Kea IPv4 DHCP server (ver 2.2.0) running on Debian 12, serving addresses on second network interface (PCIe card).
On reboot the server starts, but warns that it could not open the socket on the prescribed interface, and so is not serving any addresses. Running
systemctl status kea-dhcp4-server.service
The error is
kea-dhcp4[582]: WARN DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: the interface enp3s0 is not running
kea-dhcp4[582]: INFO DHCP4_OPEN_SOCKETS_FAILED maximum number of open service sockets attempts: 0, has been exhausted without success
Restarting the service afterwards works normally. This is a known problem. There are various suggestions to fix the ordering, but the simplest (albeit slightly inelegant) way to get it to work is to tell it to retry a bunch of times with the service-sockets-max-retries and service-sockets-retry-wait-time options. So the start of the configuration looks like this:
Read more...