On Friday, March 2, 2018 at 9:51:00 PM UTC+1, [email protected] wrote:
> On 2018-03-01 18:47, awokd wrote:
> > On Fri, March 2, 2018 4:20 am, [email protected] wrote:
> >> On 2018-03-01 18:16, awokd wrote:
> >>
> >>> On Fri, March 2, 2018 4:10 am, [email protected] wrote:
> >>>
> >>>
> >>>> When you see the message "Will you specify the DeviceURI ?",
> >>>>
> >>>>
> >>>>
> >>>> For USB Users: Choose N(No)
> >>>> For Network Users: Choose Y(Yes) and DeviceURI number.
> >>>> ---
> >>>>
> >>>>
> >>>>
> >>>> So, I chose "yes" then it wanted something like the IPP:// address
> >>>> ;
> >>>>
> >>>
> >>> You have to put your printer's IP address in here.
> >>>
> >>>
> >>>> I
> >>>> may have put in the gateway address and got nowhere I guess your
> >>>> saying it doesn't matter if it didn't work in the Template ,
> >>>
> >>> Right, doesn't matter it doesn't work, but put in the right IP address.
> >>>
> >>>
> >>>
> >>>> And for the IP address of the printer in the AppVM use the gateway of
> >>>> the AppVM ?
> >>>>
> >>>> in system-config-printer there are various options in settings->
> >>>> device URI: usb://dev/usblp0 is filled in , and in printer state it
> >>>> say "waiting for printer to become available"
> >>>
> >>> Change this to IPP:// and your printer's address.
> >>>
> >>>
> >>>
> >>>> perhaps I DONT need to tweak the fw settings in the VM Manager, but
> >>>> how or do I need to input the IP of the printer (I have a DDWRT
> >>>> router fwiw, if I'm supposed to assign a static IP somehow, and if
> >>>> that is not going to mess up the other computers using the network
> >>>> printer)
> >>>
> >>> Check what IP address they are printing to.
> >>>
> >>>
> >>>> As a final option, I don't use sys-usb qubes, so maybe I could
> >>>> connect the USB cable and try it that way instead ... sigh
> >>>>
> >>>>
> >>
> >>
> >> thanks for responding , as you can see the common theme, is I've no clue,
> >> how to find my printer IP , and apparently it may change if it's not
> >> static?
> >
> > Look in system-config-printer on one of your working systems. Yes, it
> > might change if it's not static. How did you set up the other system?
> >
> >> I had been told that the gateway address Was the printer IP , but I've
> >> really no idea
> >
> > That's usually incorrect, unless the printer is connected directly to your
> > router by USB.
>
> The working Linux Mint system says :
> dnssd://Brother%20HL-L2360D%20series._ipp._tcp.local/
>
> I pasted that into the AppVM as root with system-printer-config ->
> settings-> change -> IPP (ipp)
> and IPP (ipps) with no luck
>
> I did notice when I launched system-printer-config in terminal I see:
> Error creating proxy: The connection is closed (g-io-error-quark, 18)
>
> doing a web search on it but not hopeful
>
>
> 1) does it matter is system-printer-config runs as root or user in AppVM
>
> 2) will re running the driver setup /cups etc tarball package conflict
> with what I already did in the fedora-26-cloneprinter Template VM ?
>
> 3) I'm afraid static IPs are going to be a nonstarter for chronic
> newb as myself https://dd-wrt.com/phpBB2/viewtopic.php?t=263998
>
>
> 4) so much for qubes printing is so easy posts I've seen ...... even
> without a sys-usb :P
1) As memory serves, no root required. If it doesn't in a legitimate situation
ask for root access, don't use it.
2) It might be better to just make a new template, this way you cut away
clutter and you're sure you don't introduce new issues. As an alternative, you
can make CUPS active in your AppVM instead of your Template, by editing this
file /rw/config/rc.local which even has an example inside it for CUPS, all you
need to do is remove the three # marks. But keep in mind that this will
introduce additional exploit/attack surfaces to your AppVM, since CUPS
management will stay permanent between AppVM reboots. But in contrast it will
allow you easier management to printer changes, which may be important if you
make frequent printer adjustments or use it as a remote printer server which
requires server changes on the CUPS server. If you just need to install a
printer rarely, then it might be better to keep CUPS in the template, and put
the driver/IP-address in the template, so that the AppVM can find it.
3) Try see if your printer has a Network or System feature that allows you to
print out a print of your printers status and information. Many modern
printers, and many of a few years old printers too, have this feature today. It
might tell you various good things, like for example a name such as DNS name
you can use, which stays the same even if the IP changes dynamically.
4) Are you on Qubes 4? That might be why it's a bit more tricky now, since the
template has no network access to verify if it works or not, while Qubes 3.2.
templates had network access.
Another work-around, which is by no means official approach, is to disable your
networks internet access and isolate or remove any other systems on your
network (so only your printer, computer and maybe your router without an
internet cable in it, is networked), and then "temporarily" give your template
network access in your VM settings. Once the printer works, you can remove the
internet access to the template again, and re-apply your network again. Be
mindful this isn't a perfect solution though, but it might be a last solution
to consider if everything else fails.
As for another mention, some USB devices do not work in dom0 when it comes to
qvm-usb and qvm-block {typically advanced devices like printers/yubi-keys, but
not keyboards/mouse/some-usb-hdd's (semi because of design, and semi because of
a bug. A bug which will likely not get fixed since we're trying to move away
from dom0 USB uses in Qubes 4 on-wards. It causes issues on some hardware
though, I'm in a similar boat to you here as I have to keep USB controller in
dom0 to have a working system as too much other essential hardware is
internally bound to the USB controller).
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/8f9089cf-fab1-4a82-a3bb-6ad493b92c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
