I have unearthed a new problem

When I attempt to use the scanner I get an error


Failed to open device brother4:net1;dev0

Checking with MCC and "setup scanner"
I get

The following scanner

- Brother SCANNER MFC-9340CDW

is available on your system.


The printer is networked and has worked flawlessly.

*Thanks Bit Twister*

The only change is a new router since the NBN fibre was activated. This
may or may not be pertinent. I am not absolutely sure if I've used the
scanner since the changeover - I doubt it. Scanning is an infrequent
activity

The printer is still networked with the new router and it prints OK and
pings OK

~]$ ping -c1 prnt
PING prnt.cryptid.test (192.168.20.3) 56(84) bytes of data.
64 bytes from prnt.cryptid.test (192.168.20.3): icmp_seq=1 ttl=255
time=2.23 ms

- --- prnt.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.225/2.225/2.225/0.000 ms


There have been several OS updates since the new router was installed
but this may also be a dud lead.

Wondering should I use MCC and remove / re-install the scanner despite
MCC claim that it is available.


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Thu, 10 Dec 2020 18:02:06 +1100, faeychild wrote:

I have unearthed a new problem

When I attempt to use the scanner I get an error

Have you ever used the scanner after you moved/set it static and networked before the router change?

Failed to open device brother4:net1;dev0

Checking with MCC and "setup scanner"
I get

The following scanner

- Brother SCANNER MFC-9340CDW

is available on your system.

The printer is networked and has worked flawlessly.

*Thanks Bit Twister*

The only change is a new router since the NBN fibre was activated. This
may or may not be pertinent. I am not absolutely sure if I've used the scanner since the changeover - I doubt it. Scanning is an infrequent
activity

The printer is still networked with the new router and it prints OK and pings OK

~]$ ping -c1 prnt
PING prnt.cryptid.test (192.168.20.3) 56(84) bytes of data.
64 bytes from prnt.cryptid.test (192.168.20.3): icmp_seq=1 ttl=255
time=2.23 ms

Well that is different. I would like the following please:

url of router manual.

cat /etc/hosts
id -nG

Wondering should I use MCC and remove / re-install the scanner despite
MCC claim that it is available.

Do bookmark this URL

https://support.brother.com/g/b/downloadlist.aspx?c=us&lang=en&prod=mfc9340cdw_ all&os=127

Quick check of
Release Date
(Version)
shows updates since 06/04/2020

I have no idea how you did your install, but I know a whole lot of of
my problems went away when I used the brother install script.

WARNING: Brother install script attempts to pick your package manager.
You need to disable all package managers prior to running it.

My install_printer script runs
disable_enable_pkg_mgrs -d
runs the install script then
disable_enable_pkg_mgrs -e

----8<----8<----8<----8<--cut below this line --8<----8<----8<
#!/bin/bash #**********************************************************************
#*
#* disable_enable_pkg_mgrs - Enable/disable package managers
#*
#**********************************************************************

set -u # Show usage of unset variables as an error to help catch typos.

_cmd_line_args="$@"

_fn=""
_pkg_mgrs="/usr/bin/dpkg /usr/bin/dnf /usr/bin/yum"
_to_do=""


function usage ()
{
echo "
$_exe $_arg1 is incorrect
Usage: $_exe [ -e -d ]
-e will enable $_pkg_mgrs
-d will disable $_pkg_mgrs
"
exit 0
} # end usage



#*******************************************
#* command line argument check
#*******************************************

set -- $_cmd_line_args
while [ $# -gt 0 ] ; do
_arg1=$1
case $_arg1 in
-d) _to_do='-x' ;;
-e) _to_do='+x' ;;
*) usage ; exit 1 ;;
esac
shift
done


for _fn in $_pkg_mgrs ; do
if [ -e $_fn ] ; then
chmod $_to_do $_fn
fi
done


#************** End disable_enable_pkg_mgrs *********************

NOTE:
The warranty and liability expired as you read this message.
If the above breaks your system, it's yours and you keep both pieces.
Practice safe computing. Backup the file before you change it.
Do a, man command_here or cat command_here, before using it.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 11/12/20 1:39 am, Bit Twister wrote:

On Thu, 10 Dec 2020 18:02:06 +1100, faeychild wrote:

I have unearthed a new problem

When I attempt to use the scanner I get an error

Have you ever used the scanner after you moved/set it static and networked before the router change?

Yes! I asked myself that question after getting printer networked
Does the scanner work, Surprised!!! it did.

~]$ ping -c1 prnt
PING prnt.cryptid.test (192.168.20.3) 56(84) bytes of data.
64 bytes from prnt.cryptid.test (192.168.20.3): icmp_seq=1 ttl=255
time=2.23 ms

Well that is different. I would like the following please:

url of router manual.\\

https://support.netcommwireless.com/products/NF18MESH

cat /etc/hosts

~]$ cat /etc/hosts
# generated by drakhosts
127.0.0.1 localhost.localdomain localhost
192.168.20.4 unimatrix.cryptid.test nic
192.168.20.3 prnt.cryptid.test prnt
192.168.20.1 gateway.cryptid.test gtwy
100.66.0.1 wangate.cryptid.test wgtwy
100.66.35.87 wanip.cryptid.test wanip

id -nG

~]$ id -nG
faeychild lp cdrom usb systemd-journal wireshark scanner

I have no idea how you did your install, but I know a whole lot of of
my problems went away when I used the brother install script.

Yes Installed by script

WARNING: Brother install script attempts to pick your package manager.
You need to disable all package managers prior to running it.

Yes I remember this. I don't recall how/if I got around it.


When xsane is first activated I get a popup before the fail error

HPLIP STATUS
HP_Scan_Devices_Scanner (1.1.1.1)
(5018)

This appears once after each login or reboot

regards


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Thu, 10 Dec 2020 18:02:06 +1100, faeychild wrote:

I have unearthed a new problem

When I attempt to use the scanner I get an error

Failed to open device brother4:net1;dev0

Checking with MCC and "setup scanner"
I get

The following scanner

