OT: Dymo printer printserver on Pi Zero W.

[T i m]

A while back I asked here about the idea of using the Raspberry Pi as
a low power printserver for a Dymo LabelWriter and was given some good
pointers by Theo.

I was then able to set up a printserver (using Raspbian Linux) on my
Raspberry Pi(1)B with a WiFi dongle and was able to print to the Dymo
450 from Windows XP, 7, 8 and 10 and Ubuntu (although I could only
print a test page from Ubuntu as there is no Dymo app for Linux).

Then they released the Raspberry Pi Zero W (with wireless) and I have
been using one successfully to run Domoticz so thought it might be a
better solution for the Dymo PS (wifi built in, smaller / lower power
etc).

So, I've managed to install the latest Jessie Lite, get it on the Wlan
(headless) and installed CUPS, the Dymo drivers and Samba via SSH but
whilst the likes of XP 'can' see the shared printer, it can't install
it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
test page so it is 'there' and so maybe a Samba configuration thing?

Then whilst trying to configure it for static IP I stumbled into what
seems to be yet another Linux based clusterfcuk with 'them' (?)
changing fairly important stuff between releases? ;-(

https://www.raspberrypi.org/forums/viewtopic.php?p=798866#p798866

So, after following a suggestion on that thread I'm now (remotely)
shut out of the Pi and so I either have to waste even more time
plugging in a keyboard and display and trying to sort it out locally
or re-image it again and start from scratch (with no real hope I'll
get it working any better / further). ;-(

Is it one of these things where you need to limit the Raspbian to an
older release (and not apply any updates / upgrades) to try to avoid
all the problems ... as I was really hopeful that this would be a
really neat and useable solution?

Cheers, T i m

p.s. The Pi1 Dymo PS still works. ;-)

pi@Pi1Print:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie

[Capitol]

Reads like a normal Linux problem. My Elemental install with the Latest
Seamonkey is crap on handling pdfs. My Android phone can read the pdfs
but can't see the printer from email pdfs. Email prints ok if it's a
jpeg. My old install of Ubuntu 10.4 works perfectly. My Seamonkey
install on MS is crap and doesn't see pdf attachments for some reason.
The old Seamonkey works perfectly on MS and Ubuntu Linux.

I dont't update systems which are working ever.

[T i m]

On Sun, 2 Apr 2017 14:40:33 +0100, Capitol <sp...@whereva.uk> wrote:

<snip>

>>
>> Is it one of these things where you need to limit the Raspbian to an
>> older release (and not apply any updates / upgrades) to try to avoid
>> all the problems ... as I was really hopeful that this would be a
>> really neat and useable solution?
>>
>>

>> p.s. The Pi1 Dymo PS still works. ;-)
>>
>> pi@Pi1Print:~ $ lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Raspbian
>> Description: Raspbian GNU/Linux 8.0 (jessie)
>> Release: 8.0
>> Codename: jessie
>>
>
> Reads like a normal Linux problem.

It certainly seems to be something common amongst 'ordinary semi-tech
users' that's for sure (as the link I posted to people *wanting* to be
able to use Linux confirms).

> My Elemental install with the Latest
>Seamonkey is crap on handling pdfs.

Is there no better pdf tool for it?

>My Android phone can read the pdfs
>but can't see the printer from email pdfs. Email prints ok if it's a
>jpeg.

Again, not 'uncommon' combinations of things that may or may not work,
especially with anything not represented/ing 80% of the desktop using
public (Windows).

> My old install of Ubuntu 10.4 works perfectly.

I have several Linux installs (mainly Mint / Ubuntu) on a range of
machines and they too 'work' for my temporary use and with a given
subset of what I typically require on my 'main machine'.

>My Seamonkey
>install on MS is crap and doesn't see pdf attachments for some reason.

Strange ... the last time I used a suite like that was Netscape
Communicator (on Windows) but now I just use FF an TB.

>The old Seamonkey works perfectly on MS and Ubuntu Linux.

Ok.

>
> I dont't update systems which are working ever.

