Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #228493 > unrolled thread

Instructions for command line usage of WiFi.

Back to article view | Back to linux.debian.user

Contents

  Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-06 01:00 +0100
    Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-06 06:30 +0100
      Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-15 23:00 +0100
        Re: Instructions for command line usage of WiFi. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-11-15 23:10 +0100
        Re: Instructions for command line usage of WiFi. David Wright <deblis@lionunicorn.co.uk> - 2020-11-17 16:40 +0100
      Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-25 00:50 +0100
        Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-25 08:50 +0100
          Re: Instructions for command line usage of WiFi. Celejar <celejar@gmail.com> - 2020-11-25 15:20 +0100
            Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-25 15:50 +0100
              Re: Instructions for command line usage of WiFi. Celejar <celejar@gmail.com> - 2020-11-25 16:40 +0100
                Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-25 17:20 +0100
                  Re: Instructions for command line usage of WiFi. Celejar <celejar@gmail.com> - 2020-11-25 19:10 +0100
          Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-27 01:00 +0100
            Re: Instructions for command line usage of WiFi. Gene Heskett <gheskett@shentel.net> - 2020-11-27 02:10 +0100
              Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-27 17:10 +0100
            Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-27 07:40 +0100
              Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-27 18:40 +0100
                Re: Instructions for command line usage of WiFi. Dan Ritter <dsr@randomstring.org> - 2020-11-27 18:50 +0100
                Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-27 19:10 +0100
                  Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-30 04:10 +0100
                    Re: Instructions for command line usage of WiFi. Doug McGarrett <dmcgarrett@optonline.net> - 2020-11-30 05:50 +0100
                    Re: Instructions for command line usage of WiFi. ghe2001 <ghe2001@protonmail.com> - 2020-11-30 07:10 +0100
                    Re: Instructions for command line usage of WiFi. Reco <recoverym4n@enotuniq.net> - 2020-11-30 09:50 +0100
                      Use of external connectors on a Sharp Mebius laptop; was Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-12-01 03:10 +0100
                Re: Instructions for command line usage of WiFi. Gene Heskett <gheskett@shentel.net> - 2020-11-27 22:00 +0100
                  Re: Instructions for command line usage of WiFi. Richard Hector <richard@walnut.gen.nz> - 2020-11-29 11:40 +0100
                    Re: Instructions for command line usage of WiFi. Gene Heskett <gheskett@shentel.net> - 2020-11-29 13:40 +0100
          Instructions for command line usage of WiFi. peter@easthope.ca - 2020-11-27 04:50 +0100
        Re: Instructions for command line usage of WiFi. Wim <factotum_muth@web.de> - 2020-11-29 20:40 +0100
          Graphical environment; was, Re: Instructions for command line usage of WiFi. peter@easthope.ca - 2020-12-01 15:50 +0100

Page 2 of 2 — ← Prev page 1 [2]

#229171

On 11/29/20 9:42 PM, peter@easthope.ca wrote:
> From: Reco <recoverym4n@enotuniq.net>
> Date: Fri, 27 Nov 2020 21:09:26 +0300
>> I'm mildly curious how you managed to obtain a laptop which does not
>> have any kind of wireless connectivity, ...
> The machine is a Sharp Mebius PC-CB1-M1.
> https://jp.sharp/support/mebius/spec/pc_cb1_m1.html
>
> It has an 8P8C socket and a 6P2C socket.  lspci reports VIA
> VT6102/VT6103 Ethernet Controller and VIA AC'97 Modem Controller. No
> evidence of IEEE 802.11 or Bluetooth.
>
> This is the only Sharp machine I've used.  They could have made a
> similar model with WiFi.  I don't know.
>
> Regards,                        ... P.
>
There are plug-in wireless adapters for very little money that should
solve your wireless connectivity problem. See:

https://www.amazon.com/customerpicks/Explore-external-WIFI-adapters-for-laptops/e679dff1b9ef87bf0396

--doug

[toc] | [prev] | [next] | [standalone]

#229172

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Here's a script that turns WiFi on and off on my Dell laptop.  (It works on my 2-hole desktop as well -- so the complexity.  'slsware' is my domain.)

# Makes sure the primary Ethernet port (ETH0) is up and
# sets a route to rrc through ETH0 (so SSH down there will by happy with the IP it gets) and
# sets DNS (/etc/resolv.conf) to the standard slsware values (in /etc/resolv.conf.sls)
#
# UP brings up the secondary Ethernet port (ETH1) by DHCP from the Frasier_Residents DHCP server,
# removes the ETH0 default route, and replaces it with an ETH1 default
#
# DOWN just puts things back as though there were no ETH1