- Brother SCANNER MFC-9340CDW

is available on your system.

Well, I am going to assume you have gone through the printer interface
and verified its static ip address is now 192.168.20.3

Next I would get into mcc Hardware->Set up scanner delete any scanner
entries, then scan for scanners and pick the scanner.

I do hope that fixes your problem. I have no other ideas.
So far everything provided so far looks ok.

HPLIP STATUS
HP_Scan_Devices_Scanner (1.1.1.1)
(5018)

This appears once after each login or reboot

Because I no longer buy any HP printer products I did not install
that rpm so I have no suggestions for that error.

Since I also have a Brother printer/scanner I have a question for
you.

When I use google maps and print the map, I can barley see the streets
let alone the street names.

Is your print the same?


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 11/12/20 8:01 am, Bit Twister wrote:

Well, I am going to assume you have gone through the printer interface
and verified its static ip address is now 192.168.20.3

Yes And it returns ping and it does print

Next I would get into mcc Hardware->Set up scanner delete any scanner entries, then scan for scanners and pick the scanner.

I do hope that fixes your problem. I have no other ideas.
So far everything provided so far looks ok.

Because I no longer buy any HP printer products I did not install
that rpm so I have no suggestions for that error.

If the printer is installed through MCC, it will insist on installing
the HP stuff




Once upon a time this was needed in 60-libsane.rules

*************
"#Support for Brother unlisted scanner.
# At the end of /lib/udev/rules.d/60-libsane.rules,
# add two lines between the two labels as follows:
# add user to "lp" and "scanner"

LABEL="libsane_scsi_rules_end"
# Brother MFC-J825DW
ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"

LABEL="libsane_rules_end"

*****************

60-libsane.rules specifies that it covers USB and SCSI printers and I
think that addition was eliminated by the use of Brother script.

Now it is networked and no longer USB or SCSI but then again maybe it's
some sort of a wrapper.

I do have a vanilla install of Mageia 6. I could attempt to install the printer there as a sacrificial test base

Since I also have a Brother printer/scanner I have a question for
you.

When I use google maps and print the map, I can barley see the streets
let alone the street names.

Is your print the same?

Indeed! A very shitty low contrast pastel print - almost useless.

Once I tried to beef up the contrast with Gimp - but - Law of
diminishing returns

The printer is not fast with graphics/pictures. It can sometimes seem to
take forever before it starts to print. This is the same with USB and networked

It just took about 30 seconds to wake up and print the CUPS test page. I
have no idea if this is normal. The test page is not graphic intensive

regards



--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 11 Dec 2020 09:02:39 +1100, faeychild wrote:

On 11/12/20 8:01 am, Bit Twister wrote:

Because I no longer buy any HP printer products I did not install
that rpm so I have no suggestions for that error.

If the printer is installed through MCC, it will insist on installing
the HP stuff

Ok, since I used the brother install script, I do not bother with mcc.

Now it is networked and no longer USB or SCSI but then again maybe it's
some sort of a wrapper.

Entered saned brother network printer in the first box
at https://www.google.com/advanced_search and got
About 28,200 results (0.64 seconds)

Maybe not. take a look at https://askubuntu.com/questions/1029154/network-scan-with-brother-mfc
answers.

Sorry I can not play with your problem. Trying to install
v4l2loopback - a kernel module to create V4L2 loopback devices
so that I can use a network webcam on zoom.

Thank you for google map print answer. Was worried it was a bug on
my system. Will research it when I have nothing else to do.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 11/12/20 9:36 am, Bit Twister wrote:

On Fri, 11 Dec 2020 09:02:39 +1100, faeychild wrote:

On 11/12/20 8:01 am, Bit Twister wrote:

Because I no longer buy any HP printer products I did not install
that rpm so I have no suggestions for that error.

If the printer is installed through MCC, it will insist on installing
the HP stuff

Ok, since I used the brother install script, I do not bother with mcc.

It has been a while for me and I don't remember if the script is all
that is needed without further setting up

Entered saned brother network printer in the first box
at https://www.google.com/advanced_search and got
About 28,200 results (0.64 seconds)

Maybe not. take a look at https://askubuntu.com/questions/1029154/network-scan-with-brother-mfc answers.

Some interesting hits there,

Sorry I can not play with your problem. Trying to install
v4l2loopback - a kernel module to create V4L2 loopback devices
so that I can use a network webcam on zoom.

Suggest you concentrate your immediate problems. The scanner is non
essential and just a curiosity. I have video processing tying me up and
I can't logout / reboot for a while. I'm stuck anyway.

Thanks Bits

Regards



--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2020-12-10, Bit Twister <BitTwister@mouse-potato.com> wrote:

On Fri, 11 Dec 2020 09:02:39 +1100, faeychild wrote:

On 11/12/20 8:01 am, Bit Twister wrote:

Because I no longer buy any HP printer products I did not install
that rpm so I have no suggestions for that error.

If the printer is installed through MCC, it will insist on installing
the HP stuff

Ok, since I used the brother install script, I do not bother with mcc.

Now it is networked and no longer USB or SCSI but then again maybe it's
some sort of a wrapper.

Entered saned brother network printer in the first box
at https://www.google.com/advanced_search and got
About 28,200 results (0.64 seconds)

Maybe not. take a look at https://askubuntu.com/questions/1029154/network-scan-with-brother-mfc answers.

Sorry I can not play with your problem. Trying to install
v4l2loopback - a kernel module to create V4L2 loopback devices
so that I can use a network webcam on zoom.

What webcam? I just plugged it in and it worked. Install gucview to set
up the camera (colour, contrast, etc)

Thank you for google map print answer. Was worried it was a bug on
my system. Will research it when I have nothing else to do.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 11 Dec 2020 02:21:26 -0000 (UTC), William Unruh wrote:

On 2020-12-10, Bit Twister <BitTwister@mouse-potato.com> wrote:

Sorry I can not play with your problem. Trying to install
v4l2loopback - a kernel module to create V4L2 loopback devices
so that I can use a network webcam on zoom.

