Copy: [email protected] (Shai Berger)

Shai,

On Sunday, May 18, 2025 2:21:08 AM Mountain Standard Time Shai Berger wrote:

Hi,

I've been trying for a while, and failing, to get a hotspot working on
my (testing) desktop, so my phone can connect through it.

At first, it was a problem with autentication. But that has been solved
now. The phone connects to the access points, and once I added
kdeconnect as a service to the shared-zone configuration on the
firewall, I can use that -- but I don't get access to the internet. I
don't get it even when the firewall is off.

When I look at it at kernel level:

cat /proc/sys/net/ipv4/conf/*/forwarding

prints just a series of "1"s.

I had suspected it might have something to do with earlier messing with
the hotspot connection. So I deleted it and created a new one. No
change. The way I created it was with the "Hotspot" button in the
network panel applet (see attached image, if the mailing-list doesn't
kill it on the way).

Any idea where to look next?

I tried to setup on of these Hotspots by clicking this button and it didn’t work for me either. Mine failed at the “Setting network address” stage with
the error “IP configuration was unavailable”.

I would recommend you submit a bug report. Probably beginning with the plasma-nm package, although it might get moved somewhere else depending on where the real problem is.

--
Soren Stoutner
[email protected]
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmguZCMACgkQwufLJ66w tgN1xhAAsN/7LAaFNT0CYwieFhunBLXE0Qk0rBFw7rTaIi1m00l79+rRIEaPWdiw kx+OMDZLbCLF+defTRoe24ZWr9VJHKlUKxcUHiMq6MaMFyRsuru3C2i0mvaeXxdG MVyNb9oIBklR6yJk8jjVIG50IY1ULiFSTh2n2d9stIcum7fQgMfJwJK0YQeK7D/V vAviUUrJGc1LfQiZdy0rdsKWztNqyyPh4YTTKjz/saFnD9FTjgdeYn2Iqy1T7u6I Za1wbA48x1XxkW0roDJckVkAIRosdl85FuDmGUE9gCPKn6xCJIWdAbjLF8R8bErZ KVyYwdbqh65nE1OujUPamLg95jDOWLR1jG9oHtbYzejEK2aSjG9U2yUlpeMKwKz3 OQ5pRazJKib2/I2mO7ZAVCOBTcETXkznjgCLsMSkFP15dd2Vav5Yak3Hazs4RMBi TSC8qkhmk6iqfXeyGGoblvqC1NZRGuvru7g7HTBny19cVmqgjxQ7Lkr1MuOF9W/U ZkIkj0OAFJw1WUXjJiQuZ3QLbPjk6zwYQ0mvXriGO8I7kWUgGReUJe2fz1vohn4q xDlmikODh+Fb2s7HH3PKlcZrbVCaoTYpnyfefv1OxsrdUZv0sliEtVaAWgTABgJn g7VGSSc927oDetP4eHemttqiS5ZS8juigZ7TSAN2nvN8Y7FRrD8=
=2BfY
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Soren,

On Wed, 21 May 2025 16:39:14 -0700
Soren Stoutner <[email protected]> wrote:

I would recommend you submit a bug report. Probably beginning with
the plasma-nm package, although it might get moved somewhere else
depending on where the real problem is.

Submitted at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106398

Thanks,
Shai.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I finally solved this, I think.

The full details are now in the bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106398

TL;DR: The hotspot was set up reasonably, so that packets going
through it are forwarded for handling by the rest of the system. But I
had previously used Docker on this system, and *it* set up a forwarding
rule which allows forwarding from/to the docker network, but not any
other network. And that rule was having the last word.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)