ETH0_DEFAULT_IP="216.17.134.201"
ETH1_DEFAULT_IP="10.200.184.254"
TRUE="0"
leadingSpace="      "

function cleanUp()
{
	# remove detritus
	sudo rm ifconfig.all ifconfig.status route.status 2>/dev/null
	# set DNS
	sudo cp /etc/resolv.conf.sls /etc/resolv.conf
	# say goodbye
	if [ "$1" != "" ]
	then
		echo ; echo "${leadingSpace}$1"
	fi
	# show routing table
	echo ; echo "${leadingSpace}route:" ; echo
	sudo route
	echo
}

ETH0="lo only"
ETH1=$ETH0
function getInterfaceNameStyle()
{
	# get an 'ifconfig' of all interfaces
	sudo ip a >ifconfig.all

	egrep -q "eth.:" ifconfig.all
	if [ "$?" == "$TRUE" ]
	then
		ETH0="eth0"
		ETH1="wlan0"
		return
	fi

	egrep -q "enp.s" ifconfig.all
	if [ "$?" == "$TRUE" ]
	then
		ETH0="enp6s0"
		ETH1="enp7s0"
		return
	fi

	if [ "$ETH0" == "lo only" ]
	then
		cleanUp "$ETH0"
		exit 0
	fi
}

# are the interfaces in the eth<n> style?
getInterfaceNameStyle

# get current ifconfig status
ip -4 link ls up >ifconfig.status

# is ETH0 up?
egrep -q "${ETH0}:.*UP" ifconfig.status
ETH0_UP=$?
# is ETH1 up?
egrep -q "${ETH1}:.*UP" ifconfig.status
ETH1_UP=$?

# make sure ETH0 is up (it probably is, but...)
if [ "$ETH0_UP" != "$TRUE" ]
then
	echo ; echo "${leadingSpace}bringing up $ETH0" ; echo
	sudo ifup $ETH0
	$ETH0_UP == "$TRUE"
fi

if [ "$1" == "up" ]
then
	# is ETH1 already up?
	if [ "${ETH1_UP}" == "$TRUE" ]
	then
		cleanUp "$ETH1 is already up"
		exit 0
	else
		echo ; echo "${leadingSpace}bringing up $ETH1" ; echo
		# bring up the DHCP interface
		sudo ifup $ETH1
		ip route >route.status
		# remove the ETH0 default route
		sudo ip route del default via $ETH0_DEFAULT_IP dev $ETH0
		# is the wifi default not in the routing table?
		egrep "default.*$ETH1" route.status
		if [ "$?" != "$TRUE" ]
		then
			# if not, put it in
			sudo ip route add default via $ETH1_DEFAULT_IP dev $ETH1
		fi
		# remove the ETH1 route to the LAN (there's already one for ETH0)
		sudo ip route del 216.17.134.0/24 dev $ETH1
	fi
elif [ "$1" == "down" ]
then
	# is ETH1 already down?
	if [ "$ETH1_UP" != "$TRUE" ]
	then
		cleanUp "$ETH1 is already down"
		exit 0
	else
 		sudo ifdown $ETH1
		sudo ip route add default via $ETH0_DEFAULT_IP dev $ETH0
		sudo cp /etc/resolv.conf.sls /etc/resolv.conf
	fi
else
	cleanUp "You forgot to say 'up' or 'down'..."
	exit 0

fi

cleanUp ""


And here's a piece of /etc/network/interfaces:

# wlan0 -- Get DHCP from SSID: Frasier_Residents, PW: <password>
iface wlan0 inet dhcp
	pre-up sudo ip addr flush dev wlan0
	wpa-ssid Frasier_Residents
	wpa-psk <password>


Hope this helps...

--
Glenn English




-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJfxIqdACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDI02Qf8CkOUUDV1BfSUZhRNT/7Fvp8Fjqqcfy/VXTkuUDCyhBXGCqEh
gQfe+LVlq/HyZkjsDMSQl4qVzZzhETafopVi8MMwXCmcp9eVt37pLeJS+Wyh
k6/CXTqHy2or+TXW2vKtI7mWDlEqHFRlj7E1FkJJpN8WorAbuAhnX2xEGBcf
NzncvyOXsndbbqY3T1pwZFywivH9HiqAPJ4rRyjoBX7XNrv6Q170Icukq30A
y3reL1HRWmPH6JMZ7awiVWMxVe74bLQDlrYP+znwqopwQvEpYsCBP2Gd4lGv
fnUROVW6FvOvPuFEn+eK57KIgQoa/9oLdq4MbnmYEV7oebjrOQe+1w==
=Itjc
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#229173

	Hi.

