Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

SOLVED-mx 17.1 - problems since latest updates - UPDATED

Message
Author
User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: mx 17.1 - problems since latest updates - UPDATED

#21 Post by fehlix » Tue Nov 06, 2018 9:14 pm

Might be this printer does not provide a web-interface?
OK, another attempt (already requested :lipsrsealed: )
add the IP to the host table. Open a terminal window and this:

Code: Select all

gksudo -k featherpad /etc/hosts
Now copy and paste this line of printer IP:

Code: Select all

192.168.1.5   BRN30055CBFCCB4 BRN30055CBFCCB4.local BRN30055CBFCCB4.local.
and paste as a newline into the editor and save the file /etc/hosts.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

jbloggs
Forum Novice
Forum  Novice
Posts: 59
Joined: Tue Aug 08, 2017 9:11 pm

Re: mx 17.1 - problems since latest updates - UPDATED

#22 Post by jbloggs » Fri Nov 09, 2018 3:30 am

as suggested, added

192.168.1.5 BRN30055CBFCCB4 BRN30055CBFCCB4.local BRN30055CBFCCB4.local.

to /hosts file

made no difference.

Discovered that I could access in browser localhost:631 and 192.165.1.5 if I TURNED OFF Killswitch in PIA VPN settings.

Documents can be sent to printer but don't print - nothing in print queue.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: mx 17.1 - problems since latest updates - UPDATED

#23 Post by fehlix » Fri Nov 09, 2018 8:24 am

Looks like your PIA VPN setup is interfering with your local network. Sounds like an iptable-rule is missing ... or which could fix it.
Would suggest first make sure printer (-setup) works without VPN. Better remove printer and add new, so no printer-queues or something else is blocking.
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

jbloggs
Forum Novice
Forum  Novice
Posts: 59
Joined: Tue Aug 08, 2017 9:11 pm

Re: mx 17.1 - problems since latest updates - UPDATED

#24 Post by jbloggs » Sun Nov 11, 2018 11:35 pm

thanks fehlix

Same problem with SparkyLinux installation.

Just ran Sparky Live CD and installed printer both as USB and Ethernet - printed fine in both cases.
Copied the Ethernet printer setup to MX 17.1 - still wont print - even with the VPN disconnected.

Have just logged a Support request with Private Internet Access as the problem is definitely with their app.

IPTABLES is as follows:-
--------------------
bill@main-pc-mx17:~
$ sudo iptables -S
[sudo] password for bill:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N PIA_ALLOW_LAN_RULES
-N PIA_DNS_LEAK_EXEMPT_IP
-N PIA_FIX_LINUX_DNS_LEAK_RULES
-N PIA_KILLSWITCH_OUTPUT_RULES
-A INPUT -p udp -m multiport --dports 5353 -j ACCEPT
-A INPUT -p tcp -m multiport --dports 4000 -j ACCEPT
-A PIA_ALLOW_LAN_RULES -d 192.168.0.0/16 -j ACCEPT
-A PIA_ALLOW_LAN_RULES -d 172.16.0.0/12 -j ACCEPT
-A PIA_ALLOW_LAN_RULES -d 10.0.0.0/8 -j ACCEPT
-A PIA_ALLOW_LAN_RULES -d 224.0.0.0/4 -j ACCEPT
-A PIA_ALLOW_LAN_RULES -d 169.254.0.0/16 -j ACCEPT
-A PIA_FIX_LINUX_DNS_LEAK_RULES -j PIA_DNS_LEAK_EXEMPT_IP
-A PIA_FIX_LINUX_DNS_LEAK_RULES -o lo+ -p udp -m udp --dport 53 -j ACCEPT
-A PIA_FIX_LINUX_DNS_LEAK_RULES -o lo+ -p tcp -m tcp --dport 53 -j ACCEPT
-A PIA_FIX_LINUX_DNS_LEAK_RULES ! -o tun+ -p udp -m udp --dport 53 -j DROP
-A PIA_FIX_LINUX_DNS_LEAK_RULES ! -o tun+ -p tcp -m tcp --dport 53 -j DROP
-A PIA_KILLSWITCH_OUTPUT_RULES -d 127.0.0.0/8 -j RETURN
-A PIA_KILLSWITCH_OUTPUT_RULES -o tun+ -j RETURN
-A PIA_KILLSWITCH_OUTPUT_RULES -j DROP
bill@main-pc-mx17:~

