subject:"Wifi"

I just tried using Trixie and it's the same issues. Seems that the 
installer isn't even recognizing wifi card at all  so no matter what 
drives I give it refuses to use them. *No Ethernet card was found on the 
system.* I think my only option is using wifi usb adapter that works, I 
already tried using usb wifi adapter that I had at hand but didn't work 
because it too uses proprietary driver.

Re: Debian bookwork 12.4 installation wifi card not being detected

2024-02-10 Thread Timothy M Butterworth

On Sat, Feb 10, 2024 at 1:07 PM Exeonz  wrote:

> Hey thanks for your time in advance. I'm trying to install debian bookworm
> 12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
> doesn't recognize it's wifi card and what drivers it needs for the card to
> work. From searching the web I found that it uses Broadcom BCM 4360
> wireless network adapter and requires broadcom-sda-dkms firmware drivers to
> function. The installer doesn't detect the wifi card and none of the
> drivers from the select list work and when I use 2nd bootable USB formatted
> as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
> folder it doesn't accept drivers and gives out error "ethernet card not
> found" I've looked through entire debian wiki and other wikis and forums
> like arch wiki and found no answers anywhere. I have successfully installed
> ubuntu on this macbook air and it works just fine with the wifi card. Could
> you please shed some light on how I can possibly install debian on this
> macbook air.
>
> Some other things that I've tried that didn't work.
> Every available driver from the install list.
> Older non-free debian version 11.8.0 because I thought it would have
> drivers but it didn't work either.
> Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/
> onto USB formatted as FAT32 in root and firmware folder
> Using command like during installation for extra option to load drivers
> off USB. (this command doesn't seem to work on bookwork 12.4)
> https://wiki.debian.org/Firmware
>
>
>
> *Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
> 2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
> Using rtl8812au-5.2.20 firmware drivers
> Ripping out firmware drivers from ubuntu install that works fine with this
> wifi card and putting it on same USB
> *bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*
>
Try installing Trixie
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/. Debian 12
is starting to show its age. It uses the LTS kernel 6.1. You really have
two choices:

1. Install Debian Bullseye with a working USB WiFi adapter. Configure
Debian backports and upgrade the kernel and install the needed drivers.

2. Install Debian Testing (Trixie). Trixie has a much newer kernel and the
latest drivers. It also contains newer versions of the other software as
well. I ran Debian testing for Debian 12 for a little over a year until
Bullseye was released!




>
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Debian bookworm 12.4 installation wifi card not being detected


Results on ubuntu are

/03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries 
BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
    Subsystem: Apple Inc. BCM4360 802.11ac Wireless Network Adapter 
[106b:0117]

    Kernel driver in use: wl
    Kernel modules: bcma, wl/


During debian install it's same result but without /kernel driver and 
kernel modules/

I use an iOS device and I don't think tethering feature is supported there.

Re: D12 Installer does not recognize rtl8xxxu wifi

2024-02-10 Thread Felix Natter

Charles Curley  writes:
> On Thu, 08 Feb 2024 19:24:35 +0100
> Felix Natter  wrote:
>
>> If I start a shell from the installer, I can see that the necessary
>> module rtl8xxxu is loaded (the same one that is loaded in live
>> option). So I guess it is a firmware issue. How can I get an
>> installer with non-free firmware (if that is the problem)?
>> I just found one page that says the (non-free?) FW is always included
>> in the images (starting from bookworm). Is that true?
>> Any other idea?

hello Charles,

thank you for your reply. 

> My understanding is that the non-free firmware is now included on
> Debian installation media.

yes, it is pretty clearly stated here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

> I've been using "Debian GNU/Linux 12.2.0 "Bookworm" - Official amd64
> NETINST with firmware 20231007-10:28" and had no problems with non-free
> firmware on my several computers.
>
> So to diagnose this further, exactly what hardware? Please run lspci,
> and run lspci -v for the offending device.
>
> Also, you can run the netinst installer at least through the relevant
> installation phase. Then please capture the logs, probably under
> /var/log. Searching syslog on the word "firmware" should turn up some
> interesting messages.

As I wrote in the other reply, I was mainly concerned about Wifi not
working after installation (I wanted to understand it). I can install
from LAN.

Many Thanks for the reply,
Felix
-- 
Felix Natter

Re: D12 Installer does not recognize rtl8xxxu wifi

2024-02-10 Thread Felix Natter

hello Franco,

thanks for the answer.

Franco Martelli  writes:
> On 08/02/24 at 19:24, Felix Natter wrote:
>> Dear debian-users,
>> I put this on a stick and booted it:
>> debian-live-12.4.0-amd64-gnome.iso
>> When I boot the live option, the network is immediately loaded and I can
>> connect to a WIFI network. However, if I use the same stick
>> (or one with debian 12.4.0 netinst) with the installation option,
>> the LAN is recognized, but WLAN is not.
>
> Hope I'm wrong, but I've heard that D-I has trouble with USB devices other
> than keyboard and mouse. The rtl8xxxu module is usually for USB NIC, if
> it's the case I think you can rely only to LAN for the installation.

I was mainly concerned with Wifi not working after installation. I
bought a long LAN cable and can install via LAN. Now that I understand
the limitation (a search on google seems to confirm this), I am not
worried any more :)

Many Thanks and Best Regards,
Felix
-- 
Felix Natter

Re: Debian bookworm 12.4 installation wifi card not being detected

2024-02-10 Thread Marco Moock

Am Sat, 10 Feb 2024 05:55:17 -0600
schrieb Exeonz :

> I'm trying to install debian bookworm 12.4 on MacbookAir7,2 that
> doesn't have an ethernet port and the installer doesn't recognize
> it's wifi card and what drivers it needs for the card to work. From
> searching the web I found that it uses Broadcom BCM 4360 wireless
> network adapter and requires broadcom-sda-dkms firmware drivers to
> function.

Please run 
lspci -nnk
and post the result of the network card here.
That includes the ID and that makes it possible to identify it and find
the right driver/firmware.

Do you have a smart phone with a USB cable?
You can connect that and use tethering to get internet connection.

Debian bookworm 12.4 installation wifi card not being detected

Hey thanks for your time in advance. I'm trying to install debian bookworm
12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
doesn't recognize it's wifi card and what drivers it needs for the card to
work. From searching the web I found that it uses Broadcom BCM 4360
wireless network adapter and requires broadcom-sda-dkms firmware drivers to
function. The installer doesn't detect the wifi card and none of the
drivers from the select list work and when I use 2nd bootable USB formatted
as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
folder it doesn't accept drivers and gives out error "ethernet card not
found" I've looked through entire debian wiki and other wikis and forums
like arch wiki and found no answers anywhere. I have successfully installed
ubuntu on this macbook air and it works just fine with the wifi card. Could
you please shed some light on how I can possibly install debian on this
macbook air.

Some other things that I've tried that didn't work.
Every available driver from the install list.
Older non-free debian version 11.8.0 because I thought it would have
drivers but it didn't work either.
Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/ onto
USB formatted as FAT32 in root and firmware folder
Using command line during installation for extra options to load drivers
off USB. (this command doesn't seem to work on bookwork 12.4)
https://wiki.debian.org/Firmware



*Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
Using rtl8812au-5.2.20 firmware drivers
Ripping out firmware drivers from ubuntu install that works fine with this
wifi card and putting it on same USB
*bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*

Debian bookwork 12.4 installation wifi card not being detected

Hey thanks for your time in advance. I'm trying to install debian bookworm
12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer
doesn't recognize it's wifi card and what drivers it needs for the card to
work. From searching the web I found that it uses Broadcom BCM 4360
wireless network adapter and requires broadcom-sda-dkms firmware drivers to
function. The installer doesn't detect the wifi card and none of the
drivers from the select list work and when I use 2nd bootable USB formatted
as FAT32 with broadcom-sda-dkms firmware drivers saved to root and firmware
folder it doesn't accept drivers and gives out error "ethernet card not
found" I've looked through entire debian wiki and other wikis and forums
like arch wiki and found no answers anywhere. I have successfully installed
ubuntu on this macbook air and it works just fine with the wifi card. Could
you please shed some light on how I can possibly install debian on this
macbook air.

Some other things that I've tried that didn't work.
Every available driver from the install list.
Older non-free debian version 11.8.0 because I thought it would have
drivers but it didn't work either.
Downloading all firmware from https://cdimage.debian.org/cdimage/firmware/
onto USB formatted as FAT32 in root and firmware folder
Using command like during installation for extra option to load drivers off
USB. (this command doesn't seem to work on bookwork 12.4)
https://wiki.debian.org/Firmware



*Installation+Archive+USBStickpreseed/early_command="modprobe vfat ; sleep
2 ;mount /dev/disk/by-label/FIRMWARE /media ;cp -a /media/firmware /lib"*
Using rtl8812au-5.2.20 firmware drivers
Ripping out firmware drivers from ubuntu install that works fine with this
wifi card and putting it on same USB
*bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu10~22.04.1_amd64*

Re: D12 Installer does not recognize rtl8xxxu wifi

2024-02-08 Thread Franco Martelli


On 08/02/24 at 19:24, Felix Natter wrote:

Dear debian-users,

I put this on a stick and booted it:
debian-live-12.4.0-amd64-gnome.iso

When I boot the live option, the network is immediately loaded and I can
connect to a WIFI network. However, if I use the same stick
(or one with debian 12.4.0 netinst) with the installation option,
the LAN is recognized, but WLAN is not.


Hope I'm wrong, but I've heard that D-I has trouble with USB devices 
other than keyboard and mouse. The rtl8xxxu module is usually for USB 
NIC, if it's the case I think you can rely only to LAN for the installation.


Cheers,
--
Franco Martelli

Re: D12 Installer does not recognize rtl8xxxu wifi

2024-02-08 Thread Charles Curley

On Thu, 08 Feb 2024 19:24:35 +0100
Felix Natter  wrote:

> If I start a shell from the installer, I can see that the necessary
> module rtl8xxxu is loaded (the same one that is loaded in live
> option). So I guess it is a firmware issue. How can I get an
> installer with non-free firmware (if that is the problem)?
> I just found one page that says the (non-free?) FW is always included
> in the images (starting from bookworm). Is that true?
> Any other idea?

My understanding is that the non-free firmware is now included on
Debian installation media.

I've been using "Debian GNU/Linux 12.2.0 "Bookworm" - Official amd64
NETINST with firmware 20231007-10:28" and had no problems with non-free
firmware on my several computers.

So to diagnose this further, exactly what hardware? Please run lspci,
and run lspci -v for the offending device.

Also, you can run the netinst installer at least through the relevant
installation phase. Then please capture the logs, probably under
/var/log. Searching syslog on the word "firmware" should turn up some
interesting messages.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

D12 Installer does not recognize rtl8xxxu wifi

2024-02-08 Thread Felix Natter

Dear debian-users,

I put this on a stick and booted it:
debian-live-12.4.0-amd64-gnome.iso

When I boot the live option, the network is immediately loaded and I can
connect to a WIFI network. However, if I use the same stick
(or one with debian 12.4.0 netinst) with the installation option,
the LAN is recognized, but WLAN is not.

If I start a shell from the installer, I can see that the necessary
module rtl8xxxu is loaded (the same one that is loaded in live option).
So I guess it is a firmware issue. How can I get an installer with
non-free firmware (if that is the problem)?
I just found one page that says the (non-free?) FW is always included
in the images (starting from bookworm). Is that true?
Any other idea?

Many Thanks and Best Regards,
Felix
-- 
Felix Natter

Re: ip link versus nmcli device, WIFI

2024-01-23 Thread Max Nikulin


On 24/01/2024 04:18, Geert Stappers wrote:

|root@nero:~# nmcli device | grep -e wifi -e gsm
|ttyACM1   gsm   unavailable --
|wlp2s0wifi  unavailable --


If the devices are hard-blocked then you may need to enable them in 
firmware (BIOS) setup. Old laptop models may have a hardware switch. 
Whether Fn+something or a dedicated key works, depends on particular 
implementation. Running various commands you may change state of soft 
block, but at first you need to get it "hard" unblocked.

Re: ip link versus nmcli device, WIFI

2024-01-23 Thread Geert Stappers

On Mon, Jan 22, 2024 at 06:36:57AM +0200, Anssi Saari wrote:
> Geert Stappers  writes:
> >
> > Here on a laptop does `ip link` see a WIFI device,
> > but `nmcli device` does not.
> 
> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
> sometimes comes up with a wwx ID like that, sometimes wwan0.

Oh, yes.  Oops.  The wwx028037ec0200 is indeed "GSM Modem".


Below output from the original machine,  WITH  firmware installed.

|root@nero:~# ip --brief link show | grep ^w
|wwx028037ec0200  DOWN   02:80:37:ec:02:00  
|wlp2s0   DOWN   da:eb:4f:4d:b7:5e  
|root@nero:~# nmcli device | grep -e wifi -e gsm
|ttyACM1   gsm   unavailable -- 
|wlp2s0wifi  unavailable -- 
|root@nero:~#


Thanks for pointing out.

 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: ip link versus nmcli device, WIFI

2024-01-23 Thread Anssi Saari

David Wright  writes:

> On Mon 22 Jan 2024 at 06:36:57 (+0200), Anssi Saari wrote:

>> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
>> sometimes comes up with a wwx ID like that, sometimes wwan0. I even
>> explicitly rename it to wwan0 if that happens to make life easier.
>
> I think that's a different device, for use with mobile networks.
> AIUI that would involve a SIM card, and someone footing the bill.

That's what a WWAN device usually is today.

Re: ip link versus nmcli device, WIFI

2024-01-23 Thread David Wright

On Mon 22 Jan 2024 at 06:36:57 (+0200), Anssi Saari wrote:
> Geert Stappers  writes:
> >
> > Here on a laptop does `ip link` see a WIFI device,
> > but `nmcli device` does not.
> 
> And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
> sometimes comes up with a wwx ID like that, sometimes wwan0. I even
> explicitly rename it to wwan0 if that happens to make life easier.

I think that's a different device, for use with mobile networks.
AIUI that would involve a SIM card, and someone footing the bill.

Of course, it's always possible that distant memories of such usage,
now elapsed, could lead one to suppose that the machine had been
wifi-connected when it hadn't. In our household, we were using WWAN
long before WiFi, when I was still in the world of 33.6 modems.

Cheers,
David.

Re: ip link versus nmcli device, WIFI

2024-01-21 Thread Anssi Saari

Geert Stappers  writes:

> Hello,
>
>
>
> Here on a laptop does `ip link` see a WIFI device,
> but `nmcli device` does not.

And you're sure wwx028037ec0200 is a WIFI device? My WWAN device
sometimes comes up with a wwx ID like that, sometimes wwan0. I even
explicitly rename it to wwan0 if that happens to make life easier.

Re: Regarding: ip link versus nmcli device, WIFI

2024-01-21 Thread David Wright

On Sun 21 Jan 2024 at 18:24:53 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 05:34:53PM +0100, Marco Moock wrote:
> > Am 21.01.2024 um 17:21:13 Uhr schrieb Geert Stappers privat:
> > 
> > > It was a firmware thing.
> > 
> > How did you solve it?
> > 
> 
> In the private[1] message was, besides 'Hello Marco':

I can see that you might consider that a hint, but
few here or elsewhere would take that greeting into
account as to whether a message is private or otherwise.
That's why I normally clear all the salutations, closing
compliments and signatures from my replies.

> } } Will reporting also to the ML
> 
> 
> That report became https://lists.debian.org/debian-user/2024/01/msg01038.html
> 
> 
> This message now adds to the mailinglist archive
> that Marco Moock felt 2024-01-21 it a "good thing" to reply on-list
> to something that was send off-list.
> 
> Yeah, I'm **not amused** about the "you MUST tell it to others"
> 
> 
> Time will tell if there will future misbehaviours like that.
> [1] non-public. However, "private" is a much more complex concept.