What webcam? I just plugged it in and it worked.

Going to guess your webcam connects via a usb cable. :)

I am out of usb ports on the back of my desktop pc
so I am going to try a network webcam which requires making il look
like a video device instead of a network device.

Thank for your time/response in zoom question thread.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Thu, 10 Dec 2020 18:02:06 +1100, faeychild wrote:

I have unearthed a new problem

When I attempt to use the scanner I get an error

Failed to open device brother4:net1;dev0

Checking with MCC and "setup scanner"
I get

The following scanner

- Brother SCANNER MFC-9340CDW

is available on your system.

having just completed another install I got the same thing but
the big buttons would not let do much of anything else.
I was thing clicking the scan button would get me access to something
but does not.


did a google search with
"brother4:net1;dev0"

This looks like it might help.

http://neithere.net/2013/02/18/archlinux_brother_7860.html

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 14/12/20 4:30 pm, Bit Twister wrote:

having just completed another install I got the same thing but
the big buttons would not let do much of anything else.
I was thing clicking the scan button would get me access to something
but does not.

did a google search with
"brother4:net1;dev0"

This looks like it might help.

http://neithere.net/2013/02/18/archlinux_brother_7860.html

It does!!

***********
brsaneconfig4 -d

<snip lots of terrifying stuff>

ping
test SCANNER
ping 192.168.1.200 -w 10

PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data.
From 100.66.0.1 icmp_seq=1 Packet filtered

- --- 192.168.1.200 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

*******************

We have an address conflict

the hosts entry for printer

192.168.20.2 prnt.cryptid.test prnt
This responds to ping but the scanner address 192.168.1.200 is clearly different


when I get time to research I must find how to reset the scanner address


We are zeroing in Bits.

regards

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 18 Dec 2020 09:44:56 +1100, faeychild wrote:

On 14/12/20 4:30 pm, Bit Twister wrote:

having just completed another install I got the same thing but
the big buttons would not let do much of anything else.
I was thing clicking the scan button would get me access to something
but does not.


did a google search with
"brother4:net1;dev0"

This looks like it might help.

http://neithere.net/2013/02/18/archlinux_brother_7860.html

It does!!

***********
brsaneconfig4 -d

<snip lots of terrifying stuff>

ping
test SCANNER
ping 192.168.1.200 -w 10

PING 192.168.1.200 (192.168.1.200) 56(84) bytes of data.
From 100.66.0.1 icmp_seq=1 Packet filtered

--- 192.168.1.200 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

*******************

We have an address conflict

the hosts entry for printer

192.168.20.2 prnt.cryptid.test prnt
This responds to ping but the scanner address 192.168.1.200 is clearly different

when I get time to research I must find how to reset the scanner address

Should be easy enough. Sounds like you can have an address for the printer
and another for scanner. If so, add one in /etc/hosts,
then bring up your browser and enter the printer url guessing 192.168.20.3


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 18/12/20 10:05 am, Bit Twister wrote:

Should be easy enough. Sounds like you can have an address for the printer and another for scanner. If so, add one in /etc/hosts,
then bring up your browser and enter the printer url guessing 192.168.20.3

Nope!
One address for all; The scanner software is looking for the old address
for the printer from the old modem.
That has to be corrected.
--


faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 18/12/20 12:10 pm, faeychild wrote:

On 18/12/20 10:05 am, Bit Twister wrote:

Should be easy enough. Sounds like you can have an address for the
printer
and another for scanner. If so, add one in /etc/hosts,
then bring up your browser and enter the printer url guessing
192.168.20.3

Nope!
One address for all; The scanner software is looking for the old address
for the printer  from the old modem.
That has to be corrected.

Firstly check out Bits' link page

http://neithere.net/2013/02/18/archlinux_brother_7860.html

Check with "brsaneconfig4 -d": that it pings the correct address

mine didn't

The config file is "/opt/brother/scanner/brscan4/brsanenetdevice4.cfg"

edit the IP address

regards


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 18 Dec 2020 13:02:08 +1100, faeychild wrote:

I do hope you logged into your printer and changed password.

Upon login, I got a notice about a firmware update.
Took about 10 to 20 minutes, I did not time it.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 18/12/20 1:50 pm, Bit Twister wrote:

On Fri, 18 Dec 2020 13:02:08 +1100, faeychild wrote:

I do hope you logged into your printer and changed password.

Upon login, I got a notice about a firmware update.
Took about 10 to 20 minutes, I did not time it.

The printer has a password??
How do you log into the printer?

How did you initiate an update?

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 18 Dec 2020 14:45:36 +1100, faeychild wrote:

On 18/12/20 1:50 pm, Bit Twister wrote:

On Fri, 18 Dec 2020 13:02:08 +1100, faeychild wrote:

I do hope you logged into your printer and changed password.

Upon login, I got a notice about a firmware update.
Took about 10 to 20 minutes, I did not time it.

The printer has a password??

I am going to assume yours does because mine does.

How do you log into the printer?

Entered the printer ip address in my browser and filled
in the password in the password box. :)

How did you initiate an update?

I think it automagically called home, saw a higher release
and prompted me to install it. If not, just like your router
you need to hunt around in the web page.

I said yes/ok, got nervous after waiting a few minutes,
went off and did something else and when I heard the
online tone I came back and looked around all the
screens like I do for my modem.


How do I log into my Brother printer?

Just like you would for your router.

I am going to guess you are now going to ask me what your
printer's password is. :)

My google search said to get it off the back of the printer.

After disconnecting cables and moving stuff, found out
it is not on the back of mine. More googling suggested
initpass, I just now checked and found other suggestions.

Wish you luck.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

My google search said to get it off the back of the printer.

After disconnecting cables and moving stuff, found out
it is not on the back of mine. More googling suggested
initpass, I just now checked and found other suggestions.

Wish you luck.

Well I'll be stuffed and mounted, Bits.

I have never considered plugging the IP address of the printer into the browser. A whole new world to explore.

Actually the printer interface opened on the General tab
At the top of the page to the right of the model name is an orange box
that says Please configure the password >>

