Přeskočit na hlavní obsah

Network scanning with Lexmark CX410

It took me some time to get Lexmark CX410 network scanning working on my Ubuntu (16.04 LTS). Scanning programs were not able to discover the device even if the correct driver was installed. So here are some troubleshooting steps, you can try if you also experience some problems with the network scanning.

Download and install the driver


Download network scan driver for CX410 from Lexmark support page
support.lexmark.com

install it:
sudo dpkg -i lexmark_network-scan-linux-glibc2_12212015_x86_64.deb

And now add the secret ingredient. Link the installed drivers to a proper location:

sudo ln -s /usr/local/lexmark/unix_scan_drivers/lib/sane /usr/lib/sane

Installation verification


$ scanimage -L
device `lexmark_nscan:libnet/SPECIFY_DEVICE' is a Lexmark Network Scanner
device `lexmark_nscan:libnet/0021B76D22F6' is a Lexmark Lexmark CX410de Ethernet Scanner```

Komentáře

Populární příspěvky z tohoto blogu

Three ways to redirect HTTP requests to HTTPs in WildFly and JBoss EAP

WildFly application server (and JBoss EAP) supports several simple ways how to redirect the communication from plain HTTP to TLS protected HTTPs. This article presents 3 ways. Two are on the application level and the last one is on the server level valid for requests to all deployments. 1. Request confidentiality in the deployment descriptor The first way is based on the Servlet specification. You need to specify which URLs should be protected in the web.xml deployment descriptor. It's the same approach as the one used for specifying which URLs require authentication/authorization. Just instead of requesting an assigned role, you request a transport-guarantee . Sample content of the WEB-INF/web.xml <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" version="3.1

Simple TLS certificates in WildFly 18

It's just 2 weeks when WildFly 18 was released. It includes nice improvements in TLS certificates handling through ACME protocol (Automatic Certificate Management Environment), it greatly simplifies obtaining valid HTTPS certificates. There was already a support for the Let's Encrypt CA in WildFly 14 as Farah Juma described in her blog post last year. New WildFly version allows using other CA-s with ACME protocol support. It also adds new switch --lets-encrypt to interactive mode of security enable-ssl-http-server JBoss CLI commands. Let's try it. Before we jump on WildFly configuration, let's just mention the HTTPs can be used even in the default configuration and a self-signed certificate is generated on the fly. Nevertheless, it's not secure and you should not use it for any other purpose than testing. Use Let's Encrypt signed certificate for HTTPs application interface Start WildFly on a machine with the public IP address. Run it on the defaul

Weby ministerstev a jejich zabezpečení

Nedávno jsem hledal informaci na webu ministerstva zdravotnictví a zarazilo mě, že jsem nebyl automaticky přesměrován na zabezpečený protokol HTTPs. Napadlo mě podívat se, jak jsou na tom weby jednotlivých ministerstev s podporou tohoto protokolu. Rozdíly v zabezpečení jsou mezi weby velké a u některých ministerstev přímo překvapivé. Ministerstvo HTTPs Auto Redirect TLS 1.2 TLS 1.3 !RC4 !TLS 1 EV cert Doprava mdcr.cz Finance mfcr.cz Kultura mkcr.cz Místní rozvoj mmr.cz Obrana army.cz Práce a soc. věcí mpsv.cz Průmysl mpo.cz Spravedlnost justice.cz Školství msmt.cz Vnitra mvcr.cz Zahraničí mzv.cz Zdravotnictví mzcr.cz Zemědělství eagri.cz Životní prostředí mzp.cz Trocha teorie Proč HTTPs HTTPs znamená HTTP komunikaci přes spojení šifrované pomocí TLS protokolu (dříve SSL). Protokol HTTPs poskytuje nejen šifrování komunikace, ale t