Jeff writes:
> I would probably contact the FCC and see what their [the FTC] position
> is when a city attempts to grant a monopoly to a service provider.
Cities can decide who they allow to string cables over or under their
streets. They can't regulate radio, though.
> It does not affect your
pocket writes:
> wireless "high-speed" Internet access is prohibited as stated in the
> agreement (made in the year 1995) between city council and time warner
> who was bought out by charter/spectrum
That's binding on the city government, not on you. In the USA the city
, then
it is possible that even if wireless "high-speed" Internet access could
in a technical sense work in that area it might be prohibited in a
contractual sense.
You are exactly correct
wireless "high-speed" Internet access is prohibited as stated in the agreement
(made in the year 1995)
provider, I leave un-discussed for at least the time
> being.)
>
> If that is correct, and if Pocket resides in such an environment, then
> it is possible that even if wireless "high-speed" Internet access could
> in a technical sense work in that area it might be prohibited in a
&
live now when I moved here, where all utilities except
satellite dishes and TV antennas are underground. It still applies for wired
broadband, but now there's wireless to compete with it.
No other providers are allowed.
That could be a historical concept, depending exactly on where you live. Some
live now when I moved here, where all utilities except
satellite dishes and TV antennas are underground. It still applies for wired
broadband, but now there's wireless to compete with it.
>>> No other providers are allowed.
>> That could be a historical concept, depending exactly on
of motivations for doing this, on the part of both the
management and the provider, I leave un-discussed for at least the time
being.)
If that is correct, and if Pocket resides in such an environment, then
it is possible that even if wireless "high-speed" Internet access could
in a technical
On 12/20/23 19:39, Felix Miata wrote:
Pocket composed on 2023-12-20 17:55 (UTC-0500):
Actually I can not change as the ISP has exclusive rights to the high
speed internet in the area I reside in.
No other providers are allowed.
That could be a historical concept, depending exactly on where
ely
through the provider chosen by the management of the apartment building.
(The question of motivations for doing this, on the part of both the
management and the provider, I leave un-discussed for at least the time
being.)
If that is correct, and if Pocket resides in such an environment, then
it is possi
Pocket composed on 2023-12-20 17:55 (UTC-0500):
> Actually I can not change as the ISP has exclusive rights to the high
> speed internet in the area I reside in.
>
> No other providers are allowed.
That could be a historical concept, depending exactly on where you live. Some of
us mericans who
Am Freitag, dem 14.07.2023 um 21:52 +0200 schrieb zithro:
> On 14 Jul 2023 10:53, Joe wrote:
> > On Fri, 14 Jul 2023 09:27:12 +0200
> > Bruno Kleinert wrote:
> >
> > > Hello,
> > >
> > > I'm looking for a wireless way to measure temperature and h
I was just researching this myself a couple of days ago, and spent
several hours going down a rabbit hole.
It seems that many folks are going the way of using an open source
solution, Home Assistant (aka, HA), (https://www.home-assistant.io/).
Even to the point where I found that folks that used
zithro wrote:
> On 14 Jul 2023 10:53, Joe wrote:
> > On Fri, 14 Jul 2023 09:27:12 +0200
> > Bruno Kleinert wrote:
> >
> >> Hello,
> >>
> >> I'm looking for a wireless way to measure temperature and humidity
> >> indoor with hardw
On Fri, 14 Jul 2023 21:52:01 +0200
zithro wrote:
>
> Joe, out of curiosity, what are you using to display the graphs ?
> If you didn't read above, I'm using jpgraph, a PHP lib.
>
Basic stuff, Imagick which is a PHP binding to some ImageMagick
functions.
--
Joe
On 14 Jul 2023 10:53, Joe wrote:
On Fri, 14 Jul 2023 09:27:12 +0200
Bruno Kleinert wrote:
Hello,
I'm looking for a wireless way to measure temperature and humidity
indoor with hardware off the shelf and software included in Debian 12
bookworm.
Sensors --> Radio --> Receiver --> An
Nate Bargmann wrote:
> * On 2023 14 Jul 02:37 -0500, Bruno Kleinert wrote:
> > Hello,
> >
> > I'm looking for a wireless way to measure temperature and humidity
> > indoor with hardware off the shelf and software included in Debian
> > 12 bookworm.
>
>
On Fri, Jul 14, 2023 at 3:37 AM Bruno Kleinert wrote:
>
> I'm looking for a wireless way to measure temperature and humidity indoor
> with hardware off the shelf and software included in Debian 12 bookworm.
>
> Sensors --> Radio --> Receiver --> Any typical PC interface
* On 2023 14 Jul 02:37 -0500, Bruno Kleinert wrote:
> Hello,
>
> I'm looking for a wireless way to measure temperature and humidity
> indoor with hardware off the shelf and software included in Debian 12
> bookworm.
Off the shelf the Davis Vantage Pro 2 is probably one of the m
On 14/7/23 15:27, Bruno Kleinert wrote:
Do you have any hardware recommendations and can you share experience?
The big problem is power at the collection point. Some people use a
solar panel and batteries but other options are available
Once you know your power budget you can use a
On Fri, 14 Jul 2023 09:27:12 +0200
Bruno Kleinert wrote:
> Hello,
>
> I'm looking for a wireless way to measure temperature and humidity
> indoor with hardware off the shelf and software included in Debian 12
> bookworm.
>
> Sensors --> Radio --> Receiver -->
Hello,
I'm looking for a wireless way to measure temperature and humidity
indoor with hardware off the shelf and software included in Debian 12
bookworm.
Sensors --> Radio --> Receiver --> Any typical PC interface, e.g., USB,
Ethernet.
I don't need a visual interface, but plan t
pt with mirrors and updated the
> apt cache. however, upon reboot after the install, the wireless nic isn't
> configured. it did say wlan0 is now wlp2s0 in dmesg.
>
> last done using same iso was to install the DE and kde plasma. now that
> selection have my nic remained configured a
, the wireless nic isn't
configured. it did say wlan0 is now wlp2s0 in dmesg.
last done using same iso was to install the DE and kde plasma. now that
selection have my nic remained configured and working with dhcp.
why is that? is there a way to NOT install the DE and still have the
wireless nic remain
On Sun 05 Mar 2023 at 20:57:25 (+), Albretch Mueller wrote:
> On 3/5/23, David Wright wrote:
> >
> > I run installed systems, so wifi passwords are either in individual
> > /var/lib/iwd/.psk files (with iwd), or collectively in
> > /etc/wpa_supplicant/.conf (with
David Wright writes:
> So what was wrong with using a .link file like:
>
> [Match]
> Type=wwan
> [Link]
> NamePolicy=keep kernel
>
> or
>
> [Match]
> Type=wwan
> [Link]
> Name=my4g
>
> Did this not work?
Nothing was wrong but I just added a few lines to my management script
to
henever I boot it.
>>
>> sudo iwlist wlp2s0 scan | grep ESSID
>>
>> will list the wireless networks around. All I need now is a way to
>> somehow pass the password into the script in the command line of
>> through a config file so that I don't have to enter it ever
On Sun 05 Mar 2023 at 21:22:10 (+0200), Anssi Saari wrote:
> Curt writes:
>
> > * UNPREDICTABILITY
> > it turns out even after all this [**an enumeration of complications and
> > corner
> > cases**] there are still reported cases of interfaces changing their name
> > on a
> > reboot.
>
> I
ally in the first few seconds after
> > booting up.
>
> I would always go into exposed mode using a DL DVD that is what I
> meant when I said "re start". So, I will need to run a dkpg script
> whenever I boot it.
>
> sudo iwlist wlp2s0 scan | grep ESSID
>
I thought “unpredictability” was the name of my daily drama show, but
apparently “I am not the only one”. Yes, I know javascript is the
primary vector they use to mess with whomever they choose, regardless
of if they wear a “tiny tin hat” or expensive shoes.
In my case, among many other things,
On Sun, Mar 05, 2023 at 09:22:10PM +0200, Anssi Saari wrote:
> I have just this fun kind of unpredictability in my router's 4G
> module. Mostly, it comes up as wwan0 but sometimes it's wwx. So
> I put something in my 4G management script to rename such interface if
> there's no wwan0.
If you're
Curt writes:
> * UNPREDICTABILITY
> it turns out even after all this [**an enumeration of complications and corner
> cases**] there are still reported cases of interfaces changing their name on a
> reboot.
I have just this fun kind of unpredictability in my router's 4G
module. Mostly, it comes
2023-03-04, Jeffrey Walton wrote:
> On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>>
>> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
>> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
>> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
>> > > >
e using a DL DVD that is what I
meant when I said "re start". So, I will need to run a dkpg script
whenever I boot it.
sudo iwlist wlp2s0 scan | grep ESSID
will list the wireless networks around. All I need now is a way to
somehow pass the password into the script in the command li
On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>
> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > > The 'p' is a pci bus, the 's' is a slot
On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > does not move around once
gt; # modprobe ath10k_pci
> >
> > and check dmesg again.
>
> Bingo! Those were the steps that enable me to see the wireless
> network with nmtui ...
Good to hear.
> a) sudo rmmod ath10k_pci
>
> b) cat /proc/modules | grep "ath10k_pci"
>
> c) sud
t (I will when I get a chance, in
fact, dmesg logs should do), but booting the 16Gb RAM laptop I am
using right now with a Debian Live DVD takes definitely more than one
minute.
Something else "weird" that I noticed is that the BIOS not only kept
a connection to a wireless network around
On Fri, Mar 03, 2023 at 06:09:40PM -0500, Greg Wooledge wrote:
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like
On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
>
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like 'enp4s0'.
On 3/3/23, David Wright wrote:
>
> Try removing the atheros module with:
>
> # rmmod ath10k_pci
>
> (check its name in /proc/modules), and then reload it with
>
> # modprobe ath10k_pci
>
> and check dmesg again.
Bingo! Those were the steps that enable
On Fri, Mar 3, 2023 at 6:36 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller wrote:
>
>> since it was included in the Linux kernel anyway I (apparently
>> wrongly) thought I didn't have to install any packages. After
>>
On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install
On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> The 'p' is a pci bus, the 's' is a slot number. Since the interface
> does not move around once installed, the interface will always have
> the same name like 'enp4s0'.
That's a wonderful idea, but it doesn't quite work in
configuration: broadcast=yes driver=r8169
> driverversion=5.10.0-18-amd64 latency=0 link=no multicast=yes
>resources: irq:16 ioport:3000(size=256)
> memory:9140-91400fff memory:9120-91203fff
> *-network
>description: Network controller
>
On Fri 03 Mar 2023 at 21:45:27 (+), Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install
Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
> Selecting previously
since it was included in the Linux kernel anyway I (apparently
wrongly) thought I didn't have to install any packages. After
downloading and installing the required firmware:
$ sudo dpkg --install firmware-atheros_20210315-3_all.deb
Selecting previously unselected package firmware-atheros.
6.ad812ee0.0
8265-36.ucode op_mode iwlmvm
[2.649050] iwlwifi :04:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)
[2.802163] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC
8265, REV=0x230
[2.862957] iwlwifi :04:00.0: base HW address: 00:e1:8c:eb:ce:bd
[
On Fri, Mar 3, 2023 at 12:01 PM Albretch Mueller wrote:
> On 3/3/23, Timothy M Butterworth wrote:
> > Just run `ip link` or `ip address` and it will show you the name.
>
> I had already done so, but I don't see the "logical name" or the IP
> of the wireless interfa
On 3/3/23, Timothy M Butterworth wrote:
> Just run `ip link` or `ip address` and it will show you the name.
I had already done so, but I don't see the "logical name" or the IP
of the wireless interface on my very "temperamental" DELL Inspiron
which seems to have a mind
On Fri, Mar 3, 2023 at 10:46 AM Albretch Mueller wrote:
> $ sudo lspci | grep --ignore-case Wireless
> 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
> Network Adapter (rev 31)
> $
>
> $ sudo lshw -class network
> *-network DISABLED
>
$ sudo lspci | grep --ignore-case Wireless
02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
Network Adapter (rev 31)
$
$ sudo lshw -class network
*-network DISABLED
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
Hi Maximiliano
10.09.2022 19:46 tarihinde Maximiliano Estudies yazdı:
I want to use the reportbug feature but I don't know which package I
should enter. Anyone else having similar issues?
My system settings: Linux version 5.18.0-4-amd64
(debian-ker...@lists.debian.org) (gcc-11 (Debian
On 9/10/22 19:46, Maximiliano Estudies wrote:
Hi,
I seem to have hit a bug with the wireless card driver of my laptop.
This happened twice already, my laptop became unresponsive and I
couldn't issue any sudo commands. After hard rebooting the laptop I
see this entries in the syslog:
Sep 10 14
Hi,
I seem to have hit a bug with the wireless card driver of my laptop.
This happened twice already, my laptop became unresponsive and I
couldn't issue any sudo commands. After hard rebooting the laptop I
see this entries in the syslog:
Sep 10 14:51:50 user-thinkpad kernel: mt7921e :03:00.0
Hello,
Since I've installed the package linux-image-amd64 (5.16.12-1~bpo11+1) from
bullseye-backports, the speed of the wireless connection is very unstable.
Ping varies constantly from 5 to 1500 ms while it is stable and around 5 ms for
the other wireless devices running with bullseye 5.10
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will
On 10/5/21 4:25 PM, Gary L. Roach wrote:
Hi again,
I finally found a straight forward installation process for shared
folders. See:
*https://nts.strzibny.name/how-to-set-up-shared-folders-in-virt-manager/*
If you are using something like /home/gary/vmshare as a folder name
use that when
Thanks for the reply
I am interested in printer only. As I stated in my email: The HP printer
is wifi connected to my local network and is accessible by all of the
computers on the network. *This includes the host system*. Right now the
shared folder is probably more important because I can
On Mon, 4 Oct 2021 14:10:21 -0700
"Gary L. Roach" wrote:
> I have my Debian 11 installation as host. I installed Debian 10 on
> qemu/kvm to run a program that needs Qt4. I need to set up a shared
> folder and connection to my wifi networked HP Officejet Pro 8600
> printer.
What do you need
Hi all,
Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-8-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CAICOS
I have my Debian
On Jo, 30 sep 21, 13:24:46, David Wright wrote:
>
> Nor I, but I certainly intend to try it out, and have read through
> that Arch wiki page. It (iwd) is in buster, but then, so is wicd,
> and I've been using wicd/wpa_supplicant for some years with no need
> to change. I'm somewhat surprised that
quot;nm" didn't used to (and may still
> not) play nice with similar packages installed on the same machine. It
> was an either/or situation. I took the "or" with wicd then wicd-curses
> and have never looked back.
With me it was the other way around. I tried wicd,
Stella Ashburne writes:
> Yes, I was referring to using the old script update-resolv-conf with OpenVPN.
>
>> I never got that to do the right thing with any
>> reliability.
>>
> Please explain what you meant by your statement.
>
> I've been using update-resolv-conf with OpenVPN without problems
On 9/30/21, Stella Ashburne wrote:
> Hi
>
> Thanks for sharing your experience with me.
Hi, Stella, you're most welcome. :)
>> Sent: Thursday, September 30, 2021 at 2:38 PM
>> From: "riveravaldez"
>> To: debian-user@lists.debian.org
>> Subject:
On Thu 30 Sep 2021 at 14:46:50 (-0400), Greg Wooledge wrote:
> On Thu, Sep 30, 2021 at 01:30:20PM -0500, David Wright wrote:
> > 192.168.1.1 looks like the d-i ran a DHCP client to get an address
> > for your PC, and that the DHCP server that responded was probably
> > your router, address
st place.
> >>
> >> This remark was, IMO, unnecessary: after all, that's how we learn around
> >> here,
> >> don't we?
> >>
> >> At least that's how I learn.
> >>
> > Bingo. I couldn't agree with you more.
>
> Seriously!!? My wir
On Thu 30 Sep 2021 at 19:33:45 +0200, to...@tuxteam.de wrote:
> On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote:
> > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote:
>
> [...]
>
> > > At least that's how I learn.
> > >
> >
> > That is not me.
>
> People tend
On Thu, Sep 30, 2021 at 02:05:50PM -0400, Henning Follmann wrote:
[...]
> No apology necessary.
OK, thanks.
> I know I am opinionated and right in your
> face (and a reverse snob as my wife regularly points out).
> But I am also a big boy, I can take it if you yell back at me.
Still I try
On Thu, Sep 30, 2021 at 01:30:20PM -0500, David Wright wrote:
> 192.168.1.1 looks like the d-i ran a DHCP client to get an address
> for your PC, and that the DHCP server that responded was probably
> your router, address 192.168.1.1, and so the d-i figured that your
> router would be able to
On Thu 30 Sep 2021 at 15:55:54 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, September 30, 2021 at 1:22 PM
> > From: "David Wright"
> > > [Security]
> > > PreSharedKey=a long string of alphanumeric characters
> > > Passphrase=aquickbrownfoxjumpsoverthelazydog
> >
> > I take it that you
On Thu 30 Sep 2021 at 15:17:03 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, September 30, 2021 at 1:38 PM
> > From: "David Wright"
> >
> > My usual strategy is to let the Debian installer set the dns server to
> > IP address of the router, and configure the router to query 8.8.8.8/1.1.1.1.
On Thu 30 Sep 2021 at 07:21:04 (-0400), Greg Wooledge wrote:
> On Thu, Sep 30, 2021 at 12:38:29AM -0500, David Wright wrote:
> > My usual strategy is to let the Debian installer set the dns server to
> > IP address of the router, and configure the router to query 8.8.8.8/1.1.1.1.
> > It's not
On Thu 30 Sep 2021 at 16:09:44 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, September 30, 2021 at 6:06 AM
> > From: "Dan Ritter"
> >
> > Might I suggest wicd, which people here do have experience with
> > and have used successfully?
> >
> Before writing this reply, I checked with
On 9/30/21, Stella Ashburne wrote:
> Hi Tomas
>
>> Sent: Thursday, September 30, 2021 at 11:48 PM
>> From: to...@de
>> To: debian-user@lists.debian.org
>> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
>> Connection statu
On Thu 30 Sep 2021 at 12:23:45 -0400, Henning Follmann wrote:
> On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote:
> > On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote:
> >
> > [...]
> >
> > > What baffels me is though, at what length someone would go to not use
On Thu, Sep 30, 2021 at 07:33:45PM +0200, to...@tuxteam.de wrote:
> On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote:
> > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote:
>
> [...]
>
> > > At least that's how I learn.
> > >
> >
> > That is not me.
>
> People
On Thu, Sep 30, 2021 at 04:06:09PM +0200, Stella Ashburne wrote:
> Based on the above description, do you think that update-resolv-conf in
> Bullseye will leak the IP addresses of my ISP's DNS resolvers?
It's impossible to tell.
DNS is a simple L7 protocol, so DNS queries can be easily routed to
On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote:
> On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote:
[...]
> > At least that's how I learn.
> >
>
> That is not me.
People tend to be different. That makes things... interesting.
> I will not encourage anyone to
On Thursday, September 30, 2021 12:28:54 PM Stella Ashburne wrote:
> Your statement: "Be bold, go where no man has gone before"
>
> I suppose that "man" refers to both men and women, right? (Just kidding. In
> this time and age, one has to be seen to be politically correct, yes?)
Yes, or at
Stella Ashburne wrote:
> Hi
>
> Thanks for your words of encouragement.
>
> > Sent: Thursday, September 30, 2021 at 11:39 PM
> > From: rhkra...@gmail.com
> > To: debian-user@lists.debian.org
> > Subject: Re: iwd: Using iwd to connect to a wireless network (
Stella Ashburne wrote:
> Hi Dan
>
> > Sent: Thursday, September 30, 2021 at 11:15 PM
> > From: "Dan Ritter"
> > To: "Stella Ashburne"
> > Cc: debian-user@lists.debian.org
> > Subject: Re: iwd: Using iwd to connect to a wireless net
Hi
Thanks for your words of encouragement.
> Sent: Thursday, September 30, 2021 at 11:39 PM
> From: rhkra...@gmail.com
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable
On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote:
> On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote:
>
> [...]
>
> > What baffels me is though, at what length someone would go to not use the
> > default
> > methods to connect via wifi. Especially when they
Hi Tomas
> Sent: Thursday, September 30, 2021 at 11:48 PM
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to surf the net)
>
> On Thu, Sep 30, 202
Hi Dan
> Sent: Thursday, September 30, 2021 at 11:15 PM
> From: "Dan Ritter"
> To: "Stella Ashburne"
> Cc: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to su
On Thu, Sep 30, 2021 at 04:54:17PM +0200, Stella Ashburne wrote:
> Hi Henning
>
> > Sent: Thursday, September 30, 2021 at 10:14 PM
> > From: "Henning Follmann"
> > To: debian-user@lists.debian.org
> > Subject: Re: iwd: Using iwd to connect to a wireless
On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote:
[...]
> What baffels me is though, at what length someone would go to not use the
> default
> methods to connect via wifi. Especially when they showed limited experience
> in networking in the first place.
This remark was, IMO,
On Thursday, September 30, 2021 10:54:17 AM Stella Ashburne wrote:
> Yes, their email address are displayed on the project's website.
>
> No, they didn't mention that any Tom, Dick and Harry are welcome to write
> to them.
Well, thank goodness your name is Stella ;-) (Sorry!)
I think the
Stella Ashburne wrote:
> Oh dear! Oh dear!
>
> After a reboot, I typed the following word at the command prompt:
>
> iwctl
>
> Next, I typed
>
> station wlan0 show
>
> The output was: No device found
Try
ip link show
and look for the name of a device which could be your wifi NIC.
-dsr-
Hi Henning
> Sent: Thursday, September 30, 2021 at 10:14 PM
> From: "Henning Follmann"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to surf the net)
>
>
> Tha
Oh dear! Oh dear!
> Sent: Thursday, September 30, 2021 at 1:22 PM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to surf the net)
>
> >
On Thursday, September 30, 2021 09:19:45 AM Stella Ashburne wrote:
> Do you think any one of them will reply to my email? It's a long shot, I
> know.
You don't have much to lose by sending an email. If it would require a long
email that would take you a fair amount of time to write, you might
On Thu, Sep 30, 2021 at 03:19:45PM +0200, Stella Ashburne wrote:
> Hi
>
> > Sent: Thursday, September 30, 2021 at 2:29 PM
> > From: to...@tuxteam.de
> > To: debian-user@lists.debian.org
> > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
Hi Dan,
Thanks for your reply.
> Sent: Thursday, September 30, 2021 at 6:06 AM
> From: "Dan Ritter"
> To: "Stella Ashburne"
> Cc: "debian-user mailing list"
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Conn
Hi Reco
Thanks for sharing your experience with me.
> Sent: Thursday, September 30, 2021 at 9:52 PM
> From: "Reco"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 2 - DNS
> managers)
>
>
> The limit
Hola David
> Sent: Thursday, September 30, 2021 at 1:22 PM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to surf the net)
>
>
> So t
Hi.
On Thu, Sep 30, 2021 at 03:41:27PM +0200, Stella Ashburne wrote:
> > Of course, if you intend to use openvpn-provided DNS list only, things
> > will be more complicated.
> >
> What did you mean by "openvpn-provided DNS list only"? I didn't know that
> OpenVPN provides a list of DNS
Hi David
> Sent: Thursday, September 30, 2021 at 1:25 PM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 -
> Connection status show OK but unable to surf the net)
>
>
> Err,
Hi Reco
I'm happy to hear from you again.
> Sent: Thursday, September 30, 2021 at 8:20 PM
> From: "Reco"
> To: debian-user@lists.debian.org
> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 2 - DNS
> managers)
>
>
> Works for me since Debi
1 - 100 of 5686 matches
Mail list logo