It would seem that mine hasn't been set. I wonder can it perform a
factory reset and password clear.

It has yet to initiate an upgrade



On the back of my printer, from the rear view aspect. In the bottom left corner is a sticker with model and serial and compliance numbers.
No password.
If it is underneath, well.. it will be while before I swing that thing
over my head

regards

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 18 Dec 2020 17:58:53 +1100, faeychild wrote:

My google search said to get it off the back of the printer.

After disconnecting cables and moving stuff, found out
it is not on the back of mine. More googling suggested
initpass, I just now checked and found other suggestions.

Wish you luck.

Well I'll be stuffed and mounted, Bits.

I have never considered plugging the IP address of the printer into the browser. A whole new world to explore.

Actually the printer interface opened on the General tab
At the top of the page to the right of the model name is an orange box
that says Please configure the password >>

It would seem that mine hasn't been set. I wonder can it perform a
factory reset and password clear.

I would bet money that a factory would reset the password back
to the default password. Mine was initpass. Now the we are back
on this subject, going to add that to the file where I stored my
passwords.

It has yet to initiate an upgrade

Then you printer setup is different than mine,
Go ahead and look around to find the firmware check.

On the back of my printer, from the rear view aspect. In the bottom left corner is a sticker with model and serial and compliance numbers.
No password.
If it is underneath, well.. it will be while before I swing that thing
over my head

I hear that. :)

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 18/12/20 6:29 pm, Bit Twister wrote:

On the back of my printer, from the rear view aspect. In the bottom left
corner is a sticker with model and serial and compliance numbers.
No password.
If it is underneath, well.. it will be while before I swing that thing
over my head

I hear that. :)

Further on the printers, Bits
A query on speed/response
The printer responds almost instantly with a text page.

BUT!

This morning, for example, I printed a newsletter comprising 10 A4
pages of text and photographs.

I sent the job at 8:12
The printer started at 8:28
It printed each page separately and finished at 8:41.

I wonder if this is normal or I have a bottleneck somewhere.

regards


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 19 Dec 2020 08:59:28 +1100, faeychild wrote:

Further on the printers, Bits
A query on speed/response
The printer responds almost instantly with a text page.

BUT!

This morning, for example, I printed a newsletter comprising 10 A4
pages of text and photographs.

I sent the job at 8:12
The printer started at 8:28
It printed each page separately and finished at 8:41.

You could have a loss while document is being munged to some
format the printer likes, then next loss is printer changing
to something for printing.

All above is just theory on my part. You could use wireshark
to see transmissions.

I wonder if this is normal or I have a bottleneck somewhere.

Checking ping times between other nodes on Lan against printer
ping is an option.

Want to test your Lan throughput between nodes, use iperf3
Example:

On node 1 iperf3 -s
On node 2 iperf3 -c


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 10:13 am, Bit Twister wrote:

On node 1 iperf3 -s
On node 2 iperf3 -c

iperf3 is not in the repository.
did you install independently.
--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 10:13 am, Bit Twister wrote:

You could have a loss while document is being munged to some
format the printer likes, then next loss is printer changing
to something for printing.

All above is just theory on my part. You could use wireshark
to see transmissions.

Yes! I considered processing munging delays. The onboard ram is 256 Meg.
I assume that your printer doesn't exhibit this delay

I wonder if this is normal or I have a bottleneck somewhere.

Checking ping times between other nodes on Lan against printer
ping is an option.

Want to test your Lan throughput between nodes, use iperf3
Example:

On node 1 iperf3 -s
On node 2 iperf3 -c

ping -c1 nic
PING unimatrix.cryptid.test (192.168.20.4) 56(84) bytes of data.
64 bytes from unimatrix.cryptid.test (192.168.20.4): icmp_seq=1 ttl=64 time=0.043 ms

- --- unimatrix.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.043/0.043/0.043/0.000 ms



ping -c1 prnt
PING prnt.cryptid.test (192.168.20.2) 56(84) bytes of data.
64 bytes from prnt.cryptid.test (192.168.20.2): icmp_seq=1 ttl=255
time=0.420 ms

- --- prnt.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.420/0.420/0.420/0.000 ms



ping -c1 wgtwy (wangateway)
PING wangate.cryptid.test (100.66.0.1) 56(84) bytes of data.
64 bytes from wangate.cryptid.test (100.66.0.1): icmp_seq=1 ttl=254
time=6.48 ms

- --- wangate.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 6.484/6.484/6.484/0.000 ms

ping -c1 gtwy
PING gateway.cryptid.test (192.168.20.1) 56(84) bytes of data.
64 bytes from gateway.cryptid.test (192.168.20.1): icmp_seq=1 ttl=64 time=0.581 ms


- --- gateway.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.581/0.581/0.581/0.000 ms


I think an education in how to Wireshark may be imminent.


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 18 Dec 2020 18:36:48 -0500, faeychild <faeychild@nomail.afraid.org> wrote:

On 19/12/20 10:13 am, Bit Twister wrote:

On node 1 iperf3 -s
On node 2 iperf3 -c

iperf3 is not in the repository.
did you install independently.

$ urpmf bin/iperf3
iperf:/usr/bin/iperf3

The command is iperf3. The package is iperf.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2020-12-19, faeychild <faeychild@nomail.afraid.org> wrote:

On 19/12/20 10:13 am, Bit Twister wrote:

You could have a loss while document is being munged to some
format the printer likes, then next loss is printer changing
to something for printing.

All above is just theory on my part. You could use wireshark
to see transmissions.

Yes! I considered processing munging delays. The onboard ram is 256 Meg.
I assume that your printer doesn't exhibit this delay

It might be a printer problem. I have an HP M402 and some stuff sent to
it just take a horribly long time coming out ( or never do) I think it
is a problem with the pdf interpreter on the printer messing things up. Sometimes I have viewed it with okular (no problem) saved it as a pdf
and that pdf has no trouble being printed. (And at times the is smaller
buy a factor of 10).

I wonder if this is normal or I have a bottleneck somewhere.