On Sun, Nov 29, 2020 at 06:42:22PM -0800, peter@easthope.ca wrote:
> > I'm mildly curious how you managed to obtain a laptop which does not 
> > have any kind of wireless connectivity, ...
> 
> The machine is a Sharp Mebius PC-CB1-M1.  
> https://jp.sharp/support/mebius/spec/pc_cb1_m1.html

I don't read Japanese, but these letters (PCMCIA) are familiar to me:

PCカード	Type Ⅱ×1、 PCMCIA 2.1/JEIDA 4.2仕様準拠 CardBus対応


You're supposed to use so called Wireless PCMCIA Card to get wireless
with this laptop.
About the only advantage over your current USB WiFi dongle is that you
get to free that USB slot though :)

Reco

[toc] | [prev] | [next] | [standalone]

#229188 — Use of external connectors on a Sharp Mebius laptop; was Re: Instructions for command line usage of WiFi.

From: Reco <recoverym4n@enotuniq.net>
Date: Mon, 30 Nov 2020 11:47:40 +0300
> You're supposed to use so called Wireless PCMCIA Card to get wireless
> with this laptop. About the only advantage over your current USB WiFi 
> dongle is that you get to free that USB slot though :)

(1) PCMCIA Ethernet adapter has projecting antenna.
   SD card in projecting USB adapter.
 
(2) Projecting USB Ethernet adapter.
   SD card in PCMCIA adapter; nothing projecting there
   
The advantage of (2) is one less gizmo to unplug before putting 
the laptop in a carrying case.

                                    ... P.
                                    
 



-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#229138

On Friday 27 November 2020 11:51:49 peter@easthope.ca wrote:

> From: Reco <recoverym4n@enotuniq.net>
> Date: Fri, 27 Nov 2020 09:30:04 +0300
>
> > This one works for me:
> >
> > $ lspci  | grep Wireless
> > 03:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
> >
> > It's a mini-PCI card, inserted in PCI-X adapter.
>
> OK, thanks.  A USB TP-Link here is used with a laptop.  For a desktop
> system, a PCI-X adapter might perform better than a USB.  Will see
> what is available.
>
> > It would be illegal in US, and you have to thank FCC for that - [1].
> > Applies to WiFi cards too.
> > [1] https://hackaday.com/2016/02/26/fcc-locks-down-router-firmware/
>
> Interesting article about commercial products.
>
> I imagined FPGA based hardware assembled by J. Doe on the kitchen
> table.  It would need to be licensed similar to amateur radio? But
> available licenses don't cover the WiFi band? Wouldn't it be similar
> to licensing outdoor Christmas lights because they radiate a week EM
> field?  Isn't radiated power below some level exempted?
>
> Does the FCC (Industry Canada) drive around every residential
> neighbourhood and knock on every door where a field is detected and
> ask to verify that it is generated by licensed equipment?  Seems
> unrealistic.
>
> Regards,                                  ... P.

It could happen. My only interfacing with such an FCC inspector consisted 
of educating him on the finer points of the violation citation he had on 
his clipboard, which resulted in his tearing up the cite, I knew far 
more about it than he did, and while the FCC truck was fairly well 
equipt with monitoring gear, the monitor I was going by for compliance, 
which I pointed to in my rack, sold for about $10G's more than the 
similar purpose unit his truck was setup with. Since his was out of 
calibration date, he left saying that it would get sent in for recal, 
and if it was good, he would be back. Since it was only about 125 miles 
to his home office in Grand Island Nebraska I expected to see him in 
about 8 weeks.  Never showed up again.  At the time I was managing a 
330kw ERP educational site on channel 19 for the Nebraska ETV 
Commission. Needless to say that klystron based tech has now been 
replaced by more efficient means of generating high power UHF tv 
signals.  A lot has happened to the technology in the 50+ years since. 

That station was at the time, Wayne county public powers biggest 
customer. Nominal power drain was about 250kwh an hour for around 17.5 
hours a day.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#229163

On 28/11/20 9:58 am, Gene Heskett wrote:
> Nominal power drain was about 250kwh an hour

That's about 250kW then? :-)

Richard

[toc] | [prev] | [next] | [standalone]

#229165

On Sunday 29 November 2020 05:32:04 Richard Hector wrote:

> On 28/11/20 9:58 am, Gene Heskett wrote:
> > Nominal power drain was about 250kwh an hour
>
> That's about 250kW then? :-)

