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.
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.
"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.
https://www.openprinting.org/printer/Epson/Epson-WF-2510_Series
"works perfectly"
Epson WF-2510
On 11/03/2022 14:21, gareth evans wrote:
Epson WF-2510
https://www.openprinting.org/printer/Epson/Epson-WF-2510_Series
"works perfectly"
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
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.
Quoting from that page...
Epson WF-2510 Series
Color inkjet printer, max. 5760x1440 dpi, works Perfectly
Recommended Driver: epson-201211w (Home page, Driver packages: x86 32
bit: 1.0.0 (RPM for LSB 3.2) (Signed), 1.0.0 (DEB for LSB 3.2)
(Signed), x86 64 bit: 1.0.0 (RPM for LSB 3.2) (Signed), 1.0.0 (DEB for
LSB 3.2) (Signed) (How to install))
The recommended drivers are epson provided and x86 32/64 bit. It doesn't mention arm versions.
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.
The best thing with linux is to switch everything smart off, set the
printer on a fixed IP address and use ONE protocol. 'Raw socket or IPP '
is a good one.
"The Natural Philosopher" <tnp@invalid.invalid> wrote in message news:t0icad$4b5$1@dont-email.me...
The best thing with linux is to switch everything smart off, set the
printer on a fixed IP address and use ONE protocol. 'Raw socket or IPP
' is a good one.
And if I need to give anything a static IP address, I use the "reserved address" feature of most modern routers (when a device with a given MAC address requests an IP, always give it this one) rather than setting it
as static IP at the printer etc. This means that if I temporarily
connect the printer to a different network, I won't run the risk of a)
an IP in the wrong subnet => no communication, or b) an IP which
conflicts with one that the different network's router is quite
correctly handing out to something else => neither device will work.
On 13/03/2022 18:17, NY wrote:
"The Natural Philosopher" <tnp@invalid.invalid> wrote in message
news:t0icad$4b5$1@dont-email.me...
The best thing with linux is to switch everything smart off, set the
printer on a fixed IP address and use ONE protocol. 'Raw socket or IPP ' >>> is a good one.
And if I need to give anything a static IP address, I use the "reserved
address" feature of most modern routers (when a device with a given MAC
address requests an IP, always give it this one) rather than setting it
as static IP at the printer etc. This means that if I temporarily connect
the printer to a different network, I won't run the risk of a) an IP in
the wrong subnet => no communication, or b) an IP which conflicts with
one that the different network's router is quite correctly handing out to
something else => neither device will work.
I often thought about that but, having grown up with static IP addresses
know how to do that easily enough, I have a reserved range for them set up
in the router.
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've been bitten too many times with IP address clashes to use static IP >(configured at the computer) unless there is no alternative. 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.
On a sunny day (Mon, 14 Mar 2022 09:49:06 -0000) it happened "NY"
<me@privacy.invalid> wrote in <t0n33i$37h$1@dont-email.me>:
I've been bitten too many times with IP address clashes to use static IP >>(configured at the computer) unless there is no alternative. 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.
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
Just imagine everybody's phone number changing al the time....
:-)
I have many scripts that send data to other computers (raspis, light controllor,
servers, what not) some even use netcat.
Why make things complicated that can be done simple.
On a sunny day (Mon, 14 Mar 2022 09:49:06 -0000) it happened "NY" <me@privacy.invalid> wrote in <t0n33i$37h$1@dont-email.me>:
I've been bitten too many times with IP address clashes to use static IP >>(configured at the computer) unless there is no alternative. 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.
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
Just imagine everybody's phone number changing al the time....
:-)
I have many scripts that send data to other computers (raspis, light controllor,
servers, what not) some even use netcat.
Why make things complicated that can be done simple.
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
"Jan Panteltje" <pNaonStpealmtje@yahoo.com> wrote in message >news:t0nbm5$l6t$1@dont-email.me...
On a sunny day (Mon, 14 Mar 2022 09:49:06 -0000) it happened "NY"
<me@privacy.invalid> wrote in <t0n33i$37h$1@dont-email.me>:
I've been bitten too many times with IP address clashes to use static IP >>>(configured at the computer) unless there is no alternative. 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.
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
Just imagine everybody's phone number changing al the time....
:-)
I have many scripts that send data to other computers (raspis, light
controllor,
servers, what not) some even use netcat.
Why make things complicated that can be done simple.
I agree with giving some computers reserved addresses if you may need to >access them by IP rather than by computer name because the name service
won't resolve for all types of computer than may need to access them.
Windows PCs seem to be able to access by name even after a router is
rebooted and/or its DNS cache is cleared. But other operating systems such
as Android and iPad often can't resolve by name so if I need to access an >HTTP web interface for software on my Pis, I usually configure everything to >use http://128.168.1.x:9981 etc rather than http://martin-pi4:9981.
If one computer doesn't need to access another one, or if the name service
is sufficient for it to work, then it doesn't matter what IP a computer has >today. It's only servers that need fixed IP addresses.
But I prefer to achieve this reserving of IP addresses at the router rather >than at each device. In particular, a portable device such as a phone,
tablet or laptop will almost certainly need to be used on networks other
than the one in your home, so you can't fix its IP address for its wifi >interface. AFAIK, an IP is fixed for the interface, not for the specific
SSID of the network, so you can't fix the IP when connected to your home
SSID but allow it to get the IP by DHCP for any other SSID.
The other week I had to change my network fairly radically which required >changing from 10.120.1.x to 192.168.1.x, for reasons which are fairly >complicated but boil down to wanting one DHCP/DNS rather than two cascaded >(one on Linksys Velop and one on VDSL router) in the hope that it would cure >an obscure problem (*). It would have been a right pain if I've had to
change the static IP on every single computer on the network. Instead I >copied the address reservations from 10.120.1.x to 192.120.1.x (I kept the >same "x" for a given computer because I'd learned that 72 and 73 were my two >Pis etc).
To use your telephone analogy, the allocation of phone numbers is done at
the exchange by allocating a given number to a given line-pair. If the
number had to be changed (eg adding a new prefix digit such as changing 0532 >671xxx to 0113 2671xxx on PhONEday) it is done centrally at the exchange:
you don't have to go round to everyone's house to change a phone number >allocation on the phone.
(*) It didn't: after about a month of flawless service, I'm back to certain >Adnroid and iPad devices not being able to access one specific web site, >which isn't cured by rebooting router or phone/tablet, or clearing browser >caches. Why it only affects some devices, one specific (public) web server >and my VDSL connection (but not my phone's mobile internet) is still a >mystery.
And if I need to give anything a static IP address, I use the "reserved address" feature of most modern routers (when a device with a given MAC address requests an IP, always give it this one)
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
Just imagine everybody's phone number changing al the time....
:-)
I have many scripts that send data to other computers (raspis, light controllor,
servers, what not) some even use netcat.
Why make things complicated that can be done simple.
Am 11.03.2022 um 15:21 schrieb gareth evans:
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 own exactly this printer and have no problems.
FW
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.
On a sunny day (Mon, 14 Mar 2022 09:49:06 -0000) it happened "NY" <me@privacy.invalid> wrote in <t0n33i$37h$1@dont-email.me>:
I've been bitten too many times with IP address clashes to use static IP
(configured at the computer) unless there is no alternative. 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.
FYI I only use static IP adresses on my local network.
Killing dhcpd is in my start up scripts, that stuff is s nuisance.
Just imagine everybody's phone number changing al the time....
:-)
I have many scripts that send data to other computers (raspis, light controllor,
servers, what not) some even use netcat.
Why make things complicated that can be done simple.
The Natural Philosopher wrote:
These are the only 'servers' on the network.
I want to be able to access any file on any machine from whatever screen
and keyboard I happen to be sitting in front of at the moment.
mind, my router offers a "always give this MAC the same IP every time" setting. Guests and their phones may vary, but the number of my own
machines at home is pretty constant, so no need to come back to that
setting often. I have to do it once anyway, because the groups
"standard" and "my computers" have different filters and use of
blacklist.
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
These are the only 'servers' on the network.
On 14/03/2022 10:23, F. W. wrote:
Am 11.03.2022 um 15:21 schrieb gareth evans:
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 own exactly this printer and have no problems.
FW
And you also access it from an ARM based Pi?
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
On Tue, 15 Mar 2022 10:04:42 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:
It used to be something like (sudo) ifconfig eth0:1 192.168.20.27/24 up
Still is with ifconfig installed.
I think today its more like (sudo) ip addr add 192.168.20.27/24 dev eth0
I have never understood this game of replacing standard commands
used across many operating systems with "ooh shiny new syntax".
But never
mind, my router offers a "always give this MAC the same IP every time" setting. Guests and their phones may vary, but the number of my own machines at home is pretty constant, so no need to come back to that setting often. I have to do it once anyway, because the groups
"standard" and "my computers" have different filters and use of
blacklist.
The argument between 'set machines up statically' and 'assign fixed
addresses by DHCP' is almost totally balanced.
- the end result is identical
- the amount of configuration required is very similar .
- neither gets rid of the need for host files or DNS.
- the DHCP case is slightly more complicated if you change a network
card or motherboard.
"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?
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
"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?
On Wed, 16 Mar 2022 10:32:13 -0000
"NY" <me@privacy.invalid> wrote:
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
The two (or more) IP configurations are just that multiple configurations and should be to non overlapping subnets or to individual hosts /32 so that the kernel can work out from the destination which local
IP address to use when assembling the initial packet (using a /32 for multiple hosts in the same subnet is a bit of a hack - no outgoing packet will match that network so only reply packets will go out carrying it as
the local address).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 371 |
Nodes: | 16 (2 / 14) |
Uptime: | 37:30:26 |
Calls: | 7,932 |
Calls today: | 2 |
Files: | 12,998 |
Messages: | 5,805,624 |