subject:"Wlan"

Re: rfkill list wlan, Hard blocked: yes

2024-01-23 Thread David Wright

On Sun 21 Jan 2024 at 21:57:20 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > > [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.
> > > 
> > > Installed package `rfkill`  (it wasn't installed before)
> > > and tried it.
> > > 
> > > It does report "hard blocked", but rfkill can't change it.
> > > 
> > > I always tried a "function key" on the keyboard of the laptop,
> > > also without the desired effect.
> > 
> > Has that worked in the past … on previous Debians … on
> > the originally installed OS?
> 
> I think it has.  Years ago.

You might need to firm up that answer. I now see thinkpad
added to your Subject line, and also occurring in the logs.
A naive search for such a device turns up:
https://www.amazon.com/Centrino-Wireless-N-112BNHMW-300Mbps-Wireless/dp/B009WJ44CA
which warns "About this item // Note: this wireless card
could not work on IBM/Lenovo/Thinkpad and HP version laptop".
Several reviews expressed disappointment with the product.

Cheers,
David.

Re: rfkill list wlan, Hard blocked: yes

2024-01-21 Thread David Wright

On Sun 21 Jan 2024 at 21:57:20 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > > [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.
> > > 
> > > Installed package `rfkill`  (it wasn't installed before)
> > > and tried it.
> > > 
> > > It does report "hard blocked", but rfkill can't change it.
> > > 
> > > I always tried a "function key" on the keyboard of the laptop,
> > > also without the desired effect.
> > 
> > Has that worked in the past … on previous Debians … on
> > the originally installed OS?
> 
> I think it has.  Years ago.
> 
> In recent years only the ethernet interface has been used.

Just checking, as some laptops are supplied without a wifi option.

You could try checking the BIOS—my Lenovo has an ?InsydeH2O BIOS
with a section:

WirelessEnabled
Bluetooth   Enabled
Power Beep  Disabled
Intel Virtual TechnologyDisabled
BIOS Back Flash Disabled
HotKey Mode Enabled → Disabled
Always On USB   Disabled
AOAC Configuration  Enabled
Deep S3 FunctionDisabled

You could install the regulatory database if it's not there
(wireless-regdb). However, I think normal behaviour is to
allow wifi to run at the lowest legal power when the
regulatory domain is not known.

After that, I'm getting out of my depth:

> [8.002917] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
> blocked
> [8.019804] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
> [8.685725] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
> control

Possibilities here are suggested by:

https://www.reddit.com/r/debian/comments/8c6ytj/active_state_power_management_aspm/

https://www.reddit.com/r/debian/comments/y4ahsh/solution_cant_disable_aspm_os_doesnt_have_aspm/

and:

https://www.kernel.org/doc/html/v5.19/admin-guide/kernel-parameters.html

which warns:

  pcie_aspm=   [PCIE] Forcibly enable or disable PCIe Active State Power 
Management.
   off Disable ASPM.
   force   Enable ASPM even on devices that claim not to support it.
   WARNING: Forcing ASPM on may cause system lockups.

Cheers,
David.

Re: rfkill list wlan, Hard blocked: yes

2024-01-21 Thread Geert Stappers

On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > [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.
> > 
> > Installed package `rfkill`  (it wasn't installed before)
> > and tried it.
> > 
> > It does report "hard blocked", but rfkill can't change it.
> > 
> > I always tried a "function key" on the keyboard of the laptop,
> > also without the desired effect.
> 
> Has that worked in the past … on previous Debians … on
> the originally installed OS?

I think it has.  Years ago.

In recent years only the ethernet interface has been used.

> Do you see any reaction in the logs (daemon.log and syslog)
> when you press that function key? Does xev show a XF86WLAN
> keysym occurring (or anything)?

The laptop doesn't run  X any more. Tried `xev` anyway:

| # xev
| xev:  unable to open display ''
| #

With `dmesg -w` was neither the function key press seen.

> Presumably as there's a function key, there's no button
> on the laptop, as commonly found on ones old enough.

Indeed, no dedicated "airplane switch" present.

Tried with parameter for the rfkill kernel module.
Either I did that wrong or it had not the desired effect.

Further suggestions appriciated.

What follows is the parameter attempt.

root@nero:~# modinfo -p rfkill
master_switch_mode:SW_RFKILL_ALL ON should: 0=do nothing (only unlock); 
1=restore; 2=unblock all (uint)
default_state:Default initial state for all radio types, 0 = radio off (uint)
root@nero:~# echo 'rfkill master_switch_mode=2' > 
/etc/modules-load.d/rfkil_unblock.conf
root@nero:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.10.0-27-amd64
root@nero:~# dmesg | grep -e rfkill -e iwlwifi
[8.002917] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
blocked
[8.019804] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
[8.685725] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[8.768395] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-1000-5.ucode
[8.768624] iwlwifi :02:00.0: loaded firmware version 39.31.5.1 build 
35138 1000-5.ucode op_mode iwldvm
[8.768677] iwlwifi :02:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[9.074938] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[9.074943] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[9.074946] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[9.074950] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 
1000 BGN, REV=0x6C
[9.088734] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[9.088763] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[9.194253] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
root@nero:~# reboot
Connection to nero closed by remote host.
Connection to nero closed.
stappers@paddy:~
$ bong
E: Missing hostname
I: This programm reduces output of 
I: Like  is a hostname as parameter required
stappers@paddy:~
$ bong nero

21:24:18 just_started 0:00:00
PING nero.gpm.stappers.nl (172.24.0.54) 56(84) bytes of data.
21:24:19 still_up 0:00:01
21:26:09 up_again 0:01:50
stappers@paddy:~
$ ssh nero
Linux nero 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jan 21 20:25:08 2024 from 172.24.0.36
stappers@nero:~$ sudo su -
root@nero:~# dmesg | grep -e rfkill -e iwlwifi
[7.952756] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
blocked
[7.976749] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
[8.397512] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[8.405654] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-1000-5.ucode
[8.405864] iwlwifi :02:00.0: loaded firmware version 39.31.5.1 build 
35138 1000-5.ucode op_mode iwldvm
[8.405909] iwlwifi :02:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[8.658837] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[8.658843] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[8.658846] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[8.658850] iwlwifi :02:00.0: Detected Intel(R) Centrino(R)

Re: rfkill list wlan, Hard blocked: yes

2024-01-21 Thread David Wright

On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > [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.
> 
> Installed package `rfkill`  (it wasn't installed before)
> and tried it.
> 
> It does report "hard blocked", but rfkill can't change it.
> 
> I always tried a "function key" on the keyboard of the laptop,
> also without the desired effect.

Has that worked in the past … on previous Debians … on
the originally installed OS?

Do you see any reaction in the logs (daemon.log and syslog)
when you press that function key? Does xev show a XF86WLAN
keysym occurring (or anything)?

Presumably as there's a function key, there's no button
on the laptop, as commonly found on ones old enough.

Cheers,
David.

Re: rfkill list wlan, Hard blocked: yes

2024-01-21 Thread Marco Moock

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

> It does report "hard blocked", but rfkill can't change it.

Look for a hardware switch or a keystroke (mostly combined with FN) to
enable it.

rfkill list wlan, Hard blocked: yes

2024-01-21 Thread Geert Stappers



In-Reply-To: 
Subject: Re: ip link   versus   nmcli device,   WIFI   firmware related


On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > [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.

Installed package `rfkill`  (it wasn't installed before)
and tried it.

It does report "hard blocked", but rfkill can't change it.


root@nero:~# rfkill
ID TYPE  DEVICE   SOFTHARD
 0 bluetooth tpacpi_bluetooth_sw   blocked blocked
 1 wwan  tpacpi_wwan_sw  unblocked blocked
 2 wlan  phy0unblocked blocked
root@nero:~# nmcli radio
WIFI-HW  WIFI  WWAN-HW  WWAN 
enabled  disabled  enabled  disabled 
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
root@nero:~# rfkill unblock wlan
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
root@nero:~# rfkill unblock all
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
root@nero:~# nmcli radio
WIFI-HW  WIFI  WWAN-HW  WWAN 
enabled  disabled  enabled  disabled 
root@nero:~#


I always tried a "function key" on the keyboard of the laptop,
also without the desired effect.

So now in doubt how to proceed.




 
> Cheers,
> David.


Groeten
Geert Stappers
-- 
Silence is hard to parse

RE: Debian Bullseye 64 bits : wlan wifi pas possible

2023-01-17 Thread Hugues Larrive

Bonjour,

--- Original Message ---
Le mardi 17 janvier 2023 à 09:12, Frédéric BOITEUX  
a écrit :


> 

> 

> Bonjour,
> 

> C’est dans la doc d’installation : pour les nouvelles installation de Debian 
> 11, le nommage des interfaces n’est plus géré par udev mais par systemd (avec 
> des noms du genre de wlp2s0, pas forcément bien intuitif). Si on veut les 
> renommer, il faut passer par des fichiers dans /etc/systemd/network/*.link 
> (avec un initrd regéréré avec cette config…).
> 

Pour apporter quelques précisions à ce sujet, on peut trouver toutes les 
explications sur la façon dont systemd renome les interfaces dans une page de 
man systemd.net-naming-scheme.

Si comme moi vous préférez que les interfaces gardent leur nom linux vous 
pouvez ajouter net.ifnames=0 à GRUB_CMDLINE_LINUX_DEFAULT dans 
/etc/default/grub suivi d'un update-grub et si systemd vous "gonfle" il y a 
toujours la possibilité de migrer le système en devuan : 
https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera

Toutefois il semble qu'il y ait un autre soucis mais je ne comprends pas : si 
ifconfig -a retourne wlp2s0, alors ifup wlp2s0 ne devrait pas retourner 
d'erreur.

Que donne dmesg | grep wlan ?

Quel est le contenu de /etc/network/interfaces ?

Utilisez-vous interfaces + wpa_supplicant pour configurer le wifi ou bien 
network-manager (je crois qu'il y a aussi une 3ème possibilité avec systemd) ?

@+
Hugues


> Cdlt,
> Fred.
> 

> -Message d'origine-
> De : ajh-valmer awache...@gmail.com
> 

> Envoyé : lundi 16 janvier 2023 23:48
> À : debian-user-french@lists.debian.org
> Objet : Re: Debian Bullseye 64 bits : wlan wifi pas possible
> 

> Bonjour,
> 

> Ma connexion réseau fonctionne bien mais qu'en mode filaire Ethernet eth0.
> 

> Par contre, plus de connexion wlan possible :
> J'ai bien modifié le fichier "70-persistent-rules" par eth0 et wlan0, 
> rebooté, "wlp2s0" reste présent dans la commande ifconfig -a , ifup wlan0 ou 
> wlp2s0 : "cannot find wlan0 et wlp2s0"
> (interfaces non reconnues).
> 

> Malgré consultation de nombreux liens sur ce sujet, rien ne fonctionne.
> 

> Merci d'une aide, une piste...
> 

> A. Valmer

publickey - hlarrive@pm.me - 0xE9429B87.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[was: Debian Bullseye 64 bits] Re: Debian Bullseye 64 bits : wlan wifi pas possible

2023-01-17 Thread didier gaumet



- ifconfig est remplacé par ip et gère les interfaces filaires

- iwconfig est remplacé par iw et gère les interfaces sans fil: si tu
veux gérer une interface sans fil en CLI par des commandes de bas-
niveau à effet immédiat c'est iw qui est adapté.

- dans le même genre les commandes init et telinit que tu as
mentionnées dans un précédent post sont remplacées (si tu utilises
Systemd ce qui est le cas par défaut sous Debian) par systemctl
start/stop graphical.target pour être ou non dans une session
graphique.

- si tu utilises Trinity, tu peux regarder par apt quelles sont les
dépendances de ses paquets et tu vas plus que probablement découvrir
qu'il utilise network-manager ou quelque chose d'approchant. Et donc
que tout ce que tu configures à la main par ailleurs relativement au
wifi risque d'entrer en conflit avec la gestion du sans-fil par
Trinity: il vaudrait mieux dans ce cas à mon sens oublier tes
paramétrages manuels et laisser Trinity s'occuper de ça (paramétrer
dans Trinity ton réseau sans fil avec la carte qui t'es proposée)

Re: Debian Bullseye 64 bits : wlan wifi pas possible

2023-01-17 Thread Basile Starynkevitch




On 17/01/2023 09:12, Frédéric BOITEUX wrote:

Bonjour,

C’est dans la doc d’installation : pour les nouvelles installation de Debian 
11, le nommage des interfaces n’est plus géré par udev mais par systemd (avec 
des noms du genre de wlp2s0, pas forcément bien intuitif). Si on veut les 
renommer, il faut passer par des fichiers dans /etc/systemd/network/*.link 
(avec un initrd regéréré avec cette config…).

Cdlt,
Fred.

-Message d'origine-
De : ajh-valmer 
Envoyé : lundi 16 janvier 2023 23:48
À : debian-user-french@lists.debian.org
Objet : Re: Debian Bullseye 64 bits : wlan wifi pas possible

Bonjour,

Ma connexion réseau fonctionne bien mais qu'en mode filaire Ethernet eth0.

Par contre, plus de connexion wlan possible :
J'ai bien modifié le fichier "70-persistent-rules" par eth0 et wlan0, rebooté, "wlp2s0" 
reste présent dans la commande ifconfig -a , ifup wlan0 ou wlp2s0 : "cannot find wlan0 et wlp2s0"
(interfaces non reconnues).




L'utilitaire iw pourrait être utile. https://linuxcommandlibrary.com/man/iw

(paquet Debian iw)



--
Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

RE: Debian Bullseye 64 bits : wlan wifi pas possible

2023-01-17 Thread Frédéric BOITEUX

Bonjour,

C’est dans la doc d’installation : pour les nouvelles installation de Debian 
11, le nommage des interfaces n’est plus géré par udev mais par systemd (avec 
des noms du genre de wlp2s0, pas forcément bien intuitif). Si on veut les 
renommer, il faut passer par des fichiers dans /etc/systemd/network/*.link 
(avec un initrd regéréré avec cette config…).

Cdlt,
Fred.

-Message d'origine-
De : ajh-valmer  
Envoyé : lundi 16 janvier 2023 23:48
À : debian-user-french@lists.debian.org
Objet : Re: Debian Bullseye 64 bits : wlan wifi pas possible

Bonjour,

Ma connexion réseau fonctionne bien mais qu'en mode filaire Ethernet eth0.

Par contre, plus de connexion wlan possible :
J'ai bien modifié le fichier "70-persistent-rules" par eth0 et wlan0, rebooté, 
"wlp2s0" reste présent dans la commande ifconfig -a , ifup wlan0 ou wlp2s0 : 
"cannot find wlan0 et wlp2s0"
(interfaces non reconnues).

Malgré consultation de nombreux liens sur ce sujet, rien ne fonctionne.

Merci d'une aide, une piste...

A. Valmer

Re: Debian Bullseye 64 bits : wlan wifi pas possible

2023-01-16 Thread ajh-valmer

Bonjour,

Ma connexion réseau fonctionne bien mais qu'en mode filaire Ethernet eth0.

Par contre, plus de connexion wlan possible :
J'ai bien modifié le fichier "70-persistent-rules" par eth0 et wlan0,
rebooté, "wlp2s0" reste présent dans la commande ifconfig -a ,
ifup wlan0 ou wlp2s0 : "cannot find wlan0 et wlp2s0"
(interfaces non reconnues).

Malgré consultation de nombreux liens sur ce sujet, rien ne fonctionne.

Merci d'une aide, une piste...

A. Valmer

Re: Drucker/Scanner HP ENVY 6020e WLAN damit scannen und Email versenden

2022-04-28 Thread tomas

On Thu, Apr 28, 2022 at 09:59:54PM +0200, diverses wrote:
> Hallo,
> mein USB Drucker ist kaputt gegangen. Da hatte ich z.B. ein Script
> geschrieben wo ich nach jeder Seite eine Taste gedrückt haben, dann wurde
> die nächste gescannt. Und zum Schluss eine Taste dann wurde daraus ein pdf
> gemacht und per Email versandt.
> Auf die Schnelle habe ich nun ein HP ENVY 6020e gekauft.
> Das Ding ist über WLAN anzusprechen mit HP  Smart. Dann habe ich aber mit
> meinen SAMSUNG Smartphone habe keine andere Verbindungen mehr und kann das
> nicht mehr gleich als Email versenden.
> Ist das so gewollt oder mache ich einen Denkfehler wie man das sonst alles
> anders machen könnte.
> Gruss Thomas

[english below]

Hey Thomas,

das ist eine englischsprachige Mailingliste. Du hast vielleicht mehr
Glück in debian-user-german [1] haben.

Mit Druckern kenne ich mich leider nicht aus, aber die beste Seite,
die ich kenne, um solche Dinge zu klären ist hier [2]. Ich schaue
da immer rein /bevor/ ich eine Kaufempfehlung ausspreche. Hersteller
von Druckern haben oft seltsame Ideen.

[English]

Hey, Thomas

this is an English-speaking mailing list. You are perhaps luckier
at [1].

Unfortunately, I don't know much about printers, but the best
page I know to clear up such things is here [2]. I always have
a look there /before/ recommending anything to buy. Printer
manufacturers often have strange ideas on how they want to treat
their customers.

Grüsse

[1] https://lists.debian.org/debian-user-german/
[2] https://openprinting.org/

-- 
tomás

signature.asc
Description: PGP signature

Drucker/Scanner HP ENVY 6020e WLAN damit scannen und Email versenden

2022-04-28 Thread diverses


Hallo,
mein USB Drucker ist kaputt gegangen. Da hatte ich z.B. ein Script 
geschrieben wo ich nach jeder Seite eine Taste gedrückt haben, dann 
wurde die nächste gescannt. Und zum Schluss eine Taste dann wurde daraus 
ein pdf gemacht und per Email versandt.

Auf die Schnelle habe ich nun ein HP ENVY 6020e gekauft.
Das Ding ist über WLAN anzusprechen mit HP  Smart. Dann habe ich aber 
mit meinen SAMSUNG Smartphone habe keine andere Verbindungen mehr und 
kann das nicht mehr gleich als Email versenden.
Ist das so gewollt oder mache ich einen Denkfehler wie man das sonst 
alles anders machen könnte.

Gruss Thomas

Drucker/Scanner HP ENVY 6020e WLAN damit scannen und Email versenden

2022-04-28 Thread debiangerman


Hallo,
mein USB Drucker ist kaputt gegangen. Da hatte ich z.B. ein Script 
geschrieben wo ich nach jeder Seite eine Taste gedrückt haben, dann 
wurde die nächste gescannt. Und zum Schluss eine Taste dann wurde daraus 
ein pdf gemacht und per Email versandt.

Auf die Schnelle habe ich nun ein HP ENVY 6020e gekauft.
Das Ding ist über WLAN anzusprechen mit HP  Smart. Dann habe ich aber 
mit meinen SAMSUNG Smartphone habe keine andere Verbindungen mehr und 
kann das nicht mehr gleich als Email versenden.
Ist das so gewollt oder mache ich einen Denkfehler wie man das sonst 
alles anders machen könnte.

Gruss Thomas

Drucker/Scanner HP ENVY 6020e WLAN damit scannen und Email versenden

2022-04-28 Thread diverses


Hallo,
mein USB Drucker ist kaputt gegangen. Da hatte ich z.B. ein Script 
geschrieben wo ich nach jeder Seite eine Taste gedrückt haben, dann 
wurde die nächste gescannt. Und zum Schluss eine Taste dann wurde daraus 
ein pdf gemacht und per Email versandt.

Auf die Schnelle habe ich nun ein HP ENVY 6020e gekauft.
Das Ding ist über WLAN anzusprechen mit HP  Smart. Dann habe ich aber 
mit meinen SAMSUNG Smartphone habe keine andere Verbindungen mehr und 
kann das nicht mehr gleich als Email versenden.
Ist das so gewollt oder mache ich einen Denkfehler wie man das sonst 
alles anders machen könnte.

Gruss Thomas

Re: Slow SSH over WLAN? How to check?

2020-09-05 Thread rhkramer

On Saturday, September 05, 2020 10:35:24 AM Lee wrote:
> On 9/3/20, riveravaldez  wrote:

> > What could I do to check/test the health/performance of the connection
> > in order to diagnose if there's effectively a problem?
> 
> You can use iperf to see how bad wireless thruput is.  LinSSID
>   https://packages.debian.org/buster/linssid
> is an easy way to find a relatively open wireless channel.
> 
> Then there's spectrum analyzers that show how much noise/interference
> there is on wireless.. but they cost money and other than moving your
> laptop or AP somewhere else there isn't a whole lot you can do about
> interference :(  I suspect you'd be better off spending your money on
> a better wireless card or a better AP.

Or, installing some Cat 5 or 6 cable, possibly in combination with some 
additional WiFi WAPs in strategic locations.

Re: Slow SSH over WLAN? How to check?

2020-09-05 Thread Lee

On 9/3/20, riveravaldez  wrote:
> Hi,
>
> I'm under the impression that one of my LAN-SSH connections is working
> poorly. When I SSH from a wired desktop machine (generic) to a
> Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
> excessive amounts of time to happen (you type and the text appears a
> moment later, etc.). This is just a
> desktop→cable→router→Wi-Fi→notebook (W)LAN scheme.
> Issue appears also logging from notebook to desktop.
>
> Also I've been having some apparent poor performance in simple
> web-navigation with that notebook (always through Wi-Fi), so, I'm
> suspecting: maybe some issue with the firmware-iwlwifi?
>
> $ lspci | grep "Network controller"
> 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
> [Taylor Peak] (rev 34)
>
> Both machines run Debian testing (updated).
>
> What could I do to check/test the health/performance of the connection
> in order to diagnose if there's effectively a problem?

You can use iperf to see how bad wireless thruput is.  LinSSID
  https://packages.debian.org/buster/linssid
is an easy way to find a relatively open wireless channel.

Then there's spectrum analyzers that show how much noise/interference
there is on wireless.. but they cost money and other than moving your
laptop or AP somewhere else there isn't a whole lot you can do about
interference :(  I suspect you'd be better off spending your money on
a better wireless card or a better AP.

Regards
Lee

Re: Slow SSH over WLAN? How to check?

2020-09-03 Thread David Christensen


On 2020-09-03 06:48, riveravaldez wrote:

Hi,

I'm under the impression that one of my LAN-SSH connections is working
poorly. When I SSH from a wired desktop machine (generic) to a
Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
excessive amounts of time to happen (you type and the text appears a
moment later, etc.). This is just a
desktop→cable→router→Wi-Fi→notebook (W)LAN scheme.
Issue appears also logging from notebook to desktop.

Also I've been having some apparent poor performance in simple
web-navigation with that notebook (always through Wi-Fi), so, I'm
suspecting: maybe some issue with the firmware-iwlwifi?

$ lspci | grep "Network controller"
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
[Taylor Peak] (rev 34)

Both machines run Debian testing (updated).

What could I do to check/test the health/performance of the connection
in order to diagnose if there's effectively a problem?

Thanks a lot!



I assume your access point has utilities to determine what channel(s) 
are in use and to survey the radio environment to see how much traffic 
is on each channel.  Run it.  If your access point has the ability to 
dynamically choose a channel with less traffic, enable that feature.  If 
your access point does not, set the channel(s) to those with less 
traffic.  Also, check if the radio(s) have power settings -- it may be 
possible to increase the transmitter power.



How far is your laptop from the access point?  Is there a clear line of 
sight, or are there walls, ceilings, floors, or other objects in 
between; especially objects made of conductive materials and/or 
containing electric circuits?  The ideal situation is to have clear 
line-of-sight between your device and the access point.  In an indoor 
home environment, this is most readily accomplished by mounting an 
access point on the ceiling near the center of every room where Wi-Fi is 
used.  If you use Wi-Fi outdoors, mount an access point to the house 
wall facing the area.  You will want access points that are designed to 
work together.



David

Re: Slow SSH over WLAN? How to check?

2020-09-03 Thread John Conover



Might try variants of:

ssh -v -v -v theu...@thedomain.tld

to see what ssh/sshd are doing.

John

Bob Weber writes:
> On 9/3/20 9:48 AM, riveravaldez wrote:
> > Hi,
> >
> > I'm under the impression that one of my LAN-SSH connections is working
> > poorly. When I SSH from a wired desktop machine (generic) to a
> > Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
> > excessive amounts of time to happen (you type and the text appears a
> > moment later, etc.). This is just a
> > desktopâcableârouterâWi-Fiânotebook (W)LAN scheme.
> > Issue appears also logging from notebook to desktop.
> >
> > Also I've been having some apparent poor performance in simple
> > web-navigation with that notebook (always through Wi-Fi), so, I'm
> > suspecting: maybe some issue with the firmware-iwlwifi?
> >
> > $ lspci | grep "Network controller"
> > 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
> > [Taylor Peak] (rev 34)
> >
> > Both machines run Debian testing (updated).
> >
> > What could I do to check/test the health/performance of the connection
> > in order to diagnose if there's effectively a problem?
> >
> > Thanks a lot!
> >
> Try iperf3.Â  Install on both machines and start one as a server and one as a 
> client to see the network speed. Run with the -R option to see the reverse 
> speed.Â  Make sure there is no firewall on the server machine or open the 
> port 5201.
> 
> 
> -- 
> 
> 
> *...Bob*
> 
>   
> 
>   
>   
> On 9/3/20 9:48 AM, riveravaldez wrote:
> 
>  cite="mid:cad8u+g_gzwdw7tufmaxkpeybsv9cw1gp5vjmcx6n_bnfpm+...@mail.gmail.com">
>   Hi,
> 
> I'm under the impression that one of my LAN-SSH connections is working
> poorly. When I SSH from a wired desktop machine (generic) to a
> Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
> excessive amounts of time to happen (you type and the text appears a
> moment later, etc.). This is just a
> desktopâcableârouterâWi-Fiânotebook (W)LAN scheme.
> Issue appears also logging from notebook to desktop.
> 
> Also I've been having some apparent poor performance in simple
> web-navigation with that notebook (always through Wi-Fi), so, I'm
> suspecting: maybe some issue with the firmware-iwlwifi?
> 
> $ lspci | grep "Network controller"
> 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
> [Taylor Peak] (rev 34)
> 
> Both machines run Debian testing (updated).
> 
> What could I do to check/test the health/performance of the connection
> in order to diagnose if there's effectively a problem?
> 
> Thanks a lot!
> 
> 
> 
> Try iperf3.Â  Install on both machines and start
> one as a server and one as a client to see the network speed.Â 
> Run with the -R option to see the reverse speed.Â  Make sure
> there is no firewall on the server machine or open the port
> 5201.
> 
> 
> -- 
>   
>   
>   ...Bob
> 
>   
> 

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/

Re: Slow SSH over WLAN? How to check?

2020-09-03 Thread Bob Weber


On 9/3/20 9:48 AM, riveravaldez wrote:

Hi,

I'm under the impression that one of my LAN-SSH connections is working
poorly. When I SSH from a wired desktop machine (generic) to a
Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
excessive amounts of time to happen (you type and the text appears a
moment later, etc.). This is just a
desktop→cable→router→Wi-Fi→notebook (W)LAN scheme.
Issue appears also logging from notebook to desktop.

Also I've been having some apparent poor performance in simple
web-navigation with that notebook (always through Wi-Fi), so, I'm
suspecting: maybe some issue with the firmware-iwlwifi?

$ lspci | grep "Network controller"
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
[Taylor Peak] (rev 34)

Both machines run Debian testing (updated).

What could I do to check/test the health/performance of the connection
in order to diagnose if there's effectively a problem?

Thanks a lot!

Try iperf3.  Install on both machines and start one as a server and one as a 
client to see the network speed. Run with the -R option to see the reverse 
speed.  Make sure there is no firewall on the server machine or open the port 5201.



--


*...Bob*

Slow SSH over WLAN? How to check?

2020-09-03 Thread riveravaldez

Hi,

I'm under the impression that one of my LAN-SSH connections is working
poorly. When I SSH from a wired desktop machine (generic) to a
Wi-Fi-ed notebook (ThinkPadX220) things take irregular and seemingly
excessive amounts of time to happen (you type and the text appears a
moment later, etc.). This is just a
desktop→cable→router→Wi-Fi→notebook (W)LAN scheme.
Issue appears also logging from notebook to desktop.

Also I've been having some apparent poor performance in simple
web-navigation with that notebook (always through Wi-Fi), so, I'm
suspecting: maybe some issue with the firmware-iwlwifi?

$ lspci | grep "Network controller"
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
[Taylor Peak] (rev 34)

Both machines run Debian testing (updated).

What could I do to check/test the health/performance of the connection
in order to diagnose if there's effectively a problem?

Thanks a lot!

Re: What's missing for wake on wlan?

2018-07-30 Thread David Wright

On Mon 30 Jul 2018 at 17:27:04 (+0200), Markus Grunwald wrote:
> Hello,
> 
> While wake on lan works well on my T570 with debian buster, I'm not able
> get wake on WLAN working...
> 
> % sudo iw phy0 wowlan show
> WoWLAN is enabled:
>  * wake up on disconnect
>  * wake up on magic packet
> 
> % /sbin/ifconfig wlp4s0 | grep ether
> ether e4:70:b8:fb:25:89  txqueuelen 1000  (Ethernet)
> 
> 
> So I send the machine to suspend-to-ram and try to wake it up with:
> 
> wakeonlan e4:70:b8:fb:25:89
> 
> But nothing happens...
> 
> I'm using Wicd 1.7.4
> 
> Any ideas?

Is it on mains power?
Does the router still know it's there (ie that it's staying connected)?

Cheers,
David.

What's missing for wake on wlan?

2018-07-30 Thread Markus Grunwald

Hello,

While wake on lan works well on my T570 with debian buster, I'm not able
get wake on WLAN working...

% sudo iw phy0 wowlan show
WoWLAN is enabled:
 * wake up on disconnect
 * wake up on magic packet

% /sbin/ifconfig wlp4s0 | grep ether
ether e4:70:b8:fb:25:89  txqueuelen 1000  (Ethernet)


So I send the machine to suspend-to-ram and try to wake it up with:

wakeonlan e4:70:b8:fb:25:89

But nothing happens...

I'm using Wicd 1.7.4

Any ideas?
-- 
Markus Grunwald
https://www.the-grue.de/~markus/markus_grunwald.gpg

Mais de uma "wlan" no arquivo interfaces

2017-08-04 Thread Valentim Carlos


Boa Tarde,



   Estou com uma questão aqui na empresa sobre montagem cifs em um laptop.

   Tendo algumas opções no momento:

   - Com cabo conectado: montando no /etc/fstab  o driver do servidor windows 
sobe normalmente no ponto de montgem.

   - Sem o cabo conectado: não monta. Solução é um script mount.cifs para 
efetuar a montagem posterior, porém o processo não é automático.

   - Sem o cabo conectado: subindo a wlan pelo /etc/network/interfaces o fstab 
já monta na inicialização, porém quando mudo de rede não conecta na wlan.



   Será possível estabelecer mais de uma opção de wlan no arquivo interfaces ?

  



Agradeço desde já.



Valentim Carlos

Re: WLAN connection: 5 GHz priority

2017-07-20 Thread Dan Purgert

solitone wrote:
> On Thursday, 20 July 2017 10:05:56 CEST Dan Purgert wrote:
>> That being said, most network admins worth anything will be approaching
>> the problem from their side too (e.g. with band steering), in order to
>> "encourage" client devices to connect to the 5 GHz signal.
>
> I've tried the band steering option on my AP, but my network card
> would rather connect to the 2.4 GHz channel anyhow. It seems to worth
> signal level very much, and the 5 GHz signal is usually weaker than
> 2.4. Therefore I made do with weakening the 2.4 GHz signal. 

Yep, this is a usual / recommended thing.  I usually have 2.4 on "low"
(or lowest power setting possible), and 5 GHz on "medium" (or somewhere
around midrange Tx power).

Then again, I'm just as apt to turn 2.4 off.

>
> Funnily enough other clients (two android devices and a windows
> laptop) prefer 5 GHz even when it's weaker and my linux laptop
> connects to 2.4.

Yep, some clients are better at going to 5 (or listening to the
recommendations from the AP).


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: WLAN connection: 5 GHz priority

2017-07-20 Thread solitone

On Thursday, 20 July 2017 10:05:56 CEST Dan Purgert wrote:
> That being said, most network admins worth anything will be approaching
> the problem from their side too (e.g. with band steering), in order to
> "encourage" client devices to connect to the 5 GHz signal.

I've tried the band steering option on my AP, but my network card would rather 
connect to the 2.4 GHz channel anyhow. It seems to worth signal level very 
much, and the 5 GHz signal is usually weaker than 2.4. Therefore I made do 
with weakening the 2.4 GHz signal. 

Funnily enough other clients (two android devices and a windows laptop) prefer 
5 GHz even when it's weaker and my linux laptop connects to 2.4.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁Sent from my brain using neurons fueled by glucose.
⢿⡄⠘⠷⠚⠋⠀ 
⠈⠳⣄

Re: WLAN connection: 5 GHz priority

2017-07-20 Thread Dan Purgert

solitone wrote:
> [...]
> Is there some tweak I can do on the kernel module, so that the choice
> doesn't rely on any specific configuration on the AP?

Not directly (usually), it's a mix of a few things (as you'd done/
mentioned).  You may be able to set some preferences in Network Manager
/ wicd / whatever, but really you're at the mercy of a myriad of factors
that you really have little to no control over.

That being said, most network admins worth anything will be approaching
the problem from their side too (e.g. with band steering), in order to
"encourage" client devices to connect to the 5 GHz signal.

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

WLAN connection: 5 GHz priority

2017-07-20 Thread solitone

Although this issue is widely discussed, but I didn't find a way to solve it. 
My access point provides both 2.4 GHz and 5 GHz bands, and I'd like my WiFi 
adapter chose 5 GHz over 2.4.

To accomplish this, I reduced the AP's TX power for 2.4 GHz, and increased 
that for 5 GHz. The point is that when the 2.4 GHz signal is higher than 5 
GHz, my WiFi adapter prefers the 2.4 channel, even though usually the 5 GHz 
channel is less crowded and has less interference and therefore its 
performance would likely be better.

Another way would be to configure two separate SSIDs, one for 2.4 GHz, the 
other for 5 GHz. However, neither option is viable when I have no control on 
the APs, like in a university wireless campus.

Is there some tweak I can do on the kernel module, so that the choice doesn't 
rely on any specific configuration on the AP?

My laptop features a Broadcom BCM43602 802.11ac WiFi adapter, supported by the 
brcmfmac driver:

$ sudo lspci -vnn |grep BCM43602 -A17
03:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11ac Wireless 
LAN SoC [14e4:43ba] (rev 01)
Subsystem: Apple Inc. BCM43602 802.11ac Wireless LAN SoC [106b:0133]
Flags: bus master, fast devsel, latency 0, IRQ 55
Memory at c140 (64-bit, non-prefetchable) [size=32K]
Memory at c100 (64-bit, non-prefetchable) [size=4M]
Capabilities: [48] Power Management version 3
Capabilities: [58] MSI: Enable+ Count=1/16 Maskable- 64bit+
Capabilities: [68] Vendor Specific Information: Len=44 
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 0f-bd-a7-ff-ff-9d-98-01
Capabilities: [150] Power Budgeting 
Capabilities: [160] Virtual Channel
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [220] #15
Capabilities: [240] L1 PM Substates
Kernel driver in use: brcmfmac
Kernel modules: brcmfmac

I found this patch that seems relevant:
brcmfmac: Give priority to 5GHz band in selecting target BSS
https://patchwork.kernel.org/patch/4156831/

but it seems it wasn't ever applied.
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁Sent from my brain using neurons fueled by glucose.
⢿⡄⠘⠷⠚⠋⠀ 
⠈⠳⣄

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Curt

On 2017-06-25, Hans  wrote:
> I read the original post now (in German, and as I am German, no problem).
> In his case I think "kismet" is a good start. So he can see, if there are 
> other AP on the same frequency. I also suggest "wavemon", which shows all AP 
> and its strenth.
>
> If the neighbour is sending weired pckages (maybe with aireplay-ng, who 
> knows), then wireshark or tshark is working fine for it. Also you have then 
> evidence for his doings, which is illegal (here in Germany). 
>
> Maybe also the package "horst" is also helpful, which is designed for 
> excactly 
> these issues: check your traffic. (I have never used it for now).

Was ist mit den hunden? 

> Hope this helps
>
> Best regards
>
> Hans
>
>
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Hans

I read the original post now (in German, and as I am German, no problem).
In his case I think "kismet" is a good start. So he can see, if there are 
other AP on the same frequency. I also suggest "wavemon", which shows all AP 
and its strenth.

If the neighbour is sending weired pckages (maybe with aireplay-ng, who 
knows), then wireshark or tshark is working fine for it. Also you have then 
evidence for his doings, which is illegal (here in Germany). 

Maybe also the package "horst" is also helpful, which is designed for excactly 
these issues: check your traffic. (I have never used it for now).

Hope this helps

Best regards

Hans

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Thomas Schmitt

Hi,

Reco wrote:
> Using aireplay-ng for the purpose of lowering signal quality
> for neighbor WiFi can be subject to criminal penalties

That would be a good catch in a neighborhood feud which normally is
rather faught by unnecessary lawn mowing, loud music, stinking garbage
cans, or obscene garden gnomes. (The use of song loving roosters is
widely banned.)

I rather imagined a radio noise generator like

https://commons.wikimedia.org/wiki/File:BWB_23342_ARTUS_Radaranlage_Typ_ME_0632.jpg

Have a nice day :)

Thomas

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Reco

Hi.

On Sun, 25 Jun 2017 10:06:38 +0200
Hans  wrote:

> I believe tshark (and wireshark of course) is also be capable of showing bad 
> or corrupted traffic. You can set filters, i.e. to filter out rejects and 
> similar, 
> and if they are abnormal high, you know, something is bad.
> 
> Just an idea...

It's complex at best. While tshark, wireshark or plain tcpdump can be
used for this purpose, it would take a non-trivial post-processing to
show signal quality/junk ratio grouped by APs.

An invocation of 'airmon-ng wlan0' is much simpler IMO.

Of course, if neighbor in question actually managed to connect to OP's
APs, and wreaking havoc from inside the OP's LAN - then wireshark would
be priceless.

Reco

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Hans

I believe tshark (and wireshark of course) is also be capable of showing bad 
or corrupted traffic. You can set filters, i.e. to filter out rejects and 
similar, 
and if they are abnormal high, you know, something is bad.

Just an idea...

Best 

Hans

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Reco

On Sun, 25 Jun 2017 11:00:28 +0300
Reco <recovery...@gmail.com> wrote:

>   Hi.
> 
> On Sun, 25 Jun 2017 09:36:57 +0200
> "Thomas Schmitt" <scdbac...@gmx.net> wrote:
> 
> > Hi,
> > 
> > debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
> >   debian-user-ger...@lists.debian.org
> > 
> > 
> > Just in case somebody knows a program for WLAN quality surveillance:
> > 
> > The OP suspects that his neighbor after annoying the dogs has now
> > taken measures to hamper the WLAN. The question is whether there are
> > programs which can diagnose WLAN quality problems and identify potential
> > causes.
> 
> airodump-ng from aircrack-ng will solve this with ease.
> kismet will too.
> 
> Just observe which WiFi channels are most crowded and switch own
> Access Point (s) to a least crowded one.
> 
> Repeat as needed.

Followup. Using aireplay-ng for the purpose of lowering signal quality
for neighbor WiFi can be subject to criminal penalties and therefore is
not recommended.

Reco

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Reco

Hi.

On Sun, 25 Jun 2017 09:36:57 +0200
"Thomas Schmitt" <scdbac...@gmx.net> wrote:

> Hi,
> 
> debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
>   debian-user-ger...@lists.debian.org
> 
> 
> Just in case somebody knows a program for WLAN quality surveillance:
> 
> The OP suspects that his neighbor after annoying the dogs has now
> taken measures to hamper the WLAN. The question is whether there are
> programs which can diagnose WLAN quality problems and identify potential
> causes.

airodump-ng from aircrack-ng will solve this with ease.
kismet will too.

Just observe which WiFi channels are most crowded and switch own
Access Point (s) to a least crowded one.

Repeat as needed.

Reco

Re: WLAN laufende Qualitaetsmessung

2017-06-25 Thread Thomas Schmitt

Hi,

debian-user ist englischsprachig. Probier's mal auf dem deutschen Ableger:
  debian-user-ger...@lists.debian.org


Just in case somebody knows a program for WLAN quality surveillance:

The OP suspects that his neighbor after annoying the dogs has now
taken measures to hamper the WLAN. The question is whether there are
programs which can diagnose WLAN quality problems and identify potential
causes.


Have a nice day :)

Thomas

WLAN laufende Qualitätsmessung

2017-06-24 Thread Thomas

Hallo,
mein neuer Nachbar ist ein bisschen komisch. Er hat schon einen 
Ultraschallvertreiber gegen unsere zwei Hunde direkt an unserem Zaun 
eingesteckt. Als er mitbekommen hat das wir das gemerkt haben hat er den 
schnell entfernt.

Nun haben wir laufend Probleme mit dem WLAN, mal kommt keiner mehr rein, ein 
anderes mal bricht zyklisch die dbm Sendeleistung  zusammen als wäre der 
Sender zwei Häuser weiter. (Android WiFi Manager)

Mit welcher Software kann ich messen was da wann los ist. Sehen kann ich kein 
Netzwerk mit SSID auf dem gleichen Kanal.

Gruss

Re: NAT sobre WLAN [SOLUCIONADO]

2016-06-10 Thread Camaleón

El Thu, 09 Jun 2016 14:06:46 -0300, JAP escribió:

> TIP:
> "El orden de las interfaces en /etc/network/interfaces,
> ALTERA EL PRODUCTO"

(...)

Bueno, no es que "altere el resultado" sino que los datos del archivo 
"interfaces" se ejecutan por orden, por lo que si invocas un comando que 
añade una ruta hacia una interfaz que aún no se ha cargado lo que sucede 
simplemente es que esa orden no se va a ejecutar (en tu caso, las reglas 
"post-up" seguramente son las que te ha generado el problema).

> Todo el problema que tuve para lograr el funcionamiento, se debió a lo
> siguiente, por orden de importancia:
> 
> A - El orden de inicio de las interfaces de red.
> B - El uso de "restart" en lugar de reiniciar el sistema.

Realmente no es necesario reiniciar el sistema, pero no siempre se sabe 
qué demonios o procesos son los que necesitan recargarse y resulta más 
sencillo reiniciar el sistema completo.

Saludos,

-- 
Camaleón

Re: NAT sobre WLAN [SOLUCIONADO]

2016-06-09 Thread JAP


El 07/06/16 a las 15:34, JAP escribió:

Estimados:

Una vez más, yo peleándome con las redes.
Paso a explicar.

Tengo un equipo corriendo Debian "jessie":
# uname -a
Linux javier 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06)
x86_64 GNU/Linux

¿Qué quiero hacer?
Que los equipos conectados por WiFi a la placa wlan0 accedan a internet
a través de la placa eth1.


Tengo una red cableada a Internet:
# ifconfig eth1
eth1  Link encap:Ethernet  HWaddr a0:f3:c1:01:da:92
   inet addr:192.168.2.52  Bcast:192.168.2.255  Mask:255.255.255.0
   inet6 addr: fe80::a2f3:c1ff:fe01:da92/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:1523 errors:0 dropped:0 overruns:0 frame:0
   TX packets:1596 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:705060 (688.5 KiB)  TX bytes:299878 (292.8 KiB)

Me conecto a dicha red mediante un portal cautivo provisto por un
servido ZeroShell, sobre el cual me identifico con un "script" en python.

Tengo una placa de red inalámbrica que provee servicio dhcp para mis
otros aparatos:

En otro entorno más "natural", lo que he hecho toda mi vida, fue montar
un puente br0 desde eth1 a wlan0.
El problema que tengo es que en este lugar, debo pasar por el portal
cautivo, y el maldito no me permite más de una conexión con una mac
definida. Los puentes (bridges), generan una nueva MAC, y asignan
direcciones IP del servidor. Y como dije, con una clave, no puedo tener
más de una conexión. Y el BAFH no me da otra clave de acceso.

Por lo que presto y diligente, decidí hacer una conexión NAT.
Para ello, monté un servidor dhcp con isc-dhcp-server, el cual da su
servicio a través de la placa inalámbrica:
# ifconfig wlan0
wlan0 Link encap:Ethernet  HWaddr 00:87:30:23:0e:a8
   inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
   inet6 addr: fe80::287:30ff:fe23:ea8/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:265 errors:0 dropped:0 overruns:0 frame:0
   TX packets:861 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:12142 (11.8 KiB)  TX bytes:60578 (59.1 KiB)

Mi celular se conecta al enrutador configurado sin inconvenientes:
# ping 192.168.5.10 -c 3
PING 192.168.5.10 (192.168.5.10) 56(84) bytes of data.
64 bytes from 192.168.5.10: icmp_seq=1 ttl=64 time=150 ms
64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=195 ms
64 bytes from 192.168.5.10: icmp_seq=3 ttl=64 time=203 ms
--- 192.168.5.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 150.223/183.033/203.074/23.394 ms


He intentado montar una NAT de no menos de 30 formas distintas, y no
logro hacer que el navegador del celular vea internet.
Las órdenes que he estado utilizando básicamente son

iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
iptables -A FORWARD -i wlan0 -j ACCEPT

Que, si la teoría no me falla, enmascara eth1, y reenvía los paquetes
que vienen de wlan0.

# iptables -t nat -L -v
Chain PREROUTING (policy ACCEPT 3 packets, 545 bytes)
  pkts bytes target prot opt in out source destination

Chain INPUT (policy ACCEPT 2 packets, 307 bytes)
  pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 58 packets, 5878 bytes)
  pkts bytes target prot opt in out source destination

Chain POSTROUTING (policy ACCEPT 36 packets, 2841 bytes)
  pkts bytes target prot opt in out source destination
22  3037 MASQUERADE  all  --  anyeth1anywhere anywhere

Las reglas de iptables, las he variado en muchas formas, y realmente, ya
no sé qué hacer.
Otros ejemplo que he usado:

iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j SNAT
--to-source 192.168.2.52

También:
iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j MASQUERADE

Bueno. No funciona.
El teléfono no tiene accesos a internet.
Google no me da la solución.

Escucho ofertas

Muchas gracias en adelanto.

JAP





TIP:
"El orden de las interfaces en /etc/network/interfaces,
ALTERA EL PRODUCTO"

He solucionado el problema.

Mi red tiene ADEMÁS de las dos que mencioné, una interfaz en el segmento 
10.0.0.0.
Yo estaba haciendo todo bien, salvo que el ORDEN de inicio de las 
interfaces estaba generando el problema.

Como "receta" para el futuro, transcribo todo lo que hice.


CÓMO COMPARTIR POR WiFi UNA CONEXIÓN DE RED EN UN AMBIENTE MUY 
CONTROLADO POR UN BAFH.


Entorno:
Una red corporativa conectada a eth0 en el segmento 10.0.0.0
Una red internet, conectada a un enrutador de portal cautivo ZeroShell a 
eth1 en el segmento 192.168.2.0/24
Una red WiFi, como enrutador privado, conectado a wlan0, en el segmento 
192.128.0.0/24


¿Qué queremos hacer?
Habilitar la conexión de aparatos con WiFi, como una NAT hacia internet.
Es de destacar que el portal cautivo SÓLO

Re: NAT sobre WLAN

2016-06-08 Thread Camaleón

El Wed, 08 Jun 2016 12:50:23 -0300, JAP escribió:

> El 08/06/16 a las 12:43, Camaleón escribió:

(...)

>>> He intentado tu consejo.
>>> El clonado hace que aparezca otra interfaz con la misma MAC, pero como
>>> es un Portal Cautivo ZeroShell, me pide la contraseña nuevamente, y
>>> por ende, no me deja tener más de una sesión abierta.
>>
>> Pues echa un ojo a ver cómo funciona ese portal, si conoces a tu
>> enemigo podrás derrotarlo :-)
>>
>> The enemies of the Captive Portal
>> http://www.zeroshell.org/hotspot-router/#issues
>>
> Eso lo he estudiado a fondo, y por ello mi sistema tiene un script
> python en vez de andar trasteando con una pantalla del navegador siempre
> abierto.

¿Y ya sabes qué tipo de filtro aplica ese portal? Por número de sesiones 
no es, desde luego y según dices, por MAC tampoco.

>>> Lo que me "vuela" la cabeza, es que con VirtualBox, armé una NAT
>>> interna, y es transparente para las máquinas virtuales.
>>
>> ¿Quieres decir que desde una máquina virtual de VB te permitía acceder
>> al portal?
>>
> Sí. Accede en forma transparente.
> Por eso no entiendo qué estoy haciendo mal.

¿Qué tipo de sistema red tienes configurada en el adaptador de la máquina 
virtual?

Saludos,

-- 
Camaleón

Re: NAT sobre WLAN

2016-06-08 Thread JAP


El 08/06/16 a las 12:43, Camaleón escribió:

El Wed, 08 Jun 2016 12:08:28 -0300, JAP escribió:


El 08/06/16 a las 10:52, Camaleón escribió:

(...)

Un truco muy habitual que solían hacer los clientes de Ono (antigua
operadora de cable en España) era clonar la MAC de todos los equipos de
la red interna (de su casa) para poder acceder a Internet a través del
cable-módem que la operadora les instalaba.

Cuento esto porque quizá te sirva hacer lo mismo en tu caso, teniendo
en cuenta que el portal cautivo es el que te impide la conexión,
seguramente mediante técnicas similares de identificación de los
clientes.



He intentado tu consejo.
El clonado hace que aparezca otra interfaz con la misma MAC, pero como
es un Portal Cautivo ZeroShell, me pide la contraseña nuevamente, y por
ende, no me deja tener más de una sesión abierta.


Pues echa un ojo a ver cómo funciona ese portal, si conoces a tu enemigo
podrás derrotarlo :-)

The enemies of the Captive Portal
http://www.zeroshell.org/hotspot-router/#issues

Eso lo he estudiado a fondo, y por ello mi sistema tiene un script 
python en vez de andar trasteando con una pantalla del navegador siempre 
abierto.




Lo que me "vuela" la cabeza, es que con VirtualBox, armé una NAT
interna, y es transparente para las máquinas virtuales.


¿Quieres decir que desde una máquina virtual de VB te permitía acceder al
portal?


Sí. Accede en forma transparente.
Por eso no entiendo qué estoy haciendo mal.



Saludos,

Re: NAT sobre WLAN

2016-06-08 Thread Camaleón

El Wed, 08 Jun 2016 12:08:28 -0300, JAP escribió:

> El 08/06/16 a las 10:52, Camaleón escribió:
>> (...)
>>
>> Un truco muy habitual que solían hacer los clientes de Ono (antigua
>> operadora de cable en España) era clonar la MAC de todos los equipos de
>> la red interna (de su casa) para poder acceder a Internet a través del
>> cable-módem que la operadora les instalaba.
>>
>> Cuento esto porque quizá te sirva hacer lo mismo en tu caso, teniendo
>> en cuenta que el portal cautivo es el que te impide la conexión,
>> seguramente mediante técnicas similares de identificación de los
>> clientes.
>>
> 
> He intentado tu consejo.
> El clonado hace que aparezca otra interfaz con la misma MAC, pero como
> es un Portal Cautivo ZeroShell, me pide la contraseña nuevamente, y por
> ende, no me deja tener más de una sesión abierta.

Pues echa un ojo a ver cómo funciona ese portal, si conoces a tu enemigo 
podrás derrotarlo :-)

The enemies of the Captive Portal
http://www.zeroshell.org/hotspot-router/#issues

> Lo que me "vuela" la cabeza, es que con VirtualBox, armé una NAT
> interna, y es transparente para las máquinas virtuales.

¿Quieres decir que desde una máquina virtual de VB te permitía acceder al 
portal?

Saludos,

-- 
Camaleón

Re: NAT sobre WLAN

2016-06-08 Thread JAP


El 08/06/16 a las 10:52, Camaleón escribió:

(...)

Un truco muy habitual que solían hacer los clientes de Ono (antigua
operadora de cable en España) era clonar la MAC de todos los equipos de
la red interna (de su casa) para poder acceder a Internet a través del
cable-módem que la operadora les instalaba.

Cuento esto porque quizá te sirva hacer lo mismo en tu caso, teniendo en
cuenta que el portal cautivo es el que te impide la conexión, seguramente
mediante técnicas similares de identificación de los clientes.

Saludos,

-- Camaleón


He intentado tu consejo.
El clonado hace que aparezca otra interfaz con la misma MAC, pero como 
es un Portal Cautivo ZeroShell, me pide la contraseña nuevamente, y por 
ende, no me deja tener más de una sesión abierta.


Lo que me "vuela" la cabeza, es que con VirtualBox, armé una NAT 
interna, y es transparente para las máquinas virtuales.


JAP

Re: NAT sobre WLAN

2016-06-08 Thread Camaleón

El Tue, 07 Jun 2016 15:34:45 -0300, JAP escribió:

> Tengo un equipo corriendo Debian "jessie":
> # uname -a Linux javier 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1
> (2016-03-06) x86_64 GNU/Linux
> 
> ¿Qué quiero hacer?
> Que los equipos conectados por WiFi a la placa wlan0 accedan a internet
> a través de la placa eth1.
> 
> 
> Tengo una red cableada a Internet:
> # ifconfig eth1 eth1  Link encap:Ethernet  HWaddr a0:f3:c1:01:da:92
>inet addr:192.168.2.52  Bcast:192.168.2.255 
>Mask:255.255.255.0 inet6 addr: fe80::a2f3:c1ff:fe01:da92/64
>Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>RX packets:1523 errors:0 dropped:0 overruns:0 frame:0 TX
>packets:1596 errors:0 dropped:0 overruns:0 carrier:0
>collisions:0 txqueuelen:1000 RX bytes:705060 (688.5 KiB)  TX
>bytes:299878 (292.8 KiB)
> 
> Me conecto a dicha red mediante un portal cautivo provisto por un
> servido ZeroShell, sobre el cual me identifico con un "script" en
> python.
> 
> Tengo una placa de red inalámbrica que provee servicio dhcp para mis
> otros aparatos:
> 
> En otro entorno más "natural", lo que he hecho toda mi vida, fue montar
> un puente br0 desde eth1 a wlan0.
> El problema que tengo es que en este lugar, debo pasar por el portal
> cautivo, y el maldito no me permite más de una conexión con una mac
> definida. Los puentes (bridges), generan una nueva MAC, y asignan
> direcciones IP del servidor. Y como dije, con una clave, no puedo tener
> más de una conexión. Y el BAFH no me da otra clave de acceso.

(...)

Un truco muy habitual que solían hacer los clientes de Ono (antigua  
operadora de cable en España) era clonar la MAC de todos los equipos de 
la red interna (de su casa) para poder acceder a Internet a través del 
cable-módem que la operadora les instalaba.

Cuento esto porque quizá te sirva hacer lo mismo en tu caso, teniendo en 
cuenta que el portal cautivo es el que te impide la conexión, seguramente 
mediante técnicas similares de identificación de los clientes.

Saludos,

-- 
Camaleón

Re: NAT sobre WLAN

2016-06-07 Thread JavierDebian


El 07/06/16 a las 18:59, fernando sainz escribió:

¿has habilidato el ip_forwarding?

# Habilitamos el ip forwarding.
echo 1 > /proc/sys/net/ipv4/ip_forward


S2.


Básico.
Es lo primero que se hace.
Es más, está habilitado desde el /etc/sysctl.conf.

JAP

Re: NAT sobre WLAN

2016-06-07 Thread fernando sainz

El día 7 de junio de 2016, 20:34, JAP  escribió:
> Estimados:
>
> Una vez más, yo peleándome con las redes.
> Paso a explicar.
>
> Tengo un equipo corriendo Debian "jessie":
> # uname -a
> Linux javier 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64
> GNU/Linux
>
> ¿Qué quiero hacer?
> Que los equipos conectados por WiFi a la placa wlan0 accedan a internet a
> través de la placa eth1.
>
>
> Tengo una red cableada a Internet:
> # ifconfig eth1
> eth1  Link encap:Ethernet  HWaddr a0:f3:c1:01:da:92
>   inet addr:192.168.2.52  Bcast:192.168.2.255  Mask:255.255.255.0
>   inet6 addr: fe80::a2f3:c1ff:fe01:da92/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1523 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:1596 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:705060 (688.5 KiB)  TX bytes:299878 (292.8 KiB)
>
> Me conecto a dicha red mediante un portal cautivo provisto por un servido
> ZeroShell, sobre el cual me identifico con un "script" en python.
>
> Tengo una placa de red inalámbrica que provee servicio dhcp para mis otros
> aparatos:
>
> En otro entorno más "natural", lo que he hecho toda mi vida, fue montar un
> puente br0 desde eth1 a wlan0.
> El problema que tengo es que en este lugar, debo pasar por el portal
> cautivo, y el maldito no me permite más de una conexión con una mac
> definida. Los puentes (bridges), generan una nueva MAC, y asignan
> direcciones IP del servidor. Y como dije, con una clave, no puedo tener más
> de una conexión. Y el BAFH no me da otra clave de acceso.
>
> Por lo que presto y diligente, decidí hacer una conexión NAT.
> Para ello, monté un servidor dhcp con isc-dhcp-server, el cual da su
> servicio a través de la placa inalámbrica:
> # ifconfig wlan0
> wlan0 Link encap:Ethernet  HWaddr 00:87:30:23:0e:a8
>   inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
>   inet6 addr: fe80::287:30ff:fe23:ea8/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:265 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:861 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:12142 (11.8 KiB)  TX bytes:60578 (59.1 KiB)
>
> Mi celular se conecta al enrutador configurado sin inconvenientes:
> # ping 192.168.5.10 -c 3
> PING 192.168.5.10 (192.168.5.10) 56(84) bytes of data.
> 64 bytes from 192.168.5.10: icmp_seq=1 ttl=64 time=150 ms
> 64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=195 ms
> 64 bytes from 192.168.5.10: icmp_seq=3 ttl=64 time=203 ms
> --- 192.168.5.10 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 1999ms
> rtt min/avg/max/mdev = 150.223/183.033/203.074/23.394 ms
>
>
> He intentado montar una NAT de no menos de 30 formas distintas, y no logro
> hacer que el navegador del celular vea internet.
> Las órdenes que he estado utilizando básicamente son
>
> iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
> iptables -A FORWARD -i wlan0 -j ACCEPT
>
> Que, si la teoría no me falla, enmascara eth1, y reenvía los paquetes que
> vienen de wlan0.
>
> # iptables -t nat -L -v
> Chain PREROUTING (policy ACCEPT 3 packets, 545 bytes)
>  pkts bytes target prot opt in out source destination
>
> Chain INPUT (policy ACCEPT 2 packets, 307 bytes)
>  pkts bytes target prot opt in out source destination
>
> Chain OUTPUT (policy ACCEPT 58 packets, 5878 bytes)
>  pkts bytes target prot opt in out source destination
>
> Chain POSTROUTING (policy ACCEPT 36 packets, 2841 bytes)
>  pkts bytes target prot opt in out source destination
>22  3037 MASQUERADE  all  --  anyeth1anywhere anywhere
>
> Las reglas de iptables, las he variado en muchas formas, y realmente, ya no
> sé qué hacer.
> Otros ejemplo que he usado:
>
> iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j SNAT
> --to-source 192.168.2.52
>
> También:
> iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j MASQUERADE
>
> Bueno. No funciona.
> El teléfono no tiene accesos a internet.
> Google no me da la solución.
>
> Escucho ofertas
>
> Muchas gracias en adelanto.
>
> JAP
>


¿has habilidato el ip_forwarding?

# Habilitamos el ip forwarding.
echo 1 > /proc/sys/net/ipv4/ip_forward


S2.

NAT sobre WLAN

2016-06-07 Thread JAP


Estimados:

Una vez más, yo peleándome con las redes.
Paso a explicar.

Tengo un equipo corriendo Debian "jessie":
# uname -a
Linux javier 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) 
x86_64 GNU/Linux


¿Qué quiero hacer?
Que los equipos conectados por WiFi a la placa wlan0 accedan a internet 
a través de la placa eth1.



Tengo una red cableada a Internet:
# ifconfig eth1
eth1  Link encap:Ethernet  HWaddr a0:f3:c1:01:da:92
  inet addr:192.168.2.52  Bcast:192.168.2.255  Mask:255.255.255.0
  inet6 addr: fe80::a2f3:c1ff:fe01:da92/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1523 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1596 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:705060 (688.5 KiB)  TX bytes:299878 (292.8 KiB)

Me conecto a dicha red mediante un portal cautivo provisto por un 
servido ZeroShell, sobre el cual me identifico con un "script" en python.


Tengo una placa de red inalámbrica que provee servicio dhcp para mis 
otros aparatos:


En otro entorno más "natural", lo que he hecho toda mi vida, fue montar 
un puente br0 desde eth1 a wlan0.
El problema que tengo es que en este lugar, debo pasar por el portal 
cautivo, y el maldito no me permite más de una conexión con una mac 
definida. Los puentes (bridges), generan una nueva MAC, y asignan 
direcciones IP del servidor. Y como dije, con una clave, no puedo tener 
más de una conexión. Y el BAFH no me da otra clave de acceso.


Por lo que presto y diligente, decidí hacer una conexión NAT.
Para ello, monté un servidor dhcp con isc-dhcp-server, el cual da su 
servicio a través de la placa inalámbrica:

# ifconfig wlan0
wlan0 Link encap:Ethernet  HWaddr 00:87:30:23:0e:a8
  inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
  inet6 addr: fe80::287:30ff:fe23:ea8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:265 errors:0 dropped:0 overruns:0 frame:0
  TX packets:861 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:12142 (11.8 KiB)  TX bytes:60578 (59.1 KiB)

Mi celular se conecta al enrutador configurado sin inconvenientes:
# ping 192.168.5.10 -c 3
PING 192.168.5.10 (192.168.5.10) 56(84) bytes of data.
64 bytes from 192.168.5.10: icmp_seq=1 ttl=64 time=150 ms
64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=195 ms
64 bytes from 192.168.5.10: icmp_seq=3 ttl=64 time=203 ms
--- 192.168.5.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 150.223/183.033/203.074/23.394 ms


He intentado montar una NAT de no menos de 30 formas distintas, y no 
logro hacer que el navegador del celular vea internet.

Las órdenes que he estado utilizando básicamente son

iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
iptables -A FORWARD -i wlan0 -j ACCEPT

Que, si la teoría no me falla, enmascara eth1, y reenvía los paquetes 
que vienen de wlan0.


# iptables -t nat -L -v
Chain PREROUTING (policy ACCEPT 3 packets, 545 bytes)
 pkts bytes target prot opt in out source 
destination


Chain INPUT (policy ACCEPT 2 packets, 307 bytes)
 pkts bytes target prot opt in out source 
destination


Chain OUTPUT (policy ACCEPT 58 packets, 5878 bytes)
 pkts bytes target prot opt in out source 
destination


Chain POSTROUTING (policy ACCEPT 36 packets, 2841 bytes)
 pkts bytes target prot opt in out source 
destination
   22  3037 MASQUERADE  all  --  anyeth1anywhere 
anywhere


Las reglas de iptables, las he variado en muchas formas, y realmente, ya 
no sé qué hacer.

Otros ejemplo que he usado:

iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j SNAT 
--to-source 192.168.2.52


También:
iptables -t nat -A POSTROUTING ! -d 192.168.5.0/24 -o eth1 -j MASQUERADE

Bueno. No funciona.
El teléfono no tiene accesos a internet.
Google no me da la solución.

Escucho ofertas

Muchas gracias en adelanto.

JAP

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

thanks dude ! i upgraded my driver. But can you tell why some packages
break after updating to newer version and still debian stable version is
named so.
infact after updating java.. libreoffice4 failed and i had to install
libreoffice5 from jessie backports.
Is this normal or and issue?
Thanks for the help!

On Sun, Oct 4, 2015 at 3:35 PM, Eduard Bloch  wrote:

> Hallo,
> * Himanshu Shekhar [Sun, Oct 04 2015, 03:06:34PM]:
> > I have no idea of what has happened to my system. My sources.list is
> > attached along with make.log. If I need to downgrade my kernel, please
> > provide a fix.
> > Thanks for replying... I was waiting!
>
> Downgrade the kernel or upgrade the driver, your choice.
>
> https://packages.debian.org/sid/broadcom-sta-dkms
> https://packages.debian.org/sid/broadcom-sta-common
> https://packages.debian.org/sid/broadcom-sta-source
>
> Regards,
> Eduard.
>

-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

I have no idea of what has happened to my system. My sources.list is
attached along with make.log. If I need to downgrade my kernel, please
provide a fix.
Thanks for replying... I was waiting!

I would appreciate any help!

On Sun, Oct 4, 2015 at 2:53 PM, Petter Adsen  wrote:

> On Sun, 4 Oct 2015 13:22:44 +0530
> Himanshu Shekhar  wrote:
>
> > I updated my system last night after which I was not able to use network
> on
> > my laptop. I tried to install ethernet driver as I had it locally but
> could
> > not make the wifi work.
> > Earlier the /lib/modules folder had 3.16* directory only, now I could see
> > some 4.1* alongside. Also, the driver in use was *wl* which was working
> > fine, but now I couldn't install wl. The installation reports are in the
> > attachments.
> > The first time I installed Debian 8.1, I had the same issue, traversed
> > Synaptic and installed broadcom-sta-dkms which fixed the issue.
>
> Your 'wl' issue is a red herring, that package is a mail client for
> Emacs, not a driver. broadcom-sta-dkms failed to build, if you read the
> final line of output it advises you on your next course of action:
>
> "Consult /var/lib/dkms/broadcom-sta/6.30.223.248/build/make.log for
> more information."
>
> My guess is that it has problems with the newer kernel, but without
> that file it's impossible to say why it failed to build. Another guess
> would be that you haven't installed the kernel headers, which are
> required to build that package.
>
> AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos,
> you might be better off running a supported one.
>
> Petter
>
> --
> "I'm ionized"
> "Are you sure?"
> "I'm positive."
>
>


-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006
DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-0.bpo.2-amd64 (x86_64)
Sun Oct  4 12:46:39 IST 2015
/bin/sh: 1: [: Illegal number: 
/bin/sh: 1: [: Illegal number: 
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.1.0-0.bpo.2-amd64/build M=`pwd`
make[1]: Entering directory '/usr/src/linux-headers-4.1.0-0.bpo.2-amd64'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
Kernel architecture is X86_64
  LD  /var/lib/dkms/broadcom-sta/6.30.223.248/build/built-in.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_iw.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_cfg80211_get_key’:
/var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c:1390:9: warning: passing argument 1 of ‘memcpy’ discards ‘const’ qualifier from pointer target type
  memcpy(params.key, key.data, params.key_len);
 ^
In file included from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/string.h:4:0,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/string.h:17,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/bitmap.h:8,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/cpumask.h:11,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/cpumask.h:4,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/msr.h:10,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/processor.h:20,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/thread_info.h:49,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/thread_info.h:54,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/preempt.h:6,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/preempt.h:18,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/spinlock.h:50,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/seqlock.h:35,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/time.h:5,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/stat.h:18,
 from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/module.h:10,
 from /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/include/linuxver.h:40,
 from /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c:26:
/usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/string_64.h:34:14: note: expected ‘void *’ but argument is of type ‘const u8 *’
 extern void *memcpy(void *to, const void *from, size_t len);
  ^

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

Yup! got it. I attached my sources.list file in the very first message of
the thread. I would like to have suggestions on the same.
Also, I have installed few packages from tarballs, as my realtek r8101
ethernet driver, skype.
That's all!

On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz  wrote:

> On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> > thanks dude ! i upgraded my driver. But can you tell why some packages
> > break after updating to newer version and still debian stable version is
> > named so.
> > infact after updating java.. libreoffice4 failed and i had to install
> > libreoffice5 from jessie backports.
> > Is this normal or and issue?
> > Thanks for the help!
>
> There is not enough detail here, but it is probably something to do with
> the
> fact that you have jessie backports in your sources list.  If you stick to
> Jessie, and only Jessie, things won't break after updating to a newer
> version.  In fact, things normally won't update to a newer version.
> Basically, Stabel only gets security updates.
>
> I personally have never had a problem with backports, but you don't say how
> you are using backpprts or how you have got them pinned.  And have you any
> packages installed from tarballs, or otherwise not in Debian's repos?
>
> You might want to sort out your security repos.
>
> Lisi
>
>


-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006

Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

I updated my system last night after which I was not able to use network on
my laptop. I tried to install ethernet driver as I had it locally but could
not make the wifi work.
Earlier the /lib/modules folder had 3.16* directory only, now I could see
some 4.1* alongside. Also, the driver in use was *wl* which was working
fine, but now I couldn't install wl. The installation reports are in the
attachments.
The first time I installed Debian 8.1, I had the same issue, traversed
Synaptic and installed broadcom-sta-dkms which fixed the issue.


-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006


dkms-install
Description: Binary data


lspci
Description: Binary data


modprobe_wl
Description: Binary data


wl_install
Description: Binary data

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Petter Adsen

On Sun, 4 Oct 2015 13:22:44 +0530
Himanshu Shekhar  wrote:

> I updated my system last night after which I was not able to use network on
> my laptop. I tried to install ethernet driver as I had it locally but could
> not make the wifi work.
> Earlier the /lib/modules folder had 3.16* directory only, now I could see
> some 4.1* alongside. Also, the driver in use was *wl* which was working
> fine, but now I couldn't install wl. The installation reports are in the
> attachments.
> The first time I installed Debian 8.1, I had the same issue, traversed
> Synaptic and installed broadcom-sta-dkms which fixed the issue.

Your 'wl' issue is a red herring, that package is a mail client for
Emacs, not a driver. broadcom-sta-dkms failed to build, if you read the
final line of output it advises you on your next course of action:

"Consult /var/lib/dkms/broadcom-sta/6.30.223.248/build/make.log for
more information."

My guess is that it has problems with the newer kernel, but without
that file it's impossible to say why it failed to build. Another guess
would be that you haven't installed the kernel headers, which are
required to build that package.

AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos,
you might be better off running a supported one.

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Eduard Bloch

Hallo,
* Himanshu Shekhar [Sun, Oct 04 2015, 03:06:34PM]:
> I have no idea of what has happened to my system. My sources.list is
> attached along with make.log. If I need to downgrade my kernel, please
> provide a fix.
> Thanks for replying... I was waiting!

Downgrade the kernel or upgrade the driver, your choice.

https://packages.debian.org/sid/broadcom-sta-dkms
https://packages.debian.org/sid/broadcom-sta-common
https://packages.debian.org/sid/broadcom-sta-source

Regards,
Eduard.

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Lisi Reisz

On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> thanks dude ! i upgraded my driver. But can you tell why some packages
> break after updating to newer version and still debian stable version is
> named so.
> infact after updating java.. libreoffice4 failed and i had to install
> libreoffice5 from jessie backports.
> Is this normal or and issue?
> Thanks for the help!

There is not enough detail here, but it is probably something to do with the 
fact that you have jessie backports in your sources list.  If you stick to 
Jessie, and only Jessie, things won't break after updating to a newer 
version.  In fact, things normally won't update to a newer version.  
Basically, Stabel only gets security updates.

I personally have never had a problem with backports, but you don't say how 
you are using backpprts or how you have got them pinned.  And have you any 
packages installed from tarballs, or otherwise not in Debian's repos?

You might want to sort out your security repos.

Lisi

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

here's the sources.list file


On Sun, Oct 4, 2015 at 5:59 PM, Himanshu Shekhar 
wrote:

> Yup! got it. I attached my sources.list file in the very first message of
> the thread. I would like to have suggestions on the same.
> Also, I have installed few packages from tarballs, as my realtek r8101
> ethernet driver, skype.
> That's all!
>
> On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz  wrote:
>
>> On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
>> > thanks dude ! i upgraded my driver. But can you tell why some packages
>> > break after updating to newer version and still debian stable version is
>> > named so.
>> > infact after updating java.. libreoffice4 failed and i had to install
>> > libreoffice5 from jessie backports.
>> > Is this normal or and issue?
>> > Thanks for the help!
>>
>> There is not enough detail here, but it is probably something to do with
>> the
>> fact that you have jessie backports in your sources list.  If you stick to
>> Jessie, and only Jessie, things won't break after updating to a newer
>> version.  In fact, things normally won't update to a newer version.
>> Basically, Stabel only gets security updates.
>>
>> I personally have never had a problem with backports, but you don't say
>> how
>> you are using backpprts or how you have got them pinned.  And have you any
>> packages installed from tarballs, or otherwise not in Debian's repos?
>>
>> You might want to sort out your security repos.
>>
>> Lisi
>>
>>
>
>
> --
> Himanshu Shekhar
> IIIT-Allahabad
> IRM2015006
>



-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006


sources.list
Description: Binary data

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Eduard Bloch

Hallo,
* Himanshu Shekhar [Sun, Oct 04 2015, 04:09:55PM]:
> thanks dude ! i upgraded my driver. But can you tell why some packages
> break after updating to newer version and still debian stable version is
> named so.
> infact after updating java.. libreoffice4 failed and i had to install
> libreoffice5 from jessie backports.
> Is this normal or and issue?

This is not the whole truth. You DELIBERATELY installed a kernel from
backports, now you have to deal with consequences.

Regards,
Eduard.

-- 
Fällt der Pfarrer in den Mist, lacht der Bauer, bis er pißt.

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Lisi Reisz

On Sunday 04 October 2015 13:29:32 Himanshu Shekhar wrote:
> Yup! got it. I attached my sources.list file in the very first message of
> the thread. I would like to have suggestions on the same.
Read:
https://wiki.debian.org/SourcesList

Then the following might be helpful - but beware, they are not official.  But 
neither is the mess you have at the moment!

(http://www.debianadmin.com/debian-sources-list-generator.html)
This looks great, but didn't work for me.

http://debgen.simplylinux.ch/
Out of date, but works fine if used carefully.

Here is my wheezy sources.list:
---
deb http://ftp.uk.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.uk.debian.org/debian wheezy main contrib non-free

deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib non-free

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

deb http://ftp.at.debian.org/debian wheezy-backports main contrib non-free

deb http://mozilla.debian.net/ wheezy-backports iceweasel-release

deb http://www.deb-multimedia.org wheezy main non-free


You need the first, third and fifth (having changed wheezy to jessie).  src is 
up to you.  Use anything else with caution and having researched the caveats.

Lisi

> Also, I have installed few packages from tarballs, as my realtek r8101
> ethernet driver, skype.
> That's all!
>
> On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz  wrote:
> > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> > > thanks dude ! i upgraded my driver. But can you tell why some packages
> > > break after updating to newer version and still debian stable version
> > > is named so.
> > > infact after updating java.. libreoffice4 failed and i had to install
> > > libreoffice5 from jessie backports.
> > > Is this normal or and issue?
> > > Thanks for the help!
> >
> > There is not enough detail here, but it is probably something to do with
> > the
> > fact that you have jessie backports in your sources list.  If you stick
> > to Jessie, and only Jessie, things won't break after updating to a newer
> > version.  In fact, things normally won't update to a newer version.
> > Basically, Stabel only gets security updates.
> >
> > I personally have never had a problem with backports, but you don't say
> > how you are using backpprts or how you have got them pinned.  And have
> > you any packages installed from tarballs, or otherwise not in Debian's
> > repos?
> >
> > You might want to sort out your security repos.
> >
> > Lisi

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Himanshu Shekhar

apt-get upgrade possible upgraded openjdk 6 to openjdk7 (possibly because
backports are included in my sources, I don't know precisely), after which
libreoffice didn't start even from terminal.
After much guess work, I tried installing libreoffice5, which was available
in backports.
Now, libreoffice is working fine, without any issue.

Also, please clarify about *using backports safely*

On Sun, Oct 4, 2015 at 8:10 PM, Lisi Reisz  wrote:

> On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> > infact after updating java..
>
> How?  You need to give a lot more detail.
>
> > libreoffice4 failed and i had to install
> > libreoffice5 from jessie backports.
>
> Lisi
>
>

-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Lisi Reisz

On Sunday 04 October 2015 15:46:36 Himanshu Shekhar wrote:
> apt-get upgrade possible upgraded openjdk 6 to openjdk7 (possibly because
> backports are included in my sources, I don't know precisely), after which
> libreoffice didn't start even from terminal.
> After much guess work, I tried installing libreoffice5, which was available
> in backports.
> Now, libreoffice is working fine, without any issue.
>
> Also, please clarify about *using backports safely*

http://backports.debian.org/Instructions/

Lisi
>
> On Sun, Oct 4, 2015 at 8:10 PM, Lisi Reisz  wrote:
> > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> > > infact after updating java..
> >
> > How?  You need to give a lot more detail.
> >
> > > libreoffice4 failed and i had to install
> > > libreoffice5 from jessie backports.
> >
> > Lisi

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Lisi Reisz

On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote:
> infact after updating java..

How?  You need to give a lot more detail.

> libreoffice4 failed and i had to install 
> libreoffice5 from jessie backports.

Lisi

Re: Broadcom 43121 wlan issue

2015-10-04 Thread Stephen Allen

On Sun, Oct 04, 2015 at 11:23:29AM +0200, Petter Adsen wrote:
> 
> My guess is that it has problems with the newer kernel, but without
> that file it's impossible to say why it failed to build. Another guess
> would be that you haven't installed the kernel headers, which are
> required to build that package.
> 
> AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos,
> you might be better off running a supported one.

It's in Jessie backports.

Re: wlan disappeared

2015-08-06 Thread Beco


 On 6 August 2015 at 02:28, Beco r...@beco.cc wrote:
 Earlier today I picked at BIOS to see if there was something there I could
 change. The only reference to network there is to select where to boot from.

 But I'll double check to be sure.




Ok, I got some results.

I found on BIOS an option to disable NIC, and I did. Booted to see:

# lspci -v
09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030
[Rainbow Peak] (rev 34)
Subsystem: Intel Corporation Centrino Wireless-N 1030 BGN
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at f7e0 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 4c-eb-42-ff-ff-7b-a0-16
Kernel driver in use: iwlwifi

# rfkill list

0: phy0: Wireless LAN

Soft blocked: no

Hard blocked: yes

Booted again, enabled and things got very weird.

First, the FN+F2 key started working just as rffill block/unblock. So I
unblocked it.

At start, the network worked for a minute. I thought that all would be
good. But then, NetworkManager told me wifi connection deactivated.

So I run some tests:

dmesg

[Thu Aug  6 05:17:50 2015] iwlwifi :09:00.0: firmware: direct-loading
firmware iwlwifi-6000g2b-6.ucode
[Thu Aug  6 05:17:50 2015] iwlwifi :09:00.0: loaded firmware version
18.168.6.1 op_mode iwldvm

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Error sending
REPLY_TXFIFO_FLUSH: time out after 2000ms.

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Current CMD queue read_ptr
141 write_ptr 142


[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Loaded firmware version:
18.168.6.1
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Start IWL Error Log Dump:

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Status: 0x004C, count:
-30718
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x14607C40 |
ADVANCED_SYSASSERT
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | uPc

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x000A | branchlink1

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | branchlink2

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x0024 |
interruptlink1
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x |
interruptlink2
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x14607C80 | data1

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | data2

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0xA0557620 | line

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | beacon time

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x16192C14 | tsf low

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | tsf hi

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | time gp1

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | time gp2

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x14607CD8 | time gp3

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | uCode version

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0xA0416B0A | hw version

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | board version

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | hcmd

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x0020 | isr0

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | isr1

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x14607CE8 | isr2

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | isr3

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x14607CA8 | isr4

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | isr_pref

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x15CB8000 | wait_event

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x8802 | l2p_control

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x00A01C30 | l2p_duration

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | l2p_mhvalid

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x0001 |
l2p_addr_match
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | lmpm_pmg_sel

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x0001 | timestamp

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: 0x | flow_handler


[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Log capacity -1515870811
is bogus, limit to 1 entries

[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Log write index
-1515870811 is bogus, limit to 1
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: Start IWL Event Log Dump:
display last 1 entries
[Thu Aug  6 05:22:01 2015] iwlwifi :09:00.0: flush request fail

[Thu Aug  6 05:22:03 2015] iwlwifi :09:00.0: Failing on timeout while
stopping DMA channel 0 [0x5a5a5a5a]

[Thu Aug  6 05:22:05 2015] iwlwifi :09:00.0: Failing on timeout while
stopping DMA

Re: wlan disappeared

2015-08-06 Thread Hans

Am Donnerstag, 6. August 2015, 06:47:52 schrieb Beco:
Hi Beco,

is wlan0 existent? Try ifconfig -a

If yes, try wicd instead of network manager.

FYI I had trouble with my network devices with kernel 4.0, but reverting to 
3.16 did the trick.

Also see, if the correct kernel module for your card is used. However, I 
think, it is. And, of course, check, if youre card needs firmware. If so, 
install the required firmware.

Last but not least, you can check with some linux livefile systems, like 
Knoppix, or Debian Livefile.

Hope this helps.

Good luck!

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1438875206.5MxeWfl2Wc@protheus7

Re: wlan disappeared

2015-08-05 Thread briand

On Wed, 5 Aug 2015 23:23:35 -0300
Beco r...@beco.cc wrote:

 Hi guys,
 
 Something odd happened today, on my first clean boot of the day.
 (notebook DELL vostro v131)
 
 Simply, no wlan0 at all.
 

there is often a hardware switch which disables WLAN.

Is it possible that it's been turned off ?

lspci should _absolutely_ show it's existence regardless of whether or not the 
drivers have been loaded.  Either it's off, if it's a separate card it's come 
loose/disconnected, or if it's on-board then you probably have a hardware 
failure.

Brian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150805210453.14c98...@cedar.deldotd.com

wlan disappeared

2015-08-05 Thread Beco

Hi guys,

Something odd happened today, on my first clean boot of the day.
(notebook DELL vostro v131)

Simply, no wlan0 at all.

$ ifconfig -a #shows only eth0 and lo.
$ lspci #shows no wifi at all (should be a Intel Centrino Wireless-N 1030
BGN Rev=0xB0)
$ lshw -C Network #shows only eth0
$ rfkill list #shows nothing

I checked all logs, no error. dmesg, syslog, kernelog, messages... (what
else?)

It simply disappeared out of the blue.

I bought a usb wifi dongle to work a bit, and its working fine as wlan2.

But well... What can I do, or check? Maybe try to recreate the interface.

I tried
$ rmmod iwlwifi
$ modprobe iwlwifi
but nothing seems to bring it back.

Also, old dmesg shows (when it was working) that the driver should be:

/lib/firmware/iwlwifi-6000g2b-6.ucode, version 18.168.6.1

I found this driver related to

* Intel Wireless 6005/6205 firmware, version 18.168.6.1
* Intel Wireless 6030 firmware, version 18.168.6.1

Not the Wireless-N 1030. Why it was working on what seemed to be the wrong
firmware? Why it disappeared now?

The driver

* Intel Wireless 1000 firmware, version 39.31.5.1
   (iwlwifi-1000-5.ucode)

will work with intel Wireless-N 1030 BGN?

How could I test it? Because modprobe do not select the driver.

Thanks any help.

Beco




--
Dr Beco
A.I. researcher

I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindexsearch=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Re: wlan disappeared

2015-08-05 Thread Beco

On 6 August 2015 at 01:04, bri...@aracnet.com wrote:

 On Wed, 5 Aug 2015 23:23:35 -0300
 Beco r...@beco.cc wrote:

  Hi guys,
 
  Something odd happened today, on my first clean boot of the day.
  (notebook DELL vostro v131)
 
  Simply, no wlan0 at all.
 

 there is often a hardware switch which disables WLAN.

 Is it possible that it's been turned off ?

 lspci should _absolutely_ show it's existence regardless of whether or not
 the drivers have been loaded.  Either it's off, if it's a separate card
 it's come loose/disconnected, or if it's on-board then you probably have a
 hardware failure.

 Brian



Hi Brian,

Thanks for trying to make sense of this mess.

This notebook has onboard wifi, no physical switch, but a combination of
keys FN+F2 that would supposedly turn it on or off. This combination never
worked since day one of all older debians I started with, and I never used
it. But since you mentioned, I tried some keystrokes, no luck though.

Let me put lspci here. Maybe I'm mistaken.

lspci shows:

# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family
DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family
High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 5 (rev b5)
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family
PCI Express Root Port 8 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC
Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset
Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus
Controller (rev 05)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI
Host Controller (rev 02)


As you can see... No wifi there.

I also read carefully lshw again. Nope. Nothing.

Thanks,
Beco





-- 
Dr Beco
A.I. researcher

I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindexsearch=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Re: wlan disappeared

2015-08-05 Thread Beco

On 6 August 2015 at 01:54, bri...@aracnet.com wrote:


 i forgot to ask an important question, although i'm sure you would have
 mentioned it.  you can't boot into Windows on this machine, right ?


No windows near me in any machine. :)




 Sure seems like a hardware failure.


I'm starting to think that also. But today this notebook is so weird, I
don't know. I'm still puzzled. Maybe something debian-related, you know.
These Debian Jessie 8.0 and 8.1 are a bit unstable to my taste. I hope we
move on soon to 8.2.(*)



 oh- one other thing to try.  boot up into BIOS and see if there's anything
 at all in there about your WLAN hardware.


Earlier today I picked at BIOS to see if there was something there I could
change. The only reference to network there is to select where to boot from.

But I'll double check to be sure.


Tx.,
Beco.

PS. Or Debian Stretch, see my ascii-art for it (in monospaced font,
please):

_\O/_
/|\


-- 
Dr Beco
A.I. researcher

I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindexsearch=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Re: wlan disappeared

2015-08-05 Thread briand

On Thu, 6 Aug 2015 01:29:50 -0300
Beco r...@beco.cc wrote:

 Hi Brian,
 
 Thanks for trying to make sense of this mess.
 
 This notebook has onboard wifi, no physical switch, but a combination of
 keys FN+F2 that would supposedly turn it on or off. This combination never
 worked since day one of all older debians I started with, and I never used
 it. But since you mentioned, I tried some keystrokes, no luck though.

oh ok- i know what you are talking about.

i forgot to ask an important question, although i'm sure you would have 
mentioned it.  you can't boot into Windows on this machine, right ?

 
 Let me put lspci here. Maybe I'm mistaken.

you don't appear to be mistaken.

that's just weird.

Sure seems like a hardware failure.

oh- one other thing to try.  boot up into BIOS and see if there's anything at 
all in there about your WLAN hardware.


Brian


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150805215452.0a75e...@cedar.deldotd.com

Re: Wlan

2015-07-11 Thread Jerome BENOIT

Bonjour Stephan:

debian-user@lists.debian.org is an English spoken forum:
you may either expose your issue in English or send your
issue to the corresponding German forum.

Bonne chance,
Jerome

On 11/07/15 13:25, stephan roehling wrote:
 Hallo,
 meine wlan-Karte wird von linux nicht gefunden.
 apt-get install firmware-linux-nonfree funktioniert nicht. Es erscheint
 die meldung Paket nicht gefunden.
 Kann jemand helfen.
 Stephan
 
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55a102d9.6060...@rezozer.net

Wlan

2015-07-11 Thread stephan roehling

Hallo,
meine wlan-Karte wird von linux nicht gefunden.
apt-get install firmware-linux-nonfree funktioniert nicht. Es erscheint
die meldung Paket nicht gefunden.
Kann jemand helfen.
Stephan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1436613938.1393.1.ca...@gmx.de

Re: udev - set persistent name for WLAN Adapter

2015-04-27 Thread csanyipal

Bob Proulx b...@proulx.com writes:

 csanyi...@gmail.com wrote:
 Bob Proulx writes:
  Michael Biebl wrote:
  Any idea why it changes the MAC?
 
  Hmm...  Is 'macchanger' involved in this in any way?

 I just installed macchanger and run:

 Wait!  That was NOT a request to install macchanger.  The question was
 why is your ethernet address changing?  I asked if perhaps you had
 already installed macchanger to intentionally change it.  If so then
 that would explain why your mac address was changing.  Now that you
 have definitely installed it it is possible that you now have *two*
 things changing your ethernet address.  As they say, Now you have two
 problems.

Sorry for misunderstanding.

 First you should purge macchanger from your system.

   # apt-get purge macchanger

Done; I have no macchanger installed anymore.

 Then get back to your original problem.  (Squirrel!)  Stay on target.

 Now the line is:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
 ATTR{address}==00:e0:4c:81:92:*, ATTR{dev_id}==0x0, \
  ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

 Other people have been answering this part of your question.

Yes, but I feel I have not a solution for this problem.

-- 
Regards from Pal


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87mw1subcc@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-26 Thread David Wright

Quoting Pascal Hambourg (pas...@plouf.fr.eu.org):
 csanyi...@gmail.com a écrit :
 
  After that, when I replug the WLAN Adapter, I get in
  70-persistent-net.rules another line:
  # USB device 0x:0x (rtl8192cu)
  SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
  ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
  , ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
  
  and after another replugging I get:
  # USB device 0x:0x (rtl8192cu)
  SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
  ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
  , ATTR{type}==1, KERNEL==wlan*, NAME=wlan2
 
 Weird that the interface has a different MAC (although very similar)
 address each time.

I had a Netgear router that appeared thus:
c4:3d:c7:c2:c1:b4   netgear-adsl-g wlan and eth
c4:3d:c7:c2:c1:b3   netgear-adsl-n wlan

Perhaps it's autoselecting between g and n.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150426161917.GA1069@alum

Re: udev - set persistent name for WLAN Adapter

2015-04-26 Thread Pascal Hambourg

csanyi...@gmail.com a écrit :

 I should wrote here like:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb, \
 ATTR{idVendor}==0586, ATTR{idProduct}==341f, \
 ATTR{manufacturer}==Realtek, \
 ATTR{product}==802.11n WLAN Adapter, ATTR{dev_id}==0x0, \
 ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

This is wrong, as I wrote earlier : idVendor, idProduct, manufacturer
and product should use ATTRS instead of ATTR, because these attributes
belong to parent devices, not to the network interface itself.

udevadm info -a -p /sys/class/net/wlan0

 I have found the solution:

Not *the* solution, just *a* solution.

 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
 ATTR{address}==00:e0:4c:81:92:*, ATTR{dev_id}==0x0, \
  ATTR{type}==1, KERNEL==wlan*, NAME=wlan0
 
 I don't use neither
 ATTR{idVendor}==0586, nor
 ATTR{idProduct}==341f
 
 and it still works.
 Why?

See above : it works now because they would not match. If you remove
criteria, the match is less restrictive (at the risk of matching other
devices too).


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/553cb34a.5050...@plouf.fr.eu.org

Re: udev - set persistent name for WLAN Adapter

2015-04-26 Thread Bob Proulx

csanyi...@gmail.com wrote:
 Bob Proulx writes:
  Michael Biebl wrote:
  Any idea why it changes the MAC?
 
  Hmm...  Is 'macchanger' involved in this in any way?

 I just installed macchanger and run:

Wait!  That was NOT a request to install macchanger.  The question was
why is your ethernet address changing?  I asked if perhaps you had
already installed macchanger to intentionally change it.  If so then
that would explain why your mac address was changing.  Now that you
have definitely installed it it is possible that you now have *two*
things changing your ethernet address.  As they say, Now you have two
problems.

This reminds me of: 
http://en.wikipedia.org/w/index.php?title=World%27s_funniest_jokeoldid=633478023

 macchanger -s wlan0
 Permanent MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
 Current   MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)

Shows the mac address using the -s option.  Okay.  No changes made.
This is trivially the same as:

  ip addr show wlan0 | grep link

 # macchanger -m 00:e0:4c:81:92:dc wlan0
 Permanent MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
 Current   MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
 It's the same MAC!!

This sets the mac address to the value specified using the -m option.
Therefore of course it is the same mac.  You have explicitly set the
mac to the same one as before.  Did you expect something different?
What?

 So after this what should I do with udev rules in
 70-persistent-net.rules ?

First you should purge macchanger from your system.

  # apt-get purge macchanger

Then get back to your original problem.  (Squirrel!)  Stay on target.

 Now the line is:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
 ATTR{address}==00:e0:4c:81:92:*, ATTR{dev_id}==0x0, \
  ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

Other people have been answering this part of your question.

Bob


signature.asc
Description: Digital signature

Re: udev - set persistent name for WLAN Adapter

2015-04-26 Thread csanyipal

Michael Biebl bi...@debian.org writes:

 Am 25.04.2015 um 22:20 schrieb Pascal Hambourg:
 csanyi...@gmail.com a écrit :

 After that, when I replug the WLAN Adapter, I get in
 70-persistent-net.rules another line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan1

 and after another replugging I get:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan2
 
 Weird that the interface has a different MAC (although very similar)
 address each time.

 Indeed, that seems to be the root of the problem.
 The changing MAC address causes /lib/udev/write_net_rules to create new
 entries.

 Pal, what hardware is that specifically?

This is a Bubba | Two headless, power pc box.
CPU: 333MHz PowerPC
RAM: 256MB DDR2
Network: 2x Gigabit Ethernet ports, 802.11a/b/g WiFi
Ports: 2x USB2.0,  2x eSATA

See more eg. here:
http://www.linuxuser.co.uk/reviews/bubba-two-wifi-review

Mine Bubba 2 is the older version, that has not the two WiFi antennae on
the back.

I'm trying to set my USB ZyXEL NWD2205 WiFi adapter as an Access Point
here. 

 Any idea why it changes the MAC?

I have no idea..

-- 
Regards from Pal


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87pp6q4wi0@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-26 Thread csanyipal

Bob Proulx b...@proulx.com writes:

 Michael Biebl wrote:
 Pal, what hardware is that specifically?
 Any idea why it changes the MAC?

 Hmm...  Is 'macchanger' involved in this in any way?

   $ apt-cache show macchanger
   Description-en: utility for manipulating the MAC address of network 
 interfaces
Features:
  * set specific MAC address of a network interface
  * set the MAC randomly
  * set a MAC of another vendor
  * set another MAC of the same vendor
  * set a MAC of the same kind (eg: wireless card)
  * display a vendor MAC list (today, 6200 items) to choose from
   Homepage: http://www.alobbs.com/macchanger

 It is a useful tool.  I use it on the wifi device of my laptop.  It
 isn't without issue to do so but it does what it does well.

I just installed macchanger and run:
macchanger -s wlan0
Permanent MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
Current   MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)

# macchanger -m 00:e0:4c:81:92:dc wlan0
Permanent MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
Current   MAC: 00:e0:4c:81:92:dc (Realtek Semiconductor Corp.)
It's the same MAC!!

So after this what should I do with udev rules in
70-persistent-net.rules ?

Now the line is:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==00:e0:4c:81:92:*, ATTR{dev_id}==0x0, \
 ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

-- 
Regards from Pal


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87k2wy4w04@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread Bob Proulx

Michael Biebl wrote:
 Pal, what hardware is that specifically?
 Any idea why it changes the MAC?

Hmm...  Is 'macchanger' involved in this in any way?

  $ apt-cache show macchanger
  Description-en: utility for manipulating the MAC address of network interfaces
   Features:
 * set specific MAC address of a network interface
 * set the MAC randomly
 * set a MAC of another vendor
 * set another MAC of the same vendor
 * set a MAC of the same kind (eg: wireless card)
 * display a vendor MAC list (today, 6200 items) to choose from
  Homepage: http://www.alobbs.com/macchanger

It is a useful tool.  I use it on the wifi device of my laptop.  It
isn't without issue to do so but it does what it does well.

Bob


signature.asc
Description: Digital signature

udev - set persistent name for WLAN Adapter

2015-04-25 Thread csanyipal

Hello,

on my Wheezy system I just can't set a persistent 'wlan0' name for my
USB WiFi apadter.

In /etc/udev/rules.d/70-persistent-net.rules I have the line:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==usb, ACTION==add, DRIVERS==usb,
ATTRS{idVendor}==0586, ATTRS{idProduct}==341f, ATT
R{manufacturer}==Realtek, ATTR{product}==802.11n WLAN Adapter,
ATTR{dev_id}==0x0, ATTR{type}==1
, KERNEL==wlan*, NAME=wlan0

I did run:
# udevadm control --reload-rules

After that, when I replug the WLAN Adapter, I get in
70-persistent-net.rules another line:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
, ATTR{type}==1, KERNEL==wlan*, NAME=wlan1

and after another replugging I get:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
, ATTR{type}==1, KERNEL==wlan*, NAME=wlan2

So what am I missing here?
Why can't I set a persistent name for my WLAN Adapter?

-- 
Regards from Pal



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877ft0xbbx@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread csanyipal

songbird songb...@anthive.com writes:

 csanyi...@gmail.com wrote:
 Hello,

 on my Wheezy system I just can't set a persistent 'wlan0' name for my
 USB WiFi apadter.

 In /etc/udev/rules.d/70-persistent-net.rules I have the line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb,
 ATTRS{idVendor}==0586, ATTRS{idProduct}==341f, ATT
 R{manufacturer}==Realtek, ATTR{product}==802.11n WLAN Adapter,
 ATTR{dev_id}==0x0, ATTR{type}==1
 , KERNEL==wlan*, NAME=wlan0

   i'm not sure if the above is the exact entry, but if it
 is the entry should be all on one line.

Actually it is all on one line in the 70-persistent-net.rules file .

I should wrote here like:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==usb, ACTION==add, DRIVERS==usb, \
ATTR{idVendor}==0586, ATTR{idProduct}==341f, \
ATTR{manufacturer}==Realtek, \
ATTR{product}==802.11n WLAN Adapter, ATTR{dev_id}==0x0, \
ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

-- 
Regards from Pal


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/871tj7yjea@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread Michael Biebl

Am 25.04.2015 um 22:20 schrieb Pascal Hambourg:
 csanyi...@gmail.com a écrit :

 After that, when I replug the WLAN Adapter, I get in
 70-persistent-net.rules another line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan1

 and after another replugging I get:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan2
 
 Weird that the interface has a different MAC (although very similar)
 address each time.

Indeed, that seems to be the root of the problem.
The changing MAC address causes /lib/udev/write_net_rules to create new
entries.

Pal, what hardware is that specifically?
Any idea why it changes the MAC?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread Pascal Hambourg

csanyi...@gmail.com a écrit :
 
 on my Wheezy system I just can't set a persistent 'wlan0' name for my
 USB WiFi apadter.
 
 In /etc/udev/rules.d/70-persistent-net.rules I have the line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb,
 ATTRS{idVendor}==0586, ATTRS{idProduct}==341f, ATT
 R{manufacturer}==Realtek, ATTR{product}==802.11n WLAN Adapter,
 ATTR{dev_id}==0x0, ATTR{type}==1
 , KERNEL==wlan*, NAME=wlan0

Shouldn't ATTRS be used with {manufacturer} and {product} instead of
ATTR ? Besides, are they really useful ? Shouldn't it be enough to match
the USB vendor and product IDs ?

 After that, when I replug the WLAN Adapter, I get in
 70-persistent-net.rules another line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan1
 
 and after another replugging I get:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan2

Weird that the interface has a different MAC (although very similar)
address each time.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/553bf704.6060...@plouf.fr.eu.org

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread csanyipal

csanyi...@gmail.com writes:

 songbird songb...@anthive.com writes:

 csanyi...@gmail.com wrote:
 Hello,

 on my Wheezy system I just can't set a persistent 'wlan0' name for my
 USB WiFi apadter.

 In /etc/udev/rules.d/70-persistent-net.rules I have the line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb,
 ATTRS{idVendor}==0586, ATTRS{idProduct}==341f, ATT
 R{manufacturer}==Realtek, ATTR{product}==802.11n WLAN Adapter,
 ATTR{dev_id}==0x0, ATTR{type}==1
 , KERNEL==wlan*, NAME=wlan0

   i'm not sure if the above is the exact entry, but if it
 is the entry should be all on one line.

 Actually it is all on one line in the 70-persistent-net.rules file .

 I should wrote here like:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb, \
 ATTR{idVendor}==0586, ATTR{idProduct}==341f, \
 ATTR{manufacturer}==Realtek, \
 ATTR{product}==802.11n WLAN Adapter, ATTR{dev_id}==0x0, \
 ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

I have found the solution:
# USB device 0x:0x (rtl8192cu)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*, \
ATTR{address}==00:e0:4c:81:92:*, ATTR{dev_id}==0x0, \
 ATTR{type}==1, KERNEL==wlan*, NAME=wlan0

I don't use neither
ATTR{idVendor}==0586, nor
ATTR{idProduct}==341f

and it still works.
Why?

-- 
Regards from Pal


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87vbgjx3pr@gmail.com

Re: udev - set persistent name for WLAN Adapter

2015-04-25 Thread songbird

csanyi...@gmail.com wrote:
 Hello,

 on my Wheezy system I just can't set a persistent 'wlan0' name for my
 USB WiFi apadter.

 In /etc/udev/rules.d/70-persistent-net.rules I have the line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==usb, ACTION==add, DRIVERS==usb,
 ATTRS{idVendor}==0586, ATTRS{idProduct}==341f, ATT
 R{manufacturer}==Realtek, ATTR{product}==802.11n WLAN Adapter,
 ATTR{dev_id}==0x0, ATTR{type}==1
 , KERNEL==wlan*, NAME=wlan0

 I did run:
 # udevadm control --reload-rules

 After that, when I replug the WLAN Adapter, I get in
 70-persistent-net.rules another line:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:e7, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan1

 and after another replugging I get:
 # USB device 0x:0x (rtl8192cu)
 SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
 ATTR{address}==00:e0:4c:81:92:77, ATTR{dev_id}==0x0
 , ATTR{type}==1, KERNEL==wlan*, NAME=wlan2

 So what am I missing here?
 Why can't I set a persistent name for my WLAN Adapter?

  i'm not sure if the above is the exact entry, but if it
is the entry should be all on one line.

  i don't use the dev_id or kernel bits (not sure if this
matters).


  songbird


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3s9t0c-tu2@id-306963.user.uni-berlin.de

Wlan broadcom wifi et driver

2015-02-15 Thread frederic zulian

Bonjour,

OS : Debian , 3.16.0-4-amd64

Sur mon eepc j'ai un chipset broadcom pour la wifi :

-- 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn
Wireless Network Adapter (rev 01)

J'ai installé le driver avec ndiswrapper

ndiswrapper -l
bcmwl6 : driver installed
device (14E4:4727) present (alternate driver: bcma)


 iwconfig wlan0  répondwlan0 No such device

une idée ?


--
Frédéric ZULIAN

Re: Wlan broadcom wifi et driver

2015-02-15 Thread Bernard Schoenacker

Le Sun, 15 Feb 2015 18:07:00 +0100,
frederic zulian zul...@free.fr a écrit :

 Bonjour,
 
 OS : Debian , 3.16.0-4-amd64
 
 Sur mon eepc j'ai un chipset broadcom pour la wifi :
 
 -- 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn
 Wireless Network Adapter (rev 01)
 
 J'ai installé le driver avec ndiswrapper
 
 ndiswrapper -l
 bcmwl6 : driver installed
 device (14E4:4727) present (alternate driver: bcma)
 
 
  iwconfig wlan0  répondwlan0 No such device
 
 une idée ?
 
 
 --
 Frédéric ZULIAN


bonjour,

la solution en se trouve pas là mais ici :

apt-cache search broadcom wireless

broadcom-sta-common - Common files for the Broadcom STA Wireless driver
broadcom-sta-dkms - dkms source for the Broadcom STA Wireless driver
broadcom-sta-source - Source for the Broadcom STA Wireless driver
firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
openfwwf - Open firmware for Broadcom BCM43xx (b43) wlan devices
b43-asm - assembler and disassembler for Broadcom BCM43xx firmware

serait il possible de donner la listre des paquets installés ayant
trait au réseau wifi afin de vérifier les point qui pourraient poser
problême ...

slt
bernard







-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150215181952.3d0f9856.bernard.schoenac...@free.fr

Re: DKIM Wlan broadcom wifi et driver

2015-02-15 Thread MERLIN Philippe

Le dimanche 15 février 2015, 18:07:00 frederic zulian a écrit :
 Bonjour,
 
 OS : Debian , 3.16.0-4-amd64
 
 Sur mon eepc j'ai un chipset broadcom pour la wifi :
 
 -- 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn
 Wireless Network Adapter (rev 01)
 
 J'ai installé le driver avec ndiswrapper
 
 ndiswrapper -l
 bcmwl6 : driver installed
 device (14E4:4727) present (alternate driver: bcma)
 
 
  iwconfig wlan0  répondwlan0 No such device
 
 une idée ?
 
 
 --
 Frédéric ZULIAN
essaie,
 iwconfig eth0 
dès fois ce n'est pas wlan0 mais eth0 pour le wifi.
essaie aussi:
 lsmod pour voir si les modules sont bien installés.
des idées seulement.
Philippe Merlin

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/8330288.uGInGDzFmm@portable

Re: Wlan broadcom wifi et driver

2015-02-15 Thread zulian

Le Sunday 15 February 2015 18:19:52 Bernard Schoenacker a écrit :
 Le Sun, 15 Feb 2015 18:07:00 +0100,
 frederic zulian zul...@free.fr a écrit :
 
  Bonjour,
  
  OS : Debian , 3.16.0-4-amd64
  
  Sur mon eepc j'ai un chipset broadcom pour la wifi :
  
  -- 02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn
  Wireless Network Adapter (rev 01)
  
  J'ai installé le driver avec ndiswrapper
  
  ndiswrapper -l
  bcmwl6 : driver installed
  device (14E4:4727) present (alternate driver: bcma)
  
  
   iwconfig wlan0  répondwlan0 No such device
  
  une idée ?
  
  
  --
  Frédéric ZULIAN
 
 
 bonjour,
 
 la solution en se trouve pas là mais ici :
 
 apt-cache search broadcom wireless
 
 broadcom-sta-common - Common files for the Broadcom STA Wireless driver
 broadcom-sta-dkms - dkms source for the Broadcom STA Wireless driver
 broadcom-sta-source - Source for the Broadcom STA Wireless driver
 firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
 openfwwf - Open firmware for Broadcom BCM43xx (b43) wlan devices
 b43-asm - assembler and disassembler for Broadcom BCM43xx firmware
 
 serait il possible de donner la listre des paquets installés ayant
 trait au réseau wifi afin de vérifier les point qui pourraient poser
 problême ...
 
 slt
 bernard

Bonjour,

J'ai deux des paquets qu'apt ne trouve pas :

apt-get install  openfwwf
E: Impossible de trouver le paquet openfwwf

apt-get install   b43-asm
E: Impossible de trouver le paquet b43-asm


Les paquets installés concernant le wifi : 

b43-fwcutter - utility for extracting Broadcom 43xx firmware
firmware-b43-installer - firmware installer for the b43 driver
broadcom-sta-dkms - dkms source for the Broadcom STA Wireless driver
broadcom-sta-source - Source for the Broadcom STA Wireless driver
firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel
xfce4-wavelan-plugin - wavelan status plugin for the Xfce4 panel
ndisgtk - graphical frontend for ndiswrapper (installation of Windows WiFi 
drivers)
wicd-curses - gestionnaire de réseau filaire et sans fil - client en mode texte
wicd-daemon - gestionnaire de réseau filaire et sans-fil -- démon
wicd-gtk - gestionnaire de réseau filaire et sans fil - client GTK+
urfkill - wireless killswitch management daemon for laptops
wifi-radar - graphical utility for managing Wi-Fi profiles
wifite - Python script to automate wireless auditing using aircrack-ng tools
aircrack-ng - utilitaires de recherche de clés wifi WEP/WPA

A +

-- 
Frédéric ZULIAN
F1sxo

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: https://lists.debian.org/7502964.ePnKHCMjF8@fred-bureau

Re: Wlan broadcom wifi et driver

2015-02-15 Thread Bernard Schoenacker

Le Sun, 15 Feb 2015 21:39 +0100,
zulian zul...@free.fr a écrit :

 Le Sunday 15 February 2015 18:19:52 Bernard Schoenacker a écrit :
  Le Sun, 15 Feb 2015 18:07:00 +0100,
  frederic zulian zul...@free.fr a écrit :
  
   Bonjour,
   
   OS : Debian , 3.16.0-4-amd64
   
   Sur mon eepc j'ai un chipset broadcom pour la wifi :
   
   -- 02:00.0 Network controller: Broadcom Corporation BCM4313
   802.11bgn Wireless Network Adapter (rev 01)
   
   J'ai installé le driver avec ndiswrapper
   
   ndiswrapper -l
   bcmwl6 : driver installed
   device (14E4:4727) present (alternate driver: bcma)
   
   
iwconfig wlan0  répondwlan0 No such device
   
   une idée ?
   
   
   --
   Frédéric ZULIAN
  
  
  bonjour,
  
  la solution en se trouve pas là mais ici :
  
  apt-cache search broadcom wireless
  
  broadcom-sta-common - Common files for the Broadcom STA Wireless
  driver broadcom-sta-dkms - dkms source for the Broadcom STA
  Wireless driver broadcom-sta-source - Source for the Broadcom STA
  Wireless driver firmware-brcm80211 - Binary firmware for Broadcom
  802.11 wireless cards openfwwf - Open firmware for Broadcom BCM43xx
  (b43) wlan devices b43-asm - assembler and disassembler for
  Broadcom BCM43xx firmware
  
  serait il possible de donner la listre des paquets installés ayant
  trait au réseau wifi afin de vérifier les point qui pourraient poser
  problême ...
  
  slt
  bernard
 
 Bonjour,
 
 J'ai deux des paquets qu'apt ne trouve pas :
 
 apt-get install  openfwwf
 E: Impossible de trouver le paquet openfwwf
 
 apt-get install   b43-asm
 E: Impossible de trouver le paquet b43-asm
 
 
 Les paquets installés concernant le wifi : 
 
 b43-fwcutter - utility for extracting Broadcom 43xx firmware
 firmware-b43-installer - firmware installer for the b43 driver
 broadcom-sta-dkms - dkms source for the Broadcom STA Wireless driver
 broadcom-sta-source - Source for the Broadcom STA Wireless driver
 firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless
 cards firmware-linux-nonfree - Binary firmware for various drivers in
 the Linux kernel xfce4-wavelan-plugin - wavelan status plugin for the
 Xfce4 panel ndisgtk - graphical frontend for ndiswrapper
 (installation of Windows WiFi drivers)
 wicd-curses - gestionnaire de réseau filaire et sans fil - client en
 mode texte wicd-daemon - gestionnaire de réseau filaire et sans-fil
 -- démon wicd-gtk - gestionnaire de réseau filaire et sans fil -
 client GTK+ urfkill - wireless killswitch management daemon for
 laptops wifi-radar - graphical utility for managing Wi-Fi profiles
 wifite - Python script to automate wireless auditing using
 aircrack-ng tools aircrack-ng - utilitaires de recherche de clés wifi
 WEP/WPA
 
 A +
 

bonjour,

pour les paquets manquants il sufit d'adjoindre aptosid dans le
sources.list :

http://aptosid.com/index.php?module=Contentfunc=viewpid=2

slt
bernard

-- 
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe
vers debian-user-french-requ...@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150216083342.34381dff.bernard.schoenac...@free.fr

Re: WLAN router doesn't provide fix IP addresses

2014-11-03 Thread Lisi Reisz

On Friday 31 October 2014 08:45:41 Karl E. Jorgensen wrote:
 There is nothing wrong with configuring a server with a fixed IP
 address (=not use DHCP client), as long as you use the correct
 network, netmask and default gateway.

This would appear to me to be the obvious solution.  Is there a problem with 
it?

The catch, of course, is that you have to find a way of ensuring that the 
fixed IPs are not immediately given out to other boxen by DHCP. 

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201411040436.38005.lisi.re...@gmail.com

WLAN router doesn't provide fix IP addresses

2014-10-31 Thread B. M.

Hi list,

I have a problem with my (w)lan setup.
We use telephone and internet over the cable network and the company gives us a 
wlan modem for free. Unfortunately this modem doesn't allow me to specify fix 
IPs in the internal network for all of our machines.

Nevertheless I setup an owncloud server on one machine (which is somehow our 
server but not always running), including SSL encryption with a self-signed 
certificate for its IP address. That worked well for a couple of months because 
the IP addresses didn't change (although they were not fixed).

Now due to a technical problem our modem got replaced all of the IP addresses 
changed. (I did expect that for sometime in the future... but not so early...)

Since it's impossible to manually define the IP addresses, I've a problem. Of 
course I could create a new certificate, put it on all other machines and 
adjust all settings (owncloud server address...); but that's quite an hassle.

So I wanted to ask if there are other possibilities? I can define one or two 
DNS server in the modem's config. Would it work to setup my main machine (which 
is not always running) as an internal DNS server and use the hostnames instead 
of the IP addresses?

Thanks for any pointers to how I can proceed.

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8a103117-37c7-4712-9804-d72d6e5b8...@gmx.ch

Re: WLAN router doesn't provide fix IP addresses

2014-10-31 Thread Karl E. Jorgensen

Hi

On Fri, Oct 31, 2014 at 09:28:33AM +0100, B. M. wrote:
 Hi list,
 
 I have a problem with my (w)lan setup.  We use telephone and
 internet over the cable network and the company gives us a wlan
 modem for free. Unfortunately this modem doesn't allow me to specify
 fix IPs in the internal network for all of our machines.

Well - even if it doesn't, surely it allows you to specify which
*range* of IP addresses should be used for DHCP?

There is nothing wrong with configuring a server with a fixed IP
address (=not use DHCP client), as long as you use the correct
network, netmask and default gateway.

 Nevertheless I setup an owncloud server on one machine (which is
 somehow our server but not always running), including SSL
 encryption with a self-signed certificate for its IP address. That
 worked well for a couple of months because the IP addresses didn't
 change (although they were not fixed).

Oh. certificates for IP addresses is a new one on me :-)

 Now due to a technical problem our modem got replaced all of the IP
 addresses changed. (I did expect that for sometime in the
 future... but not so early...)
 
 Since it's impossible to manually define the IP addresses, I've a
 problem. Of course I could create a new certificate, put it on all
 other machines and adjust all settings (owncloud server address...);
 but that's quite an hassle.

Do the machines use avahi (or mdns? I'm actually not sure of the name,
but having libnss-mdns installed and mdns4 mentioned in
/etc/nsswitch.conf would indicate so).

If so, you should be able to use ${hostname}.local instead of an IP
address, and the multicast DNS resolution would sort things out.
 
 So I wanted to ask if there are other possibilities? I can define
 one or two DNS server in the modem's config. Would it work to setup
 my main machine (which is not always running) as an internal DNS
 server and use the hostnames instead of the IP addresses?

That is also a possibility. But if it is only for facilitating a
single server, then it's overkill.  And it adds a single point of
failure too: you would not be able to resolve IP addresses while the
machine is down.

If you already own/run a domain, you can also add a A record in the
DNS for this to point to it - e.g. owncloud.example.com IN A
192.168.0.45.

Using an entry in /etc/hosts is also an option.

Hope this helps
-- 
Karl E. Jorgensen


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141031084541.GB22377@hawking

Re: WLAN router doesn't provide fix IP addresses

2014-10-31 Thread B. M.

Thanks a lot for the answer, I think I'll look deeper into avahi.


Le 31 oct. 2014 à 09:45, Karl E. Jorgensen k...@jorgensen.org.uk a écrit :

 Hi
 
 On Fri, Oct 31, 2014 at 09:28:33AM +0100, B. M. wrote:
 Hi list,
 
 I have a problem with my (w)lan setup.  We use telephone and
 internet over the cable network and the company gives us a wlan
 modem for free. Unfortunately this modem doesn't allow me to specify
 fix IPs in the internal network for all of our machines.
 
 Well - even if it doesn't, surely it allows you to specify which
 *range* of IP addresses should be used for DHCP?
 
 There is nothing wrong with configuring a server with a fixed IP
 address (=not use DHCP client), as long as you use the correct
 network, netmask and default gateway.
 
 Nevertheless I setup an owncloud server on one machine (which is
 somehow our server but not always running), including SSL
 encryption with a self-signed certificate for its IP address. That
 worked well for a couple of months because the IP addresses didn't
 change (although they were not fixed).
 
 Oh. certificates for IP addresses is a new one on me :-)
 
 Now due to a technical problem our modem got replaced all of the IP
 addresses changed. (I did expect that for sometime in the
 future... but not so early...)
 
 Since it's impossible to manually define the IP addresses, I've a
 problem. Of course I could create a new certificate, put it on all
 other machines and adjust all settings (owncloud server address...);
 but that's quite an hassle.
 
 Do the machines use avahi (or mdns? I'm actually not sure of the name,
 but having libnss-mdns installed and mdns4 mentioned in
 /etc/nsswitch.conf would indicate so).
 
 If so, you should be able to use ${hostname}.local instead of an IP
 address, and the multicast DNS resolution would sort things out.
 
 So I wanted to ask if there are other possibilities? I can define
 one or two DNS server in the modem's config. Would it work to setup
 my main machine (which is not always running) as an internal DNS
 server and use the hostnames instead of the IP addresses?
 
 That is also a possibility. But if it is only for facilitating a
 single server, then it's overkill.  And it adds a single point of
 failure too: you would not be able to resolve IP addresses while the
 machine is down.
 
 If you already own/run a domain, you can also add a A record in the
 DNS for this to point to it - e.g. owncloud.example.com IN A
 192.168.0.45.
 
 Using an entry in /etc/hosts is also an option.
 
 Hope this helps
 -- 
 Karl E. Jorgensen
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/20141031084541.GB22377@hawking
 


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/34b18072-a4bf-4c61-9d30-64924c7cf...@gmx.ch

Re: WLAN router doesn't provide fix IP addresses

2014-10-31 Thread Catalin Soare

On Oct 31, 2014 11:24 AM, B. M. b-m...@gmx.ch wrote:

 Thanks a lot for the answer, I think I'll look deeper into avahi.


 Le 31 oct. 2014 à 09:45, Karl E. Jorgensen k...@jorgensen.org.uk a
écrit :

  Hi
 
  On Fri, Oct 31, 2014 at 09:28:33AM +0100, B. M. wrote:
  Hi list,
 
  I have a problem with my (w)lan setup.  We use telephone and
  internet over the cable network and the company gives us a wlan
  modem for free. Unfortunately this modem doesn't allow me to specify
  fix IPs in the internal network for all of our machines.
 
  Well - even if it doesn't, surely it allows you to specify which
  *range* of IP addresses should be used for DHCP?
 
  There is nothing wrong with configuring a server with a fixed IP
  address (=not use DHCP client), as long as you use the correct
  network, netmask and default gateway.
 
  Nevertheless I setup an owncloud server on one machine (which is
  somehow our server but not always running), including SSL
  encryption with a self-signed certificate for its IP address. That
  worked well for a couple of months because the IP addresses didn't
  change (although they were not fixed).
 
  Oh. certificates for IP addresses is a new one on me :-)
 
  Now due to a technical problem our modem got replaced all of the IP
  addresses changed. (I did expect that for sometime in the
  future... but not so early...)
 
  Since it's impossible to manually define the IP addresses, I've a
  problem. Of course I could create a new certificate, put it on all
  other machines and adjust all settings (owncloud server address...);
  but that's quite an hassle.
 
  Do the machines use avahi (or mdns? I'm actually not sure of the name,
  but having libnss-mdns installed and mdns4 mentioned in
  /etc/nsswitch.conf would indicate so).
 
  If so, you should be able to use ${hostname}.local instead of an IP
  address, and the multicast DNS resolution would sort things out.
 
  So I wanted to ask if there are other possibilities? I can define
  one or two DNS server in the modem's config. Would it work to setup
  my main machine (which is not always running) as an internal DNS
  server and use the hostnames instead of the IP addresses?
 
  That is also a possibility. But if it is only for facilitating a
  single server, then it's overkill.  And it adds a single point of
  failure too: you would not be able to resolve IP addresses while the
  machine is down.
 
  If you already own/run a domain, you can also add a A record in the
  DNS for this to point to it - e.g. owncloud.example.com IN A
  192.168.0.45.
 
  Using an entry in /etc/hosts is also an option.
 
  Hope this helps
  --
  Karl E. Jorgensen
 
 
  --
  To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
  Archive: https://lists.debian.org/20141031084541.GB22377@hawking
 


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
 Archive:
https://lists.debian.org/34b18072-a4bf-4c61-9d30-64924c7cf...@gmx.ch


You could also look into building your own dns+dhcp server. I have a
Raspberry pi, which is always on and runs isc-dhcp-server and bind9.

Or you could try dnsmask, might prove easier to setup/maintain.

The list will assist with any of these.

Cheers!

--
Sent from my Brick(TM)

Re: WLAN router doesn't provide fix IP addresses

2014-10-31 Thread Simon Hollenbach


Hello,

On 31/10/14 09:45, Karl E. Jorgensen wrote:

On Fri, Oct 31, 2014 at 09:28:33AM +0100, B. M. wrote:

Hi list,

I have a problem with my (w)lan setup.  We use telephone and
internet over the cable network and the company gives us a wlan
modem for free. Unfortunately this modem doesn't allow me to specify
fix IPs in the internal network for all of our machines.


Well - even if it doesn't, surely it allows you to specify which
*range* of IP addresses should be used for DHCP?

There is nothing wrong with configuring a server with a fixed IP
address (=not use DHCP client), as long as you use the correct
network, netmask and default gateway.

That seems the way to go to me.

Nevertheless I setup an owncloud server on one machine (which is
somehow our server but not always running), including SSL
encryption with a self-signed certificate for its IP address. That
worked well for a couple of months because the IP addresses didn't
change (although they were not fixed).

Now due to a technical problem our modem got replaced all of the IP
addresses changed. (I did expect that for sometime in the
future... but not so early...)

Since it's impossible to manually define the IP addresses, I've a
problem. Of course I could create a new certificate, put it on all
other machines and adjust all settings (owncloud server address...);
but that's quite an hassle.


Do the machines use avahi (or mdns? I'm actually not sure of the name,
but having libnss-mdns installed and mdns4 mentioned in
/etc/nsswitch.conf would indicate so).


A quick research suggests you need avahi-daemon for propagation of 
.local-domains, e.g. for machines that need to be discovered, and 
libnss-mdns for discovery of the former.


For the name, the description of libnss-mdns says:
Multicast DNS (using Zeroconf, aka Apple Bonjour / Apple Rendezvous )
It seems to have many names.


If so, you should be able to use ${hostname}.local instead of an IP
address, and the multicast DNS resolution would sort things out.


So I wanted to ask if there are other possibilities? I can define
one or two DNS server in the modem's config. Would it work to setup
my main machine (which is not always running) as an internal DNS
server and use the hostnames instead of the IP addresses?


That is also a possibility. But if it is only for facilitating a
single server, then it's overkill.  And it adds a single point of
failure too: you would not be able to resolve IP addresses while the
machine is down.


Maybe I'm mistaken, but wouldn't this just shift the problem to the 
internal DNS? It will still need a static IP or mDNS. Adding to that, it 
would need to be the only DNS in the router's config, as you cannot 
guarantee which one the router will use otherwise and the owncloud 
server wouldn't be discoverable via the second(public) DNS. And having 
your only DNS on a machine which is not always running seems a bad idea.



If you already own/run a domain, you can also add a A record in the
DNS for this to point to it - e.g. owncloud.example.com IN A
192.168.0.45.


That would need dynamic DNS if the IP is still obtained via DHCP. And 
having a public DNS propagating a private IP will make reverse lookups 
impossible, I think. Correct my if I'm wrong.


Using an entry in /etc/hosts is also an option.


This seems the way to make the machine discoverable by name, but would 
still need a fixed IP for the owncloud server.


Summarizing, mDNS generally seems to be the easiest way. But if you use 
a static IP for your owncloud server you will need to change less with 
your current setup, it seems.


Best wishes,
Simon


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5453890d.8010...@gmail.com

RT8192CU Wlan - Not Working!

2013-06-14 Thread James Hill


Hi Guys,

I have the above WLAN USB adapter.

I have followed the setup detail here:

http://wiki.debian.org/rtl819x#Debian_7.0_.22Wheezy.22

And the config detail here:

http://wiki.debian.org/WiFi/HowToUse#Command_Line

But it will not work!

All I get is:

Listening on LPF/wlan0/00:0b:81:89:61:f9
Sending on   LPF/wlan0/00:0b:81:89:61:f9
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


For some reason, whatever it may be it will not associate with the AP.

I had the same issue with Wheezy  an identical adapter on the Raspberry 
Pi, and had to overcome that by running an automated setup script that 
some guy on the Pi forum had written - but it only works for the Pi!


Are the drivers wrong?

lsusb  lsmod show the device  drivers loaded. dmesg shows it loading 
the firmware etc.


ifconfig shows it sending  receiving packets.

I'm at a total loss! I've been on this for 2 days now, and I cannot see 
what is wrong!


Can anybody throw some light on it before I can it and give up? I'm not 
going to let it beat me!


Thanks,

James


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/51bb64b8.6050...@gmail.com

wlan interface problem

2012-11-30 Thread Mostafa Hashemi

Hi all
I am using Debian 6 squeeze on my vaio fw235j with an intel wireless card
. This is not recognizable by my OS.
This is the output of rfkill :

root@debian:~# rfkill list
0: sony-wwan: Wireless WAN
Soft blocked: no
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
root@debian:~# rfkill unblock all
root@debian:~# rfkill list
0: sony-wwan: Wireless WAN
Soft blocked: no
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
root@debian:~#

There is no changes 

What should i do ?

Thanks

Re: wlan interface problem

2012-11-30 Thread Morel Bérenger

 What should i do ?


 Thanks

Checks if the driver is correctly installed? (if I am not wrong, #lsmod
should give you a list of modules on your machine)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/963c34e696aca2367ed4b85d618222a2.squir...@www.sud-ouest.org

Re: wlan interface problem

2012-11-30 Thread Andrei POPESCU

On Vi, 30 nov 12, 13:14:45, Mostafa Hashemi wrote:
 Hi all
 I am using Debian 6 squeeze on my vaio fw235j with an intel wireless card
 . This is not recognizable by my OS.

You probably need the firmware-iwlwifi package. Install it, reboot and 
if you still have problems post the output of 'lspci -nn'.

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: wlan interface problem

2012-11-30 Thread Gean Ceretta

- Original Message -
From: Andrei POPESCU
Sent: 11/30/12 08:28 AM
To: debian-user@lists.debian.org
Subject: Re: wlan interface problem

 On Vi, 30 nov 12, 13:14:45, Mostafa Hashemi wrote:  Hi all  I am using 
Debian 6 squeeze on my vaio fw235j with an intel wireless card  . This is not 
recognizable by my OS. You probably need the firmware-iwlwifi package. Install 
it, reboot and if you still have problems post the output of 'lspci -nn'. Kind 
regards, Andrei -- Offtopic discussions among Debian users and developers: 
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

 you have to enable the non-free repository to install firmware-iwlwifi, follow 
this wiki: http://wiki.debian.org/iwlwifi

--
 Gean Michel Ceretta - geancere...@linuxmail.org - geancere...@gmail.com - +55 
046 9111 8829

Re: WLAN Access Point with Intel 4965 network controller

2012-11-14 Thread Massimo

Ramon Hofer ramonhofer at bluewin.ch writes:

 
 On Thu, 05 Jan 2012 08:38:05 -0500, Celejar wrote:
 
  On Thu, 5 Jan 2012 00:32:02 + (UTC) Ramon Hofer
  ramonhofer at bluewin.ch wrote:
  
  I'm using Squeeze with 2.6.32-5-686 and I'm trying to configure my
  Thinkpad X61s to act as WLAN Access Point. It has an Intel 4965
  chipset:
  
  # lspci
  03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or
  AGN [Kedron] Network Connection (rev 61)
  
  ...
  
  Maybe the controller can't be used in master mode? Here's the output of
  # iw phy phy0 info
  http://pastebin.com/LCbYFghh
  
  It says on lines 20ff:
 Supported interface modes:
  * IBSS
  * managed
  * monitor
  
  As far as I understand this is a problem as there should also be master
  listed?
  
  According to Wikipedia, the iwlwifi drivers indeed do not support master
  mode:
  
  http://en.wikipedia.org/wiki/Comparison_of_open-Now the wiki tell that
iwlwifi support Master Mode: 

http://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers

but I try and it seems to not work 

iw phy phy0 info | less

Supported interface modes:
 * IBSS
 * managed
 * monitor
software interface modes (can always be added):
 * monitor
.




even if the output of iw command show something about 
AP and AP/VLAN for TX and RX frames:

Supported TX frame types:
 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 
 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0
 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 
 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0
 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x
 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x...
 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60..
Supported RX frame types:
 * IBSS: 0xb0 0xc0 0xd0
 * managed: 0x40 0xd0
 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
 * mesh point: 0xb0 0xc0 0xd0
 * P2P-client: 0x40 0xd0
 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0



using the last firmware available for iwlwifi:

# modinfo iwl4965
filename:  
/lib/modules/3.6-6.slh.3-aptosid-amd64/kernel/drivers/net/wirel
ess/iwlegacy/iwl4965.ko
firmware:   iwlwifi-4965-2.ucode
alias:  iwl4965
license:GPL
author: Copyright(c) 2003-2011 Intel Corporation i...@linux.intel.com
version:in-tree:
description:Intel(R) Wireless WiFi 4965 driver for Linux
srcversion: 5ACB01E1C39795670D74138
alias:  pci:v8086d4230sv*sd*bc*sc*i*
alias:  pci:v8086d4229sv*sd*bc*sc*i*
depends:iwlegacy,cfg80211,mac80211
intree: Y
vermagic:   3.6-6.slh.3-aptosid-amd64 SMP preempt mod_unload modversions 
parm:   swcrypto:using crypto in software (default 0 [hardware]) (int)
parm:   queues_num:number of hw queues. (int)
parm:   11n_disable:disable 11n functionality (int)
parm:   amsdu_size_8K:enable 8K amsdu size (int)
parm:   fw_restart:restart firmware in case of error (int)


there is someone who know why? and how to activate the AP or AP/VLAN mode? 

regards

Massimo





 source_wireless_drivers#Driver_capabilities
  
  :( My T61 also has that card ...
 
 That's too bad 
 
 But I was able to use my old Thinkpad T43 as a AP 
 
 Regards
 Ramon
 





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/loom.20121114t182839...@post.gmane.org

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 1510 matches

Mail list logo