I have some (Linux machines only) marked as 'don't upgrade' as I have
found the upgrade breaks it bigtime. All the rest (and firmware /
BIOS's) I generally do upgrade 'just because'.

Back to the Raspberry Pi Zero W, I think I read somewhere that it was
advised to stick with an older (2016?) release and of course,
potentially not upgrade it but I can't find it again.

Cheers, T i m

[Theo]

T i m <ne...@spaced.me.uk> wrote:
> I was then able to set up a printserver (using Raspbian Linux) on my
> Raspberry Pi(1)B with a WiFi dongle and was able to print to the Dymo
> 450 from Windows XP, 7, 8 and 10 and Ubuntu (although I could only
> print a test page from Ubuntu as there is no Dymo app for Linux).

You should be able to print from any app - it's just a printer.
The 'paper size' happens to be a bit smaller than normal, that's all.

> So, I've managed to install the latest Jessie Lite, get it on the Wlan
> (headless) and installed CUPS, the Dymo drivers and Samba via SSH but
> whilst the likes of XP 'can' see the shared printer, it can't install
> it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
> test page so it is 'there' and so maybe a Samba configuration thing?
>
> Then whilst trying to configure it for static IP I stumbled into what
> seems to be yet another Linux based clusterfcuk with 'them' (?)
> changing fairly important stuff between releases? ;-(

Do I understand rightly that you didn't upgrade it, you installed a new
Jessie? So I don't see how an upgrade could have mucked up your settings?

It sounds like you put the wrong option in your network config, which then
locked you out of remote access? That happens to every sysadmin sooner or
later. For this reason servers have serial consoles and remote management,
datacentres have IPKVM and dev boards have video or serial.

This is not specifically a Linux problem: if you are outside adjusting the
lock on your front door, you should make sure the back door is usable or you
left a window open.

Theo

[T i m]

On 02 Apr 2017 15:34:08 +0100 (BST), Theo

<theom...@chiark.greenend.org.uk> wrote:

>T i m <ne...@spaced.me.uk> wrote:
>> I was then able to set up a printserver (using Raspbian Linux) on my
>> Raspberry Pi(1)B with a WiFi dongle and was able to print to the Dymo
>> 450 from Windows XP, 7, 8 and 10 and Ubuntu (although I could only
>> print a test page from Ubuntu as there is no Dymo app for Linux).
>
>You should be able to print from any app - it's just a printer.
>The 'paper size' happens to be a bit smaller than normal, that's all.

Hmm, whilst you are probably right the Dymo app (however bloated some
may consider it) does make life very easy. ;-(

>
>> So, I've managed to install the latest Jessie Lite, get it on the Wlan
>> (headless) and installed CUPS, the Dymo drivers and Samba via SSH but
>> whilst the likes of XP 'can' see the shared printer, it can't install
>> it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
>> test page so it is 'there' and so maybe a Samba configuration thing?
>>
>> Then whilst trying to configure it for static IP I stumbled into what
>> seems to be yet another Linux based clusterfcuk with 'them' (?)
>> changing fairly important stuff between releases? ;-(
>
>Do I understand rightly that you didn't upgrade it, you installed a new
>Jessie? So I don't see how an upgrade could have mucked up your settings?

Sorry Theo, no, as a matter of course (as it was a fresh install etc)
I installed the image and then updated and upgraded the install and
then added Cups, the Dymo driver and Samba etc.

>
>It sounds like you put the wrong option in your network config, which then
>locked you out of remote access?

Well yes, I followed the thread where people were suffering the same
problem in the hope that it would remove any DHCP address and just
leave the static address (that I have set up on all my server /
printer type devices, including the two other RPi's).

>That happens to every sysadmin sooner or
>later.

Oh, sure, and I only did it because the Pi was in front of me and I
knew I could plug in a screen and keyboard if I wasn't to. It seemed
just a shame that I'd managed to get that far (installing and
upgrading etc) with it completely headless).

>For this reason servers have serial consoles and remote management,
>datacentres have IPKVM and dev boards have video or serial.

Understood.

>
>This is not specifically a Linux problem: if you are outside adjusting the
>lock on your front door, you should make sure the back door is usable or you
>left a window open.

True, but that wasn't really the issue ... the issue that I (and many
others apparently) were actually suffering was that a ip scan of my
network showed the Pi on two ip addresses (and given it only has one
network interface) and I could connect to it (SSH / Cups admin) on
.164 when ifconfig showed it as having .132? (I copied and pasted
another command that seemed to confirm that both ip addresses were
present and active on that Pi but I can't remember what they were
now). The last idea (deleting a specific dchp related file) was
supposed to remove the duplication but it looks like it removed the
'active' address (even though I was accessing it on what was set as a
static address)?

I was only playing with that because 1) it obviously wasn't right and
2) that I thought it might have had something to do with not being
able to connect the printer via the Windows boxes?

Cheers, T i m

[dennis@home]

On 02/04/2017 14:23, T i m wrote:

> So, I've managed to install the latest Jessie Lite, get it on the Wlan
> (headless) and installed CUPS, the Dymo drivers and Samba via SSH but
> whilst the likes of XP 'can' see the shared printer, it can't install
> it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
> test page so it is 'there' and so maybe a Samba configuration thing?