--------------------

$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere multiport dports mdns
ACCEPT tcp -- anywhere anywhere multiport dports 4000

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain PIA_ALLOW_LAN_RULES (0 references)
target prot opt source destination
ACCEPT all -- anywhere 192.168.0.0/16
ACCEPT all -- anywhere 172.16.0.0/12
ACCEPT all -- anywhere 10.0.0.0/8
ACCEPT all -- anywhere base-address.mcast.net/4
ACCEPT all -- anywhere link-local/16

Chain PIA_DNS_LEAK_EXEMPT_IP (1 references)
target prot opt source destination

Chain PIA_FIX_LINUX_DNS_LEAK_RULES (0 references)
target prot opt source destination
PIA_DNS_LEAK_EXEMPT_IP all -- anywhere anywhere
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
DROP udp -- anywhere anywhere udp dpt:domain
DROP tcp -- anywhere anywhere tcp dpt:domain

Chain PIA_KILLSWITCH_OUTPUT_RULES (0 references)
target prot opt source destination
RETURN all -- anywhere loopback/8
RETURN all -- anywhere anywhere
DROP all -- anywhere anywhere
bill@main-pc-mx17:~


----------------------------
Thanks - will post when I get reply from PIA

jbloggs
Forum Novice
Forum  Novice
Posts: 59
Joined: Tue Aug 08, 2017 9:11 pm

Re: SOLVED-mx 17.1 - problems since latest updates - UPDATED

#25 Post by jbloggs » Tue Nov 13, 2018 8:43 pm

SOLVED

set up printer in SparkyLinux - noted settings

booted MX 17.1

Added Printer - Printers Settings does not include obvious choice for GENERIC drivers

Founded by accident

here are settings

XXXX working xerox printer network setup XXXX

Generic PCL 6/PCL XL

socket://192.168.1.5:9100 -NOTE this is change from original MX installation

Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended)


Printer is Fuji Xerox Docuprint P265dw - aka Brother HL-2360DW


Hope that this helps somebody else

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: SOLVED-mx 17.1 - problems since latest updates - UPDATED

#26 Post by fehlix » Tue Nov 13, 2018 8:51 pm

jbloggs wrote:
Tue Nov 13, 2018 8:43 pm
socket://192.168.1.5:9100 -NOTE this is change from original MX installation
So finaly you made it. Cool. Strange only that, it didn't work before. As you tried it already, as recommend per post #8.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

jbloggs
Forum Novice
Forum  Novice
Posts: 59
Joined: Tue Aug 08, 2017 9:11 pm

Re: SOLVED-mx 17.1 - problems since latest updates - UPDATED

#27 Post by jbloggs » Wed Nov 14, 2018 10:31 pm

Didnt work before as Printer Settings didnt give me the Generic Printer drivers. Had to "Find 192.168.1.5" despite 2 options displayed for Fuji printer

"Find 192.168.1.5" "AppSocket/HP jetDirect" despite the printer being a Fuji not HP.
"Forward" then searched for drivers and found "Generic" and recomended Generic PCL 6/PCL XL printer Foomatic/pxcolor [en] (recommended) even though the printer is not "color"

Anyway, it now works.

Thanks again

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2064
Joined: Wed Apr 11, 2018 5:09 pm

Re: SOLVED-mx 17.1 - problems since latest updates - UPDATED

#28 Post by fehlix » Wed Nov 14, 2018 10:48 pm

jbloggs wrote:
Wed Nov 14, 2018 10:31 pm
Didnt work before as Printer Settings didnt give me the Generic Printer drivers. Had to "Find 192.168.1.5" despite 2 options displayed for Fuji printer

"Find 192.168.1.5" "AppSocket/HP jetDirect" despite the printer being a Fuji not HP.
"Forward" then searched for drivers and found "Generic" and recomended Generic PCL 6/PCL XL printer Foomatic/pxcolor [en] (recommended) even though the printer is not "color"

Anyway, it now works.

Thanks again
Ah, I see there is a little trick to select manual the printer drive from the list. Something, like: Just enter the IP and ignore what was found and select manual from the list the driver.
"AppSocket/HP JetDirect" is the "name of the protocol - not the printer ( I know it's sometime confusing ;=)
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “Hardware /Configuration”