Checking ping times between other nodes on Lan against printer
ping is an option.

Want to test your Lan throughput between nodes, use iperf3
Example:

On node 1 iperf3 -s
On node 2 iperf3 -c

ping -c1 nic
PING unimatrix.cryptid.test (192.168.20.4) 56(84) bytes of data.
64 bytes from unimatrix.cryptid.test (192.168.20.4): icmp_seq=1 ttl=64 time=0.043 ms

--- unimatrix.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.043/0.043/0.043/0.000 ms

ping -c1 prnt
PING prnt.cryptid.test (192.168.20.2) 56(84) bytes of data.
64 bytes from prnt.cryptid.test (192.168.20.2): icmp_seq=1 ttl=255 time=0.420 ms

--- prnt.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.420/0.420/0.420/0.000 ms

ping -c1 wgtwy (wangateway)
PING wangate.cryptid.test (100.66.0.1) 56(84) bytes of data.
64 bytes from wangate.cryptid.test (100.66.0.1): icmp_seq=1 ttl=254 time=6.48 ms

--- wangate.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 6.484/6.484/6.484/0.000 ms

ping -c1 gtwy
PING gateway.cryptid.test (192.168.20.1) 56(84) bytes of data.
64 bytes from gateway.cryptid.test (192.168.20.1): icmp_seq=1 ttl=64 time=0.581 ms

--- gateway.cryptid.test ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.581/0.581/0.581/0.000 ms

I think an education in how to Wireshark may be imminent.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 12:53 pm, David W. Hodgins wrote:

The command is iperf3. The package is iperf.

Regards, Dave Hodgins

why didn't I think of that. So thick sometimes

Thanks Dave

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 19 Dec 2020 12:56:22 +1100, faeychild wrote:

unimatrix 0.043/0.043/0.043/0.000 ms
prnt 0.420/0.420/0.420/0.000 ms
gateway 0.581/0.581/0.581/0.000 ms

I have a gigabit LAN network
wb. 0.065/0.065/0.065/0.000 ms
mtv 0.256/0.256/0.256/0.000 ms
tb 0.159/0.159/0.159/0.000 ms
ptr 0.390/0.390/0.390/0.000 ms
webcam2 0.349/0.349/0.349/0.000 ms
and your/my printer time looking about the same.
My webcam2 is a 100mb connection.

Take a look at your nic stats.
ifconfig $_net_nic | grep error
RX errors 0 dropped 0 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I was wondering why iperf3 was showing something like a third less
than my wb and mtv nodes. Ran ifconfig and and I had anywhere from
1 to 3 errors.

Thought that can not be a problem. Swapped nic and no real change
on throughput. I decided to change ethernet cable and throughput
jumped up about a third.

Made a note to self, quit buying the cheap cables.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 2:46 pm, William Unruh wrote:

It might be a printer problem. I have an HP M402 and some stuff sent to
it just take a horribly long time coming out ( or never do) I think it
is a problem with the pdf interpreter on the printer messing things up. Sometimes I have viewed it with okular (no problem) saved it as a pdf
and that pdf has no trouble being printed. (And at times the is smaller
buy a factor of 10).

In this case the "some stuff" is images. A page of text starts up in
seconds but a photograph seems to stick in the printers craw


I have to laugh at the claimed 22ppm. Maybe multiple copies of the same
scan. But certainly no remote print job is going to achieve 22ppm.

Thanks William.


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2020-12-19, faeychild <faeychild@nomail.afraid.org> wrote:

On 19/12/20 2:46 pm, William Unruh wrote:

It might be a printer problem. I have an HP M402 and some stuff sent to
it just take a horribly long time coming out ( or never do) I think it
is a problem with the pdf interpreter on the printer messing things up.
Sometimes I have viewed it with okular (no problem) saved it as a pdf
and that pdf has no trouble being printed. (And at times the is smaller
buy a factor of 10).

In this case the "some stuff" is images. A page of text starts up in
seconds but a photograph seems to stick in the printers craw

I have to laugh at the claimed 22ppm. Maybe multiple copies of the same scan. But certainly no remote print job is going to achieve 22ppm.

Thanks William.

You could enable the error log in cups for this printer
(/etc/cups/cups-files) with the line, say
ErrorLog /var/log/cups/error_log

AND in /etc/cups/cupsd.conf
LogLevel debug

Then after your print job has printed do

grep 'Job\[' /var/log/cups/error.log

Now look to see when the printer finished sending the file to the
printer, and compare to when the job actually came out of the printer.
That should tell you whether the problem in inside your computer, or in
the printer.



--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 3:39 pm, William Unruh wrote:

You could enable the error log in cups for this printer (/etc/cups/cups-files) with the line, say
ErrorLog /var/log/cups/error_log

AND in /etc/cups/cupsd.conf
LogLevel debug

Ah Brilliant stuff. I just won't live long enough to discover all of
these tricks
I don't have "cups-files" I do have "cups-files.conf" guessing a typo??

Then after your print job has printed do

grep 'Job\[' /var/log/cups/error.log

Now look to see when the printer finished sending the file to the
printer, and compare to when the job actually came out of the printer.
That should tell you whether the problem in inside your computer, or in
the printer.

Gotcha. Too late now to start this investigation. More tomorrow

Regards

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/12/20 2:55 pm, Bit Twister wrote:

On Sat, 19 Dec 2020 12:56:22 +1100, faeychild wrote:

unimatrix 0.043/0.043/0.043/0.000 ms
prnt 0.420/0.420/0.420/0.000 ms
gateway 0.581/0.581/0.581/0.000 ms

I have a gigabit LAN network
wb. 0.065/0.065/0.065/0.000 ms
mtv 0.256/0.256/0.256/0.000 ms
tb 0.159/0.159/0.159/0.000 ms
ptr 0.390/0.390/0.390/0.000 ms
webcam2 0.349/0.349/0.349/0.000 ms
and your/my printer time looking about the same.
My webcam2 is a 100mb connection.

It's a gigabit LAN here too.