SAMBA is file sharing not LPR.

>
> Then whilst trying to configure it for static IP I stumbled into what
> seems to be yet another Linux based clusterfcuk with 'them' (?)
> changing fairly important stuff between releases? ;-(
>
> https://www.raspberrypi.org/forums/viewtopic.php?p=798866#p798866

Its best not to set static addresses for anything but to use the static
address table in the router to assign them the same address each time
using DHCP.


It makes them portable between networks.

[Andy Burns]

dennis@home wrote:

> T i m wrote:
>
>> So, I've managed to install the latest Jessie Lite, get it on the Wlan
>> (headless) and installed CUPS, the Dymo drivers and Samba
>

> SAMBA is file sharing not LPR.

Windows clients expect to be able to load drivers from the
\\PRINTSERVER\\admin$\system32\spool\drivers
share, SAMBA can do that.

SAMBA also allows printers to be shared like Windows print queues,
rather than LPR queues

[Bob Eager]

On Sun, 02 Apr 2017 17:30:21 +0100, dennis@home wrote:

> On 02/04/2017 14:23, T i m wrote:
>
>> So, I've managed to install the latest Jessie Lite, get it on the Wlan
>> (headless) and installed CUPS, the Dymo drivers and Samba via SSH but
>> whilst the likes of XP 'can' see the shared printer, it can't install
>> it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
>> test page so it is 'there' and so maybe a Samba configuration thing?
>
> SAMBA is file sharing not LPR.

It does printer sharing too - using CIFS rather than LPD or similar.

--
My posts are my copyright and if @diy_forums or Home Owners' Hub
wish to copy them they can pay me £1 a message.
Use the BIG mirror service in the UK: http://www.mirrorservice.org
*lightning surge protection* - a w_tom conductor

[The Natural Philosopher]

or Jet direct or IPP queues.

see /etc/samba/smb.conf

for 'winshare' printers use samaba.

For other networked printer protocol use CUPS.

The cups daemon has an admin interface at http://mypi*:631 IIRC.
Its very useful.



*whatever the address of the Pi is...


--
"The great thing about Glasgow is that if there's a nuclear attack it'll
look exactly the same afterwards."

Billy Connolly

[Theo]

T i m <ne...@spaced.me.uk> wrote:
> Sorry Theo, no, as a matter of course (as it was a fresh install etc)
> I installed the image and then updated and upgraded the install and
> then added Cups, the Dymo driver and Samba etc.

OK.

> True, but that wasn't really the issue ... the issue that I (and many
> others apparently) were actually suffering was that a ip scan of my
> network showed the Pi on two ip addresses (and given it only has one
> network interface) and I could connect to it (SSH / Cups admin) on
> .164 when ifconfig showed it as having .132? (I copied and pasted
> another command that seemed to confirm that both ip addresses were
> present and active on that Pi but I can't remember what they were
> now). The last idea (deleting a specific dchp related file) was
> supposed to remove the duplication but it looks like it removed the
> 'active' address (even though I was accessing it on what was set as a
> static address)?

Two IP addresses is not a problem. In fact, most systems with IPv6 do it by
default.

If the SSH daemon is listening on 0.0.0.0 (as it likely is) you should be
able to get in via either address. The routing table will set which address
outbound connections come from.

If you removed the address for the IP you were talking to it on, the
connection would have dropped. But you should have been able to get in via
the other.

> I was only playing with that because 1) it obviously wasn't right and
> 2) that I thought it might have had something to do with not being
> able to connect the printer via the Windows boxes?

I don't think it will have been related, since CUPS/Samba would presumably
have been listening on both IPs?

Theo

[T i m]

On 02 Apr 2017 20:58:48 +0100 (BST), Theo

<theom...@chiark.greenend.org.uk> wrote:

>T i m <ne...@spaced.me.uk> wrote:
>> Sorry Theo, no, as a matter of course (as it was a fresh install etc)
>> I installed the image and then updated and upgraded the install and
>> then added Cups, the Dymo driver and Samba etc.
>
>OK.
>
>> True, but that wasn't really the issue ... the issue that I (and many
>> others apparently) were actually suffering was that a ip scan of my
>> network showed the Pi on two ip addresses (and given it only has one
>> network interface) and I could connect to it (SSH / Cups admin) on
>> .164 when ifconfig showed it as having .132? (I copied and pasted
>> another command that seemed to confirm that both ip addresses were
>> present and active on that Pi but I can't remember what they were
>> now). The last idea (deleting a specific dchp related file) was
>> supposed to remove the duplication but it looks like it removed the
>> 'active' address (even though I was accessing it on what was set as a
>> static address)?
>
>Two IP addresses is not a problem. In fact, most systems with IPv6 do it by
>default.

