On 11/03/2022 15:03, NY wrote:

"gareth evans" <headstone255@yahoo.com> wrote in message news:t0flu7$o1k$1@dont-email.me...

Before I (finally) get around to commissioning any of my
RPis, 1, 2, 3 & 4 (Yes, really. All in untouched in their
original boxes!) to replace my ageing Microsoft-programmed
laptop, does Raspbian have support for network printers, in
my case an Epson WF-2510?

I am increasingly dis-chuffed by Microsoft software and
wish to be Linuxised, having used Linux in a number of
employments.

It certainly has support for network-connected printers. It
automatically found my HP Laserjet 283 (once I'd told it I was connected
by LAN rather than USB) and even found the correct driver for ir. You
should be OK with an Epson printer.

This is using Raspbian on a Pi3 and a Pi4. Is there a list within
Raspbian (and other flavours of Unix) of the printers that are
supported? I suppose there must be for CUPS (printing service) to offer
a drop-down list of printers when you set one up manually if the auto-detection fails.

On 11/03/2022 16:32, The Natural Philosopher wrote:

https://www.openprinting.org/printer/Epson/Epson-WF-2510_Series

"works perfectly"

Thank-you both gentlemen.

As it happens, I was on the verge recently of unpacking the
RPi400 that I got last June 2021, and had cleared a space for it,
when unexpectedly an Eddystone EA12 communications receiver became
available just for the asking and it is now sitting in that
cleared space whilst I find somewhere else to put it! :-)

(I am a Radio Ham in addition to other interests)

I have been studying the ARMv8 instruction set, off and on, for
some months now in anticipation of an assembly language project
that had its genesis nearly 50 years ago when working for the
CEGB in Portishead

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 11/03/2022 14:21, gareth evans wrote:

Epson WF-2510

https://www.openprinting.org/printer/Epson/Epson-WF-2510_Series

"works perfectly"

--
Canada is all right really, though not for the whole weekend.

"Saki"

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 16-03-2022 11:32, NY wrote:

"The Natural Philosopher" <tnp@invalid.invalid> wrote:

Adding a second IP address to an Ethernet port is trivial, especially
if you don't want it to persist after a reboot.

It used to be something like (sudo) ifconfig eth0:1 192.168.20.27/24 up

I think today its more like (sudo) ip addr add 192.168.20.27/24 dev eth0

Anyway this allows you to add a (static) address temporarily to the
same network the offending device is on, and use a browser to talk to it

Well I never knew that. Does it just configure the OS to listen for *incoming* connections on the temporary IP? Does traffic from the PC to
an external device just get sent with the permanent IP, except in the
special case where it is in response to incoming traffic addressed to
the temporary IP? In other words, is Unix applying a bit on intelligence here?

Depends on the mask. The two interfaces/networks are completely
equivalent but they can't have overlapping "IP masks" or "DNS masks".
The network software knows where to route and what address to use by
checking the address and seeing in which mask it fits. Hence the "/24"
which means it's a network where the first three parts of the IPv4
address are always the same, because 3x 8 = 24 (because one part takes
up 8 bits).

There may be subtleties wrong with this explanation but that's the gist.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

"The Natural Philosopher" <tnp@invalid.invalid> wrote in message news:t0pobr$hkm$1@dont-email.me...

On 14/03/2022 09:49, NY wrote:

About the only time I've needed to set a static IP is when configuring a
device such as a security camera which comes pre-configured to use
192.168.10.1, when my router uses 192.168.1.x, so I need to find spare
network switch, connect just the camera and my PC (which I give a static
IP 192.168.10.2), access the camera's web interface to change its IP to
"use DHCP", likewise for my PC, and then connect everything back to the
router. Tedious, but there's no way round it.

Actually, with Linux (And Unix) , there absolutely *is*.

Adding a second IP address to an Ethernet port is trivial, especially if
you don't want it to persist after a reboot.

It used to be something like (sudo) ifconfig eth0:1 192.168.20.27/24 up

I think today its more like (sudo) ip addr add 192.168.20.27/24 dev eth0

Anyway this allows you to add a (static) address temporarily to the same network the offending device is on, and use a browser to talk to it

Well I never knew that. Does it just configure the OS to listen for
*incoming* connections on the temporary IP? Does traffic from the PC to an external device just get sent with the permanent IP, except in the special
case where it is in response to incoming traffic addressed to the temporary
IP? In other words, is Unix applying a bit on intelligence here?

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)