Take a look at your nic stats.
ifconfig $_net_nic | grep error
RX errors 0 dropped 0 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Assuming it's to be observed during the print run.
Do you use "watch" to update it

"ifconfig" is not found. AAAHHH I always get caught

Is there a reason NOT to add "/usr/sbin/" to user path?

Just in the normal run of things I have some drops

~]$ /usr/sbin/ifconfig $_net_nic | grep error
RX errors 0 dropped 1454 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Thought that can not be a problem. Swapped nic and no real change
on throughput. I decided to change ethernet cable and throughput
jumped up about a third.

Lucky you have a NIC on card

Made a note to self, quit buying the cheap cables.

It's the last thing I'd think of. If it has continuity-it's fine.

but not always so!

Did you solve your zoom video problem?

regards

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2020-12-19, faeychild <faeychild@nomail.afraid.org> wrote:

On 19/12/20 3:39 pm, William Unruh wrote:

You could enable the error log in cups for this printer
(/etc/cups/cups-files) with the line, say
ErrorLog /var/log/cups/error_log

AND in /etc/cups/cupsd.conf
LogLevel debug

Ah Brilliant stuff. I just won't live long enough to discover all of
these tricks
I don't have "cups-files" I do have "cups-files.conf" guessing a typo??

Yes, sorry.

Then after your print job has printed do

grep 'Job\[' /var/log/cups/error.log

Now look to see when the printer finished sending the file to the
printer, and compare to when the job actually came out of the printer.
That should tell you whether the problem in inside your computer, or in
the printer.

Gotcha. Too late now to start this investigation. More tomorrow

Regards

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Op Sat, 19 Dec 2020 12:56:22 +1100, schreef faeychild:

On 19/12/20 10:13 am, Bit Twister wrote:

You could have a loss while document is being munged to some format the
printer likes, then next loss is printer changing to something for
printing.

All above is just theory on my part. You could use wireshark to see
transmissions.

Yes! I considered processing munging delays. The onboard ram is 256
Meg.
I assume that your printer doesn't exhibit this delay

Sorry to jump in the middle of this discussion, but "onboard ram is 256
Meg" What is that, ram in the PC or in the printer/scanner???
I had some experience in using an old laptop with 256Mb RAM, and I
wouldn't even try to do anything graphical (unless very simple) on this laptop, since it spent more time swapping in and out than it did anything useful.

Herman Viaene





--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 19/12/20 8:45 pm, Herman Viaene wrote:

Sorry to jump in the middle of this discussion, but "onboard ram is 256
Meg" What is that, ram in the PC or in the printer/scanner???
I had some experience in using an old laptop with 256Mb RAM, and I
wouldn't even try to do anything graphical (unless very simple) on this laptop, since it spent more time swapping in and out than it did anything useful.

Herman Viaene

That is printer/scanner RAM, Herman.

Doesn't sound much for a printer considering that it would be used as
print buffer, as FAX RAM and telephone address book RAM, etc

regards



--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 19 Dec 2020 20:10:41 +1100, faeychild wrote:

On 19/12/20 2:55 pm, Bit Twister wrote:

Take a look at your nic stats.
ifconfig $_net_nic | grep error
RX errors 0 dropped 0 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Assuming it's to be observed during the print run.
Do you use "watch" to update it

Nope. Only way I have found to clear them is to reboot.

"ifconfig" is not found. AAAHHH I always get caught

Sorry, I forgot to add it to the post. I always /sbin and /usr/sbin
in my $PATH.

Is there a reason NOT to add "/usr/sbin/" to user path?

As far as I am concerned it is not. In my opinion any /sbin app
better not be harmful if executed by a normal user.

It is up to you if you want to add them before or after regular bin.
If after, any app in before will be the one selected.

Just in the normal run of things I have some drops

~]$ /usr/sbin/ifconfig $_net_nic | grep error
RX errors 0 dropped 1454 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Hmmm, hmmm. I would assume that many drops are not good.
Especially if system was booted recently. Take a look at my MythTV node
in relation to number of packets.

$ ifconfig $_net_nic
RX packets 7911548 bytes 3114309917 (2.9 GiB)
RX errors 0 dropped 40 overruns 0 frame 0

TX packets 15553399 bytes 20910652050 (19.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

$ ifconfig $_tuner_nic
RX packets 1933992600 bytes 2620694825413 (2.3 TiB)
RX errors 0 dropped 0 overruns 0 frame 0

TX packets 48789651 bytes 5091576107 (4.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Did you solve your zoom video problem?

Hehe, just as I was typing this reply indicating I was about to give
up hope of receiving it after waiting two weeks, I heard the mailbox
lid slam, and there is my webcam. Just not the one I thought I had
ordered. It is a usb not a network ip cam.

Probably will get to it sometime today. Gota go and finish digging
out my main water supply break in yard sprinkler system.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 20/12/20 6:09 am, Bit Twister wrote:

"ifconfig" is not found. AAAHHH I always get caught

Sorry, I forgot to add it to the post. I always /sbin and /usr/sbin
in my $PATH.

Is there a reason NOT to add "/usr/sbin/" to user path?

As far as I am concerned it is not. In my opinion any /sbin app
better not be harmful if executed by a normal user.

It is up to you if you want to add them before or after regular bin.
If after, any app in before will be the one selected.

I've added permanantly - and I'll be damned.

Just in the normal run of things I have some drops

~]$ /usr/sbin/ifconfig $_net_nic | grep error
RX errors 0 dropped 1454 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Hmmm, hmmm. I would assume that many drops are not good.
Especially if system was booted recently. Take a look at my MythTV node
in relation to number of packets.

Googled this last night

Re; ifconfig

That information is poorly documented. I will tell you what I understand
from my experience.

frame counts only misaligned frames, it means frames with a length
not divisible by 8. Because of that length is not a valid frame and it
is simply discarded.

Meanwhile errors counts CRC errors, too-short frames and too-long
frames.

overruns counts that times when there is FIFO overruns, caused by
the rate at which the buffer gets full and the kernel isn't able to
empty it.

At last, dropped counts things like unintended VLAN tags or
receiving IPv6 frames when the interface is not configured for IPv6.


Hmmmm!

Did you solve your zoom video problem?

Hehe, just as I was typing this reply indicating I was about to give
up hope of receiving it after waiting two weeks, I heard the mailbox
lid slam, and there is my webcam. Just not the one I thought I had
ordered. It is a usb not a network ip cam.

Probably will get to it sometime today. Gota go and finish digging
out my main water supply break in yard sprinkler system.

Good day for digging. If any digging is good. Digging can discover
muscles you didn't know you had. You'll locate them the next day.

Good honest work (father type advice) :-)