Ah, ok, I don't have IPv6 enabled on this PC (Mac Mini / XP) so didn't
think I would see any IPv6 related stuff? I didn't think that an IPv6
address appeared in the std 4 octets format as it's bigger?

I saw the host PiZW-Dymo-PS as 192.168.0.132 (that I didn't intend and
is within my routers DHCP scope) and the 192.168.0.164 that I intended
it to be on via a static IP address set for wlan0 in /etc/dhcpcd.conf

>
>If the SSH daemon is listening on 0.0.0.0 (as it likely is) you should be
>able to get in via either address.

I think I could.

>The routing table will set which address
>outbound connections come from.

Ok.

>
>If you removed the address for the IP you were talking to it on, the
>connection would have dropped. But you should have been able to get in via
>the other.

They both seem to be gone since I removed the dhcpcd5 package
(following a hint on the forum that gave someone else success).

>
>> I was only playing with that because 1) it obviously wasn't right and
>> 2) that I thought it might have had something to do with not being
>> able to connect the printer via the Windows boxes?
>
>I don't think it will have been related, since CUPS/Samba would presumably
>have been listening on both IPs?

I thought it was a Samba issue but then Ubuntu could install and print
to the Dymo when it was added under Samba shares?

I think I'll start again, get back to as close as I can get and report
back in case there are some specific things you would like me to
check?

Cheers, T i m

[Mike Tomlinson]

>D i m <ne...@spaced.me.uk> wrote:

>> Then whilst trying to configure it for static IP I stumbled into what
>> seems to be yet another Linux based clusterfcuk with 'them' (?)
>> changing fairly important stuff between releases? ;-(

1. Pack your computer up in its original box.
2. Take it back to the shop.
3. When sullen teenage assistant asks what you want, ask for a refund
4. When STA asks why, explain that you're too stupid to own a computer.

ps. A bad workman blames his tools.

--
(\_/)
(='.'=) "Between two evils, I always pick
(")_(") the one I never tried before." - Mae West

[Tim Watts]

On 02/04/17 17:30, dennis@home wrote:
> On 02/04/2017 14:23, T i m wrote:
>
>> So, I've managed to install the latest Jessie Lite, get it on the Wlan
>> (headless) and installed CUPS, the Dymo drivers and Samba via SSH but
>> whilst the likes of XP 'can' see the shared printer, it can't install
>> it and W8 / 10 can't seem to see it. Ubuntu can see it and send it a
>> test page so it is 'there' and so maybe a Samba configuration thing?
>
> SAMBA is file sharing not LPR.

It's printing on Windows as well as filesharing.

[Tim Watts]

On 02/04/17 20:58, Theo wrote:
> T i m <ne...@spaced.me.uk> wrote:
>> Sorry Theo, no, as a matter of course (as it was a fresh install etc)
>> I installed the image and then updated and upgraded the install and
>> then added Cups, the Dymo driver and Samba etc.
>
> OK.
>
>> True, but that wasn't really the issue ... the issue that I (and many
>> others apparently) were actually suffering was that a ip scan of my
>> network showed the Pi on two ip addresses (and given it only has one
>> network interface) and I could connect to it (SSH / Cups admin) on
>> .164 when ifconfig showed it as having .132? (I copied and pasted
>> another command that seemed to confirm that both ip addresses were
>> present and active on that Pi but I can't remember what they were
>> now). The last idea (deleting a specific dchp related file) was
>> supposed to remove the duplication but it looks like it removed the
>> 'active' address (even though I was accessing it on what was set as a
>> static address)?
>
> Two IP addresses is not a problem. In fact, most systems with IPv6 do it by
> default.

And you can have as many IPv4 addresses as you like bound to an adaptor.
Linux is clever, it will do the right thing by default.

[Tim Watts]

On 03/04/17 02:56, Mike Tomlinson wrote:

> ps. A bad workman blames his tools.
>

Blehhh.

There is such a thing as a shit tool. Such as the square I bought from
Screwfix last year that wasn't!

[Mike Tomlinson]

En el artículo <pse9rd-...@squidward.local.dionic.net>, Tim Watts
<tw_u...@dionic.net> escribió:

>There is such a thing as a shit tool. Such as the square I bought from
>Screwfix last year that wasn't!

You get what you pay for.

Must be cliché day today :)

[T i m]

On Mon, 3 Apr 2017 09:48:57 +0100, Tim Watts <tw_u...@dionic.net>
wrote:

Don't worry, Tomlinson 'The mad cat woman', apart from being my
personal stalker is one of those 'Linux is perfect' fanatics and
therefore no honest opinion from an ordinary tech-user would be given
any credence what so ever.