Are you saying that "It was a firmware thing."
was private? I don't see any other information in
https://lists.debian.org/debian-user/2024/01/msg01039.html

Cheers,
David.

Re: ip link versus nmcli device, WIFI firmware related

2024-01-21 Thread David Wright

On Mon 22 Jan 2024 at 00:05:08 (+0700), Max Nikulin wrote:
> On 21/01/2024 23:33, Geert Stappers wrote:
> > The repair:
> > 
> > wget 
> > http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb
> > 
> > sudo dpkg -i firmware-iwlwifi_20210315-3_all.deb
> 
> https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split
> Chapter 5. Issues to be aware of for bookworm
> 5.1.1.  Non-free firmware moved to its own component in the archive
> 
> the updated APT source-list entry could look like:
> 
> deb https://deb.debian.org/debian bookworm main non-free-firmware

The firmware iwlwifi-1000-5.ucode is the same in both suites,
so the problem will be found more quickly, but not fixed by
the update.

Cheers,
David.

Re: Regarding: ip link versus nmcli device, WIFI

On Sun, Jan 21, 2024 at 05:34:53PM +0100, Marco Moock wrote:
> Am 21.01.2024 um 17:21:13 Uhr schrieb Geert Stappers privat:
> 
> > It was a firmware thing.
> 
> How did you solve it?
> 

In the private[1] message was, besides 'Hello Marco':

} } Will reporting also to the ML

That report became https://lists.debian.org/debian-user/2024/01/msg01038.html

This message now adds to the mailinglist archive
that Marco Moock felt 2024-01-21 it a "good thing" to reply on-list
to something that was send off-list.

Yeah, I'm **not amused** about the "you MUST tell it to others"

Time will tell if there will future misbehaviours like that.

Groeten
Geert Stappers
[1] non-public. However, "private" is a much more complex concept.
-- 
Silence is hard to parse

Re: ip link versus nmcli device, WIFI firmware related

2024-01-21 Thread Max Nikulin


On 21/01/2024 23:33, Geert Stappers wrote:

The repair:

wget 
http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb

sudo dpkg -i firmware-iwlwifi_20210315-3_all.deb


https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split
Chapter 5. Issues to be aware of for bookworm
5.1.1.  Non-free firmware moved to its own component in the archive

the updated APT source-list entry could look like:

deb https://deb.debian.org/debian bookworm main non-free-firmware

Re: ip link versus nmcli device, WIFI firmware related

2024-01-21 Thread David Wright

On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> [7.854942] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
> [7.860452] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
> [8.356275] iwlwifi :02:00.0 wlp2s0: renamed from wlan0

Run rfkill and, if it's blocked, unblock it.

Cheers,
David.

Re: Regarding: ip link versus nmcli device, WIFI

2024-01-21 Thread Marco Moock

Am 21.01.2024 um 17:21:13 Uhr schrieb Geert Stappers:

> It was a firmware thing.

How did you solve it?

Re: ip link versus nmcli device, WIFI firmware related

On Sun, Jan 21, 2024 at 03:58:18PM +0100, Geert Stappers wrote:
> 
> Hello,
> 
> 
> 
> Here on a laptop does `ip link` see a WIFI device,
> but `nmcli device` does not.
> 
> How to make NetworkManager aware of a WIFI device?
> 

Have the firmware for WIFI card installed.


What follows are the "before"  and "after".

And inbetween the "how it was found"  and "known good"

> 
> 
> root@nero:~# ip --brief link show
> lo   UNKNOWN00:00:00:00:00:00  
> enp8s0   UP 04:7d:7b:d4:3d:68 
>  
> wwx028037ec0200  DOWN   02:80:37:ec:02:00  
> flannel.1UNKNOWN9a:1c:92:d7:74:6e 
>  
> cni0 UP 9a:24:14:8e:7e:4f 
>  
> vethbb627e99@if2 UP c6:35:08:02:62:cf 
>  
> veth55e989ba@if2 UP fe:c2:75:81:20:d9 
>  
> simular_lines_deleted
> root@nero:~# ip --brief link show | grep ^w
> wwx028037ec0200  DOWN   02:80:37:ec:02:00  
> root@nero:~# nmcli radio wifi
> enabled
> root@nero:~# nmcli dev wifi
> root@nero:~# nmcli dev wwx028037ec0200
> Error: argument 'wwx028037ec0200' not understood. Try passing --help instead.
> root@nero:~# nmcli -f ALL dev wifi
> root@nero:~# ip link set dev wwx028037ec0200 up
> root@nero:~# ip --brief link show | grep ^w
> wwx028037ec0200  DOWN   02:80:37:ec:02:00 
>  
> root@nero:~# nmcli dev wifi
> root@nero:~# nmcli radio wifi
> enabled
> root@nero:~# nmcli dev wifi rescan
> Error: No Wi-Fi device found.
> root@nero:~# nmcli dev
> DEVICETYPE  STATE   CONNECTION 
> enp8s0ethernet  connected   Wired connection 1 
> cni0  bridgeconnected (externally)  cni0   
> flannel.1 vxlan connected (externally)  flannel.1  
> ttyACM1   gsm   unavailable -- 
> veth030c0908  ethernet  unmanaged   -- 
> veth55e989ba  ethernet  unmanaged   -- 
> simular_lines_deleted
> loloopback  unmanaged   -- 
> root@nero:~# 
> 
> 

How found

root@nero:~# dmesg | grep -i -e wifi -e 802.11
[7.700933] Intel(R) Wireless WiFi driver for Linux
[7.701191] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[7.702758] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-1000-5.ucode (-2)
[7.707186] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-1000-5.ucode failed with error -2
[7.707245] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-1000-4.ucode (-2)
[7.709490] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-1000-4.ucode failed with error -2
[7.709539] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-1000-3.ucode (-2)
[7.712091] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-1000-3.ucode failed with error -2
[7.716667] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-1000-2.ucode (-2)
[7.721228] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-1000-2.ucode failed with error -2
[7.722201] iwlwifi :02:00.0: firmware: failed to load 
iwlwifi-1000-1.ucode (-2)
[7.724465] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-1000-1.ucode failed with error -2
[7.724480] iwlwifi :02:00.0: minimum version required: iwlwifi-1000-1
[7.726733] iwlwifi :02:00.0: maximum version supported: iwlwifi-1000-5
[7.729207] iwlwifi :02:00.0: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
root@nero:~# 



The repair:

wget 
http://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210315-3_all.deb


sudo dpkg -i firmware-iwlwifi_20210315-3_all.deb

reboot was needed


root@nero:~# dmesg | grep -i -e wifi -e 802.11
[7.523821] Intel(R) Wireless WiFi driver for Linux
[7.524061] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[7.530205] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-1000-5.ucode
[7.530438] iwlwifi :02:00.0: loaded firmware version 39.31.5.1 build 
35138 1000-5.ucode op_mode iwldvm
[7.530482] iwlwifi :02:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[7.841311] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[7.841316] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[7.841320] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[7.841324] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 
1000 BGN, REV=0x6C
[7.854942] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[7.860452] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[8.356275] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
root@nero:~# nmcli device
DEVICET

Re: ip link versus nmcli device, WIFI

2024-01-21 Thread Marco Moock

Am 21.01.2024 um 16:36:09 Uhr schrieb Geert Stappers:

> Even better   :-)
> 
> It doesn't exist in /etc/network

Is system-networkd being used?

How did you configure it in the past?

Re: ip link versus nmcli device, WIFI

On Sun, Jan 21, 2024 at 04:26:46PM +0100, Marco Moock wrote:
> Am 21.01.2024 um 15:58:18 Uhr schrieb Geert Stappers:
> 
> > How to make NetworkManager aware of a WIFI device?
> 
> Is the device commented out in /etc/network?
> 

Even better   :-)

It doesn't exist in /etc/network