I'm tied up with video edit/transcoding this morning

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 20 Dec 2020 07:22:16 +1100, faeychild wrote:

On 20/12/20 6:09 am, Bit Twister wrote:

st in the normal run of things I have some drops

~]$ /usr/sbin/ifconfig $_net_nic | grep error
RX errors 0 dropped 1454 overruns 0 frame 0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Hmmm, hmmm. I would assume that many drops are not good.
Especially if system was booted recently. Take a look at my MythTV node
in relation to number of packets.

Googled this last night

Re; ifconfig

That information is poorly documented. I will tell you what I understand
from my experience.

frame counts only misaligned frames, it means frames with a length
not divisible by 8. Because of that length is not a valid frame and it
is simply discarded.

Meanwhile errors counts CRC errors, too-short frames and too-long frames.

overruns counts that times when there is FIFO overruns, caused by
the rate at which the buffer gets full and the kernel isn't able to
empty it.

At last, dropped counts things like unintended VLAN tags or
receiving IPv6 frames when the interface is not configured for IPv6.

Hmmmm!

Well now, thank you for your information. I wondered this past month
why I am getting little batches of drops. I had assumed it was from the
malware installed from some A$$hold who cracked my security cams.

But drop pattern is not matching malware scan activities.

My ISP has assigned me a IPV4 connection, so I have ipv6 disabled.
If you have not disabled it on your system, that could be reason
for your drops.

The best one stop location to disable ipv6 I have found, is a kernel
command line option.
For that I added it to my custom options in default grub

$ grep ipv6 /etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1 numerous_other_ops_snipped"

Anytime /etc/default/grub is changed, run update-grub which updates /boot/grub2/grub.cfg

Next boot will pickup the change(s).

Probably will get to it sometime today. Gota go and finish digging
out my main water supply break in yard sprinkler system.

Good day for digging. If any digging is good. Digging can discover
muscles you didn't know you had. You'll locate them the next day.

I am in the black clay area. Ground had not dried out enough to use a
shovel to remove the dirt. Damp clay sticks to tools.

Faster to use shovel to break it up and use a garden trowel to get the
dirt out. Using a long kitchen knife to clean trowel.
I am sitting cross legged bent over to get to bottom of hole. :(

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 20/12/20 8:47 am, Bit Twister wrote:

The best one stop location to disable ipv6 I have found, is a kernel
command line option.
For that I added it to my custom options in default grub

$ grep ipv6 /etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1 numerous_other_ops_snipped"

Anytime /etc/default/grub is changed, run update-grub which updates /boot/grub2/grub.cfg

Next boot will pickup the change(s).

Network Center > Advanced Setting > TCPIP > Disable IPv6. - is
unchecked so, theoretically, I should have IPv6, But my RSP is still
dinking with a beta setup.


https://test-ipv6.com/

Probably will get to it sometime today. Gota go and finish digging
out my main water supply break in yard sprinkler system.

I have rock hard clay about a foot down so I feel your pain

I am sitting cross legged bent over to get to bottom of hole. :(

A bad position for the back. OK for the knees!

I must go through the commands you posted further back to check network connection/bandwidth to the printer and make a new brain page.

regards

--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 20 Dec 2020 12:53:14 +1100, faeychild wrote:

On 20/12/20 8:47 am, Bit Twister wrote:

The best one stop location to disable ipv6 I have found, is a kernel
command line option.
For that I added it to my custom options in default grub

$ grep ipv6 /etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1 numerous_other_ops_snipped"

Anytime /etc/default/grub is changed, run update-grub which updates
/boot/grub2/grub.cfg

Next boot will pickup the change(s).

Network Center > Advanced Setting > TCPIP > Disable IPv6. - is
unchecked so, theoretically, I should have IPv6, But my RSP is still
dinking with a beta setup.

https://test-ipv6.com/

Yeah, but your method means you have to remember to make the change on
new installs. My grub_changes script makes my change for me. :)

I must go through the commands you posted further back to check network connection/bandwidth to the printer

Unless you can get to a command line prompt, you can not run iperf3 -c
from your printer.

and make a new brain page.

Heheh, I went to research your firmware update question and found out
I did not put my printer pw in my brain book.

Had to hunt around in the panel screen to find the factory reset.

Your Firmware Update should be under Administration Tab.


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 20/12/20 2:30 pm, Bit Twister wrote:

Next boot will pickup the change(s).

Network Center > Advanced Setting > TCPIP > Disable IPv6. - is
unchecked so, theoretically, I should have IPv6, But my RSP is still
dinking with a beta setup.


https://test-ipv6.com/

Yeah, but your method means you have to remember to make the change on
new installs. My grub_changes script makes my change for me. :)

Yes I try to make my new installs few and far between

I must go through the commands you posted further back to check network
connection/bandwidth to the printer

Unless you can get to a command line prompt, you can not run iperf3 -c
from your printer.

FROM the printer!! How do I run a command from the printer?

BTW running iperf3 -c prints the help options

So I tried the printer address

~]$ iperf3 -c 192.168.20.2
iperf3: error - unable to connect to server: Connection refused


yes well

More mysteries. Time to Google!

and make a new brain page.

Heheh, I went to research your firmware update question and found out
I did not put my printer pw in my brain book.

Had to hunt around in the panel screen to find the factory reset.

Your Firmware Update should be under Administration Tab.

My Administration Tab Currently has enter /confirm password fields only. Doing so may open up further stuff