By it's reckoning, anyone having trouble with the disorganised mess
that Linux can often be (especially to non-nerds) must be wrong and
inferior to him / them.

And this is in spite of some Linux distos suggesting that they are
very easy to install and use but I'm not sure how that explains the
millions of posts from reasonably computer savvy people who are
perfectly able to get similar stuff working in Windows and OSX
(including those trying to do exactly what I have).

I have *never* wasted anything like such time trying to get any other
OS going as I have Linux. I'm not surprised that's the case of course
because it's not 'a product but a conglomeration of often disparate
ideas and modules from many different sources and with no real
direction. This of course is *exactly* why many of the Linux nerds
believe Linux is the best thing since sliced bread. It's all my fault
of course <rolls eyes> because I don't find it exciting or
entertaining to sit their ploughing though 'man pages' just to make
work something that should 'just work' in the first place.

However, I carry on trying (and am slowing getting better) because
that's the only way you can (and even I often do) work round it and
it's issues and then get to something that often works well.

You only need to read *any* Linux support type thread to see even the
nerds contradicting and arguing with each other re what the problem /
solution might be.

So, this particular project (print server for Dymo label printer)
should have been a fairly straightforward process (and I have
previously got it going on a Std Pi1, with the help of Theo) except
the Raspberry Pi Zero W is a fairly new Pi variant and the Raspbian
Linux spin way of doing things has recently changed and thrown quite a
few people into confusion.

That Pi1 solution only sported one ip address and now the (now
running) Pi Zero W version only sports one ip address. <shrug>

Cheers, T i m

[T i m]

On Sun, 2 Apr 2017 17:44:32 +0100, Andy Burns <use...@andyburns.uk>
wrote:

>dennis@home wrote:
>
>> T i m wrote:
>>
>>> So, I've managed to install the latest Jessie Lite, get it on the Wlan
>>> (headless) and installed CUPS, the Dymo drivers and Samba
>>
>> SAMBA is file sharing not LPR.
>
>Windows clients expect to be able to load drivers from the
>\\PRINTSERVER\\admin$\system32\spool\drivers
>share, SAMBA can do that.

I think this may hint at something that may have been part of the
problem Andy.

On the instruction I followed re installing SAMBA on the Pi it
suggested that you change the driver location within the Pi SAMBA
server to:

path = /usr/share/cups/drivers (as there isn't such a place)

but it actually should have been (left at?):

path = /var/lib/samba/printers (even though the sub folders appear
empty)?

This also got me some of the way:

https://chicagodist.com/blogs/news/15272985-using-the-raspberry-pi-as-a-print-server-for-a-dymo-4xl-label-printer

>
>SAMBA also allows printers to be shared like Windows print queues,
>rather than LPR queues

Yup. I was able to see and print to the Dymo (via the Pi PS) from
Ubuntu before installing SAMBA (using the 'browse to printer' type
method) but only able to do the same from Windows after installing an
configuring SAMBA.

Cheers, T i m

[The Natural Philosopher]

Its there to emulate winders file *and* printer sharing,, so of course
it doesn't use LPR protocols to do it.

M$soft didnt invent LPR, so why would they use it to print?

--
"Corbyn talks about equality, justice, opportunity, health care, peace,
community, compassion, investment, security, housing...."
"What kind of person is not interested in those things?"

"Jeremy Corbyn?"

[The Natural Philosopher]

Of copurse, we cpuld debate forever what was the 'right ting'

I do remember an urgent support call from a customer 'my NT box is
losing 50% of its IP packets..." "EXACTLY 50%?"'

"Yes..."

Well that's what happens when you have two interfaces and *both* are
nominated as the 'default' route.

Even *nix has never been stupid enough to allow that.

[Bob Eager]

On Mon, 03 Apr 2017 10:52:59 +0100, The Natural Philosopher wrote:

> On 03/04/17 09:28, Tim Watts wrote:
>> On 02/04/17 17:30, dennis@home wrote:
>>> On 02/04/2017 14:23, T i m wrote:
>>>
>>>> So, I've managed to install the latest Jessie Lite, get it on the
>>>> Wlan (headless) and installed CUPS, the Dymo drivers and Samba via
>>>> SSH but whilst the likes of XP 'can' see the shared printer, it can't
>>>> install it and W8 / 10 can't seem to see it. Ubuntu can see it and
>>>> send it a test page so it is 'there' and so maybe a Samba
>>>> configuration thing?
>>>
>>> SAMBA is file sharing not LPR.
>>
>> It's printing on Windows as well as filesharing.
>>
> Its there to emulate winders file *and* printer sharing,, so of course
> it doesn't use LPR protocols to do it.
>
> M$soft didnt invent LPR, so why would they use it to print?

Doesn't stop them from providing LPR as a way to print.

[The Natural Philosopher]

On 03/04/17 12:54, Bob Eager wrote:
> On Mon, 03 Apr 2017 10:52:59 +0100, The Natural Philosopher wrote:
>
>> On 03/04/17 09:28, Tim Watts wrote:
>>> On 02/04/17 17:30, dennis@home wrote:
>>>> On 02/04/2017 14:23, T i m wrote:
>>>>
>>>>> So, I've managed to install the latest Jessie Lite, get it on the
>>>>> Wlan (headless) and installed CUPS, the Dymo drivers and Samba via
>>>>> SSH but whilst the likes of XP 'can' see the shared printer, it can't
>>>>> install it and W8 / 10 can't seem to see it. Ubuntu can see it and
>>>>> send it a test page so it is 'there' and so maybe a Samba
>>>>> configuration thing?
>>>>
>>>> SAMBA is file sharing not LPR.
>>>
>>> It's printing on Windows as well as filesharing.
>>>
>> Its there to emulate winders file *and* printer sharing,, so of course
>> it doesn't use LPR protocols to do it.
>>
>> M$soft didnt invent LPR, so why would they use it to print?
>
> Doesn't stop them from providing LPR as a way to print.
>
>

LPD I assume


--
All political activity makes complete sense once the proposition that
all government is basically a self-legalising protection racket, is
fully understood.

[Bob Eager]

On Mon, 03 Apr 2017 15:01:56 +0100, The Natural Philosopher wrote:

> On 03/04/17 12:54, Bob Eager wrote:
>> On Mon, 03 Apr 2017 10:52:59 +0100, The Natural Philosopher wrote:
>>
>>> On 03/04/17 09:28, Tim Watts wrote:
>>>> On 02/04/17 17:30, dennis@home wrote:
>>>>> On 02/04/2017 14:23, T i m wrote:
>>>>>
>>>>>> So, I've managed to install the latest Jessie Lite, get it on the
>>>>>> Wlan (headless) and installed CUPS, the Dymo drivers and Samba via
>>>>>> SSH but whilst the likes of XP 'can' see the shared printer, it
>>>>>> can't install it and W8 / 10 can't seem to see it. Ubuntu can see
>>>>>> it and send it a test page so it is 'there' and so maybe a Samba
>>>>>> configuration thing?
>>>>>
>>>>> SAMBA is file sharing not LPR.
>>>>
>>>> It's printing on Windows as well as filesharing.
>>>>
>>> Its there to emulate winders file *and* printer sharing,, so of course
>>> it doesn't use LPR protocols to do it.
>>>
>>> M$soft didnt invent LPR, so why would they use it to print?
>>
>> Doesn't stop them from providing LPR as a way to print.
>>
>>
> LPD I assume

Yes, although Windows refers to it as an 'LPR' port. The machine that
does print serving here doesn't run Samba, so I run bare LPD.

[T i m]

On 02/04/2017 17:30, dennis@home wrote:

<snip>

> Its best not to set static addresses for anything but to use the static
> address table in the router to assign them the same address each time
> using DHCP.
>
>
> It makes them portable between networks.
>

Whilst it might, I prefer for those devices that are very unlikely to be
run anywhere other than my LAN to set static IP address as there is more
chance I'll have to replace the router (and so have to setup the
reservations again) than run the kit elsewhere.

Also (and FWIW), my FritzBox doesn't seem to allow you to reserve a
specific address, just the address that is currently assigned. I could I
suppose set a static address on the device first, then reserve it on the
router then set the device back to dhcp again.

So, as my lan is connected to my mates next door and he only has a few
network devices, he turns off his dhcp and reserves his addresses. His
router ip is .1 and all his addresses are below .99. My router is .100,
the dhcp scope is .120-.149, my desktops all static from .150-159 and
servers (WHS, Domoticz, OMV, Pi Dymo PS etc .160 on.

Cheers, T i m









---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[T i m]

On Sun, 02 Apr 2017 23:36:43 +0100, T i m <ne...@spaced.me.uk> wrote:

<snip>

>I think I'll start again, get back to as close as I can get and report
>back in case there are some specific things you would like me to
>check?

I did start again and I'm not sure what / if I did differently to the
first time(s) but this time it worked. I've tried to document (for
myself and maybe others) the key steps in the hope that it's still
pertinent the next time.

If you (Theo?) wouldn't mind running a quick eye over it in case I've
missed or added something that isn't correct.

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

