Hi mtbvfr. Thanks for the private message with the requested info.

I understand your laptop has a successful internet connection using ethernet cable on the eth0 nic, and you want to share that internet connection wirelessly by creating an access point on wlan0.

Based on the information you provided, it seems wlan0 is ready to be used for this purpose--its driver/firmware is loaded and it supports AP mode.

It seems create_ap is no longer maintained, so let's not bother with it.

I managed to get this working on Devuan Daedalus as follows:

0. No need to uninstall or disable NetworkManager if you have it

1. Install some packages:

sudo apt install iproute2 iptables dnsmasq hostapd haveged 

2. Create a script named skinny-create-ap somewhere in your PATH and make it executable. Script should look like this:

#!/bin/sh

# skinny-create-ap v2.3 (February 19, 2024)
# Bruno "GNUser" Dantas (GPLv3)

# Purpose: Turn a GNU/Linux system into a wireless router
# Dependencies: iproute2 iptables dnsmasq hostapd
# Not a dependency but highly recommended: haveged
# Syntax: $ sudo skinny-create-ap <lan_if> <wan_if> <ssid> <passphrase>
# Example usage: $ sudo skinny-create-ap wlan0 eth0 DevuanHotspot TopSecret123
# To turn off the hotspot: $ sudo pkill hostapd; sudo pkill -f 'dnsmasq.*/tmp/dnsmasq.conf'

# user variables:
lan_if="$1"
wan_if="$2"
ssid="$3"
password="$4"
ip_stem=192.168.50
channel=6
#dns_server=1.1.1.1

main()
{
	prevent_nm_interference
	setup_kernel
	setup_nat
	setup_dhcp
	setup_ap
}

prevent_nm_interference()
{
	nmcli dev set "$lan_if" managed no >/dev/null 2>&1
}

setup_kernel()
{
	echo 1 >/proc/sys/net/ipv4/conf/"$wan_if"/forwarding
	echo 1 >/proc/sys/net/ipv4/ip_forward
}

setup_nat()
{
	iptables -t nat -A POSTROUTING -o "$wan_if" -j MASQUERADE
	iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
	iptables -A FORWARD -i "$lan_if" -o "$wan_if" -j ACCEPT
}

setup_dhcp()
{
	# first, bring up $lan_if and give it a suitable ip address:
	if ip link set "$lan_if" up; then
		ip addr add $ip_stem.1/24 dev "$lan_if"
	else
		echo "$lan_if does not exist or cannot be brought up. Make sure necessary driver +/- firmware is installed." >&2
		exit 1
	fi

	# create dnsmasq config file:
	echo "
dhcp-leasefile=/tmp/dnsmasq.leases
dhcp-range=$ip_stem.100,$ip_stem.200,255.255.255.0,24h
#dhcp-option-force=option:dns-server,$dns_server
" >/tmp/dnsmasq.conf

	# start dnsmasq (with care not to clash with any dnsmasq instances that might already be running):
	dnsmasq --interface="$lan_if" --bind-interfaces --except-interface=lo -C /tmp/dnsmasq.conf 
}

setup_ap()
{
	# create hostapd config file:
	echo "
ssid=$ssid
interface=$lan_if
driver=nl80211
channel=$channel
ignore_broadcast_ssid=0
hw_mode=g
auth_algs=1
wpa=2 
wpa_passphrase=$password
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
rsn_pairwise=CCMP

# N
ieee80211n=1
wmm_enabled=1
" >/tmp/hostapd.conf

	# start hostapd:
	hostapd /tmp/hostapd.conf &
}

main

3. Run the script like this, for example:

sudo skinny-create-ap wlan0 eth0 DevuanHotspot TopSecret123

Now your wireless devices (e.g., Android phone) should be able to connect to DevuanHotspot using the password TopSecret123.

Let me know how you fare.

----------

PS1: Regarding radio frequency--the shell script above creates a 2.4 GHz 802.11n ("Wi-Fi 4") access point. 2.4 GHz is a good default because it has better range, simpler configuration, no regulatory issues, and broader hardware support in AP mode. If your wireless nic supports creation of 5 GHz AP and you would prefer 5 GHz, just tweak the "setup_ap" function as appropriate (let me know if you need help).

PS2: Regarding DNS lookups--if you want dnsmasq to tell wireless clients which dns sever to use, just uncomment the two lines where you see dns_server. If you leave those two lines commented, wireless clients will rely on the router (i.e., your laptop) to resolve domain names, which is a perfectly sane default.

PS3: To turn the hotspot off, run this command: sudo pkill hostapd; sudo pkill -f 'dnsmasq.*/tmp/dnsmasq.conf'

Hi penguin. I would give deepforest a warning for the inappropriate post if I could but, alas, I'm just a fellow user.

Have you tried setxkbmap? Start with setxkbmap -query to see what your current settings are for "model" and "layout". In my case, this is what I see:

$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     us

To set available models, layouts, variants, and options, do this:

$ less /usr/share/X11/xkb/rules/evdev.lst

To change settings, this is the syntax:

$ setxkbmap [-model xkb_model] [-layout xkb_layout] [-variant xkb_variant] [-option xkb_options]

So to keep your current keyboard model and change to Russian layout, for example, do:

$ setxkbmap -layout ru

You mentioned that your Russian layout seems to have some characters off position. Maybe you are not using the Russian variant that has the positions you expect? Another possibility is that the keyboard model setting is not correct--look at your keyboard and compare it with internet images of different keyboard models to ensure that setxkbmap's "model" setting is correct for your hardware.

Yes, I think s2idle uses more battery than deep.
Switching to s2idle is the only fix I ever found that allowed the keyboard on one of my laptops to work after suspend. Sorry I couldn't help you find a satisfactory fix. Happy hacking!

Hi, rechvs. I once had a similar problem, where laptop keyboard was unresponsive after resuming from suspend. Laptop in question ran Devuan (I don't remember which version) and did have pm-utils installed.

The problem/solution may vary depending on exact hardware. For me, changing suspend method from the default "deep" (i.e., suspend-to-RAM) to "s2idle" (i.e., suspend-to-idle) solved the problem:

$ sudo sh -c "echo s2idle >/sys/power/mem_sleep"

Maybe so, but the affected laptop only has one (built-in) screen and the config file has no effect unless I use Device1.

Thank you, HoaS. I found this thread and your excellent instructions while investigating Xorg crashes on an old Sony Vaio after upgrading from Chimaera to Daedalus.

For completion's sake, these are the steps I needed to follow after your instructions:
0. The debuild -us -uc step generates six new .deb packages.
1. Install the six new packages with sudo apt install *.deb. These new packages do not conflict with any of the currently-installed graphics packages, so there is no need to uninstall anything.
2. Add this line to /etc/environment: MESA_LOADER_DRIVER_OVERRIDE=i965
3. Reboot

After rebooting, inxi -G shows that mesa-amber is being used (i.e., you'll see that dri = i965 and mesa version = 21).

P.S. In my specific case, it seems mesa version 22 has nothing to do with the Xorg crashes, so mesa-amber unfortunately did not fix the problem. I'll describe my problem and its solution in a separate thread.

Rant: Did you actually read this?

This illustrates exactly what I dislike about Xorg. Everything is overly complicated. This is not a human-friendly description. The header says the DontZap option is boolean, so expected default values would be "true" or "false", not "off" (what exactly is off?).

But all's well that ends well. Thanks to lightdm and sxhkd I don't have to deal with this

I figured it out. I just needed to add a line to /etc/lightdm/lightdm.conf. Now instead of just this in the relevant section:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0

I have this:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0
session-cleanup-script=service lightdm restart

With that added line, now all I need to restart Xorg is sudo pkill Xorg. Thanks for pointing me in the right direction, HoaS!

I do have autologin enabled for my user, with this in /etc/lightdm/lightdm.conf:

[SeatDefaults]
autologin-user=bruno
autologin-user-timeout=0

I'd rather not ditch lightdm, since I would have to reconfigure multiple machines.

There's no actual problem. A few years ago, Xorg disabled Control+Alt+Backspace as the keyboard shortcut for restarting X (supposedly for security reasons). I liked having that shortcut because it was useful for the rare instances when X would freeze. If X acts up, I'd rather simply restart it than doing a full reboot. So the goal is to bring back that functionality by creating a script that works as intended, then binding it to Control+Alt+Backspace.

Wanting to get this script to work is mostly an exercise in getting my computer to do what I want it to do.

Thank you, HoaS. Yes, that's helpful. I'll give patching caja a shot sometime.

Meanwhile, I'll let the MATE developers know about the issue and patch so that they can consider adopting it. It would be nice to have this without having to recompile anything.

Hi, viverna. Anything sold on thinkpenguin.com (their prices are high but the customer service is excellent) will have universal GNU/Linux compatibility because they only sell free software-friendly devices. Here's something they sell:
https://www.thinkpenguin.com/gnu-linux/ … 1394bapcie

Also, the FSF maintains the helpful h-node.org database. To see the firewire adapters in their database, go to duckduckgo.com and enter this search query: firewire site:h-node.org. If the "does it work with free software?" line says "yes" then the device will have universal GNU/Linux compatibility.

Hi, Devuman. Sorry for leading you on a wild goose chase trying to ssh into R2. It seems ralph.ronnquist was right and your router does not offer ssh access into it.

I'm glad you were able to achieve what you needed by setting up a "virtual server" on R2.

P.S. In the future, if you ever have to choose between ralph.ronnquist's advice and someone else's, save yourself some trouble and just go with ralph.ronnquist's