|root@nero:/etc/network# cat interfaces
|# This file describes the network interfaces available on your system
|# and how to activate them. For more information, see interfaces(5).
|
|source /etc/network/interfaces.d/*
|
|# The loopback network interface
|auto lo
|iface lo inet loopback
|root@nero:/etc/network# ls interfaces.d/
|root@nero:/etc/network# 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: ip link versus nmcli device, WIFI

2024-01-21 Thread Marco Moock

Am 21.01.2024 um 15:58:18 Uhr schrieb Geert Stappers:

> How to make NetworkManager aware of a WIFI device?

Is the device commented out in /etc/network?

ip link versus nmcli device, WIFI



Hello,



Here on a laptop does `ip link` see a WIFI device,
but `nmcli device` does not.

How to make NetworkManager aware of a WIFI device?



root@nero:~# ip --brief link show
lo   UNKNOWN00:00:00:00:00:00  
enp8s0   UP 04:7d:7b:d4:3d:68 
 
wwx028037ec0200  DOWN   02:80:37:ec:02:00  
flannel.1UNKNOWN9a:1c:92:d7:74:6e 
 
cni0 UP 9a:24:14:8e:7e:4f 
 
vethbb627e99@if2 UP c6:35:08:02:62:cf 
 
veth55e989ba@if2 UP fe:c2:75:81:20:d9 
 
simular_lines_deleted
root@nero:~# ip --brief link show | grep ^w
wwx028037ec0200  DOWN   02:80:37:ec:02:00  
root@nero:~# nmcli radio wifi
enabled
root@nero:~# nmcli dev wifi
root@nero:~# nmcli dev wwx028037ec0200
Error: argument 'wwx028037ec0200' not understood. Try passing --help instead.
root@nero:~# nmcli -f ALL dev wifi
root@nero:~# ip link set dev wwx028037ec0200 up
root@nero:~# ip --brief link show | grep ^w
wwx028037ec0200  DOWN   02:80:37:ec:02:00 
 
root@nero:~# nmcli dev wifi
root@nero:~# nmcli radio wifi
enabled
root@nero:~# nmcli dev wifi rescan
Error: No Wi-Fi device found.
root@nero:~# nmcli dev
DEVICETYPE  STATE   CONNECTION 
enp8s0ethernet  connected   Wired connection 1 
cni0  bridgeconnected (externally)  cni0   
flannel.1 vxlan connected (externally)  flannel.1  
ttyACM1   gsm   unavailable -- 
veth030c0908  ethernet  unmanaged   -- 
veth55e989ba  ethernet  unmanaged   -- 
simular_lines_deleted
loloopback  unmanaged   -- 
root@nero:~# 



Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

Finalement le seul fait d'avoir intercalé le gs105e entre la LB6 et le reste 
semble résoudre le problème sans passer par les vlan ...

Gaëtan 

Le 6 janvier 2024 22:44:59 GMT+01:00, "Gaëtan Perrier"  
a écrit :
>Bonjour,
>
>Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
>sur la liste. ;)
>
>Mon problème est le suivant. Chez les parents d'un ami qui a des
>chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
>réseaux:
>- un réseau pour les proprio avec du Wifi et des périph filaires,
>- un réseau pour les clients uniquement en Wifi.
>
>On veut que les clients ne puissent pas accéder au réseau proprio.
>
>Actuellement on est installé le matériel suivant:
>- Livebox 6 Pro,
>- un switch GS105Ev2 derrière,
>- 3 AP Netgear WAX214
>- divers périph reliés en eth (RPI, PC, NAS,etc.)
>
>La LB6 est le routeur.
>
>Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
>clients.
>Le proprio est sur 192.168.1.* et le client configuré comme "invité"
>est sûr 192.168.200.*
>
>
>Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
>les RPI, PC, NAS, etc sur 192.168.1.* 
>
>Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
>place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
>GS105E et sur les AP.
>Mais là je perds la connexion et plus rien ne passe ...
>
>Qu'elle est la bonne solution ?
>
>Merci d'avance pour votre aide.
>
>Gaëtan
>

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

Le samedi 06 janvier 2024 à 23:49 +0100, MERLIN Philippe a écrit :
> Le samedi 6 janvier 2024, 23:24:09 CET Jérémy Prego a écrit :
> > Bonjour,
> > 
> > j'apporte pas forcément une réponse, mais j'ai des questions
> > 
> > Par hasard, quel est le mask réseau configuré que  ça soit sur le
> > 192.168.1.* et / ou le 192.168.200.* ?
> > 
> > Quel périphérique distribue les ip en 192.168.200.* ?
> > 
> > Concernant la perte du réseau quand des vlans
> > sont configurés, c'est normal, si la livebox ne fait pas de vlan,
> > qu'elle ne récupère pas le traffic qui vient du vlan en question.
> > 
> > Jerem
> > 
> > Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > > Bonjour,
> > > 
> > > Je fais un gros HS mais je suis sûr qu'il y a des personnes
> > > compétentes
> > > sur la liste. ;)
> > > 
> > > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > > réseaux:
> > > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > > - un réseau pour les clients uniquement en Wifi.
> > > 
> > > On veut que les clients ne puissent pas accéder au réseau
> > > proprio.
> > > 
> > > Actuellement on est installé le matériel suivant:
> > > - Livebox 6 Pro,
> > > - un switch GS105Ev2 derrière,
> > > - 3 AP Netgear WAX214
> > > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > > 
> > > La LB6 est le routeur.
> > > 
> > > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un
> > > pour les
> > > clients.
> > > Le proprio est sur 192.168.1.* et le client configuré comme
> > > "invité"
> > > est sûr 192.168.200.*
> > > 
> > > 
> > > Le problème c'est que depuis le Wifi client (192.168.200.*) on
> > > voit les
> > > les RPI, PC, NAS, etc sur 192.168.1.*
> > > 
> > > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de
> > > mettre en
> > > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs
> > > sur le
> > > GS105E et sur les AP.
> > > Mais là je perds la connexion et plus rien ne passe ...
> > > 
> > > Qu'elle est la bonne solution ?
> > > 
> > > Merci d'avance pour votre aide.
> > > 
> > > Gaëtan
> Pourquoi faire compliqué quand on peut faire simple.
> On ajoute un routeur Wifi connecté en éthernet à ta Livebox qui
> gérera que les 
> clients le coût du routeur est très faible.
> Pour tes parents le réseau Wifi de la Livebox.
> Philippe Merlin

Non ça ne répond pas au besoin. Il y a 400m2 à couvrir avec les deux
réseaux. D'où les 3 AP (reliés en filaire).

Gaëtan

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread MERLIN Philippe

Le samedi 6 janvier 2024, 23:24:09 CET Jérémy Prego a écrit :
> Bonjour,
> 
> j'apporte pas forcément une réponse, mais j'ai des questions
> 
> Par hasard, quel est le mask réseau configuré que  ça soit sur le
> 192.168.1.* et / ou le 192.168.200.* ?
> 
> Quel périphérique distribue les ip en 192.168.200.* ?
> 
> Concernant la perte du réseau quand des vlans
> sont configurés, c'est normal, si la livebox ne fait pas de vlan,
> qu'elle ne récupère pas le traffic qui vient du vlan en question.
> 
> Jerem
> 
> Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > Bonjour,
> > 
> > Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
> > sur la liste. ;)
> > 
> > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > réseaux:
> > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > - un réseau pour les clients uniquement en Wifi.
> > 
> > On veut que les clients ne puissent pas accéder au réseau proprio.
> > 
> > Actuellement on est installé le matériel suivant:
> > - Livebox 6 Pro,
> > - un switch GS105Ev2 derrière,
> > - 3 AP Netgear WAX214
> > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > 
> > La LB6 est le routeur.
> > 
> > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
> > clients.
> > Le proprio est sur 192.168.1.* et le client configuré comme "invité"
> > est sûr 192.168.200.*
> > 
> > 
> > Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
> > les RPI, PC, NAS, etc sur 192.168.1.*
> > 
> > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
> > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
> > GS105E et sur les AP.
> > Mais là je perds la connexion et plus rien ne passe ...
> > 
> > Qu'elle est la bonne solution ?
> > 
> > Merci d'avance pour votre aide.
> > 
> > Gaëtan
Pourquoi faire compliqué quand on peut faire simple.
On ajoute un routeur Wifi connecté en éthernet à ta Livebox qui gérera que les 
clients le coût du routeur est très faible.
Pour tes parents le réseau Wifi de la Livebox.
Philippe Merlin

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

Le samedi 06 janvier 2024 à 23:24 +0100, Jérémy Prego a écrit :
> Bonjour,
> 
> j'apporte pas forcément une réponse, mais j'ai des questions
> 
> Par hasard, quel est le mask réseau configuré que  ça soit sur le 
> 192.168.1.* et / ou le 192.168.200.* ?

255.255.255.0 pour les deux.

> 
> Quel périphérique distribue les ip en 192.168.200.* ?

L'AP WAX214

> Concernant la perte du réseau quand des vlans
> sont configurés, c'est normal, si la livebox ne fait pas de vlan, 
> qu'elle ne récupère pas le traffic qui vient du vlan en question.

Ça veut dire qu'il faudrait mettre un routeur VLAN derrière la LB6 ?
Est-ce qu'il faut aussi que tous les switchs intermédiaires soient VLAN
compatibles ?

Existe-t'il une solution pour isoler les deux réseaux sans VLAN ?

Gaëtan 


> 
> Jerem
> Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :
> > Bonjour,
> > 
> > Je fais un gros HS mais je suis sûr qu'il y a des personnes
> > compétentes
> > sur la liste. ;)
> > 
> > Mon problème est le suivant. Chez les parents d'un ami qui a des
> > chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
> > réseaux:
> > - un réseau pour les proprio avec du Wifi et des périph filaires,
> > - un réseau pour les clients uniquement en Wifi.
> > 
> > On veut que les clients ne puissent pas accéder au réseau proprio.
> > 
> > Actuellement on est installé le matériel suivant:
> > - Livebox 6 Pro,
> > - un switch GS105Ev2 derrière,
> > - 3 AP Netgear WAX214
> > - divers périph reliés en eth (RPI, PC, NAS,etc.)
> > 
> > La LB6 est le routeur.
> > 
> > Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour
> > les
> > clients.
> > Le proprio est sur 192.168.1.* et le client configuré comme
> > "invité"
> > est sûr 192.168.200.*
> > 
> > 
> > Le problème c'est que depuis le Wifi client (192.168.200.*) on voit
> > les
> > les RPI, PC, NAS, etc sur 192.168.1.*
> > 
> > Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre
> > en
> > place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur
> > le
> > GS105E et sur les AP.
> > Mais là je perds la connexion et plus rien ne passe ...
> > 
> > Qu'elle est la bonne solution ?
> > 
> > Merci d'avance pour votre aide.
> > 
> > Gaëtan
> > 
>

Re: [HS][HELP] Livebox 6, AP WIFI & VLAN

2024-01-06 Thread Jérémy Prego


Bonjour,

j'apporte pas forcément une réponse, mais j'ai des questions

Par hasard, quel est le mask réseau configuré que  ça soit sur le 
192.168.1.* et / ou le 192.168.200.* ?


Quel périphérique distribue les ip en 192.168.200.* ?

Concernant la perte du réseau quand des vlans
sont configurés, c'est normal, si la livebox ne fait pas de vlan, 
qu'elle ne récupère pas le traffic qui vient du vlan en question.


Jerem
Le 06/01/2024 à 22:44, Gaëtan Perrier a écrit :

Bonjour,

Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
sur la liste. ;)

Mon problème est le suivant. Chez les parents d'un ami qui a des
chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
réseaux:
- un réseau pour les proprio avec du Wifi et des périph filaires,
- un réseau pour les clients uniquement en Wifi.

On veut que les clients ne puissent pas accéder au réseau proprio.

Actuellement on est installé le matériel suivant:
- Livebox 6 Pro,
- un switch GS105Ev2 derrière,
- 3 AP Netgear WAX214
- divers périph reliés en eth (RPI, PC, NAS,etc.)

La LB6 est le routeur.

Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
clients.
Le proprio est sur 192.168.1.* et le client configuré comme "invité"
est sûr 192.168.200.*


Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
les RPI, PC, NAS, etc sur 192.168.1.*

Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
GS105E et sur les AP.
Mais là je perds la connexion et plus rien ne passe ...

Qu'elle est la bonne solution ?

Merci d'avance pour votre aide.

Gaëtan

[HS][HELP] Livebox 6, AP WIFI & VLAN

Bonjour,

Je fais un gros HS mais je suis sûr qu'il y a des personnes compétentes
sur la liste. ;)

Mon problème est le suivant. Chez les parents d'un ami qui a des
chambres d'hôtes on veut couvrir l'ensemble de la maison avec 2
réseaux:
- un réseau pour les proprio avec du Wifi et des périph filaires,
- un réseau pour les clients uniquement en Wifi.

On veut que les clients ne puissent pas accéder au réseau proprio.

Actuellement on est installé le matériel suivant:
- Livebox 6 Pro,
- un switch GS105Ev2 derrière,
- 3 AP Netgear WAX214
- divers périph reliés en eth (RPI, PC, NAS,etc.)

La LB6 est le routeur.

Sur les WAX214 2 SSID sont configurés: un pour les proprio,un pour les
clients.
Le proprio est sur 192.168.1.* et le client configuré comme "invité"
est sûr 192.168.200.*


Le problème c'est que depuis le Wifi client (192.168.200.*) on voit les
les RPI, PC, NAS, etc sur 192.168.1.* 

Pour isoler les 2, la LB6 ne faisant pas VLAN, j'ai tenté de mettre en
place des VLAN en activant la fonctionnalité 802.1Q-based VLANs sur le
GS105E et sur les AP.
Mais là je perds la connexion et plus rien ne passe ...

Qu'elle est la bonne solution ?

Merci d'avance pour votre aide.

Gaëtan

WiFi issue on Bullseye

2023-12-21 Thread Andrea Neroni


Dear all,
I am having issues with my laptop wifi (Debian Bullseye). The connection comes 
and goes making using internet impossible.I assumed a firmware problem, so I 
tried several versions of the firmware-iwlwifi.deb package without 
improvements.Specifically I tried the versions 20190114, 20210315-3 and 
currently 20230210-5 from Bookworm.
>From the /var/log/messages file I keep finding entries like
Dec 21 16:48:53 hellnote02 kernel: [  309.357125] wlp2s0: authenticate with 
1c:ed:6f:f6:06:d2Dec 21 16:48:53 hellnote02 kernel: [  309.360810] wlp2s0: send 
auth to 1c:ed:6f:f6:06:d2 (try 1/3)Dec 21 16:48:53 hellnote02 kernel: [  
309.364095] wlp2s0: authenticatedDec 21 16:48:53 hellnote02 kernel: [  
309.367660] wlp2s0: associate with 1c:ed:6f:f6:06:d2 (try 1/3)Dec 21 16:48:53 
hellnote02 kernel: [  309.377138] wlp2s0: RX AssocResp from 1c:ed:6f:f6:06:d2 
(capab=0x1431 status=0 aid=1)Dec 21 16:48:53 hellnote02 kernel: [  309.382335] 
wlp2s0: associatedDec 21 16:48:53 hellnote02 gnome-shell[1231]: An active 
wireless connection, in infrastructure mode, involves no access point?Dec 21 
16:49:21 hellnote02 kernel: [  337.696611] wlp2s0: authenticate with 
b0:f2:08:c3:d9:21Dec 21 16:49:21 hellnote02 kernel: [  337.698907] wlp2s0: send 
auth to b0:f2:08:c3:d9:21 (try 1/3)Dec 21 16:49:21 hellnote02 kernel: [  
337.707314] wlp2s0: authenticatedDec 21 16:49:21 hellnote02 kernel: [  
337.711160] wlp2s0: associate with b0:f2:08:c3:d9:21 (try 1/3)Dec 21 16:49:21 
hellnote02 kernel: [  337.717298] wlp2s0: RX AssocResp from b0:f2:08:c3:d9:21 
(capab=0x1431 status=0 aid=1)Dec 21 16:49:21 hellnote02 kernel: [  337.722306] 
wlp2s0: associatedDec 21 16:49:21 hellnote02 gnome-shell[1231]: An active 
wireless connection, in infrastructure mode, involves no access point?Dec 21 
16:49:21 hellnote02 gnome-shell[1231]: An active wireless connection, in 
infrastructure mode, involves no access point?Dec 21 16:49:21 hellnote02 
gnome-shell[1231]: An active wireless connection, in infrastructure mode, 
involves no access point?
while from dmesg
[  309.357125] wlp2s0: authenticate with 1c:ed:6f:f6:06:d2[  309.360810] 
wlp2s0: send auth to 1c:ed:6f:f6:06:d2 (try 1/3)[  309.364095] wlp2s0: 
authenticated[  309.367660] wlp2s0: associate with 1c:ed:6f:f6:06:d2 (try 1/3)[ 
 309.377138] wlp2s0: RX AssocResp from 1c:ed:6f:f6:06:d2 (capab=0x1431 status=0 
aid=1)[  309.382335] wlp2s0: associated[  309.849855] wlp2s0: Limiting TX power 
to 20 (20 - 0) dBm as advertised by 1c:ed:6f:f6:06:d2[  337.696611] wlp2s0: 
authenticate with b0:f2:08:c3:d9:21[  337.698907] wlp2s0: send auth to 
b0:f2:08:c3:d9:21 (try 1/3)[  337.707314] wlp2s0: authenticated[  337.711160] 
wlp2s0: associate with b0:f2:08:c3:d9:21 (try 1/3)[  337.717298] wlp2s0: RX 
AssocResp from b0:f2:08:c3:d9:21 (capab=0x1431 status=0 aid=1)[  337.722306] 
wlp2s0: associated[  337.723407] wlp2s0: Limiting TX power to 20 (20 - 0) dBm 
as advertised by b0:f2:08:c3:d9:21
Note that I have several devices connected to the same wifi (computers and 
phones) with no issues.
Any experience with this problem?
Thanks and kind regards,Andrea

wifi issue on bullseye

2023-12-21 Thread Andrea Neroni

Dear all,
I am having issues with my laptop wifi (Debian Bullseye). The connection comes 
and goes making using internet impossible.I assumed a firmware problem, so I 
tried several versions of the firmware-iwlwifi.deb package without 
improvements.Specifically I tried the versions 20190114, 20210315-3 and 
currently 20230210-5 from Bookworm.
>From the /var/log/messages file I keep finding entries like
Dec 21 16:48:53 hellnote02 kernel: [  309.357125] wlp2s0: authenticate with 
1c:ed:6f:f6:06:d2Dec 21 16:48:53 hellnote02 kernel: [  309.360810] wlp2s0: send 
auth to 1c:ed:6f:f6:06:d2 (try 1/3)Dec 21 16:48:53 hellnote02 kernel: [  
309.364095] wlp2s0: authenticatedDec 21 16:48:53 hellnote02 kernel: [  
309.367660] wlp2s0: associate with 1c:ed:6f:f6:06:d2 (try 1/3)Dec 21 16:48:53 
hellnote02 kernel: [  309.377138] wlp2s0: RX AssocResp from 1c:ed:6f:f6:06:d2 
(capab=0x1431 status=0 aid=1)Dec 21 16:48:53 hellnote02 kernel: [  309.382335] 
wlp2s0: associatedDec 21 16:48:53 hellnote02 gnome-shell[1231]: An active 
wireless connection, in infrastructure mode, involves no access point?Dec 21 
16:49:21 hellnote02 kernel: [  337.696611] wlp2s0: authenticate with 
b0:f2:08:c3:d9:21Dec 21 16:49:21 hellnote02 kernel: [  337.698907] wlp2s0: send 
auth to b0:f2:08:c3:d9:21 (try 1/3)Dec 21 16:49:21 hellnote02 kernel: [  
337.707314] wlp2s0: authenticatedDec 21 16:49:21 hellnote02 kernel: [  
337.711160] wlp2s0: associate with b0:f2:08:c3:d9:21 (try 1/3)Dec 21 16:49:21 
hellnote02 kernel: [  337.717298] wlp2s0: RX AssocResp from b0:f2:08:c3:d9:21 
(capab=0x1431 status=0 aid=1)Dec 21 16:49:21 hellnote02 kernel: [  337.722306] 
wlp2s0: associatedDec 21 16:49:21 hellnote02 gnome-shell[1231]: An active 
wireless connection, in infrastructure mode, involves no access point?Dec 21 
16:49:21 hellnote02 gnome-shell[1231]: An active wireless connection, in 
infrastructure mode, involves no access point?Dec 21 16:49:21 hellnote02 
gnome-shell[1231]: An active wireless connection, in infrastructure mode, 
involves no access point?
while from dmesg
[  309.357125] wlp2s0: authenticate with 1c:ed:6f:f6:06:d2[  309.360810] 
wlp2s0: send auth to 1c:ed:6f:f6:06:d2 (try 1/3)[  309.364095] wlp2s0: 
authenticated[  309.367660] wlp2s0: associate with 1c:ed:6f:f6:06:d2 (try 1/3)[ 
 309.377138] wlp2s0: RX AssocResp from 1c:ed:6f:f6:06:d2 (capab=0x1431 status=0 
aid=1)[  309.382335] wlp2s0: associated[  309.849855] wlp2s0: Limiting TX power 
to 20 (20 - 0) dBm as advertised by 1c:ed:6f:f6:06:d2[  337.696611] wlp2s0: 
authenticate with b0:f2:08:c3:d9:21[  337.698907] wlp2s0: send auth to 
b0:f2:08:c3:d9:21 (try 1/3)[  337.707314] wlp2s0: authenticated[  337.711160] 
wlp2s0: associate with b0:f2:08:c3:d9:21 (try 1/3)[  337.717298] wlp2s0: RX 
AssocResp from b0:f2:08:c3:d9:21 (capab=0x1431 status=0 aid=1)[  337.722306] 
wlp2s0: associated[  337.723407] wlp2s0: Limiting TX power to 20 (20 - 0) dBm 
as advertised by b0:f2:08:c3:d9:21
Note that I have several devices connected to the same wifi (computers and 
phones) with zero issues.

Any experience with this problem?
Thanks and kind regards,Andrea

Re: connect two hosts over wifi without router?

2023-11-27 Thread Tim Woodall


On Mon, 27 Nov 2023, Hans wrote:


Hi folks,

just before I am trying forever:

Is it possible, to connect two hosts directly over wlan without using a
router?



Yes. It's called adhoc networking. No AP, no router, just two wifi cards
acting as a ptp link.

But I doubt you can do it other than by low level commands.

I have done it in the past when trying to connect two points via a very
marginal link but I don't recall details. At some point I'll boot up my
eeepc and see if I still have scripts around - if nobody else sorts your
problem.

Re: connect two hosts over wifi without router?

2023-11-27 Thread Jeffrey Walton

On Mon, Nov 27, 2023 at 2:11 PM Hans  wrote:
>
> Hi folks,
>
> just before I am trying forever:
>
> Is it possible, to connect two hosts directly over wlan without using a
> router?
>
> The background: I want to stream video from my drone using RTMP to my
> notebook.
>
> This is already possible, when i am using a router. But in the fields, I got 
> no
> router available (I have a portable router, yes, but I want to mimize and ease
> as possible).
>
> The goal of my project I am working of, shall be a bootable live-usb or live-
> cd, which is preconfigured with the network address, a listening nginx for
> RTMP, automatically started X with automatically started VLC.
>
> The user just has to start his drone software (or whatever) on a tablet or
> mobile, input an IP in the streaming software and is ready.
>
> Everything shall be done without any router (because of avoiding as much
> latencies as possible).
>
> At the moment I am stuck with the directly connection.
>
> If someone has running this already, I would be happy for any configurations,
> or also with the help of some priciples.
>
> With an ethernet cable, this is easy (using a crossover ethernet cable), but
> how do this with wireless? Is this technically possible at all???

I think you want an ad-hoc wifi network. It is a peer to peer network
using Independent Basic Service Set (IBSS). See
<https://wiki.archlinux.org/title/ad-hoc_networking> and more
generally <https://www.google.com/search?q=linux+wifi+create+adhoc+network>.

Jeff

Re: connect two hosts over wifi without router?

2023-11-27 Thread Anssi Saari

Hans  writes:

> Hi folks,
>
> hmm, looks like the only way is using a hotspot, either one as a vitual one 
> using hostapd (or some similar software). 

I don't know much about drones but even a cursory look seemed to
indicate some drones can act as wifi hotspots themselves? And newer
drones support Wifi Direct but that doesn't help you since Wifi Direct
isn't usually supported on PCs. It's common on mobile devices running
Android or iOS.

Re: connect two hosts over wifi without router?

2023-11-27 Thread hw

On Mon, 2023-11-27 at 17:48 +0100, Hans wrote:
> Hi folks,
> 
> hmm, looks like the only way is using a hotspot, either one as a vitual one 
> using hostapd (or some similar software). 
> 
> But this is just what I wanted to avoid, as every software between
> streaming device and receiving device will cause delays (which I
> also get when using a router

To minimize delays, you could use a recording device on the drone
(Don't they record by default?); or put a dashcam or something similar
on it that can record.

Are there are any recording devices that don't use software and do
everything in hardware instead?  They did that in the past, i. e. you
might have to use film for that.

What does it matter when it takes a few milliseconds before the data
reaches the recording device?  It's just a recrding.  As long as you
are under 10ms, you can have phone conversations without the delays
getting to long.  Is there someone in the air somewhere you need to
talk to through a drone?

You could use (thin) wires instead.  Wires make for better connections
than radio waves alone do, and you can have it as real-time as it
gets, and even analog.

> i.e. some Fritz!Box

Those are the worst junk you can get; avoid them.  Letting all their
other problems aside, they're designed solely to save energy, not for
any kind of performance.

> or similar).
>
> So at the moment it looks like there is no "wireless-crossover-connection". I 
> also never heard of it, that it is possible at all. 
> 
> Well, still keep searching. At the moment I am falling back to the combination
> 
> Host 1 > AP -> Host 2
> 
> Thanks for all the help. See it as solved, but I will let this question some 
> time open, and then mark it as [SOLVED] in a few days.
> 
> Best regards
> 
> 
> Hans 
> 
> 
> 
>

Re: connect two hosts over wifi without router?

2023-11-27 Thread Hans

Hi folks,

hmm, looks like the only way is using a hotspot, either one as a vitual one 
using hostapd (or some similar software). 

But this is just what I wanted to avoid, as every software between streaming 
device and receiving device will cause delays (which I also get when using a 
router i.e. some Fritz!Box or similar).

So at the moment it looks like there is no "wireless-crossover-connection". I 
also never heard of it, that it is possible at all. 

Well, still keep searching. At the moment I am falling back to the combination

Host 1 > AP -> Host 2

Thanks for all the help. See it as solved, but I will let this question some 
time open, and then mark it as [SOLVED] in a few days.

Best regards


Hans

Re: connect two hosts over wifi without router?

2023-11-27 Thread Dan Ritter

Hans wrote: 
> Is it possible, to connect two hosts directly over wlan without using a 
> router?

Sometimes. The capability is called Ad-Hoc mode.

If you have two Linux machines with wifi NICs that support it,
you can do it.

If one of the hosts is a drone, it might not be capable of that.

Instead, some wifi NICs support host mode on the Linux side,
which turns your Linux machine into an access point. That might
be just as good.

The package you want is hostapd.

-dsr-

Re: connect two hosts over wifi without router?

2023-11-27 Thread tomas

On Mon, Nov 27, 2023 at 03:06:40PM +0100, hw wrote:
> On Mon, 2023-11-27 at 14:54 +0100, Hans wrote:
> > Hi folks,
> > 
> > just before I am trying forever:
> > 
> > Is it possible, to connect two hosts directly over wlan without using a 
> > router?
> 
> You don't need a router for it; you can do it via an access point.

...and as others have said, you might set your laptop up as an access
point, so you possibly don't need extra hardware. Hostapd is the program
to do the magic [0]. As people have said here, you need your WiFi
adapter to play along, not everyone seems willing to.

And then, there is WiFi Ad Hoc, here [1] in the Debian context. No idea
whether this would work with any WiFi hardware.

Cheers

[0] https://packages.debian.org/stable/hostapd
[1] https://wiki.debian.org/WiFi/AdHoc
-- 
t

signature.asc
Description: PGP signature

Re: connect two hosts over wifi without router?

2023-11-27 Thread Joel Roth

On Mon, Nov 27, 2023 at 02:54:44PM +0100, Hans wrote:
> Hi folks,
> 
> just before I am trying forever:
> 
> Is it possible, to connect two hosts directly over wlan without using a 
> router?
> 
> The background: I want to stream video from my drone using RTMP to my 
> notebook. 
> 
> This is already possible, when i am using a router. But in the fields, I got 
> no 
> router available (I have a portable router, yes, but I want to mimize and 
> ease 
> as possible). 
> 
> The goal of my project I am working of, shall be a bootable live-usb or live-
> cd, which is preconfigured with the network address, a listening nginx for 
> RTMP, automatically started X with automatically started VLC.
> 
> The user just has to start his drone software (or whatever) on a tablet or 
> mobile, input an IP in the streaming software and is ready.
> 
> Everything shall be done without any router (because of avoiding as much 
> latencies as possible).
> 
> At the moment I am stuck with the directly connection.
> 
> If someone has running this already, I would be happy for any configurations, 
> or also with the help of some priciples. 
> 
> With an ethernet cable, this is easy (using a crossover ethernet cable), but 
> how do this with wireless? Is this technically possible at all???
> 
> Thanks for any help.
> 
> Best regards
> 
> Hans 
 
Probably there are a lot more knowledgeable people here than
myself, but a naive search for "wifi adapter client host
mode linux" brings up this page.

https://woshub.com/create-wi-fi-access-point-hotspot-linux/

Most wifi adapters can operate as an access point, which is
indicated by AP and AP/VLAN appearing in the output of `iw list`.

Hope this helps


-- 
Joel Roth

Re: connect two hosts over wifi without router?

2023-11-27 Thread Joe

On Mon, 27 Nov 2023 14:54:44 +0100
Hans  wrote:

> Hi folks,
> 
> just before I am trying forever:
> 
> Is it possible, to connect two hosts directly over wlan without using
> a router?
> 
> The background: I want to stream video from my drone using RTMP to my 
> notebook. 
> 
> This is already possible, when i am using a router. But in the
> fields, I got no router available (I have a portable router, yes, but
> I want to mimize and ease as possible). 
> 
> The goal of my project I am working of, shall be a bootable live-usb
> or live- cd, which is preconfigured with the network address, a
> listening nginx for RTMP, automatically started X with automatically
> started VLC.
> 
> The user just has to start his drone software (or whatever) on a
> tablet or mobile, input an IP in the streaming software and is ready.
> 
> Everything shall be done without any router (because of avoiding as
> much latencies as possible).
> 
> At the moment I am stuck with the directly connection.
> 
> If someone has running this already, I would be happy for any
> configurations, or also with the help of some priciples. 
> 
> With an ethernet cable, this is easy (using a crossover ethernet
> cable), but how do this with wireless? Is this technically possible
> at all???
> 
>
Have a look at this: (your wifi adaptor must be capable of access point
mode, or you need to buy a dongle that is).

https://owlhowto.com/how-to-create-a-wifi-hotspot-on-debian-12/

Note: I've never done this.

-- 
Joe

Re: connect two hosts over wifi without router?

2023-11-27 Thread hw

On Mon, 2023-11-27 at 14:54 +0100, Hans wrote:
> Hi folks,
> 
> just before I am trying forever:
> 
> Is it possible, to connect two hosts directly over wlan without using a 
> router?

You don't need a router for it; you can do it via an access point.
Something like a HP MSM430 or something from Aruba should do, and you
can find them for good prices on Ebay.  You'll need something to power
it, like a POE injector or a POE switch connected to a portable power
station or to an inverter connected to a car maybe.

And this is cheap enough to experiment with.


> 
> The background: I want to stream video from my drone using RTMP to my 
> notebook. 
> 
> This is already possible, when i am using a router. But in the fields, I got 
> no 
> router available (I have a portable router, yes, but I want to mimize and 
> ease 
> as possible). 
> 
> The goal of my project I am working of, shall be a bootable live-usb or live-
> cd, which is preconfigured with the network address, a listening nginx for 
> RTMP, automatically started X with automatically started VLC.
> 
> The user just has to start his drone software (or whatever) on a tablet or 
> mobile, input an IP in the streaming software and is ready.
> 
> Everything shall be done without any router (because of avoiding as much 
> latencies as possible).
> 
> At the moment I am stuck with the directly connection.
> 
> If someone has running this already, I would be happy for any configurations, 
> or also with the help of some priciples. 
> 
> With an ethernet cable, this is easy (using a crossover ethernet cable), but 
> how do this with wireless? Is this technically possible at all???
> 
> Thanks for any help.
> 
> Best regards
> 
> Hans 
> 
>  
> 
>

connect two hosts over wifi without router?

2023-11-27 Thread Hans

Hi folks,

just before I am trying forever:

Is it possible, to connect two hosts directly over wlan without using a 
router?

The background: I want to stream video from my drone using RTMP to my 
notebook. 

This is already possible, when i am using a router. But in the fields, I got no 
router available (I have a portable router, yes, but I want to mimize and ease 
as possible). 

The goal of my project I am working of, shall be a bootable live-usb or live-
cd, which is preconfigured with the network address, a listening nginx for 
RTMP, automatically started X with automatically started VLC.

The user just has to start his drone software (or whatever) on a tablet or 
mobile, input an IP in the streaming software and is ready.

Everything shall be done without any router (because of avoiding as much 
latencies as possible).

At the moment I am stuck with the directly connection.

If someone has running this already, I would be happy for any configurations, 
or also with the help of some priciples. 

With an ethernet cable, this is easy (using a crossover ethernet cable), but 
how do this with wireless? Is this technically possible at all???

Thanks for any help.

Best regards

Hans

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-09 Thread Max Nikulin


On 08/11/2023 20:39, Martin wrote:

Here is output from phone connected to WiFi setup program:
Default gateway: 192.168.231.3


It seems dnsmasq is able to serve reasonable settings with minimal 
configuration.



 chain postrouting {
 type nat hook postrouting priority srcnat; policy accept;
 ip saddr 192.168.231.0/24 oifname "wlxe8de27a5ab1c" masquerade


You had a rule that was working for you.

I do not see obvious issues with this one besides docker0 instances are 
likely inaccessible from the phone.



10:47:52.614642 enp3s0 In  IP 192.168.231.243.48257 > 192.168.231.3.53: 29809+ 
A? www.google.com. (32)
10:47:52.614851 wlxe8de27a5ab1c Out IP 192.168.0.16.34673 > 81.24.247.14.53: 
10155+ A? www.google.com. (32)
10:47:52.614902 wlxe8de27a5ab1c Out IP 192.168.0.16.34673 > 81.24.247.44.53: 
10155+ A? www.google.com. (32)
10:47:52.791389 wlxe8de27a5ab1c In  IP 81.24.247.14.53 > 192.168.0.16.34673: 
10155 1/0/0 A 142.251.208.132 (62)
10:47:52.791559 enp3s0 Out IP 192.168.231.3.53 > 192.168.231.243.48257: 29809 
1/0/0 A 142.251.208.132 (62)
10:47:52.794704 enp3s0 In  IP 192.168.231.243.46639 > 142.251.208.132.80: Flags 
[S], seq 4183167263, win 29200, options [mss 1460,sackOK,TS val 19413 ecr 
0,nop,wscale 6], length 0
10:47:52.846385 enp3s0 In  IP 192.168.231.243.46640 > 142.251.208.132.80: Flags 
[S], seq 1626803236, win 29200, options [mss 1460,sackOK,TS val 19418 ecr 
0,nop,wscale 6], length 0


Since packets from wlxe8de27a5ab1c to 142.251.208.132:80 are missed, 
perhaps IP forwarding is disabled or there is a blocking forwarding rule 
in the firewall. If I am not wrong, masquerading should affect source IP 
address of forwarded packets, but not their presence.



Warning: if you have not configured network interfaces for DHCP in dnsmasq
then do it. Otherwise other computers connected to the upstream WiFi link
may receive DHCP leases emitted from wlxe8de27a5ab1c.


Only thing I added to dnsmasq configuration is one line in
/etc/dnsmasq.d/myHomeDHCPrange file:
dhcp-range=192.168.231.241,192.168.231.254,12h


Dnsmasq may be smart enough to not send DHCP leases to interfaces with 
addresses inconsistent with the specified range, but I would still limit 
interfaces that dnsmasq listens to.


On 08/11/2023 21:30, Anssi Saari wrote:


systemctl start nftables.service

So if you're experimenting, you edit /etc/nftables.conf and after
editing run systemctl restart nftables.service


And be prepared that this command flushes away rules added by docker. It 
is a reason why earlier I suggested to create a dedicated file that may 
reload specific set of rules using "nft -f".


Current set of rules is more important than state of the service.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-09 Thread Anssi Saari

Martin  writes:

> I just enabled it (again) now:
> root@redmoon:~# systemctl enable nftables.service
> Created symlink /etc/systemd/system/sysinit.target.wants/nftables.service → 
> /lib/systemd/system/nftables.service.
> root@redmoon:~# systemctl status nftables.service
> ○ nftables.service - nftables
>  Loaded: loaded (/lib/systemd/system/nftables.service; enabled; preset: 
> enabled)
>  Active: inactive (dead)
>Docs: man:nft(8)
>  http://wiki.nftables.org

In case it's unclear, enabling a service just means it'll be started at
boot. In practice it just creates a symlink as shown above. If you want
to start the service manually you do

systemctl start nftables.service

So if you're experimenting, you edit /etc/nftables.conf and after
editing run systemctl restart nftables.service

Re: WiFi b/g/n

2023-11-08 Thread Marco M.

Am 08.11.2023 um 11:04:54 Uhr schrieb William Torrez Corea:

> 06:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless

|A highly integrated, all CMOS combo-chip for 2.4 GHz 802.11n wireless
|local area networks (WLANs) and Bluetooth 4 solution for PC
|applications.

https://www.qualcomm.com/products/internet-of-things/networking/wi-fi-networks/qca9565

You cannot use 5 GHz (nor 60 GHz) because it only support 2.4 GHz.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-08 Thread Martin

On Sun, Nov 05, 2023 at 10:55:12PM +0700, Max Nikulin wrote:
> It should be checked first and
> 
> journalctl -b -u nftables.service
> 
> alongside with searching for any nft messages in "journalctl -b". I
> suggested earlier to read /usr/share/doc/nftables/README.Debian It
> explicitly recommends to enable the service.

I just enabled it (again) now:
root@redmoon:~# systemctl enable nftables.service
Created symlink /etc/systemd/system/sysinit.target.wants/nftables.service → 
/lib/systemd/system/nftables.service.
root@redmoon:~# systemctl status nftables.service
○ nftables.service - nftables
 Loaded: loaded (/lib/systemd/system/nftables.service; enabled; preset: 
enabled)
 Active: inactive (dead)
   Docs: man:nft(8)
 http://wiki.nftables.org
root@redmoon:~# journalctl -b -u nftables.service
-- No entries --

> > 2: enp3s0:  mtu 1500 qdisc fq_codel state 
> > UP group default qlen 1000
> > inet 192.168.231.3/24 brd 192.168.231.255 scope global enp3s0
> 
> I hope, your router allows to view configuration received from the DHCP
> server. Since static addresses were working (and it can be rechecked), I
> guess, gateway is not explicitly configured, so the router tries to send
> packets to 192.168.231.1. Either change the interface IP or configure
> dnsmasq to send 192.168.231.3.

I think WiFi is configured properly (with automatic setup it does have same
settings as I did with manual settings)

Here is output from phone connected to WiFi setup program:
Connectino type: DHCP
 IP address: 192.168.231.243
Subnet mask: 255.255.255.0
Default gateway: 192.168.231.3
DNS: 192.168.231.3

Those are same values I was providing previously when I used manual setup too.

> To debug run wireshark or tcpdump on enp3s0 and wlxe8de27a5ab1c to check
> that packets from the phone are properly received and routed.

Well this is the part where my knowledge is thin as it can be, sadly.
I have read part of manual page for tcpdump, some web page with tutorials
and all I came with is to issue command:
$ sudo tcpdump -s 0 -i any -w  any-0.pcap
$ tcpdump -r any-0.pcap  > any-0.tcpdump

While tcpdump was recording what was going on network I issued those commands
from my phone:
connect to with browser: http://www.google.com
In terminal program that I downloaded on phone I issued those commands
(2 top ping worked third did not)
ping -c1 192.168.0.16
ping -c1 192.168.231.3
ping -c1 google.come
connect to with browser: http://192.168.231.3/test.html

The connection to www.google.com did not worked, but connection to my own
web server did showed test.html page (which I created for this)

I have run this commands 2 times once right after rebooting when my changes to
nftables where not done yet and second time after I added this to nftables:
table ip masqrule {
chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
ip saddr 192.168.231.0/24 oifname "wlxe8de27a5ab1c" masquerade
}
}

and here are the outputs of tcpdump (I did post them to pastebin as they are 
not tiny)
(tcpdump -r any-0-no_masq.pcap  > any-0-no_masq.tcpdump) (pastebinit -i 
any-0-no_masq.tcpdump)
https://paste.debian.net/hidden/be2f7994/
(tcpdump -r any-0.pcap  > any-0.tcpdump) (pastebinit -i any-0.tcpdump)
https://paste.debian.net/hidden/1589ec04/

There are also same outputs with '-n' (to print IP numbers instead of names) 
option too:
(tcpdump -r any-0-no_masq.pcap -n > any-0-no_masq-n.tcpdump) (pastebinit -i 
any-0-no_masq-n.tcpdump)
https://paste.debian.net/hidden/08ecfd39/
(tcpdump -r any-0.pcap -n > any-0-n.tcpdump) (pastebinit -i any-0-n.tcpdump)
https://paste.debian.net/hidden/a55e6f77/

Here is extract from https://paste.debian.net/hidden/a55e6f77/ that I thing is
doing connection to google:

10:47:52.614642 enp3s0 In  IP 192.168.231.243.48257 > 192.168.231.3.53: 29809+ 
A? www.google.com. (32)
10:47:52.614851 wlxe8de27a5ab1c Out IP 192.168.0.16.34673 > 81.24.247.14.53: 
10155+ A? www.google.com. (32)
10:47:52.614902 wlxe8de27a5ab1c Out IP 192.168.0.16.34673 > 81.24.247.44.53: 
10155+ A? www.google.com. (32)
10:47:52.791389 wlxe8de27a5ab1c In  IP 81.24.247.14.53 > 192.168.0.16.34673: 
10155 1/0/0 A 142.251.208.132 (62)
10:47:52.791559 enp3s0 Out IP 192.168.231.3.53 > 192.168.231.243.48257: 29809 
1/0/0 A 142.251.208.132 (62)
10:47:52.794704 enp3s0 In  IP 192.168.231.243.46639 > 142.251.208.132.80: Flags 
[S], seq 4183167263, win 29200, options [mss 1460,sackOK,TS val 19413 ecr 
0,nop,wscale 6], length 0
10:47:52.846385 enp3s0 In  IP 192.168.231.243.46640 > 142.251.208.132.80: Flags 
[S], seq 1626803236, win 29200, options [mss 1460,sackOK,TS val 19418 ecr 
0,nop,wscale 6], length 0
10:47:53.819034 enp3s0 In  IP 192.168.231.243.46639 > 142.251.208.132.80: Flags 
[S], seq 4183167263, win 29200, options [mss 1460,sackOK,TS va

Re: WiFi b/g/n

2023-11-07 Thread Jeffrey Walton

On Tue, Nov 7, 2023 at 10:16 PM William Torrez Corea
 wrote:
>
> I have WiFi b/g/n (email, browser, streaming, social network) apparently but 
> the device acts like WiFi 1 (email).
>
> Interface: 802.11 WiFi
> Driver: ath9k
> Speed: 60 Mb/s
> Security: WPA/WPA2
> RSSI(dBm): -70
>
> Linux 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64 GNU/Linux

Turn off the 802.11 a/b protocols at the router. The 'b' protocol is
available in 2.4 GHz networks, and the 'a' protocol is available in
5.0 GHz networks. Both are antique and slow down wifi connections
nowadays. Something like <https://ibb.co/PrLGY5T>. Notice the 2.4 GHz
mode is 802.11 g/n, not 802.11 b/g/n. And the 5/0 GHz mode should be
802.11 n/ac, not 802.11 a/n/ac.

Also see 
<https://blogs.cisco.com/networking/bring-out-yer-dead-5-steps-to-eliminate-802-11b-from-your-networks>.

Jeff

Re: WiFi b/g/n

2023-11-07 Thread Marco M.

Am 07.11.2023 um 17:15:12 Uhr schrieb William Torrez Corea:

> I am using 2.4Ghz, but I can't use 5Ghz. My laptop is outdated
> (Inspiron 14R 5437).

Rund lspci and show the model name of the wireless NIC.

Re: WiFi b/g/n

2023-11-07 Thread Dan Ritter

William Torrez Corea wrote: 
> I have WiFi b/g/n (email, browser, streaming, social network) apparently
> but the device acts like WiFi 1 (email).

802.11b is a maximum of 12Mb/s.

802.11g is a maximum of 54Mb/s.

It is clear from this:

> *Interface*: 802.11 WiFi
> *Driver*: ath9k
> *Speed*: 60 Mb/s
> *Security*: WPA/WPA2
> *RSSI(dBm)*: -70

That your wifi is connecting via 802.11n or later.

Do you have a more specific symptom or issue to report?

-dsr-

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Martin

On Sun, Nov 05, 2023 at 06:48:47AM +, Tixy wrote:
> On Sat, 2023-11-04 at 20:08 +0100, Martin wrote:
> [...]
> > BTW putting above script into /etc/nftables.conf (at the bottom of file)
> > did not ever worked - I had always to run that file manualy as root.
> > Command 'nft list ruleset' only then showed this table.
> > I have no idea why. To me it seemed as if /etc/nftables.conf file
> > was not executed (I have rebooted many times so this file should run).
> [...]
> 
> Did you enable the nftables service? To do that, use:
> 
> # systemctl enable nftables.service
> 
> and to see status of the service
> 
> # systemctl status nftables.service

It was not enabled by default. I enabled it now.
That is great - now i know where to put script when it start working.
Unfortunately I am not there yet :(

Thank you.
Martin

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Martin

On Sun, Nov 05, 2023 at 10:26:17AM +0200, Anssi Saari wrote:
> Anyways, a typical masquerade rule would specify the source network and
> an outgoing interface. For example, I have in my Linux router:
> 
> ip saddr 10.0.2.0/24 oifname "enp1s0" masquerade
> 
> so for you that would become
> 
> ip saddr 192.168.231.0/24 oifname "wlxe8de27a5ab1c" masquerade

I tried this line too, unforutately it does not work either.
I mean after executing the config file with this line it shows itself in
output of command 'nft list ruleset' but I still can not connect to
internet from my phone.

I tried many lines similar to this, none works:
ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
ip saddr 192.168.231.0/24 ip daddr != 192.168.231.0/24 masquerade
ip saddr 192.168.231.0/24 oifname "wlxe8de27a5ab1c" masquerade
oifname "wlxe8de27a5ab1c" masquerade

I also noticed in output of 'nft list ruleset' that other rules there are
using capitalized letter so i try it too:
istead of   chain postrouting {
I used  chain POSTROUTING {

I also tried to put this command in table that already exist instead of
creating new one (masqrule) - instead of running my whole script I run
only one command (after reboot so there are no more changes made by me before):

nft add rule ip nat POSTROUTING oifname  wlxe8de27a5ab1c  masquerade

(note that here I used 'ip nat' table that is added autmaticaly by
docker server i guess)

Since nothing I tried does work I guess my next step should be to see
where/how those packets from phone are handled. I guess program for that
is tcpdump which I have installed. But since I am unfamiliar with this tool
I would need help from mailing list to guide me what to look for and how
to use this tool.

So please can you give me some info what command should I use with
tcpdump to see where packets from phone are going - or why they do not
go where they should?

Just a reminder - I can connect from phone to my computers web server - which
I also installed just for debugging this. The problem is I can not connect from
phone to internet (let say google.com)

Martin

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Max Nikulin


On 05/11/2023 13:48, Tixy wrote:

On Sat, 2023-11-04 at 20:08 +0100, Martin wrote:
[...]

BTW putting above script into /etc/nftables.conf (at the bottom of file)
did not ever worked - I had always to run that file manualy as root.
Command 'nft list ruleset' only then showed this table.
I have no idea why. To me it seemed as if /etc/nftables.conf file
was not executed (I have rebooted many times so this file should run).

[...]

Did you enable the nftables service? To do that, use:

# systemctl enable nftables.service

and to see status of the service

# systemctl status nftables.service


It should be checked first and

journalctl -b -u nftables.service

alongside with searching for any nft messages in "journalctl -b". I 
suggested earlier to read /usr/share/doc/nftables/README.Debian It 
explicitly recommends to enable the service.



2: enp3s0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 192.168.231.3/24 brd 192.168.231.255 scope global enp3s0


I hope, your router allows to view configuration received from the DHCP 
server. Since static addresses were working (and it can be rechecked), I 
guess, gateway is not explicitly configured, so the router tries to send 
packets to 192.168.231.1. Either change the interface IP or configure 
dnsmasq to send 192.168.231.3.


To debug run wireshark or tcpdump on enp3s0 and wlxe8de27a5ab1c to check 
that packets from the phone are properly received and routed.


Warning: if you have not configured network interfaces for DHCP in 
dnsmasq then do it. Otherwise other computers connected to the upstream 
WiFi link may receive DHCP leases emitted from wlxe8de27a5ab1c.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Anssi Saari

Martin  writes:

> #!/usr/sbin/nft -f
>
> table ip masqrule {}
> flush table ip masqrule
> table ip masqrule {
>   chain postrouting {
> type nat hook postrouting priority srcnat; policy accept;
> ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
>   }
> }
>
> When I execute this file with sudo unfortunately nothing changes, I can
> not connect to the internet (trying www.google.com from phone).

I might guess it's because your masquerade rule does nothing. I'm not
sure though.

Anyways, a typical masquerade rule would specify the source network and
an outgoing interface. For example, I have in my Linux router:

ip saddr 10.0.2.0/24 oifname "enp1s0" masquerade

so for you that would become

ip saddr 192.168.231.0/24 oifname "wlxe8de27a5ab1c" masquerade

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-05 Thread Tixy

On Sat, 2023-11-04 at 20:08 +0100, Martin wrote:
[...]
> BTW putting above script into /etc/nftables.conf (at the bottom of file)
> did not ever worked - I had always to run that file manualy as root.
> Command 'nft list ruleset' only then showed this table.
> I have no idea why. To me it seemed as if /etc/nftables.conf file
> was not executed (I have rebooted many times so this file should run).
[...]

Did you enable the nftables service? To do that, use:

# systemctl enable nftables.service

and to see status of the service

# systemctl status nftables.service

-- 
Tixy

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-11-04 Thread Martin

On Thu, Oct 26, 2023 at 10:00:08PM +0700, Max Nikulin wrote:
> On 26/10/2023 17:06, Martin wrote:
> > On Thu, Oct 26, 2023 at 09:54:22AM +0700, Max Nikulin wrote:
> > > 
> > > #!/usr/sbin/nft -f
> > > table inet sharedconnection {}
> > > flush table inet sharedconnection
> > > table ip sharedconnection { ... } from above

> I wrote "FILE" in caps trying to express that you can choose any name.
> Debian has /etc/nftables.conf and nft supports the "include" directive, see
> nft(8). So you may put your file to /etc or to create a dedicated directory,
> e.g. /etc/nftables.conf.d, for your settings and include your file from the
> main conf file, so it should be applied on each boot by nftables.service.
> You may put "table ip shared ..." content directly into /etc/nftables.conf
> as well, however I prefer to minimize changes in files provided by packages
> when it is possible to use additional ones.

> By the way, since you have dnsmasq running, you may enable its DHCP server
> (dhcp-range=192.168.231.5,192.168.231.254) and may switch mi router from
> static network configuration to DHCP.

Sorry for long pause in reply (my hard disk was dieing so I replaced HD and
installed whole debian from scratch).

Now (after reinstall everything) I am the point where I want to make my
router to work. I set up dnsmasq to enable DHCP with line in config:
dhcp-range=192.168.231.241,192.168.231.254,12h
and reseted my WiFi router after little configuring with my phone I can
connect my phone to WiFi router and to my computer (that still has address
192.168.231.3). I can access http server on my computer when I type in my
phone address to connect in web browser: http://192.168.231.3/text.html
(I created on my computer file /var/www/html/test.html)

That is all without changing anything with nft program.
I created a file with exatly this content:

#!/usr/sbin/nft -f

table ip masqrule {}
flush table ip masqrule
table ip masqrule {
  chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
  }
}

When I execute this file with sudo unfortunately nothing changes, I can
not connect to the internet (trying www.google.com from phone).

[[ this is about old system I had on old HD:
I remeber before reinstalling whole system at this point I had connection
from my phone to the internet (I could see google and then some videos on
youtube worked too on the phone) After I rebooted my old system I could not
connect to internet anymore from the phone. I slightly changed the script
from your post to current state (namely using ip allways instead of inet at
first two lines of script and using 'masqrule'as table name) I thing those
changes are ok.
]]

I have no idea what else should I try to make this work. Maybe I forgot
to issue some command (but I do not think so).

BTW putting above script into /etc/nftables.conf (at the bottom of file)
did not ever worked - I had always to run that file manualy as root.
Command 'nft list ruleset' only then showed this table.
I have no idea why. To me it seemed as if /etc/nftables.conf file
was not executed (I have rebooted many times so this file should run).

Bye
Martin

My current network connections, and 'ip route' command:
(I see 2 changes from my prevoius setup: missing tun0 and  br-7bfdce95ff27
they were before created automaticaly so I hope it does not matter they
are not present now - both where doing local addresses 10.1.1.1/24 and
172.18.0.1/16, maybe they will appeear when I install more programs from
repository - i am not worried about them, just mentioning to be complete)
root@redmoon:~# ip address list
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
   valid_lft forever preferred_lft forever
2: enp3s0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether e0:d5:5e:73:c9:d3 brd ff:ff:ff:ff:ff:ff
inet 192.168.231.3/24 brd 192.168.231.255 scope global enp3s0
   valid_lft forever preferred_lft forever
inet6 fe80::e2d5:5eff:fe73:c9d3/64 scope link proto kernel_ll
   valid_lft forever preferred_lft forever
3: wlxe8de27a5ab1c:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
link/ether e8:de:27:a5:ab:1c brd ff:ff:ff:ff:ff:ff
inet 192.168.0.16/24 brd 192.168.0.255 scope global dynamic wlxe8de27a5ab1c
   valid_lft 591334sec preferred_lft 591334sec
inet6 fe80::eade:27ff:fea5:ab1c/64 scope link proto kernel_ll
   valid_lft forever preferred_lft forever
4: docker0:  mtu 1500 qdisc noqueue state 
DOWN group default
link/ether 02:42:33:88:62:ce brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker

Re: How to install Sid with non-free firmware for wifi?

2023-11-01 Thread Martin

On Wed, Nov 01, 2023 at 09:11:45AM -0500, David Wright wrote:
> On Wed 01 Nov 2023 at 14:42:17 (+0100), Martin wrote:
> > >From above outut i figure out my adapter is:
> > Bus 003 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 
> > 802.11n
> 
> I would have thought you'd have firmware-ath9k-htc installed to
> run that device. You could download it from:
>   
> https://packages.debian.org/search?keywords=firmware=names=sid=all
> by means of your old installation if necessary.
> 
>   Package firmware-ath9k-htc
> sid (unstable) (misc): firmware for AR7010 and AR9271 USB wireless 
> adapters
> 1.4.0-108-gd856466+dfsg1-1.4: all


This driver is also included inside of cdrom immage I use to start installation.
So I do not understand why it does not initiaze my wifi USB automaticaly?

(Also I forgot to include that I have this driver installed on my current 
machine
in the first email I included list of firmares - only this one was missed -
perhaps because it is in misc/main group in aptitude and not in 
kernel/non-free-firmware)

Martin

Re: How to install Sid with non-free firmware for wifi?

2023-11-01 Thread David Wright

On Wed 01 Nov 2023 at 14:42:17 (+0100), Martin wrote:
> On Wed, Nov 01, 2023 at 02:09:57PM +0100, Marco M. wrote:
> > Am 01.11.2023 um 13:59:51 Uhr schrieb Martin:
> > 
> > Do you have USB NICs?
> > Does your computer has an Ethernet NIC (wired)?
> > 
> > Then use them for installing the packages.
> 
> I have one computer with wifi connection to internet.
> The problem is to let installer recognize this wifi adapter.
> 
> > > My wifi adapter is TP-LINK TL-WN722N
> > 
> > Relevant is the USB-ID/PCI-ID.
> > Use lsusb/lspci -nnk to find it out.
> 
> $ lsusb
> Bus 003 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 
> 802.11n
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 006 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 
> Multimedia Keyboard
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> 
> >From above outut i figure out my adapter is:
> Bus 003 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 
> 802.11n

I would have thought you'd have firmware-ath9k-htc installed to
run that device. You could download it from:
  
https://packages.debian.org/search?keywords=firmware=names=sid=all
by means of your old installation if necessary.

  Package firmware-ath9k-htc
sid (unstable) (misc): firmware for AR7010 and AR9271 USB wireless adapters
1.4.0-108-gd856466+dfsg1-1.4: all

If that proves impossible for some reason, you could try copying the
firmware that's being used on the old installation onto a USB stick,
then copy it into the installer's filesystem (using an Alt-F2 shell)
at an appropriate time.

Cheers,
David.

Re: How to install Sid with non-free firmware for wifi?

2023-11-01 Thread Martin

On Wed, Nov 01, 2023 at 02:09:57PM +0100, Marco M. wrote:
> Am 01.11.2023 um 13:59:51 Uhr schrieb Martin:
> 
> Do you have USB NICs?
> Does your computer has an Ethernet NIC (wired)?
> 
> Then use them for installing the packages.

I have one computer with wifi connection to internet.
The problem is to let installer recognize this wifi adapter.

> > My wifi adapter is TP-LINK TL-WN722N
> 
> Relevant is the USB-ID/PCI-ID.
> Use lsusb/lspci -nnk to find it out.

$ lsusb
Bus 003 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 
Multimedia Keyboard
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

>From above outut i figure out my adapter is:
Bus 003 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n

Martin

Re: How to install Sid with non-free firmware for wifi?

2023-11-01 Thread Marco M.

Am 01.11.2023 um 13:59:51 Uhr schrieb Martin:

> The problem is that my wifi receiver is not recognized by installer.

Do you have USB NICs?
Does your computer has an Ethernet NIC (wired)?

Then use them for installing the packages.

> My wifi adapter is TP-LINK TL-WN722N

Relevant is the USB-ID/PCI-ID.
Use lsusb/lspci -nnk to find it out.

How to install Sid with non-free firmware for wifi?

2023-11-01 Thread Martin

Hello,
I am currently using Sid version of Debian - in /etc/apt/sources.list i have:
deb http://httpredir.debian.org/debian/ sid main contrib non-free
non-free-firmware

non-free and non-free-firmware I have because of drivers I need for my machine
(most acute is wifi receiver, but i guess for sound and graphic too)

Now my hard drive is dieing and I bought a new HD. I want to install debian on
new HD to replace current one.

I tryed many approaches but what looks like more strightforward is using
installer from:
https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
This is net installer with all non-free firmware I guess. Ist size is 644M.

The problem is that my wifi receiver is not recognized by installer.

On my current computer it need some password to be supplied when
starting computer (it is done in /etc/network/interfaces
iface wlxe8de27a5ab1c inet dhcp
wpa-ssid Thomson
wpa-psk mypassword
)

When I use installer CD I do see that lights on this wifi adapter does
NOT blink at all (it stay off all the time).

How do I get installer to make to recognize my wifi adapter?

I have looked inside CD and it has all nonfree drivers I have installed
on my computer instalation:
firmware-linux-free
firmware-amd-graphics
firmware-atheros
firmware-misc-nonfree
firmware-realtek

My wifi adapter is TP-LINK TL-WN722N

Description of what happen when I start intaller CD:
I start installer in Expert mode (somewhere i read it is needed to install Sid)
All goes fine until installer try to detect network. It does not recognize my
wifi adapter. It does some testing with ethernet adapter (enp3s0) then test
for wifi searching DHCP and finds nothing (during this search I noticed that
it does not use my wifi adapter - it does not blink at all).
Then it offers me to enter values manualy but it uses those values with
ethernet adapter.
And I am stuck here: how do I recognize my wifi adapter?

Martin

Broadcom WiFi/Bluetooth BCM43142 issues

2023-10-29 Thread Andrew M.A. Cater

On Sun, Oct 29, 2023 at 03:24:00PM +0530, Susmita/Rajib wrote:

Rajib,

Please note the change of subject.

> I have had a conversation with the Team ThinkPenguin for the wireless
> N model model. Their USB WiFi dongle is only for WiFi connectivity.
> Not for Bluetooth.
> 
> The team has been very transparent with sharing information, and I
> thank you for letting me know about such an empowering team surviving
> within the proprietary universe.
> 

The WiFi and Bluetooth connectivity for your laptop is almost certainly
all provided by the Broadcom chipset and the firmware it requires.

If not, it may be provided by the main laptop chipset - so maybe Intel?

You have been given (off list) a method for configuring kernel modules and
using DKMS to provide support when each kernel is updated.

You may need to download a firmware "blob" and place that in /lib/firmware

The method you've been given is by using module-assistant to automate
the process of building the kernel modules

> Since the wl module already has configured and restored the WiFi
> connectivity for my laptop, I wouldn't require the said dongle.
> 
> Shortly, I will post for configuring the Bluetooth connectivity for my
> HP laptop.
> 

So - you already have some of that in place: https://wiki.debian.org/wl

As root, you can run the command dmesg to see what the kernel finds at boot.
It produces a lot of output, so you can use grep to filter that.

What does the output of: 

dmesg | grep Bluetooth | less

produce for you - some of that should give you a clue as to what firmware
is found or is missing.

> So your support is all the more expected.
> 
> Best wishes,
> Rajib
>

With best wishes, as always

Andy Cater

[amaca...@debian.org]

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-26 Thread Max Nikulin


On 26/10/2023 17:06, Martin wrote:

On Thu, Oct 26, 2023 at 09:54:22AM +0700, Max Nikulin wrote:


#!/usr/sbin/nft -f
table inet sharedconnection {}
flush table inet sharedconnection
# table ip shared connection { ... } from above


I did create FILE.conf and after executing it I can connect to internet from
my phone. THANK YOU!

Now where do I put this FILE.conf? I would like for it to run everytime
I turn on my computer.


I wrote "FILE" in caps trying to express that you can choose any name. 
Debian has /etc/nftables.conf and nft supports the "include" directive, 
see nft(8). So you may put your file to /etc or to create a dedicated 
directory, e.g. /etc/nftables.conf.d, for your settings and include your 
file from the main conf file, so it should be applied on each boot by 
nftables.service. You may put "table ip shared ..." content directly 
into /etc/nftables.conf as well, however I prefer to minimize changes in 
files provided by packages when it is possible to use additional ones.


Instead of installing dnsmasq you may specify a public dns server in 
your router settings (8.8.8.8, etc.). Or if you are sure that DNS 
configuration provided by the upstream router 192.168.0.1 is stable then 
you may use servers from DHCP lease. However having a local caching DNS 
server (dnsmasq or systemd-resolved) should not harm.


By the way, since you have dnsmasq running, you may enable its DHCP 
server (dhcp-range=192.168.231.5,192.168.231.254) and may switch mi 
router from static network configuration to DHCP.


As a final note, NetworkManager allows to create "shared" connections 
(ipv4.method). It starts dnsmasq and adds necessary firewall nat rules. 
I used it in both directions: with ethernet upstream connection to share 
wifi or to leverage 1G ethernet link to copy files between laptops while 
one of them has an active wifi connection.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-26 Thread Martin

On Thu, Oct 26, 2023 at 09:54:22AM +0700, Max Nikulin wrote:
> On 26/10/2023 02:20, Martin wrote:
> > On Wed, Oct 25, 2023 at 07:33:52PM +0700, Max Nikulin wrote:
> > > should have something like
> > > 
> > > table ip sharedconnection {
> > >chain postrouting {
> > >  type nat hook postrouting priority srcnat; policy accept;
> > >  ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
> > >}
> > > }
> 
> "sharedconnection" is an arbitrary name. It should be chosen to not conflict
> with other applications. Actually you have nat masquerading rules created by
> docker for other interfaces. Read /usr/share/doc/nftables/README.Debian and
> choose a convenient for you way to add rules. You may add the following
> heading and may save rules to a file that may be read by either "nft -f
> FILE.conf" or just executing it.
> 
> #!/usr/sbin/nft -f
> table inet sharedconnection {}
> flush table inet sharedconnection
> # table ip shared connection { ... } from above

I did create FILE.conf and after executing it I can connect to internet from
my phone. THANK YOU!

Now where do I put this FILE.conf? I would like for it to run everytime
I turn on my computer. Is there some standard place for it - perhaps in
/etc directory? Maybe i should create some script in /etc/init.d/
directory?

Martin

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-25 Thread Max Nikulin


On 26/10/2023 02:20, Martin wrote:

On Wed, Oct 25, 2023 at 07:33:52PM +0700, Max Nikulin wrote:

should have something like

table ip sharedconnection {
   chain postrouting {
 type nat hook postrouting priority srcnat; policy accept;
 ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
   }
}

I did not add any masquerading rules by myself and output of command
'nft list ruleset' is showed below. It does not have anything like you
showed in section 'table ip sharedconnection'.


"sharedconnection" is an arbitrary name. It should be chosen to not 
conflict with other applications. Actually you have nat masquerading 
rules created by docker for other interfaces. Read 
/usr/share/doc/nftables/README.Debian and choose a convenient for you 
way to add rules. You may add the following heading and may save rules 
to a file that may be read by either "nft -f FILE.conf" or just 
executing it.


#!/usr/sbin/nft -f
table inet sharedconnection {}
flush table inet sharedconnection
# table ip shared connection { ... } from above

---

Upstream WiFi router does not know that packets addressed to 
192.168.231.5 (mi router) should be sent to your computer 
(192.168.0.16), so you computer should make upstream router believing 
that all packets from your phone originates from 192.168.0.16.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-25 Thread David Wright

On Wed 25 Oct 2023 at 11:04:59 (+0300), Anssi Saari wrote:
> Martin  writes:
> > With wifi antena I receive a (rather weak) signal that connect my
> > computer to internet. I have to use windsurfer antena booster
> > (http://members.multiweb.nl/schaaijw/windsurfer_wifi_en.pdf)
> > to get usable signal. So my computer have internet signal from
> > wifi antena - yay great thing :)
> >
> > Now I also want to connect to internet with my mobile phone!
> 
> You mean you want to use some unspecified wifi signal with your phone
> also? Share the connection to your phone and computer? The link to this
> "windsurfer" doesn't work so it's a little hard to help if you can't
> describe what you have.

I presume what's going on here is that the Internet is provided by
a wifi access point that is distant and inaccessible (say, next door).
The windsurfer is a shaped piece of aluminium foil that pops over the
aerial to make a sort of parabola. Normally, you'd put this over your
modem/router's (external) aerial to increase the signal transmitted to
parts of your house (though it decreases it in the opposite direction).
But I'm guessing that here the windsurfer is on the computer's wifi
aerial, to improve the received signal.

That's why the OP's router (which, again presumably, has no Internet
Service) is connected "backwards", so the computer is the WAN, and
the mobile phone is the sole device on the LAN.

IOW Max's reply represents a string↔of↔connected↔devices rather than
- a
- bullet
- list.

> You have some kind of mysterious internet connection from
> something. That needs to connect to the router's WAN port.

That's how I would cascade two routers: a LAN port on the main
router connects by a plumbed-in Cat5 cable to a port on the
secondary router. The latter port would be the WAN connection,
but that's broken on mine, so I have to connect the cable to
a LAN port. I guess that makes my secondary router a switch?

Cheers,
David.

Re: How do I connect my new wifi router (Mi Router 4C)?

On Wed, Oct 25, 2023 at 02:15:36PM +0200, Marco M. wrote:
> Am 25.10.2023 um 13:33:48 Uhr schrieb Martin:
> 
> > On Wed, Oct 25, 2023 at 08:47:03AM +0200, Marco M. wrote:
> > > 
> > > Why don't you use DHCP like your phone does?  
> > 
> > Because I used this computer before I had WiFi and phone.
> 
> Why it is a problem to change it?
> Do you really want to deal with manually addressing machines?

I only have one computer, and now this new router. Because I only have
one computer I did not feel need to use DHCP to automaticaly assing me
an IP address.

Martin

Re: How do I connect my new wifi router (Mi Router 4C)?

On Wed, Oct 25, 2023 at 07:33:52PM +0700, Max Nikulin wrote:
> On 25/10/2023 18:24, Martin wrote:
> > On Wed, Oct 25, 2023 at 03:17:09PM +0700, Max Nikulin wrote:
> > > 
> > > So packet forwarding should be enabled on the computer.
> 
> sysctl net.ipv4.ip_forward
> 
> almost certainly enabled since you have the docker0 network interface

You are right, it is enabled:

$ sudo sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

> I hope, you have a DNS server running on this machine
> 
> host debian.org 192.168.231.3

I did not had dig installed but host worked, alas it showed me that I do
not have installed DNS server. So I installed dnsmasq package and
wonders happened (without me editing any config files - just installing
dnsmasq) - on my mobile phone when I connected to 192.168.31.1 address
(default router address when I look from phone) It showed now green line
from router to internet.

But unfortunatelly phone does not connect to internet yet. I guess I will
need to issue some 'sudo route' command to add path from my router to
outside world (actually I do not have idea if this is the problem).

> Check that you do not have blocking rules in firewall

I do not use firewall anymore, since I stoped using wired home phone
(dialup modem) to connect to internet with ppp protocol. Since I am now
connected to internet via my weak antena which is connected to router(A)
and then to internet I know that distant router(A) is protected enough
(after all it uses only local address that i can see 192.168.0.1).

> and that masquerading
> is enabled for your downstream link enp3s0
> 
> nft list ruleset
> 
> should have something like
> 
> table ip sharedconnection {
>   chain postrouting {
> type nat hook postrouting priority srcnat; policy accept;
> ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
>   }
> }

I did not add any masquerading rules by myself and output of command
'nft list ruleset' is showed below. It does not have anything like you
showed in section 'table ip sharedconnection'. I remember using iptables
command to make firewall and masquerading my computer while I was using
dialup modem internet connection. I do not set up use any iptable rules
manualy anymore.

So this is probably what I need to figure out how to use masquerading
and other firewall rules to enable my new router to connect to outside
internet. (I must admit that I forgot what rules should I use to enable
this setup - so I need your help)

Here is output of 'nft list ruleset' 'iptables -S' and 'iptables -L' command:
(I am not sure they provide different info, but here they are)

Thanks a lot
Martin

$ sudo nft list ruleset
# Warning: table ip nat is managed by iptables-nft, do not touch!
table ip nat {
chain DOCKER {
iifname "docker0" counter packets 0 bytes 0 return
iifname "br-7bfdce95ff27" counter packets 0 bytes 0 return
}

chain POSTROUTING {
type nat hook postrouting priority srcnat; policy accept;
oifname "wlxe8de27a5ab1c" ip saddr 10.1.1.0/24  counter packets 
192 bytes 11818 masquerade
oifname != "docker0" ip saddr 172.17.0.0/16 counter packets 0 
bytes 0 masquerade
oifname != "br-7bfdce95ff27" ip saddr 172.18.0.0/16 counter 
packets 0 bytes 0 masquerade
}

chain PREROUTING {
type nat hook prerouting priority dstnat; policy accept;
fib daddr type local counter packets 7727 bytes 479748 jump 
DOCKER
}

chain OUTPUT {
type nat hook output priority dstnat; policy accept;
ip daddr != 127.0.0.0/8 fib daddr type local counter packets 3 
bytes 196 jump DOCKER
}
}
# Warning: table ip filter is managed by iptables-nft, do not touch!
table ip filter {
chain DOCKER {
}

chain DOCKER-ISOLATION-STAGE-1 {
iifname "docker0" oifname != "docker0" counter packets 0 bytes 
0 jump DOCKER-ISOLATION-STAGE-2
iifname "br-7bfdce95ff27" oifname != "br-7bfdce95ff27" counter 
packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
counter packets 27 bytes 1780 return
}

chain DOCKER-ISOLATION-STAGE-2 {
oifname "docker0" counter packets 0 bytes 0 drop
oifname "br-7bfdce95ff27" counter packets 0 bytes 0 drop
counter packets 0 bytes 0 return
}

chain FORWARD {
type filter hook forward priority filter; policy drop;
 counter packets 57740 bytes 51358193 accept
counter packets 25 bytes 1644 jump DOCKER-USER
counter packets 25 bytes 1644 jump DOCKER-ISOLATION-STAGE-1
oifname "docker0" ct state related,established counter packets 
0 bytes 0 accept
oifname "docker0" counter packets 0 bytes 0 jump DOCKER
iifname "docker0" oifname != "docker0" counter packets 0

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-25 Thread Max Nikulin


On 25/10/2023 18:24, Martin wrote:

On Wed, Oct 25, 2023 at 03:17:09PM +0700, Max Nikulin wrote:


So packet forwarding should be enabled on the computer.


sysctl net.ipv4.ip_forward

almost certainly enabled since you have the docker0 network interface


However I suspect an issue with IP addresses.

I was wrong.


2: enp3s0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
 link/ether e0:d5:5e:73:c9:d3 brd ff:ff:ff:ff:ff:ff
 inet 192.168.231.3/24 brd 192.168.231.255 scope global enp3s0

[...]

3: wlxe8de27a5ab1c:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
 link/ether e8:de:27:a5:ab:1c brd ff:ff:ff:ff:ff:ff
 inet 192.168.0.16/24 brd 192.168.0.255 scope global dynamic wlxe8de27a5ab1c


looks consistent from router settings you posted earlier


 IP address: 192.168.231.5
Subnet mask: 255.255.255.0
Default gateway: 192.168.231.3
DNS: 192.168.231.3


I hope, you have a DNS server running on this machine

dig debian.org @192.168.231.3

or

host debian.org 192.168.231.3

Check that you do not have blocking rules in firewall and that 
masquerading is enabled for your downstream link enp3s0


nft list ruleset

should have something like

table ip sharedconnection {
  chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
ip saddr 192.168.231.3/24 ip daddr != 192.168.231.3/24 masquerade
  }
}

A tool for further debugging is tcpdump or wireshark.

Re: How do I connect my new wifi router (Mi Router 4C)?

2023-10-25 Thread Marco M.

Am 25.10.2023 um 13:33:48 Uhr schrieb Martin:

> On Wed, Oct 25, 2023 at 08:47:03AM +0200, Marco M. wrote:
> > 
> > Why don't you use DHCP like your phone does?  
> 
> Because I used this computer before I had WiFi and phone.

Why it is a problem to change it?
Do you really want to deal with manually addressing machines?

> > Show 
> > ip a  
> 
> I posted output of that command to Max Nikulin email.
> 
> (Do not want to to post same info twice again as first email)

This is a mailing list, please keep the discussion here on the list and
do not send emails directly to subscribers. Nobody else can read them.

Re: How do I connect my new wifi router (Mi Router 4C)?

On Wed, Oct 25, 2023 at 08:47:03AM +0200, Marco M. wrote:
> 
> Why don't you use DHCP like your phone does?

Because I used this computer before I had WiFi and phone.

> Show 
> ip a

I posted output of that command to Max Nikulin email.

(Do not want to to post same info twice again as first email)

Martin

Re: How do I connect my new wifi router (Mi Router 4C)?