The object of the exercise was to create a very small, cheap and low
power wireless (only) print server using a Raspberry Pi Zero W.

https://www.raspberrypi.org/blog/raspberry-pi-zero-w-joins-family/

In my case it was to be used to wirelessly share a Dymo LabelWriter
450 to mostly Windows clients.

Whilst I could have plugged the Pi into a HDMI monitor / TV and add a
USB keyboard and mouse, I wanted to do it 'headless'.

1) Get Raspbian image. I used Jessie Lite (v March 2017)

https://www.raspberrypi.org/downloads/raspbian/

2) Write image to uSD card. I used an 16G card and Win32DiskImager
under Windows.

https://sourceforge.net/projects/win32diskimager/

3) Because ssh is disabled by default (now), create an empty file
called 'ssh' (no quotes) on the uSD card Fat32 partition called
'boot'. I opened up Explorer, browsed to the boot partition and right
clicked there, New, > Text document, and call it ssh

4) Whilst on the boot partition, create another plain text file called
'wpa_supplicant.conf' and enter (I opened it with Notepad (Open with))
and save the following code:


network={
ssid="myssid"
psk="mypassword"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}


(change myssid and mypassword to suit your own)

5) Put the uSD card in the Pi and power up (the uUSB connector nearest
the end is for power) and wait till the green LED stops flickering
(stays on solid).

6) Locate the Pi on the LAN. I use the free 'Advanced IP Scanner' on
Windows.

https://www.advanced-ip-scanner.com/

7) Connect to the Pi using an ssd client. Many use 'Putty' and I also
use MobaXterm Personal Edition.

http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
http://mobaxterm.mobatek.net/

The default login is 'pi' with the password 'raspberry'.

8) You should now be able to run raspi-config and change some stuff
from there:

sudo raspi-config

Then as a minimum use '7 Advanced options' then A1 'Expand Filesystem

I also

Change Hostname
Set Localisation
Update utility.

Exit raspi-config (escape) and reboot

sudo reboot

(I *think* you should also update Raspbian at this point with:

sudo apt-get update
sudo apt-get upgrade)

9) If you want to use a static ip address, edit /etc/dhcpcd.conf

sudo nano /etc/dhcpcd.conf

and add / edit:


interface wlan0
static ip_address=<ip address for pi>/24
static routers=<ip address for router>
static domain_name_servers=<probably ip address for router>


Ctrl+O > Enter, Ctrl+x.


10) To create the printer server part for the Dymo I needed to install
CUPS and some other bits to be able to provide the Dymo drivers.

sudo apt-get install libcups2-dev libcupsimage2-dev g++ cups
cups-client

(It's possible that if you didn't have to make the drivers you could
just install cups)?

For the Dymo stuff I did the following.

wget
http://download.dymo.com/Download%20Drivers/Linux/Download/dymo-cups-drivers-1.4.0.tar.gz

(Watch line wrap. Should be one string)

then (one cmd at a time)

tar xvf dymo-cups-drivers-1.4.0.tar.gz
cd dymo-cups-drivers-1.4.0.5/
sudo ./configure
sudo make
sudo make install

12) add user pi to lpadmin

sudo usermod -a -G lpadmin pi

13) To be able to access the CUPS server from a workstation on the LAN
you need to edit the Cups configuration file:

sudo nano /etc/cups/cupsd.conf

You then need to change add the following 4 bits:

# Only listen for connections from the local machine
# Listen localhost:631
Port 631

< Location / >
# Restrict access to the server...
Order allow,deny
Allow @local
< /Location >

< Location /admin >
# Restrict access to the admin pages...
Order allow,deny
Allow @local
< /Location >

# Restrict access to the configuration files...
Order allow,deny
Allow @local
< /Location >

Ctrl+o Enter, Ctrl+x

restart the CUPS server:

sudo /etc/init.d/cups restart


13) You should then be able to access the CUPS admin remotely using a
web browser:

<ip address of pi>:631/admin

Username should still be 'pi' and password still 'raspberry' (unless
you have changed it previously).

Because I wanted to share the Dymo LabelWriter 450 I made sure that
was plugged into the other uUSB port (I ordered a short uUSB to Type B
usb lead from eBay). The printer then appears in the list and can be
added by just following the prompts.

Add Printer, select Dymo etc ... and make sure you check the Shared
option.

14) To share the printer to Windows machine I added SAMBA.

sudo apt-get install samba

Then edit the configuration file to resemble the following sections.

sudo nano /etc/samba/smb.conf

workgroup = WORKGROUP
(Change to your workgroup if you have one)