Yes. The original install had a 250kw sola transformer but it was 
destroyed by a lightning strike, so it got bypassed, which actually 
helped the technical operation by removing the noise choking effect of 
that ton of iron, allowing the local power powerline to absorb to a 
large extent, the 6 times per hz noise pulse cause by the slow recovery 
of the high voltage rectifiers, which had the effect of short circuiting 
the phase with the rising voltage to the decaying voltage of the phase 
going down. That was about 15 microseconds, 6 times an incoming HZ, and 
was not only visible as a noise bar slowly running thru the broadcast 
picture, but was also hell on other stuff plugged into normal wall plugs 
due the the sudden switch as the diodes finally recovered, which put a 
nominally 1 kilovolt noise spike sitting on the 127 volts from the wall. 

Small stuff that ran on 10 watts would suffer random instances of a 
failed 2 amp fuse due to the cumulative effect of that heat pulse 
causing a crystalization and eventual fatigue failure of the fuse link 
metal. The fuse wasn't blown. just broken.  The rectifiers could have 
been replaced with faster ones, but when there are 6 of the sticks about 
6 feet long, a 3 phase bridge developing 20 kilovolts for klystron beam 
power with 72 big diodes per stick, the replacements would have cost 
something north of $10k so it never got done. Transmitters using 
klystron amplifiers do not change their power draw with the brightness 
of the picture and the nearly 6 amps of beam current is not modulated by 
the video, only the beam velocity is modulated.  And at 20 kv, the 
electrons are moving at definitely relatavistic speeds and that leads to 
video distortions we didn't then know how to predistort in the opposite 
to cancel. Now we do have such. The effect is that of changing the 
length of the tube according to the power level of the output, and 
was/is caused by the increased mass of the electron as it speeds up, and 
the decreased mass as it slows down. You could slow them, but you 
couldn't speed them up to match because they got heavier when sped up, 
so at high power levels the tube effectively got longer causing timing 
distortions in the amplified signal. That to me, was prima faci evidence 
that Einstein was right. And our experiments since have proved him right 
to a considerable number of zeros to the right of the decimal point.

Your trivia factoid overload for the day.

Due to the operating expense of such a transmitter, not the least of 
which was the $125,000 cost of a new tube at 5 year or so intervals, and 
each NTSC transmitter used 2 of them, newer technology has replaced them 
and I doubt there are any left on the air here in the US today. 
Technical considerations has little to do with it, the bean counters 
will spend the sheckels to reduce the monthly power bill, they have that 
choice or have the last man out of the building turn off the lights and 
lock the door. It really is that simple.
> Richard


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#229127

From: Reco <recoverym4n@enotuniq.net>
Date: Wed, 25 Nov 2020 10:42:59 +0300
> Try increasing a value of vm.min_free_kbytes, it may help.

vm.min_free_kbytes wasn't in /etc/sysctl.conf as some Web pages claim 
but cat /proc/sys/vm/min_free_kbytes gave 39944.  Adding the line 
"vm.min_free_kbytes = 59916" in /proc/... , increasing the value by 
50%, eliminated the buffer full message.

Thx,               ... P.

-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#229167

Hi,

a bit of topic but Sway, a Wayland compositor is now available in Sid.
It's a drop in replacement for i3wm. Works very well.

On Wednesday, 25 November at 00:50, peter@easthope.ca wrote:

> Wicd is no longer needed but leaving it installed seems harmless. (When 
> wayland/weston is reliable I'll try to survive without lxde.)
> 
> Thanks,                                 ... P.
> 
> -- 
> Tel: +1 604 670 0140            Bcc: peter at easthope. ca

-- 
All the best
Wim

[toc] | [prev] | [next] | [standalone]

#229198 — Graphical environment; was, Re: Instructions for command line usage of WiFi.

From: Wim <factotum_muth@web.de>
Date: Sun, 29 Nov 2020 20:14:05 +0100
> ... Sway, a Wayland compositor is now available in Sid. It's a drop 
> in replacement for i3wm. Works very well.

Debian 10 here.  Since 2000 I've jumped to "testing" twice.  In both 
cases problems surfaced.  After the second foray I resolved to refrain 
from "testing" except for a spare machine not in regular use.  

In mid-November I started Weston.  In the first five or ten minutes it 
was useable with brief delays noticeable when Xwayland was required.  
Then artifacts appeared.  Closed a window and artifacts remained in 
the display.  Rapid flashing of patches of display associated with 
pointer movement. So not useable in 10. 

Definitely I'll be trying again in 11.

Thanks,                                     ... P.

-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web