--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 21/12/20 8:01 am, faeychild wrote:

Yeah, but your method means you have to remember to make the change on
new installs. My grub_changes script makes my change for me.  :)

Although the network centre says IPv6 is not disabled, the grub stanza
says it is

~]$ grep ipv6 /etc/default/grub
GRUB_CMDLINE_LINUX=ipv6.disable=1



--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Mon, 21 Dec 2020 08:01:35 +1100, faeychild wrote:

On 20/12/20 2:30 pm, Bit Twister wrote:

Unless you can get to a command line prompt, you can not run iperf3 -c
from your printer.

FROM the printer!! How do I run a command from the printer?

You can't. that is what I was pointing out.

BTW running iperf3 -c prints the help options

Yup, I left target argument off for the discussion.

So I tried the printer address

~]$ iperf3 -c 192.168.20.2
iperf3: error - unable to connect to server: Connection refused
yes well More mysteries. Time to Google!

iperf3 101 class.

You have to start an iperf3 server session on one node,
(iperf3 -s) then get on another node and do a connection
iperf3 -c node_where_U_ran_iperf3_-s

Your Firmware Update should be under Administration Tab.

My Administration Tab Currently has enter /confirm password fields only.

Then leave that page, you are done with changing password,
and look at tabs at top of page and/or left side of page.

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sun, 20 Dec 2020 12:53:14 +1100, faeychild wrote:

On 20/12/20 8:47 am, Bit Twister wrote:

I am sitting cross legged bent over to get to bottom of hole. :(

A bad position for the back. OK for the knees!

Sorry, I must interfere here...did not spend 30 in India for nothing...
when sitting crossed legs, position is bad for the knees if
the knees are raised at an angle.
To remedy sit on a brick or something so that knee and tigh are on an orizontal line then the position ( swastika asana ) is good both for legs and back

....sorry got to be helpful in some ways on this newsgoup
:-)

--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 22/12/20 1:57 am, santo wrote:

On Sun, 20 Dec 2020 12:53:14 +1100, faeychild wrote:

On 20/12/20 8:47 am, Bit Twister wrote:

I am sitting cross legged bent over to get to bottom of hole. :(

A bad position for the back. OK for the knees!

Sorry, I must interfere here...did not spend 30 in India for nothing...
when sitting crossed legs, position is bad for the knees if
the knees are raised at an angle.
To remedy sit on a brick or something so that knee and tigh are on an orizontal line then the position ( swastika asana ) is good both for legs

and back

The intent was to suggest that as one gets older the knees don't
tolerate crawling or kneeling all that well. Sitting cross legged is not
all that comfortable either but I can do that longer than I can kneel.

As for bending forward from that position and digging a hole - not
super comfortable either.


I should ditch the "scanner fails" subject line because the scanner is actually fixed. Time to start a new post

regards


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 21/12/20 3:10 pm, Bit Twister wrote:

Your Firmware Update should be under Administration Tab.

My Administration Tab Currently has enter /confirm password fields only.

Then leave that page, you are done with changing password,
and look at tabs at top of page and/or left side of page.

The closest I get to firmware is General Tab > Maintenance Information

Node Information

Model Name
Brother MFC-9340CDW
Serial no.
E71880L4J552158
Main Firmware Version
N
Sub1 Firmware Version
1.05
Sub2 Firmware Version
J1407100900
Memory Size
256MB


No option to upgrade is provided

Also searching for firmware + linux + brother
pull up the Brother page which mentions Linux firmware but the download
link connect to Windows Mac downloads only.

The upgrades are installed with a firmware upgrade tool, only for Win
and Mac
--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 22 Dec 2020 12:28:48 +1100, faeychild wrote:

On 21/12/20 3:10 pm, Bit Twister wrote:

Your Firmware Update should be under Administration Tab.

The closest I get to firmware is General Tab > Maintenance Information
No option to upgrade is provided

OK. In my printer,
firefox xxxx.xxx.xxx
I have a password box and a General Tab and left side has Maintenance Info
entered passwd and now have 5 tabs

General Copy Print Administrator Network
Clicked Administrator
then Firmware Update
Model Name HL-L2380DW series
Serial Number U63886G4N232108
Firmware Version
MAIN R2007211214
SUB1 1.00
SUB2 A1404230900
.------------------------.
Firmware Update | Check for new firmware |
`------------------------'
Proxy




--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 22/12/20 3:41 pm, Bit Twister wrote:

On Tue, 22 Dec 2020 12:28:48 +1100, faeychild wrote:

On 21/12/20 3:10 pm, Bit Twister wrote:

Your Firmware Update should be under Administration Tab.

The closest I get to firmware is General Tab > Maintenance Information
No option to upgrade is provided

OK. In my printer,
firefox xxxx.xxx.xxx
I have a password box and a General Tab and left side has Maintenance Info
entered passwd and now have 5 tabs

I have a General Tab A login field and an arrow in a blue box And Maintenance Info down the side.

Login gives me Tabs
General Address Book Fax Copy Print Scan Administrator Network

General Copy Print Administrator Network
Clicked Administrator
then Firmware Update
Model Name HL-L2380DW series
Serial Number U63886G4N232108
Firmware Version
MAIN R2007211214
SUB1 1.00
SUB2 A1404230900
.------------------------.
Firmware Update | Check for new firmware |
`------------------------'
Proxy

Clicked Administrator

Just password fields New Confirm

Click General Tab
Maintenance Information

Node Information

Model Name
Brother MFC-9340CDW
Serial no.
E71880L4J552158
Main Firmware Version
N
Sub1 Firmware Version
1.05
Sub2 Firmware Version
J1407100900
Memory Size
256MB

And bucket loads of stuff about pages toner drums image count remaining
life ,etc

No firmware update

Different printer. Totally different interface

Cest la Vi

Brother Page offers a Firmware update tool but only for Windows and Mac.

Tough Eh!

I could break out the old linux box with Win 10 installed and update
that way
I could also check network bandwidth with Iperf -- one day :-)

regards


--
faeychild
Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)