[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = yes
read only = yes
create mask = 0700

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = no
guest ok = no

I used the following sites for some of the info and other bits gleaned
from elsewhere.


https://www.hmazter.com/2013/05/raspberry-pi-printer-server-for-labelwriter

https://chicagodist.com/blogs/news/15272985-using-the-raspberry-pi-as-a-print-server-for-a-dymo-4xl-label-printer


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

I think I should be able to upload the drivers into the various
folders under /var/lib/samba/printers but I'm not sure where to get
them from?

Cheers, T i m

[Theo]

T i m <ne...@spaced.me.uk> wrote:
> I did start again and I'm not sure what / if I did differently to the
> first time(s) but this time it worked. I've tried to document (for
> myself and maybe others) the key steps in the hope that it's still
> pertinent the next time.
>
> If you (Theo?) wouldn't mind running a quick eye over it in case I've
> missed or added something that isn't correct.

I'm not familiar with all of the steps, but:
1-2, 5-8, 12-13b look ok

10: good practice not to 'sudo' before ./configure and make, but necessary
before make install (either way won't really make a difference here)

3-4, 9, 14 I have no experience with

Theo

[T i m]

On 05/04/2017 12:34, Theo wrote:
> T i m <ne...@spaced.me.uk> wrote:
>> I did start again and I'm not sure what / if I did differently to the
>> first time(s) but this time it worked. I've tried to document (for
>> myself and maybe others) the key steps in the hope that it's still
>> pertinent the next time.
>>
>> If you (Theo?) wouldn't mind running a quick eye over it in case I've
>> missed or added something that isn't correct.
>
> I'm not familiar with all of the steps, but:
> 1-2, 5-8, 12-13b look ok
>
> 10: good practice not to 'sudo' before ./configure and make,

Oh ok, why may I ask (as I just copied and pasted it from someone who
seemed to know more about it than I did)?

> but necessary
> before make install (either way won't really make a difference here)

Noted.

>
> 3-4, 9, 14 I have no experience with

Ok and thanks for looking. ;-)

[Theo]

T i m <ne...@spaced.me.uk> wrote:
> On 05/04/2017 12:34, Theo wrote:
> > I'm not familiar with all of the steps, but:
> > 1-2, 5-8, 12-13b look ok
> >
> > 10: good practice not to 'sudo' before ./configure and make,
>
> Oh ok, why may I ask (as I just copied and pasted it from someone who
> seemed to know more about it than I did)?

'sudo' is the equivalent of Windows' 'run as administrator', for the
command that comes after it.

Here you configure the build, build and install the program. The configure
and build don't need to run as administrator - in general the least you run
with admin privilege the better. Installation does need privilege to copy
into system folders, so you need sudo for that.

Theo

[T i m]

On 05 Apr 2017 21:33:29 +0100 (BST), Theo

<theom...@chiark.greenend.org.uk> wrote:

>T i m <ne...@spaced.me.uk> wrote:
>> On 05/04/2017 12:34, Theo wrote:
>> > I'm not familiar with all of the steps, but:
>> > 1-2, 5-8, 12-13b look ok
>> >
>> > 10: good practice not to 'sudo' before ./configure and make,
>>
>> Oh ok, why may I ask (as I just copied and pasted it from someone who
>> seemed to know more about it than I did)?
>
>'sudo' is the equivalent of Windows' 'run as administrator', for the
>command that comes after it.

Yes, I understood that much, but from my experience (of Linux) so far,
anything of any worth seems to require one to be an administrator to
do it.

>
>Here you configure the build, build and install the program. The configure
>and build don't need to run as administrator - in general the least you run
>with admin privilege the better.

Ok. I understand the suggestion and I guess that could be a good thing
for non - admin people etc, bit to me having to type in a password or
prepend each command with sudo (or use su etc) is actually a PITA and
I'm pleased when I use a system that only has one user that is an
admin by default.

FWIW, I have always run my user as Admin and with no password since
W3.1 and any other system that would let me. I'm not suggesting that
would be a good idea for most, just that it suits me best. ;-)

> Installation does need privilege to copy
>into system folders, so you need sudo for that.

The problem here is not knowing what you can or can not do without
being an Admin to do so might prepend *every* command with it to save
not being told I can't.

I even have to start the likes of nautilus as a sudo so that can
*just* open any file to edit and save it (from the gui, so I don't
have to navigate the filesystem manually and use 'sudo nano' etc).

Whilst I can use the keyboard, I'm not a typist and since we have
GUI's on most these desktop OS's, I like to use them. ;-)

Also, as I installed most of the system I use myself, I feel I also
have the right to break them (not that I have very often in nearly 40
years). ;-)

Cheers, T i m