• updates today and no desktop effects

    From faeychild@2:250/1 to All on Tue Nov 5 08:43:51 2019


    Is it just me again??

    Since I disabled the update applet I manually allowed an update today
    and it came with a new kernel

    uname -a
    Linux unimatrix 5.3.7-desktop-4.mga7 #1 SMP Thu Oct 24 20:11:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

    I checked during grub boot and found a bunch of redundant kernels which
    I removed with MCC,
    Only to find the listing still in grub boot. Running "update-grub2"
    removed them _ should not MCC software run "update-grub2" after an
    install??


    Further

    All the desktop effects a gone I still have 4 virtual desktops but no
    grid, no edge switching. transparency is gone

    And when I switch to the desktop running 4 vlc streaming TV channels the
    CPU usage runs up

    Window movements seem a little jerky.

    I am running the Nvidia propriety driver NVIDIA Driver Version:430.50

    GeForce GTX 1050 Ti

    I have switched back to Linux unimatrix 5.3.6-desktop-2.mga7 #1 SMP
    Sun Oct 13 18:22:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


    The problem is still the same - it's a bit like no acceleration

    It's not looking good

    Previous to the update I was dinking around with the ethernet
    configuration and the router, which I obviously recovered from to
    enable the update to proceed
    I can't imagine a connection there that could have clobbered the desktop effects, but I can't see that an update would have either.


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Nov 5 09:17:07 2019
    On 5/11/19 7:43 pm, faeychild wrote:


    Is it just me again??



    I should also have had the presence of mind to boot Mga6 and check
    that it wasn't hardware related.
    I can't do anything now, I am recording TV.

    I am running the previous kernel and still without desktop effects
    Linux unimatrix 5.3.6-desktop-2.mga7

    A load of stuff came through; it may be something other than kernel or
    driver.

    572939102 (Tue 05 Nov 2019 18:31:42 AEDT) kernel-desktop-devel-latest 1572939102 (Tue 05 Nov 2019 18:31:42 AEDT) lib64cdt5
    1572939102 (Tue 05 Nov 2019 18:31:42 AEDT) lib64cgraph6
    1572939102 (Tue 05 Nov 2019 18:31:42 AEDT) lib64glapi0
    1572939104 (Tue 05 Nov 2019 18:31:44 AEDT) kernel-desktop-devel-5.3.7-4.mga7 1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) cpupower
    1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) kernel-desktop-latest
    1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) lib64magic1
    1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) lib64pathplan4
    1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) lib64soup2.4_1
    1572939105 (Tue 05 Nov 2019 18:31:45 AEDT) libsoup-i18n
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) kernel-desktop-5.3.7-4.mga7 1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64drm2
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64drm_amdgpu1
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64drm_intel1
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64drm_nouveau2
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64drm_radeon1
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) lib64gbm1
    1572939107 (Tue 05 Nov 2019 18:31:47 AEDT) libdrm-common
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) file
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) kaccounts-integration
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) kernel-userspace-headers
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64dri-drivers
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64gvc6
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64kaccounts1
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64mesaegl1
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64mesagl1
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64soup-gir2.4
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) lib64xatracker2
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) mesa
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-driver-video-amdgpu
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-driver-video-ati
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-driver-video-intel
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-server-common
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-server-xorg
    1572939109 (Tue 05 Nov 2019 18:31:49 AEDT) x11-server-xwayland
    1572939110 (Tue 05 Nov 2019 18:31:50 AEDT) audacity
    1572939110 (Tue 05 Nov 2019 18:31:50 AEDT) lib64aspell15
    1572939110 (Tue 05 Nov 2019 18:31:50 AEDT) lib64pcre2_0
    1572939110 (Tue 05 Nov 2019 18:31:50 AEDT) lib64xslt1
    1572939110 (Tue 05 Nov 2019 18:31:50 AEDT) python3-urllib3



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 5 09:29:46 2019
    On Tue, 5 Nov 2019 19:43:51 +1100, faeychild wrote:


    Is it just me again??

    Let's see. log out and into junk. Do remember to change Desktop Environment
    to plasma and see what you can see.


    Since I disabled the update applet I manually allowed an update today
    and it came with a new kernel

    uname -a
    Linux unimatrix 5.3.7-desktop-4.mga7 #1 SMP Thu Oct 24 20:11:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

    Yup, working just fine after installing that a few days ago.



    I checked during grub boot and found a bunch of redundant kernels which
    I removed with MCC,
    Only to find the listing still in grub boot. Running "update-grub2"
    removed them _ should not MCC software run "update-grub2" after an
    install??

    I thought it did, since I seem to recall some grub messages. Then again
    I always remove the previous kernel if the new kernel boots.


    Further

    All the desktop effects a gone I still have 4 virtual desktops but no
    grid, no edge switching. transparency is gone

    I can't imagine a connection there that could have clobbered the desktop effects, but I can't see that an update would have either.

    If you only did a kernel update, then my guess would be re-compile of
    video driver as common point of contention. Switching video driver to
    xorg/vesa would tend to see if problem clears up somewhat.
    If so, I would get back into mcc to reset driver back to whatever
    video driver can be set for your card.

    Then again, I only have xfce installed, so there is nothing else for
    me to point at and my video hardware is
    wb: Seymour [Radeon HD 6400M Series]
    mtv: Cedar [Radeon HD 5450 Series]
    tb: NVIDIA Corporation Device 128b [GeForce GT 710] (rev a1) GeForce 420 series and later




    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 5 10:49:53 2019
    On Tue, 5 Nov 2019 20:17:07 +1100, faeychild wrote:
    On 5/11/19 7:43 pm, faeychild wrote:


    Is it just me again??



    I should also have had the presence of mind to boot Mga6 and check
    that it wasn't hardware related.

    Hindsight is 20/20. but if everything was working, before update,
    hardware failure would be my last guess.

    I can't do anything now, I am recording TV.

    I am running the previous kernel and still without desktop effects
    Linux unimatrix 5.3.6-desktop-2.mga7

    A load of stuff came through; it may be something other than kernel or driver.

    Yeah, that is a bit more than just a kernel install.

    Beside normal kernel update files, drm is digital rights management
    stuff for playing downloaded movies/video.

    mesa and the x11 video driver are definite candidates for possible video problems.

    Anytime I see new kernel, x11*, mesa. I definitely do a system/install
    backup prior to doing the updates.

    Oh yeah, as to my earlier reply of testing/fault isolation of Desktop Environment problems, it would be best to always reset the junk account
    to a day one setting. I can recommend having a script to do the work.
    Here is a quick untested script as a guide.
    - ---8<---8<---8<---8<-- cut below this line -8<---8<---8<---8<---8<---8< #!/bin/bash #*******************************************************************
    #* reset_junk - Reset junk account to day one setup for testing.
    #*
    #* Install procedure
    #* Save as reset_junk
    #* chmod +x reset_junk
    #*
    #* copy or link to a directory found in root's PATH
    #*
    #*******************************************************************

    export PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin

    _app=${0##*/}
    _exe=$0
    _gid=""
    _home_dir=""
    _line=""
    _uid=""
    _user=junk

    if [ $(id --user --name ) != "root" ] ; then
    echo "You must be root to run $_app"
    exit 1
    fi

    _home_dir=$(grep ^${_user}: /etc/passwd | awk -F':' '{print $6}')

    if [ -z "$_home_dir" ] ; then
    echo "
    Fatal error 1 from $_exe:
    no home directory entry in /etc/passwd for $_user
    "
    exit 1
    fi

    _line=$(grep ^${_user}: /etc/passwd | tr ':' ' ')
    set -- $(echo $_line)
    _uid=$3
    _gid=$4

    cd $_home_dir
    if [ $? -ne 0 ] ; then
    echo "
    Fatal error 2 from $_exe:
    Unable to
    cd $_home_dir
    "
    exit 1
    fi

    rsync -aAHSXxv --delete /etc/skel/ $PWD
    chown -R $_uid:$_gid $_home_dir

    #****************** end reset_junk *********************************

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Nov 5 11:53:00 2019
    On 5/11/19 9:49 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 20:17:07 +1100, faeychild wrote:
    On 5/11/19 7:43 pm, faeychild wrote:


    Is it just me again??



    I should also have had the presence of mind to boot Mga6 and check
    that it wasn't hardware related.

    Now is the time to tell me that I would have done myself a favour if I
    had experimented with rsync and backing up Mga7 BEFORE the update

    Hindsight is 20/20.

    Isn't it just

    but if everything was working, before update,
    hardware failure would be my last guess.

    These days, Bits I'm becoming very skeptical

    If it looks like a duck, walks like a duck and quacks like a duck...

    Ummm Get a second opinion from a duck expert. You never know :-)



    I can't do anything now, I am recording TV.

    I am running the previous kernel and still without desktop effects
    Linux unimatrix 5.3.6-desktop-2.mga7

    A load of stuff came through; it may be something other than kernel or
    driver.

    Yeah, that is a bit more than just a kernel install.

    Beside normal kernel update files, drm is digital rights management
    stuff for playing downloaded movies/video.

    mesa and the x11 video driver are definite candidates for possible video
    problems.


    I checked MCC and vesa is an option.. More fun tomorrow.

    Anytime I see new kernel, x11*, mesa. I definitely do a system/install
    backup prior to doing the updates.

    What was that you said about 20/20



    Oh yeah, as to my earlier reply of testing/fault isolation of Desktop Environment problems, it would be best to always reset the junk account
    to a day one setting. I can recommend having a script to do the work.
    Here is a quick untested script as a guide.


    I will plod through it and gain some insight.

    Junk is already a plasma installation and I found a window in my
    recording schedule to quickly test Mga6

    The desktop effects work fine on Mga6.
    So that pretty much accuses one or more of the upgrade files on Mga7.

    Baffling stuff
    I have a regular gigabyte mother board, a regular Nvidia graphic card
    the only wild card for me is the SSD.

    So why am I unique here? my hardware is not esoteric

    Time is 22:45 here and not the time to mess about.. I've learned that
    much :-(


    Regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 5 12:36:35 2019
    On Tue, 5 Nov 2019 22:53:00 +1100, faeychild wrote:
    On 5/11/19 9:49 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 20:17:07 +1100, faeychild wrote:
    On 5/11/19 7:43 pm, faeychild wrote:


    Is it just me again??



    I should also have had the presence of mind to boot Mga6 and check
    that it wasn't hardware related.

    Now is the time to tell me that I would have done myself a favour if I
    had experimented with rsync and backing up Mga7 BEFORE the update

    Hehehe, to tell the truth, I had to bite my tongue when I made the
    reply to your post, although I do admit I did have a big grin on my
    face at the time I was typing.

    I checked MCC and vesa is an option.. More fun tomorrow.

    Anytime I see new kernel, x11*, mesa. I definitely do a system/install
    backup prior to doing the updates.

    What was that you said about 20/20

    Yeah, playing in cauldron to verify my install/change scripts work,
    and managing to clobber it numerous times, my hindsight gets sharper
    all the tine. :(

    That is why I also have a cauldron_bkup partition besides the "Production" hotbu partition.




    Junk is already a plasma installation and I found a window in my
    recording schedule to quickly test Mga6

    Yes, but in your last soap opera I thought you had used it for
    xfce testing to rule out plasma restarting your nic when down.

    Still kinda hoping that is caused via Dhcp*/dynamic ip addressing.

    The desktop effects work fine on Mga6.
    So that pretty much accuses one or more of the upgrade files on Mga7.

    Baffling stuff
    I have a regular gigabyte mother board, a regular Nvidia graphic card
    the only wild card for me is the SSD.

    Yup, I would guess the SSD should only bring timing problems to light
    when new. As they wear out, I would expect weird problems.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Nov 5 22:08:08 2019
    On 5/11/19 11:36 pm, Bit Twister wrote:


    I should also have had the presence of mind to boot Mga6 and check >>>> that it wasn't hardware related.

    This morning I tried Mga6 again and the desktop effects work fine. its
    only Mga7 since the update



    Now is the time to tell me that I would have done myself a favour if I
    had experimented with rsync and backing up Mga7 BEFORE the update

    Hehehe, to tell the truth, I had to bite my tongue when I made the
    reply to your post, although I do admit I did have a big grin on my
    face at the time I was typing.


    Yes! I could see it :-) You did tell me so!



    I checked MCC and vesa is an option.. More fun tomorrow.

    I tried vesa driver this morning and lost "X" completely. I got many complaints about conflicting modules.

    Crash and burn :-(

    I was driven to consider a reinstall -Ahhggg!!!

    Fortunately Mga7 is accessible from Mga6 and I saved the ~/HOME hidden
    files knowing this would speed recovery

    But then I noticed the option to update with the install media and it
    worked !!!!

    Reinstalled the nvidia driver and we are back

    So were are still in the race.


    Anytime I see new kernel, x11*, mesa. I definitely do a system/install
    backup prior to doing the updates.

    What was that you said about 20/20

    Yeah, playing in cauldron to verify my install/change scripts work,
    and managing to clobber it numerous times, my hindsight gets sharper
    all the tine. :(

    That is why I also have a cauldron_bkup partition besides the "Production" hotbu partition.




    Junk is already a plasma installation and I found a window in my
    recording schedule to quickly test Mga6

    Yes, but in your last soap opera I thought you had used it for
    xfce testing to rule out plasma restarting your nic when down.

    I didn't get to that process.
    Not entirely sure how to switch DE anyway


    Still kinda hoping that is caused via Dhcp*/dynamic ip addressing.

    I did consider the two files in /etc/ifplugd

    #### IFPLUGD.AVTION ######

    # for more details.
    #
    # You should have received a copy of the GNU General Public License
    # along with ifplugd; if not, write to the Free Software Foundation,
    # Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.

    set -e

    if [ -z "$1" ] || [ -z "$2" ] ; then
    echo "Wrong arguments" > /dev/stderr
    exit 1
    fi

    mdv-network-event link_$2 $1 || /bin/true

    [ "$2" = "up" ] && exec /sbin/ifup $1 onlink
    [ "$2" = "down" ] && exec /sbin/ifdown $1 onlink

    exit 1



    ###### IFPLUGD.CONF ########

    # Please note that this is a bourne shell fragment sourced by the
    # init script of ifplugd.

    # Specify the interfaces to control here, separated by spaces.
    # Ifplugd processes will be started for each of these interfaces when
    # the ifplugd init script is called with the "start" argument. You may
    # use the magic string "auto" to make the init script start or stop
    # ifplugd processes for ALL eth and wlan interfaces that are available
    # according to /proc/net/dev. Note that the list of interfaces
    # appearing in /proc/net/dev may depend on which kernel modules you
    # have loaded.
    INTERFACES="eth0"# Please note that this is a bourne shell fragment
    sourced by the
    # init script of ifplugd.

    # Specify the interfaces to control here, separated by spaces.
    # Ifplugd processes will be started for each of these interfaces when
    # the ifplugd init script is called with the "start" argument. You may
    # use the magic string "auto" to make the init script start or stop
    # ifplugd processes for ALL eth and wlan interfaces that are available
    # according to /proc/net/dev. Note that the list of interfaces
    # appearing in /proc/net/dev may depend on which kernel modules you
    # have loaded.
    INTERFACES="eth0"

    # Additional parameters for ifplugd.
    # (Run "ifplugd -h" for further information.)
    ARGS="-fwI -u0 -d10"

    # Additional parameters for ifplugd for the specified interface. Note
    # that $ARGS is ignored, when a variable like this is set for an
    # interface
    #ARGS_wlan0="-MwI -u5 -d5"





    Currently the loss of the desktop switching out weighs the network.


    The desktop effects work fine on Mga6.
    So that pretty much accuses one or more of the upgrade files on Mga7.


    Has anyone else reported a desktop effects problem.

    Everybody has the same updates.

    regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Nov 5 21:38:24 2019
    On Tue, 05 Nov 2019 07:36:35 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote:

    Yup, I would guess the SSD should only bring timing problems to light
    when new. As they wear out, I would expect weird problems.

    That reminds me. A failing power supply where the power provided sometimes drops
    below whats required, but not always, will have very unpredictable effects.
    Not easy to test for though.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 5 23:22:31 2019
    On Wed, 6 Nov 2019 09:08:08 +1100, faeychild wrote:
    On 5/11/19 11:36 pm, Bit Twister wrote:



    Has anyone else reported a desktop effects problem.

    Your mouse and keyboard seem to work, why not check for yourself.

    Besides lurking on Usenet, I make a pass through Mageia bug reporting
    system every day or so.

    That keeps me abreast of possible problems on my system.

    I have a home grown index.html page with this link. Watch out
    for line wrap.

    https://bugs.mageia.org/buglist.cgi?chfieldfrom=-2d&chfieldto=Now&component=Ins taller&component=New%20RPM%20package%20request&component=Release%20%28media%20o r%20process%29&component=RPM%20Packages&component=Security&order=changeddate%20 DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=Mageia&query_format =advanced&resolution=---

    That keeps me abreast of possible problems on my system.

    Also lurking in QA and Dev mailing lists, gets me a heads up on problems
    and not to mention keeping an eye on the Mageia forum would be a fine
    place to see about latest updates causing grief.

    Since you seem to have a low priority on installing updates, you could
    always check the above sources for user problems.

    Then there is the option of testing before updating "Production".
    In your case, it would be cloning your install into another partition,
    modify cloned /etc/fstab to use the new partition, run update-grub to
    pickup the new "test install". Thereafter, any updates showing up in "Production" would allow you to boot test_install, verify it works,
    boot Production and do the install.

    Everybody has the same updates.

    Very true, except not everyone has the same hardware, used the same
    install media, let alone install the same set of packages and run
    with the same services/drivers.

    For example, I am not using the Display Manager that you are using.
    My network is controlled by systemd-networkd not, networkmanager or network.

    I checked MCC and vesa is an option.. More fun tomorrow.

    I tried vesa driver this morning and lost "X" completely.

    I way back in time I found clicking test did not work when changing x11 drivers. Always had to reboot to see if it worked.

    I got many complaints about conflicting modules.

    Yikes, I have never seen that one. I am assuming you are just using
    mcc to change driver, and not using the software package manager.

    Crash and burn :-(

    I way back in time I found clicking test to not work when changing x11
    drivers. xorg/vesa usually works for everyone.


    I was driven to consider a reinstall -Ahhggg!!!

    Fortunately Mga7 is accessible from Mga6 and I saved the ~/HOME hidden
    files knowing this would speed recovery

    But then I noticed the option to update with the install media and it
    worked !!!!

    See, now that makes no sense to me. Once you have make any updates from
    a mirror, I would assume there would never be any reason for any packages
    to update from the install media because you either have the same rpms
    from the install and any updates from the mirror would have a higher release/version.


    Reinstalled the nvidia driver and we are back

    Yep, I have seen toggling between vesa and video card driver cause
    a recompile and whatnot which clears up the problem.

    Other solutions I have used is to backup/remove the xorg conf file,
    which will cause to software to rescan and create a new configuration
    file during boot.

    So were are still in the race.

    Well, swallow your pride and make the pit stop to backup your install. :-)
    That way, when you wreck the car, you save time by not have to build
    another one from scratch.

    Yes, but in your last soap opera I thought you had used it for
    xfce testing to rule out plasma restarting your nic when down.

    I didn't get to that process.
    Not entirely sure how to switch DE anyway

    Me either for your setup.

    On your login screen, you enter the user id, say, junk, then check/ckick
    each icon to find the one which allows you set the DE to be used by that
    user, then enter junk's password.

    Still kinda hoping that is caused via Dhcp*/dynamic ip addressing.

    I did consider the two files in /etc/ifplugd

    Personally, I prefer process elimination, over researching all the code
    that might involved.

    If setting up static ip solves your problem, then you get to keep on
    keeping on.

    Your other option is to start a thread in the Mageia forum, asking
    if anyone else has their dynamic ip wired nic coming up after manually
    shutting it down.

    Do provide the commands needed for the test to get possible testers
    interested in helping you.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 5 23:33:38 2019
    On Tue, 05 Nov 2019 16:38:24 -0500, David W. Hodgins wrote:
    On Tue, 05 Nov 2019 07:36:35 -0500, Bit Twister
    <BitTwister@mouse-potato.com> wrote:

    Yup, I would guess the SSD should only bring timing problems to light
    when new. As they wear out, I would expect weird problems.

    That reminds me. A failing power supply where the power provided sometimes
    drops
    below whats required, but not always, will have very unpredictable effects. Not easy to test for though.

    Very true. lm-sensors can/might help somewhat in identifying that kind
    of event. I also install smartmontools to point out possible problems
    with hard drives.

    I can recommend having an hourly cron job to run a script to scan
    the journal, in the previous hour, for problems.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 03:50:32 2019
    On 5/11/19 8:29 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 19:43:51 +1100, faeychild wrote:


    Is it just me again??

    Let's see. log out and into junk. Do remember to change Desktop Environment to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    It does have the four desktops but I found no way to display them in a
    "grid"
    Plasma allows this by defining a screen edge to take the cursor too
    which then switches the screen to display a two by two grid of the desktops.

    I am missing this seriously - muscle memory still takes my cursor to the
    top of the screen when I expect to see the four desktops displayed.



    I thought it did, since I seem to recall some grub messages. Then again
    I always remove the previous kernel if the new kernel boots.

    I like to leave the last two.
    But then, I don't have that backup...yet



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Wed Nov 6 04:15:29 2019
    On Wed, 6 Nov 2019 14:50:32 +1100, faeychild wrote:
    On 5/11/19 8:29 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 19:43:51 +1100, faeychild wrote:


    Is it just me again??

    Let's see. log out and into junk. Do remember to change Desktop Environment >> to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    It does have the four desktops but I found no way to display them in a
    "grid"

    On any desktop, I can recommend right/left/middle click on everything
    found on the desktop, and even on an unused desktop space.
    Right click the desktop/workspace in the task bar, select properties.
    Change the row count/value.

    Plasma allows this by defining a screen edge to take the cursor too
    which then switches the screen to display a two by two grid of the desktops.

    Ok, I was thinking about the grid in the task bar.

    I am missing this seriously - muscle memory still takes my cursor to the
    top of the screen when I expect to see the four desktops displayed.

    I have always run with eight workspaces/desktops, so I have never used
    the feature.

    to switch workspaces I just roll the wheel on the mouse to cycle through desktops or middle click mouse and pick whichever app that is already
    running.

    All the above depends on the settings I have set.

    The great majority of my desktop shortcuts automagically jump to the
    desired workspace and launch the app if not already running,


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Wed Nov 6 04:18:34 2019
    On Wed, 6 Nov 2019 14:50:32 +1100, faeychild wrote:
    On 5/11/19 8:29 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 19:43:51 +1100, faeychild wrote:


    Is it just me again??

    Let's see. log out and into junk. Do remember to change Desktop Environment >> to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    Did you check if comes back up if you brought it down manually when
    running as junk?

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Wed Nov 6 04:19:37 2019
    On Tue, 5 Nov 2019 22:18:34 -0600, Bit Twister wrote:
    On Wed, 6 Nov 2019 14:50:32 +1100, faeychild wrote:
    On 5/11/19 8:29 pm, Bit Twister wrote:
    On Tue, 5 Nov 2019 19:43:51 +1100, faeychild wrote:


    Is it just me again??

    Let's see. log out and into junk. Do remember to change Desktop Environment
    to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    Did you check if comes back up if you brought it down manually when
    running as junk?

    Frap, should have said nic card instead of it.


    --
    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.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Wed Nov 6 05:29:22 2019
    On 11/5/19 3:43 AM, faeychild wrote:


    Is it just me again??

    Since I disabled the update applet I manually allowed an update today
    and it came with a new kernel

    uname -a
    Linux unimatrix 5.3.7-desktop-4.mga7 #1 SMP Thu Oct 24 20:11:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

    I checked during grub boot and found a bunch of redundant kernels which
    I removed with MCC,
    Only to find the listing still in grub boot. Running "update-grub2"
    removed them  _ should not MCC software run "update-grub2" after an install??

    It's supposed to, but this is a known bug that's been around since at
    least all of Mageia 6, where grub is not updated properly if you remove
    more than one kernel at a time.

    Further

    All the desktop effects a gone I still have 4 virtual desktops but no grid,  no edge switching. transparency is gone

    And when I switch to the desktop running 4 vlc streaming TV channels the
    CPU usage runs up

    Window movements seem a little jerky.

    I am running the Nvidia propriety driver NVIDIA Driver Version:430.50

    GeForce GTX 1050 Ti
    When you got the kernel update, did you also get the accompanying
    kernel-devel packages? If not, then dkms would have been unable to build
    the proprietary nvidia driver modules for the new kernel. If that
    happens you should have been dumped into nouveau, which may or may not
    be able to handle some of the effects with your GPU. Nouveau seems to
    work better with some GPUs than others.

    TJ

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 08:37:35 2019
    On 6/11/19 3:15 pm, Bit Twister wrote:


    I have installed xfce and ran it in "junk"

    It does have the four desktops but I found no way to display them in a
    "grid"

    On any desktop, I can recommend right/left/middle click on everything
    found on the desktop, and even on an unused desktop space.
    Right click the desktop/workspace in the task bar, select properties.
    Change the row count/value.

    I did find a "Windows Appearance" I think that allowed the transparency
    to be adjusted but not to the extent of Plasma. I suspect that the
    Plasma effects are the old Compiz 3D desktop

    Plasma allows this by defining a screen edge to take the cursor too
    which then switches the screen to display a two by two grid of the desktops.

    Ok, I was thinking about the grid in the task bar.

    Yes! That is the "Pager"


    to switch workspaces I just roll the wheel on the mouse to cycle through desktops or middle click mouse and pick whichever app that is already running.


    Well that is something I can live, mouse wheel is fine, I just need retraining
    Another curiosity is the start up wave. I never had it in Mga6 and was surprised to hear it again in Mga7

    Regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 09:13:59 2019
    On 6/11/19 3:18 pm, Bit Twister wrote:


    Let's see. log out and into junk. Do remember to change Desktop Environment
    to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    Did you check if comes back up if you brought it down manually when
    running as junk?


    In my cursory examination of Xfce I couldn't find a similar arrangement,
    ie: a net-applet to enable/disable. I didn't have time to look for long


    [OFF TOPIC]

    I was interrupted by my neighbor with a problem with his DVD player.
    His movie "Mama Mia" was all music and no dialog.
    I stood in front of the TV monitor thinking despairingly how can there
    be music and no voices when characters are clearly speaking.

    He claims that the previous disk had played fine.

    Mama mia is a copy. Had someone screwed up the rip?
    So I opened the setup menu > audio.

    Check "stereo" yes

    Digital was "OFF" - left that alone!!

    I disabled center speaker and rear speakers - because there aren't any,
    and enabled woofer - because there is one. None of which I expected to
    really do anything.
    Left the rest alone

    But after getting back out of the menu and back to the Movie, we had
    dialog.

    He said "What did you do"

    I have no fscking idea!! I wonder if the previous disk still plays??

    Do I care ?? NOPE
    But I expect to be called back on it though

    Then I came back here to the crazy desktop and NIC, to await the next pointless interruption.

    I have videos to render

    This is why I don't have time to research much of anything, Bits

    I seem to be in a barking mad twilight zone where stuff happens

    regards



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 09:15:00 2019
    On 6/11/19 3:19 pm, Bit Twister wrote:


    Did you check if comes back up if you brought it down manually when
    running as junk?

    Frap, should have said nic card instead of it.

    I gotcha anyway!!



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 09:22:03 2019
    On 6/11/19 4:29 pm, TJ wrote:


    It's supposed to, but this is a known bug that's been around since at
    least all of Mageia 6, where grub is not updated properly if you remove
    more than one kernel at a time.

    Good to know!



    GeForce GTX 1050 Ti
    When you got the kernel update, did you also get the accompanying kernel-devel packages? If not, then dkms would have been unable to build

    I believe that I did because I was running the nvidia driver.
    That was the first thing I checked.

    The desktop does seem to have been triggered by something in the recent update. Switching back to the older kernel doesn't correct it.

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Wed Nov 6 10:18:00 2019
    On Wed, 6 Nov 2019 20:13:59 +1100, faeychild wrote:
    On 6/11/19 3:18 pm, Bit Twister wrote:


    Let's see. log out and into junk. Do remember to change Desktop Environment
    to plasma and see what you can see.

    I have installed xfce and ran it in "junk"

    Did you check if comes back up if you brought it down manually when
    running as junk?


    In my cursory examination of Xfce I couldn't find a similar arrangement,
    ie: a net-applet to enable/disable. I didn't have time to look for long

    That was part of the investigation to eliminate the Desktop Environment.

    I had expected you to click up a terminal,
    su - root
    export _net_nic=enp0s31f6
    ip link set $_net_nic down
    ip -o link show $_net_nic
    verify state is DOWN then check if state goes back to UP with
    watch -n 5 "ip -o link show $_net_nic"

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 11:16:52 2019
    On 6/11/19 9:18 pm, Bit Twister wrote:

    ie: a net-applet to enable/disable. I didn't have time to look for long

    That was part of the investigation to eliminate the Desktop Environment.

    I had expected you to click up a terminal,
    su - root
    export _net_nic=enp0s31f6
    ip link set $_net_nic down
    ip -o link show $_net_nic
    verify state is DOWN then check if state goes back to UP with
    watch -n 5 "ip -o link show $_net_nic"


    It must be late night, Bits.
    The NIC is staying down on the plasma desktop It's been down for
    minutes. It usually manages about 12 seconds.

    I'll try both again in the morning
    --
    faeychild
    Running plasmashell 5.15.4 on 5.3.7-desktop-4.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Aragorn@2:250/1 to All on Wed Nov 6 14:28:23 2019
    On 06.11.2019 at 19:37, faeychild scribbled:

    On 6/11/19 3:15 pm, Bit Twister wrote:

    I have installed xfce and ran it in "junk"

    It does have the four desktops but I found no way to display them
    in a "grid"

    On any desktop, I can recommend right/left/middle click on
    everything found on the desktop, and even on an unused desktop
    space. Right click the desktop/workspace in the task bar, select properties. Change the row count/value.

    I did find a "Windows Appearance" I think that allowed the
    transparency to be adjusted but not to the extent of Plasma. I
    suspect that the Plasma effects are the old Compiz 3D desktop

    Nope. Plasma uses KWin as the default window manager, and KWin does use
    OpenGL for its compositing effects, just as Compiz does, but Compiz is
    an entirely different beast.


    --
    With respect,
    = Aragorn =


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Strider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 21:21:51 2019
    On 7/11/19 1:28 am, Aragorn wrote:

    Nope. Plasma uses KWin as the default window manager, and KWin does use OpenGL for its compositing effects, just as Compiz does, but Compiz is
    an entirely different beast.


    They always confused me because I didn't delve into it.
    Wasn't there a "Fusion" also?
    And a warning against trying to run both?

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Nov 6 21:25:41 2019
    On 6/11/19 10:16 pm, faeychild wrote:



    It must be late night, Bits.
    The NIC is staying down on the plasma desktop  It's been down for
    minutes. It usually manages about 12 seconds.

    I'll try both again in the morning

    I've returned from "junk" user and Xfce.

    I ran "rest_junk.sh" It works
    I ran your commands three times
    each time the nic went and came back up again some 10 second later

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 01:17:22 2019
    On Thu, 7 Nov 2019 08:25:41 +1100, faeychild wrote:
    On 6/11/19 10:16 pm, faeychild wrote:



    It must be late night, Bits.
    The NIC is staying down on the plasma desktop  It's been down for
    minutes. It usually manages about 12 seconds.

    I'll try both again in the morning

    I've returned from "junk" user and Xfce.

    I ran "rest_junk.sh" It works

    Good, I can recommend running it before doing any testing in that
    account when wanting to rule out or testing to see if problem(s)
    is system wide or just a user problem.

    I ran your commands three times
    each time the nic went and came back up again some 10 second later

    Once was enough.

    Well, we have ruled out Desktop Environment, systemd-networkd,
    NetworkManager, and tried HOTPULG=no and USERCTL=no in
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6

    I have no other suggestions to locating the culprit.
    Suggest a post in https://forums.mageia.org forum just to see if anyone
    else has the problem on their system.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 01:30:56 2019
    On 7/11/19 12:17 pm, Bit Twister wrote:


    Well, we have ruled out Desktop Environment, systemd-networkd, NetworkManager, and tried HOTPULG=no and USERCTL=no in
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6

    currently

    ~]$ cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=dhcp
    ONBOOT=yes
    METRIC=5
    MII_NOT_SUPPORTED=no
    USERCTL=yes
    RESOLV_MODS=no
    LINK_DETECTION_DELAY=6
    IPV6INIT=no
    IPV6TO4INIT=no
    ACCOUNTING=no
    DHCP_CLIENT=dhclient
    NEEDHOSTNAME=no
    PEERDNS=yes
    PEERYP=yes
    PEERNTPD=no


    once again I have a dead line hanging over me and no guaranteed open
    time uncommitted, I will have to try "HOTPULG=no and USERCTL=no" again
    later just to be sure..

    regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 02:39:15 2019
    On Wed, 6 Nov 2019 19:17:22 -0600, Bit Twister wrote:
    On Thu, 7 Nov 2019 08:25:41 +1100, faeychild wrote:
    On 6/11/19 10:16 pm, faeychild wrote:



    It must be late night, Bits.
    The NIC is staying down on the plasma desktop  It's been down for
    minutes. It usually manages about 12 seconds.

    I'll try both again in the morning

    I've returned from "junk" user and Xfce.

    I ran "rest_junk.sh" It works

    Good, I can recommend running it before doing any testing in that
    account when wanting to rule out or testing to see if problem(s)
    is system wide or just a user problem.

    I ran your commands three times
    each time the nic went and came back up again some 10 second later

    Once was enough.

    Well, we have ruled out Desktop Environment, systemd-networkd, NetworkManager, and tried HOTPULG=no and USERCTL=no in
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6

    I have no other suggestions to locating the culprit.

    Only two isolation paths are left, try static ip to rule out dhcp*
    and switch to using systemd-networkd

    static ip is easy enough to test, I gave you values needed to
    setup static ip when using the control center nic configuration screen.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 05:47:10 2019
    On 7/11/19 1:39 pm, Bit Twister wrote:


    static ip is easy enough to test, I gave you values needed to
    setup static ip when using the control center nic configuration screen.




    OK Bits

    I set IP = 192.168.1.100

    netmask = 255.255.255.0

    Gateway = 192.168.1.1

    DNS server 1 & 2 8.8.8.8

    Hostname = localhost.localdomain


    No go unfortunately

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 06:22:15 2019
    On Thu, 7 Nov 2019 16:47:10 +1100, faeychild wrote:
    On 7/11/19 1:39 pm, Bit Twister wrote:


    static ip is easy enough to test, I gave you values needed to
    setup static ip when using the control center nic configuration screen.




    OK Bits

    I set IP = 192.168.1.100

    netmask = 255.255.255.0

    Gateway = 192.168.1.1

    DNS server 1 & 2 8.8.8.8

    Hostname = localhost.localdomain


    No go unfortunately

    What do you mean no go?

    Connection will not stay down?
    or no connection?

    Need results of
    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    after static setup.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 06:51:13 2019
    On 7/11/19 5:22 pm, Bit Twister wrote:
    On Thu, 7 Nov 2019 16:47:10 +1100, faeychild wrote:
    On 7/11/19 1:39 pm, Bit Twister wrote:


    static ip is easy enough to test, I gave you values needed to
    setup static ip when using the control center nic configuration screen.




    OK Bits

    I set IP = 192.168.1.100

    netmask = 255.255.255.0

    Gateway = 192.168.1.1

    DNS server 1 & 2 8.8.8.8

    Hostname = localhost.localdomain


    No go unfortunately

    What do you mean no go?

    Connection will not stay down?
    or no connection?


    Yes a bit unclear, sorry. No connection!!



    ~]# ping -c1 -w3 72.30.35.10
    PING 72.30.35.10 (72.30.35.10) 56(84) bytes of data.
    From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
    From 192.168.1.100 icmp_seq=2 Destination Host Unreachable
    From 192.168.1.100 icmp_seq=3 Destination Host Unreachable

    - --- 72.30.35.10 ping statistics ---
    3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 29ms
    pipe 3


    Need results of
    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    after static setup.



    ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=static
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1
    ONBOOT=yes
    METRIC=5
    MII_NOT_SUPPORTED=no
    USERCTL=yes
    DNS1=8.8.8.8
    DNS2=8.8.8.8
    RESOLV_MODS=no
    LINK_DETECTION_DELAY=6
    IPV6INIT=no
    IPV6TO4INIT=no
    ACCOUNTING=no



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 07:04:40 2019
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:


    Yes a bit unclear, sorry. No connection!!



    ~]# ping -c1 -w3 72.30.35.10

    --- 72.30.35.10 ping statistics ---
    3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 29ms pipe 3


    Need results of
    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    after static setup.



    ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=static
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1

    Your dhcp lease file indicated 192.168.1.254 as the gateway.

    and as root, run
    locate enp0s31f6



    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 07:18:43 2019
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:

    DNS1=8.8.8.8
    DNS2=8.8.8.8

    FYI: if the first dns server can not be reached, the second one is used.

    Using
    public dns servers at https://encrypted.google.com/advanced_search
    gets me

    About 47,900,000 results (0.72 seconds)

    Small snippet from the page
    OpenDNS. Primary, secondary DNS servers: 208.67.222.222 and 208.67.220.220. ...
    Cloudflare. Primary, secondary DNS servers: 1.1.1.1 and 1.0.0.1. ...
    Google Public DNS. Primary, secondary DNS servers: 8.8.8.8 and 8.8.4.4. ...

    I tend to use OpenDNS 208.67.222.222 as dns1 and 8.8.8.8 for dns2.
    I might switch to Cloudflare as dns1 which seems easier to remember.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 07:23:33 2019
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:

    GATEWAY=192.168.1.1

    You can use "route -n" when running dhcp, to get gateway ip. Example
    $ route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.11.1 0.0.0.0 UG 0 0 0 enp3s0 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0 enp3s0

    There you can see my gateway is 192.168.11.1

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 07:42:19 2019
    On 7/11/19 6:04 pm, Bit Twister wrote:

    Need results of
    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    after static setup.



    ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=static
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1

    Your dhcp lease file indicated 192.168.1.254 as the gateway.

    Now I am confused. Does a static setup have DHCP lease



    and as root, run
    locate enp0s31f6



    ~]# locate enp0s31f6
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6 /root/.local/share/RecentDocuments/ifcfg-enp0s31f6.desktop /root/.local/share/Trash/files/ifcfg-enp0s31f6 /root/.local/share/Trash/files/ifcfg-enp0s31f6 (1) /root/.local/share/Trash/files/ifcfg-enp0s31f6-old /root/.local/share/Trash/info/ifcfg-enp0s31f6 (1).trashinfo /root/.local/share/Trash/info/ifcfg-enp0s31f6-old.trashinfo /root/.local/share/Trash/info/ifcfg-enp0s31f6.trashinfo /var/lib/dhclient/dhclient--enp0s31f6.lease



    current DHCP setup

    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=dhcp
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1
    ONBOOT=yes
    METRIC=5
    MII_NOT_SUPPORTED=no
    USERCTL=yes


    says IP = 192.168.1.100

    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::1e1b:dff:fea4:b28f prefixlen 64 scopeid 0x20<link>
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 129754 bytes 177842121 (169.6 MiB)

    says inet is 192.168.1.1 Is inet the IP address. If so I get totally
    confused


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 07:43:50 2019
    On 7/11/19 6:18 pm, Bit Twister wrote:
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:

    DNS1=8.8.8.8
    DNS2=8.8.8.8


    I used those as temp defaults to try to get the nic running static
    --
    faeychild
    Running plasmashell 5.15.4 on 5.3.7-desktop-4.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 07:46:05 2019
    On 7/11/19 6:23 pm, Bit Twister wrote:
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:

    GATEWAY=192.168.1.1

    You can use "route -n" when running dhcp, to get gateway ip. Example
    $ route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.11.1 0.0.0.0 UG 0 0 0
    enp3s0
    192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0
    enp3s0

    There you can see my gateway is 192.168.11.1

    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6


    why do I have 3 entries

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 08:18:58 2019
    On Thu, 7 Nov 2019 18:42:19 +1100, faeychild wrote:
    On 7/11/19 6:04 pm, Bit Twister wrote:

    Your dhcp lease file indicated 192.168.1.254 as the gateway.

    Now I am confused. Does a static setup have DHCP lease

    It does not. I was pulling the information from a lease file you
    had provided at some other time.






    current DHCP setup

    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=dhcp
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.1
    ONBOOT=yes
    METRIC=5
    MII_NOT_SUPPORTED=no
    USERCTL=yes


    says IP = 192.168.1.100

    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::1e1b:dff:fea4:b28f prefixlen 64 scopeid 0x20<link>
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 129754 bytes 177842121 (169.6 MiB)

    says inet is 192.168.1.1 Is inet the IP address. If so I get totally confused

    I can understand your confusion. BOOTPROTO=dhcp will cause dhcp software
    to assign you values from the lease file which caused the nic to
    have 192.168.1.1 regardless of the IPADDR=192.168.1.100 value.

    Going to have to guess your three route -n rows are caused by config
    file contents.

    and as root, run
    locate enp0s31f6


    ~]# locate enp0s31f6
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6 /var/lib/dhclient/dhclient--enp0s31f6.lease


    As root, go ahead and remove those two files, configure your nic as
    dynamic again, bring it up and ifconfig and route -n should look normal.

    Remove the two files again, set as static with something like
    static ip address as 192.168.1.100
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    Dns servers 8.8.8.8 and 1.1.1.1

    and I would expect ifconfig to show inet 192.168.1.100
    and ping -c1 -w3 yahoo.com should pass.

    not knowing your router settings, you might use
    192.168.1.20 instead of 192.168.1.100

    I would also like to see results of
    cat /etc/hosts



    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 08:55:38 2019



    As root, go ahead and remove those two files, configure your nic as
    dynamic again, bring it up and ifconfig and route -n should look normal.

    No

    ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6




    Remove the two files again, set as static with something like
    static ip address as 192.168.1.100
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    Dns servers 8.8.8.8 and 1.1.1.1

    and I would expect ifconfig to show inet 192.168.1.100
    and ping -c1 -w3 yahoo.com should pass.

    not knowing your router settings, you might use
    192.168.1.20 instead of 192.168.1.100

    It is getting a bit late and risky to continue, Bits

    I'll continue tomorrow.



    I would also like to see results of
    cat /etc/hosts



    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    172.217.167.69 mail.google.com


    regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 09:21:47 2019
    On Thu, 7 Nov 2019 19:55:38 +1100, faeychild wrote:



    As root, go ahead and remove those two files, configure your nic as
    dynamic again, bring it up and ifconfig and route -n should look normal.

    No

    ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6

    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/ indicates something is weird. I hope it was because of the file deletions.

    I hope tomorrow's boot gets you a cleaner route -n result.


    It is getting a bit late and risky to continue, Bits

    Yeah, it is 03:15:25 AM CST at the moment, about a minute after
    I posted the deletion suggestion, I got worried if it would not be
    possible to configure the nic.

    If so, I started wondering if so, if you would not panic and remember
    you could mount /mageia_6 and copy /mageia_6/etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    to /etc/sysconfig/network-scripts/ifcfg-enp0s31f6



    I'll continue tomorrow.

    Sounds like a plan.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 09:52:36 2019
    On Thu, 7 Nov 2019 03:21:47 -0600, Bit Twister wrote:
    On Thu, 7 Nov 2019 19:55:38 +1100, faeychild wrote:



    As root, go ahead and remove those two files, configure your nic as
    dynamic again, bring it up and ifconfig and route -n should look normal.

    No

    ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0
    enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0
    enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
    enp0s31f6

    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/ indicates something is weird. I hope it was because of the file deletions.

    I hope tomorrow's boot gets you a cleaner route -n result.

    I do not know if you changed your /etc/nsswitch.conf per my suggestion.

    # hosts: mdns4_minimal files nis dns mdns4 myhostname
    hosts: files dns myhostname

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 10:41:01 2019
    On Thu, 7 Nov 2019 19:55:38 +1100, faeychild wrote:

    cat /etc/hosts

    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    172.217.167.69 mail.google.com

    Hard coding ip addresses for external sites like the above, can come
    back to bite you when ip address changes are made by the site.

    I speak from experience. I have a ckip.pl script to verify ip addresses
    of sites where I use an id/pw or download updates
    $ grep '$check\[$c]\[0] = ' /local/bin/ckip.pl | wc -l
    42
    and prevent going there if it fails the check.
    I see ip changes every few months on one site or another.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Aragorn@2:250/1 to All on Thu Nov 7 14:22:43 2019
    On 07.11.2019 at 08:21, faeychild scribbled:

    On 7/11/19 1:28 am, Aragorn wrote:

    Nope. Plasma uses KWin as the default window manager, and KWin
    does use OpenGL for its compositing effects, just as Compiz does,
    but Compiz is an entirely different beast.

    They always confused me because I didn't delve into it.
    Wasn't there a "Fusion" also?
    And a warning against trying to run both?

    Well, Compiz Fusion came later. Long story short, at a given point,
    Compiz was forked into a separate project called Beryl. Later on, the
    two merged their code again and this became Compiz Fusion.

    --
    With respect,
    = Aragorn =


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Strider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Thu Nov 7 15:11:22 2019
    On 11/6/19 4:22 AM, faeychild wrote:
    On 6/11/19 4:29 pm, TJ wrote:

    When you got the kernel update, did you also get the accompanying
    kernel-devel packages? If not, then dkms would have been unable to build

    I believe that I did because I was running the nvidia driver.
    That was the first thing I checked.

    The desktop does seem to have been triggered by something in the recent update. Switching back to the older kernel doesn't correct it.


    I suspected you did, because if you had been dumped into nouveau you
    would usually get a message about it when you rebooted the first time.

    But, it doesn't hurt to be reminded to check the basics. We all forget
    some of them from time to time.

    TJ

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 21:19:10 2019
    On 7/11/19 7:18 pm, Bit Twister wrote:

    and as root, run
    locate enp0s31f6


    ~]# locate enp0s31f6
    /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    /var/lib/dhclient/dhclient--enp0s31f6.lease


    As root, go ahead and remove those two files, configure your nic as
    dynamic again, bring it up and ifconfig and route -n should look normal.

    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6

    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::1e1b:dff:fea4:b28f prefixlen 64 scopeid 0x20<link>
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 518 bytes 149946 (146.4 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 633 bytes 62090 (60.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xf7700000-f7720000


    ping -c1 -w3 yahoo.com
    PING yahoo.com (72.30.35.10) 56(84) bytes of data.
    64 bytes from yahoo.com (72.30.35.10): icmp_seq=1 ttl=44 time=236 ms

    - --- yahoo.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 235.548/235.548/235.548/0.000 ms



    Remove the two files again, set as static with something like
    static ip address as 192.168.1.100
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    Dns servers 8.8.8.8 and 1.1.1.1

    does hostname matter I used unimatrix.localdomain

    MCC reports a problem
    Net applet declares network is up

    ip -o link show $_net_nic
    2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
    state UP mode DEFAULT group default qlen 1000\ link/ether
    1c:1b:0d:a4:b2:8f brd ff:ff:ff:ff:ff:ff


    ping -c1 -w3 yahoo.com
    PING yahoo.com (72.30.35.10) 56(84) bytes of data.
    64 bytes from media-router-fp2.prod1.media.vip.bf1.yahoo.com
    (72.30.35.10): icmp_seq=1 ttl=43 time=236 ms

    - --- yahoo.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 236.464/236.464/236.464/0.000 ms


    and I would expect ifconfig to show inet 192.168.1.100
    and ping -c1 -w3 yahoo.com should pass.

    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::1e1b:dff:fea4:b28f prefixlen 64 scopeid 0x20<link>
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 645 bytes 174900 (170.8 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 790 bytes 76714 (74.9 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xf7700000-f7720000


    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 5 0 0 enp0s31f6
    169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6


    There seems to be some conflict here Bits

    not knowing your router settings, you might use
    192.168.1.20 instead of 192.168.1.100

    Router LAN page

    LAN
    PARAMETERS
    Group Name Default
    IP Address 192.168.1.254
    Subnet Mask 255.255.255.0
    IGMP Snooping Enable
    IGMP Snooping Mode Blocking Mode
    LAN side firewall Disable
    DHCP SERVER
    DHCP Server Enable
    Start IP Address 192.168.1.1
    End IP Address 192.168.1.20
    Leased Time (hour) 24
    Option 66 Disable
    Use Router's setting as DNS Server Enable
    Primary DNS server
    Secondary DNS server
    Static IP Lease List
    Host Label MAC Address IP Address Remove Edit

    IP ALIAS
    IP Alias Disable
    IP Address
    Subnet Mask


    I would also like to see results of
    cat /etc/hosts



    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    172.217.167.69 mail.google.com

    regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 21:20:44 2019
    On 7/11/19 8:21 pm, Bit Twister wrote:

    If so, I started wondering if so, if you would not panic and remember
    you could mount /mageia_6 and copy /mageia_6/etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    to /etc/sysconfig/network-scripts/ifcfg-enp0s31f6


    MCC auto default is the fallback position :-)


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 21:24:42 2019
    On 7/11/19 8:52 pm, Bit Twister wrote:


    I do not know if you changed your /etc/nsswitch.conf per my suggestion.

    # hosts: mdns4_minimal files nis dns mdns4 myhostname
    hosts: files dns myhostname



    # passwd: files nis
    # shadow: files nis
    # group: files nis

    passwd: files
    shadow: files
    group: files

    #hosts: mdns4_minimal files nis dns mdns4 myhostname
    hosts: files dns myhostname

    networks: files

    services: files

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 21:30:03 2019
    On 7/11/19 8:52 pm, Bit Twister wrote:


    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/ >> indicates something is weird. I hope it was because of the file deletions.


    This at least explains what but not why !!!
    Interesting


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 22:50:41 2019
    On Fri, 8 Nov 2019 08:30:03 +1100, faeychild wrote:
    On 7/11/19 8:52 pm, Bit Twister wrote:


    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/
    indicates something is weird. I hope it was because of the file deletions.


    This at least explains what but not why !!!
    Interesting

    I thought so also and maybe its presents might be what causes the network
    to come back up.

    Your ifconfig shows an ip ipv6 assignment. I have seen articles of security problems when in use. If your isp is not assigning you an ipv6 address
    I would not enable it in the router or use it on the lan.

    You can check/get your ISP Internet ip address by running
    wget -qO - http://icanhazip.com
    in a terminal.

    If you want to disable it on your node, add/set GRUB_CMDLINE_LINUX="ipv6.disable=1"
    in /etc/default/grub and run
    update-grub

    Next boot should have ifconfig $_net_nic without a ipv6 address
    and I hope no 169-254... route.



    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 22:55:33 2019
    On Fri, 8 Nov 2019 08:20:44 +1100, faeychild wrote:
    On 7/11/19 8:21 pm, Bit Twister wrote:

    If so, I started wondering if so, if you would not panic and remember
    you could mount /mageia_6 and copy
    /mageia_6/etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    to /etc/sysconfig/network-scripts/ifcfg-enp0s31f6


    MCC auto default is the fallback position :-)

    Hmmm, if that is the answer in a screen that I think it is,
    I always set it to NO. that way, NetworkManager does not get control
    of the nic. Control stays with the network app that uses config files
    like /etc/sysconfig/network-scripts/ifcfg-enp0s31f6

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Thu Nov 7 22:55:33 2019
    On Thu, 07 Nov 2019 16:30:03 -0500, faeychild <faeychild@nomail.afraid.org> wrote:

    On 7/11/19 8:52 pm, Bit Twister wrote:
    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/
    indicates something is weird. I hope it was because of the file deletions.

    This at least explains what but not why !!!
    Interesting

    It's normal to have the three lines in the route output.

    On my system, I have two ...
    # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.10.11 0.0.0.0 UG 5 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

    The first is for packets going to the internet (Flags set to UG), the second is for
    the local lan.

    The 169.254 range is for link local addresses, which I've disabled on my system
    by adding a line for my interface ...
    # tail -n 1 /etc/sysconfig/network-scripts/ifcfg-eth0
    NOZEROCONF=yes

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 23:30:56 2019
    On 8/11/19 9:50 am, Bit Twister wrote:


    You can check/get your ISP Internet ip address by running
    wget -qO - http://icanhazip.com
    in a terminal.


    It's IPv4


    If you want to disable it on your node, add/set GRUB_CMDLINE_LINUX="ipv6.disable=1"
    in /etc/default/grub and run
    update-grub

    Done
    Currently reencoding a TV stream so the boot must wait.

    Next boot should have ifconfig $_net_nic without a ipv6 address
    and I hope no 169-254... route.




    I have rebellious thoughts about installing a second Mga7 on a spare partition with upgrades and see how it goes.

    Just spinning my wheels.

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Thu Nov 7 23:41:06 2019
    On 8/11/19 9:55 am, Bit Twister wrote:
    On Fri, 8 Nov 2019 08:20:44 +1100, faeychild wrote:
    On 7/11/19 8:21 pm, Bit Twister wrote:

    If so, I started wondering if so, if you would not panic and remember
    you could mount /mageia_6 and copy
    /mageia_6/etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    to /etc/sysconfig/network-scripts/ifcfg-enp0s31f6


    MCC auto default is the fallback position :-)

    Hmmm, if that is the answer in a screen that I think it is,
    I always set it to NO. that way, NetworkManager does not get control
    of the nic. Control stays with the network app that uses config files
    like /etc/sysconfig/network-scripts/ifcfg-enp0s31f6


    No. I meant that any complete trashing of the nic can be recovered by
    re configuring with MCC "Boot DHCP" option. it's point and shoot

    This fall back can always restore to a working setup.
    So it's actually quite safe to do anything manually to the nic setting

    This does not terrify me.

    Grub is another matter entirely - errors are sudden death. :-(

    regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 7 23:54:49 2019
    On Fri, 8 Nov 2019 08:19:10 +1100, faeychild wrote:
    On 7/11/19 7:18 pm, Bit Twister wrote:


    Remove the two files again, set as static with something like
    static ip address as 192.168.1.100
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    Dns servers 8.8.8.8 and 1.1.1.1

    does hostname matter I used unimatrix.localdomain

    I hope it does not. BUT, I did provide lurkers/you a rfc link about hostnames/domains....

    If you setup all your nodes with static/fixed ip address and add them
    to /etc/hosts on each node/install, you will be able get to ssh into them,
    xfer files, ping them, .... but localdomain means on your node only. :(

    Based on the RFC, I see no problem with using unimatrix.home.test
    or unimatrix.local.test or unimatrix.lan.test.

    /etc/hosts would then have something like
    192.168.1.100 unimatrix.local.test unimatrix

    and you can ping -c1 unimatrix. ssh unimatrix, ....

    NOTE: Anytime you change the hostname, you need to reboot so all
    services/apps pickup the new hostname.

    Your hostname is stored in /etc/hostname and nic configuration files
    can have the domain defined. Examples:

    $ grep -i domain /etc/sysconfig/network-scripts/ifcfg-enp* /etc/sysconfig/network-scripts/ifcfg-enp3s0:DOMAIN="home.test" /etc/sysconfig/network-scripts/ifcfg-enp4s0:DOMAIN="home.test"

    $ cat /etc/hostname
    wb.home.test

    I can highly recommend changing /etc/hostname last and immediately
    doing a reboot.

    I remember changing /etc/hostname first with an editor, and suddenly
    I lost desktop control. Had to power cycle to get back in.


    ip -o link show $_net_nic

    Hey, look at you go dude. Now I can forget having to type in enp0s31f6 everywhere needed when I type at you. B-)


    and I would expect ifconfig to show inet 192.168.1.100
    and ping -c1 -w3 yahoo.com should pass.

    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255

    Your node is now static at 192.168.1.100

    inet6 fe80::1e1b:dff:fea4:b28f prefixlen 64 scopeid 0x20<link>

    has a ipv6 ip address, which has caused me problems in some apps,
    and went away after I disabled it.

    RX errors 0 dropped 0 overruns 0 frame 0
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    Looking good, all are 0.


    device interrupt 16 memory 0xf7700000-f7720000

    Hmmmm, I do not have that line and have never seen it until now.
    Entirely possible it is a new feature in the obsolete ifconfig command.
    Seen NOTE in man ifconfig


    There seems to be some conflict here Bits

    not knowing your router settings, you might use
    192.168.1.20 instead of 192.168.1.100

    Router LAN page

    DHCP Server Enable
    Start IP Address 192.168.1.1
    End IP Address 192.168.1.20

    Yup, that tells the DHCP Server to keep Dynamic assignments within
    that range. I had hoped when going static, we would stay out of that
    range but was unsure if your router would prevent the .100 assignment
    without placing an entry in some other screen.

    Static IP Lease List
    Host Label MAC Address IP Address Remove Edit

    This is where I have entered all my MAC and IP address for all my
    static ip addresses. That way when I run "arp -a" low numbered ip
    addresses stick out a little bit.



    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 00:03:45 2019
    On Fri, 8 Nov 2019 10:30:56 +1100, faeychild wrote:
    On 8/11/19 9:50 am, Bit Twister wrote:

    I have rebellious thoughts about installing a second Mga7 on a spare partition with upgrades and see how it goes.

    I understand. But, may be a good idea when upgrading to mga8.

    Since I do a / backup into my /hotbu prior to update, the
    fallback procedure is to boot other install and run restore_mga7 if update
    is useless/problematic.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 00:05:06 2019
    On 8/11/19 9:55 am, David W. Hodgins wrote:

    On my system, I have two ...
    # route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags
    Metric Ref    Use
    Iface
    0.0.0.0         192.168.10.11   0.0.0.0         UG   
    5      0        0
    eth0
    192.168.0.0     0.0.0.0         255.255.0.0     U    
    0      0        0
    eth0

    The first is for packets going to the internet (Flags set to UG), the
    second is for
    the local lan.

    The 169.254 range is for link local addresses, which I've disabled on my system
    by adding a line for my interface ...
    # tail -n 1 /etc/sysconfig/network-scripts/ifcfg-eth0
    NOZEROCONF=yes


    Ah!!

    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 5 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6

    So!!

    Something is still not right though When I take down the nic with the Net-Applet the tool tip says "You do not have a configured connection"
    and then the nic comes back up
    The Net-Appplet used to replace the green tick with a red symbol when
    it went down. Now it's a green gear sysmbol.

    Besides!! Avahi is disabled

    ~]# service avahi-daemon status
    Redirecting to /bin/systemctl status avahi-daemon.service
    ● avahi-daemon.service
    Loaded: masked (Reason: Unit avahi-daemon.service is masked.)
    Active: inactive (dead)


    Regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 00:08:28 2019
    On 8/11/19 11:05 am, faeychild wrote:


     The Net-Appplet used to replace the green tick with a red symbol when
    it went down. Now it's a green gear sysmbol.

    It's a blue gear. I developing colour blindness as well

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 00:11:32 2019
    On 8/11/19 11:03 am, Bit Twister wrote:
    On Fri, 8 Nov 2019 10:30:56 +1100, faeychild wrote:
    On 8/11/19 9:50 am, Bit Twister wrote:

    I have rebellious thoughts about installing a second Mga7 on a spare
    partition with upgrades and see how it goes.

    I understand. But, may be a good idea when upgrading to mga8.

    Since I do a / backup into my /hotbu prior to update, the
    fallback procedure is to boot other install and run restore_mga7 if update
    is useless/problematic.



    I am amazed at the organization of your setup
    How many partitions and drives do you run?

    I have an hour of render to go before I can reboot :-(

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 00:32:16 2019
    On Thu, 07 Nov 2019 17:55:33 -0500, David W. Hodgins wrote:
    On Thu, 07 Nov 2019 16:30:03 -0500, faeychild <faeychild@nomail.afraid.org>
    wrote:

    On 7/11/19 8:52 pm, Bit Twister wrote:
    Well a quick glance at
    https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/
    indicates something is weird. I hope it was because of the file deletions.

    This at least explains what but not why !!!
    Interesting

    It's normal to have the three lines in the route output.

    On my system, I have two ...
    # route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.10.11 0.0.0.0 UG 5 0 0 eth0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

    The first is for packets going to the internet (Flags set to UG), the second
    is for
    the local lan.

    The 169.254 range is for link local addresses, which I've disabled on my
    system
    by adding a line for my interface ...
    # tail -n 1 /etc/sysconfig/network-scripts/ifcfg-eth0
    NOZEROCONF=yes


    Well, would you look at that. I am impressed. I used to always add that
    for years but discontinued doing it when I thought making other changes
    made it obsolete and I had completely forgot about.

    And what is worse, a quick check of my brain book, gets me
    $ uh zeroconf
    _disable_zeroconf_eth0_ echo NOZEROCONF=no >> /etc/sysconfig/network

    and low and behold,
    $ cat /etc/sysconfig/network
    CRDA_DOMAIN=US
    FORWARD_IPV4=false
    GATEWAY=192.168.11.1
    HOSTNAME=wb.home.test
    NEEDHOSTNAME=no
    NETWORKING=yes
    NOZEROCONF=yes

    Which reminded me of https://bugs.mageia.org/show_bug.cgi?id=18935
    which is when I created the network_changes script to workaround the
    bug and not have to keep making those N*= line changes to each /etc/sysconfig/network-scripts/ifcfg-enp* file.

    Note to faeychild, if you change your hostname, do check the above file.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 00:38:11 2019
    On Fri, 8 Nov 2019 11:11:32 +1100, faeychild wrote:
    On 8/11/19 11:03 am, Bit Twister wrote:
    On Fri, 8 Nov 2019 10:30:56 +1100, faeychild wrote:
    On 8/11/19 9:50 am, Bit Twister wrote:

    I have rebellious thoughts about installing a second Mga7 on a spare
    partition with upgrades and see how it goes.

    I understand. But, may be a good idea when upgrading to mga8.

    Since I do a / backup into my /hotbu prior to update, the
    fallback procedure is to boot other install and run restore_mga7 if update >> is useless/problematic.



    I am amazed at the organization of your setup
    How many partitions and drives do you run?
    $ lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT,LABEL,PARTLABEL
    NAME SIZE TYPE FSTYPE MOUNTPOINT LABEL PARTLABEL
    sda 931.5G disk
    ├─sda1 40G part ext4 mga6 mga6
    ├─sda2 42G part ext4 mga5 mga5
    ├─sda3 40.8G part ext4 / mga7 mga7
    ├─sda4 40.5G part ext4 cauldron cauldron
    ├─sda5 21.5G part ext4 /local local local
    ├─sda6 22.4G part ext4 /accounts accounts accounts
    ├─sda7 59.4G part ext4 /misc misc misc
    ├─sda8 73.2G part ext4 /spare spare spare
    ├─sda9 362.2G part ext4 /vmguest vmguest vmguest
    └─sda10 1M part bios_grub
    sdb 931.5G disk
    ├─sdb1 8G part swap [SWAP] swap swap
    ├─sdb2 20G part ext4 bk_up bk_up
    ├─sdb3 40G part ext4 hotbu hotbu
    ├─sdb4 40G part ext4 cauldron_bkup cauldron_bkup ├─sdb5 400G part ext4 /myth myth myth
    ├─sdb6 40G part ext4 net_ins net_ins
    └─sdb7 40G part ext4 net_ins_bkup net_ins_bkup

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 01:07:21 2019
    On 8/11/19 11:38 am, Bit Twister wrote:


    I am amazed at the organization of your setup
    How many partitions and drives do you run?
    $ lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT,LABEL,PARTLABEL
    NAME SIZE TYPE FSTYPE MOUNTPOINT LABEL PARTLABEL
    sda 931.5G disk
    ├─sda1 40G part ext4 mga6 mga6
    ├─sda2 42G part ext4 mga5 mga5
    ├─sda3 40.8G part ext4 / mga7 mga7
    ├─sda4 40.5G part ext4 cauldron cauldron
    ├─sda5 21.5G part ext4 /local local local
    ├─sda6 22.4G part ext4 /accounts accounts accounts
    ├─sda7 59.4G part ext4 /misc misc misc
    ├─sda8 73.2G part ext4 /spare spare spare
    ├─sda9 362.2G part ext4 /vmguest vmguest vmguest
    └─sda10 1M part bios_grub
    sdb 931.5G disk
    ├─sdb1 8G part swap [SWAP] swap swap
    ├─sdb2 20G part ext4 bk_up bk_up
    ├─sdb3 40G part ext4 hotbu hotbu
    ├─sdb4 40G part ext4 cauldron_bkup cauldron_bkup ├─sdb5 400G part ext4 /myth myth myth
    ├─sdb6 40G part ext4 net_ins net_ins
    └─sdb7 40G part ext4 net_ins_bkup net_ins_bkup


    OK
    you've squeezed every bit into those

    How may VM's do you run in vmguest - it is quite large.
    So is myth- is it mostly recordings?

    I give up :-) "net_ins" has me beat

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 01:17:41 2019
    On 8/11/19 11:32 am, Bit Twister wrote:



    Well, would you look at that. I am impressed. I used to always add that
    for years but discontinued doing it when I thought making other changes
    made it obsolete and I had completely forgot about.

    And what is worse, a quick check of my brain book, gets me
    $ uh zeroconf
    _disable_zeroconf_eth0_ echo NOZEROCONF=no >> /etc/sysconfig/network

    and low and behold,
    $ cat /etc/sysconfig/network
    CRDA_DOMAIN=US
    FORWARD_IPV4=false
    GATEWAY=192.168.11.1
    HOSTNAME=wb.home.test
    NEEDHOSTNAME=no
    NETWORKING=yes
    NOZEROCONF=yes


    Yous is bigger than mine :-(

    ~]$ cat /etc/sysconfig/network
    HOSTNAME=unimatrix.localdomain
    NETWORKING=yes
    CRDA_DOMAIN=AU



    Which reminded me of https://bugs.mageia.org/show_bug.cgi?id=18935
    which is when I created the network_changes script to workaround the
    bug and not have to keep making those N*= line changes to each /etc/sysconfig/network-scripts/ifcfg-enp* file.


    Pub break - maybe And congratulate yourself on all the stuff you have
    kept up with.

    Note to faeychild, if you change your hostname, do check the above file.


    noted.

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri Nov 8 01:23:12 2019
    On Thu, 07 Nov 2019 19:32:16 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote:

    On Thu, 07 Nov 2019 17:55:33 -0500, David W. Hodgins wrote:
    The 169.254 range is for link local addresses, which I've disabled on my system
    by adding a line for my interface ...
    # tail -n 1 /etc/sysconfig/network-scripts/ifcfg-eth0
    NOZEROCONF=yes

    Well, would you look at that. I am impressed. I used to always add that
    for years but discontinued doing it when I thought making other changes
    made it obsolete and I had completely forgot about.

    I couldn't remember how I'd disabled it off hand either, though I did remember that it was something I had disabled. Found it by checking the output of
    "grep -r 169.254 /etc/*" which, among others showed ...

    # grep -B 1 169.254 /etc/sysconfig/network-scripts/ifup-eth
    if [ "${NOZEROCONF}" != "yes" -a "${ISALIAS}" = "no" -a "${REALDEVICE}" != "lo" ]; then
    ip route add 169.254.0.0/16 dev ${REALDEVICE} metric $((1000 + $(cat /sys/class/net/${REALDEVICE}/ifindex))) scope link

    That's what reminded me that it's the NOZEROCONF=yes I'd kept from before upgrading
    that disabled it. This install started as Mageia 3, and has been upgraded each release since then.

    BTW, the systemd network interface renaming from eth# to enp* was done to ensure
    that on systems with more than one network interface card, each card always had the
    same name assigned to it. Prior to that, the naming of the cards were reliant on
    the order the cards responded during boot, and could be inconsistent resulting in the nic name assigned to the cards switching from one boot to another. This system only has one nic, so doesn't possibly have that problem, I've disabled the
    renaming on this install with the kernel command line parameter net.ifnames=0

    That's why this install uses eth0 instead of enp7s0. On my testing installs,
    I do let systemd rename the nic based on it's location on the pci bus, so it's consistent with what most people will see.

    Which reminded me of https://bugs.mageia.org/show_bug.cgi?id=18935
    which is when I created the network_changes script to workaround the
    bug and not have to keep making those N*= line changes to each /etc/sysconfig/network-scripts/ifcfg-enp* file.

    Just checked one of my test installs on a laptop. It has CRDA_DOMAIN=CA in /etc/sysconfig/network, that was created during a clean installation.

    THE CRDA setting is only needed for wireless network interfaces as it is used to
    control which radio channels the device may use. While it can be set for ethernet
    devices, it is not used for anything. As per it's man page, the crda command is
    not intended for manual use, only for use in udev scripts that set the environment
    up as needed for that command.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri Nov 8 01:41:47 2019
    On Thu, 07 Nov 2019 20:23:12 -0500, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

    THE CRDA setting is only needed for wireless network interfaces as it is
    used to
    control which radio channels the device may use. While it can be set for
    ethernet
    devices, it is not used for anything. As per it's man page, the crda command
    is
    not intended for manual use, only for use in udev scripts that set the
    environment
    up as needed for that command.

    I should have added, that most wirless network interfaces now have hard coded CRDA
    domains based on the country that they were sold to, that can not be altered. This it to comply with local laws regarding radio interference.

    On those systems the crda command cannot alter the country setting. A royal pain
    for people who travel.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 02:12:58 2019
    On 7/11/19 6:23 pm, Bit Twister wrote:
    On Thu, 7 Nov 2019 17:51:13 +1100, faeychild wrote:

    GATEWAY=192.168.1.1

    You can use "route -n" when running dhcp, to get gateway ip. Example
    $ route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.11.1 0.0.0.0 UG 0 0 0
    enp3s0
    192.168.11.0 0.0.0.0 255.255.255.0 U 0 0 0
    enp3s0

    There you can see my gateway is 192.168.11.1



    OK We've rebooted.
    And I cant remember why I needed too

    But the network came up Ok and works

    A point of interest. The net-applet tool-tip says

    Ipv6 address: 198.168.1.100

    "a bug" ???



    route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use
    Iface
    0.0.0.0 192.168.1.254 0.0.0.0 UG 5 0 0 enp0s31f6
    192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s31f6


    ifconfig
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 1215 bytes 694682 (678.4 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1400 bytes 169997 (166.0 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xf7700000-f7720000





    I think we've won, sort off.
    The nic is still restarting

    But, like the desktop[ effects, I'll live with it.


    We have hogged the stats again, Bits

    Regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 02:19:01 2019
    On Fri, 8 Nov 2019 12:17:41 +1100, faeychild wrote:
    On 8/11/19 11:32 am, Bit Twister wrote:


    And what is worse, a quick check of my brain book, gets me
    $ uh zeroconf
    _disable_zeroconf_eth0_ echo NOZEROCONF=no >> /etc/sysconfig/network

    and low and behold,
    $ cat /etc/sysconfig/network
    CRDA_DOMAIN=US
    FORWARD_IPV4=false
    GATEWAY=192.168.11.1
    HOSTNAME=wb.home.test
    NEEDHOSTNAME=no
    NETWORKING=yes
    NOZEROCONF=yes


    Yous is bigger than mine :-(

    ~]$ cat /etc/sysconfig/network
    HOSTNAME=unimatrix.localdomain
    NETWORKING=yes
    CRDA_DOMAIN=AU

    Do not worry too much about it.

    I had added lines to be used in other scripts I use to generate system configuration file script changes.

    It is up to you where you want to put the NOZEROCONF=yes line; /etc/sysconfig/network or in each file in /etc/sysconfig/network-scripts/ifcfg-enp*
    to get a simpler route setup.



    Pub break - maybe And congratulate yourself on all the stuff you have
    kept up with.

    It's no big deal. I make the computer work for me instead of it making
    me work for it.

    I have a small ascii database for the bugs I open and a script that
    runs from my install_updates script to tell me to test my open bug
    if there is a new rpm that might have fixed it.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 02:55:16 2019
    On Fri, 8 Nov 2019 12:07:21 +1100, faeychild wrote:
    On 8/11/19 11:38 am, Bit Twister wrote:


    I am amazed at the organization of your setup
    How many partitions and drives do you run?
    $ lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT,LABEL,PARTLABEL
    NAME SIZE TYPE FSTYPE MOUNTPOINT LABEL PARTLABEL
    sda 931.5G disk
    ├─sda1 40G part ext4 mga6 mga6
    ├─sda2 42G part ext4 mga5 mga5
    ├─sda3 40.8G part ext4 / mga7 mga7
    ├─sda4 40.5G part ext4 cauldron cauldron
    ├─sda5 21.5G part ext4 /local local local
    ├─sda6 22.4G part ext4 /accounts accounts accounts
    ├─sda7 59.4G part ext4 /misc misc misc
    ├─sda8 73.2G part ext4 /spare spare spare
    ├─sda9 362.2G part ext4 /vmguest vmguest vmguest
    └─sda10 1M part bios_grub
    sdb 931.5G disk
    ├─sdb1 8G part swap [SWAP] swap swap
    ├─sdb2 20G part ext4 bk_up bk_up
    ├─sdb3 40G part ext4 hotbu hotbu
    ├─sdb4 40G part ext4 cauldron_bkup cauldron_bkup
    ├─sdb5 400G part ext4 /myth myth myth
    ├─sdb6 40G part ext4 net_ins net_ins
    └─sdb7 40G part ext4 net_ins_bkup net_ins_bkup


    OK
    you've squeezed every bit into those

    How may VM's do you run in vmguest - it is quite large.
    $ ls -1 /vmguest/vm/Machines | wc -l
    18
    and was set large to have room for several guests.
    $ df -h /vmguest
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda9 357G 153G 204G 43% /vmguest


    So is myth- is it mostly recordings?

    Pretty much just recorded Over-The-Air tv shows.
    Saved movies, pictures and whatnot are in other partitions.

    Here on the wb node it is just leftover space from when the desktop
    was doing the recordings before I bought a faster desktop to keep up
    with the occasional load when recording more than 6 channels at a time.

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique recordings at a time, and if the channel has sub-channels, myth can also
    record those on the same tuner at the same time.

    Snippet from myth system status on the mtv node at the moment

    590 GB total, 24 GB used, 565 GB (or 98%) free
    201 hours and 30 minutes remaining, using your average rate of 561
    89 hours remaining, using your average rate of 14762 kb/s


    I give up :-) "net_ins" has me beat

    Heheh, that is a network install and can be any release/version
    Usually used for regression testing of my install/change scripts and
    any research needing to see what a non modified install looks like.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 03:22:56 2019
    On Fri, 8 Nov 2019 13:12:58 +1100, faeychild wrote:
    On 7/11/19 6:23 pm, Bit Twister wrote:


    OK We've rebooted.
    And I cant remember why I needed too

    grub change to disable ipv6 and more importantly your static ip
    configuration also still working.


    But the network came up Ok and works

    A point of interest. The net-applet tool-tip says

    Ipv6 address: 198.168.1.100

    "a bug" ???

    A ipv4 value for a ipv6 display/report, Yes.



    I think we've won, sort off.
    The nic is still restarting

    Head slap. Twice, booted mga7/xfce vm guest, ifconfig $_net_nic down,
    got a pop up message nic down, ~10 sec later pop up nic is up.

    So, you have found a bug in my opinion. As a sysadmin, I say when
    I want the nic down, it should stay down. Especially when doing some
    security work and do not want to drop to a non-networking run level.

    Since I am not running network or networkmanager, but systed-networkd,
    the nic stays down when I shut it down.

    Just curious, is your setup a single node network, or do you have other
    nodes on your LAN?

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 04:09:04 2019
    On 8/11/19 2:22 pm, Bit Twister wrote:


    Just curious, is your setup a single node network, or do you have other
    nodes on your LAN?




    Yes the one and only.

    One day I will try to network the printer

    regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 06:08:51 2019
    On Fri, 8 Nov 2019 15:09:04 +1100, faeychild wrote:
    On 8/11/19 2:22 pm, Bit Twister wrote:


    Just curious, is your setup a single node network, or do you have other
    nodes on your LAN?




    Yes the one and only.

    One day I will try to network the printer

    Ah, I had forgotten about that. You should be able to configure the
    printer ethernet connection as
    static ip address as 192.168.1.200
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    dns 8.8.8.8 and 1.1.1.1

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Thereafter you can use the printer alias, example
    ping -c1 printer.

    Oh, yeah, have you changed your domain name to something
    other than .localdomain?


    Keep in mind, if using dhcp with two or more nodes/devices on a lan,
    first node/device up, can/might get the first ip address assignment.

    Your router snippet dump, showed ip leases are obsolete after 24 hours.
    That means without static ip assignments, and you were to have a power
    outage with printer and node up. after 24 your power comes back the node
    ip could be 192.168.1.2 and printer would be 192.168.1.1 if printer
    asks for an ip lease first.





    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 09:33:29 2019
    On 8/11/19 5:08 pm, Bit Twister wrote:


    Ah, I had forgotten about that. You should be able to configure the
    printer ethernet connection as
    static ip address as 192.168.1.200
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    dns 8.8.8.8 and 1.1.1.1

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Is "local.test" an official domain name or just random - can it be
    anything you choose?

    Thereafter you can use the printer alias, example
    ping -c1 printer.

    Oh, yeah, have you changed your domain name to something
    other than .localdomain?

    I am open to suggestions, "localdomain" came from the default host name
    back in the RedHat days - it just stuck


    Your router snippet dump, showed ip leases are obsolete after 24 hours.
    That means without static ip assignments, and you were to have a power outage with printer and node up. after 24 your power comes back the node
    ip could be 192.168.1.2 and printer would be 192.168.1.1 if printer
    asks for an ip lease first.


    Hence your query about other devices on the network.


    Once again it's getting late and silly mistake time
    Tomorrow then

    Regards


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 09:36:57 2019
    On 8/11/19 5:08 pm, Bit Twister wrote:


    Ah, I had forgotten about that. You should be able to configure the
    printer ethernet connection as
    static ip address as 192.168.1.200
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    dns 8.8.8.8 and 1.1.1.1

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Thereafter you can use the printer alias, example
    ping -c1 printer.

    Is it as simple as that. Or does it also require setting up through MCC
    or cups?


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 11:57:29 2019
    On Fri, 8 Nov 2019 20:36:57 +1100, faeychild wrote:
    On 8/11/19 5:08 pm, Bit Twister wrote:


    Ah, I had forgotten about that. You should be able to configure the
    printer ethernet connection as
    static ip address as 192.168.1.200
    net mask as 255.255.255.0
    gateway as 192.168.1.254
    dns 8.8.8.8 and 1.1.1.1

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Thereafter you can use the printer alias, example
    ping -c1 printer.

    Is it as simple as that.

    Yup, pretty much, I have
    $ grep -v '#' /etc/hosts | wc -l
    31
    entries in mine. For the printer
    $ grep ptr /etc/hosts
    192.168.11.190 ptr.home.test ptr



    Or does it also require setting up through MCC

    No, you could use mcc->Network & Internet->Hosts, but easier/faster
    just to use an editor to edit /etc/hosts

    or cups?

    Ah, ha. Me thinks we are in two different conversations.

    The conversation in the past about setting up a network printer, and
    ethernet cable, caused me to assume you had more than one node on the lan.
    For instance a tablet or a laptop and wanted to be able to print from them.

    Whether you stick with single node physical usb/ethernet connection
    directly on your node/desktop, or go with ethernet cable to router,
    you still have to get into cups for setting up access for printing.



    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 12:55:25 2019
    On Fri, 8 Nov 2019 20:33:29 +1100, faeychild wrote:
    On 8/11/19 5:08 pm, Bit Twister wrote:

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Is "local.test" an official domain name

    Please take about 5 minutes or less to read
    https://www.ietf.org/rfc/rfc2606.txt

    or just random- can it be anything you choose?

    Hehehe, your lease file given by your router had
    option domain-name "home.gateway";
    Might not hurt to set lan and router to use whatever domain name
    you chose.

    I refer you to section 5 into the above document.

    What I want to impress upon lurkers/you is you do not want packets/messages/mail/whatnot leaving your system/lan that should
    have stayed on the lan. Go read section 2.

    For awhile I would use ping to verify no one was using the TLD.
    I would assume some code might add .com to the name and at that
    point I could/might get into trouble for causing traffic to that domain.

    Just for fun,
    ping -c1 -w3 localdomain.com
    to see who might be irritated by getting messages destine for unimatrix.localdomain.com

    ping -c1 -w3 lan.com seems to indicate that TODAY it does not exist.
    same for ping -c1 -w3 mylan.com

    Is "local.test" an official domain name

    no, but try
    ping -c1 -w3 local.com

    My recommendation is that you should have a FQDN for every node/device
    on your system, and the TLD should be .test or if you want .invalid
    if you have not bought/have a registered domain.


    I am open to suggestions,

    I had given you three suggestions, using .test as the TLD.
    I do not recommend using .invalid because I have seen an app or two
    not work well with that TLD and when you have a second node, you might
    not be able to communicate between the two.

    "localdomain" came from the default host name
    back in the RedHat days - it just stuck

    I started my first Linux install with Slackware, and
    kinda thought darkstar was handy for a node name.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 19:32:47 2019
    On 8/11/19 11:55 pm, Bit Twister wrote:
    On Fri, 8 Nov 2019 20:33:29 +1100, faeychild wrote:
    On 8/11/19 5:08 pm, Bit Twister wrote:

    add something like
    192.168.1.200 printer.local.test printer
    to /etc/hosts.

    Is "local.test" an official domain name

    Please take about 5 minutes or less to read
    https://www.ietf.org/rfc/rfc2606.txt

    I can see their point.



    or just random- can it be anything you choose?

    Hehehe, your lease file given by your router had
    option domain-name "home.gateway";
    Might not hurt to set lan and router to use whatever domain name
    you chose.

    I refer you to section 5 into the above document.

    What I want to impress upon lurkers/you is you do not want packets/messages/mail/whatnot leaving your system/lan that should
    have stayed on the lan. Go read section 2.

    For awhile I would use ping to verify no one was using the TLD.
    I would assume some code might add .com to the name and at that
    point I could/might get into trouble for causing traffic to that domain.

    Just for fun,
    ping -c1 -w3 localdomain.com
    to see who might be irritated by getting messages destine for unimatrix.localdomain.com

    ~]# ping -c1 -w3 localdomain.com
    PING localdomain.com (67.227.226.241) 56(84) bytes of data.
    64 bytes from 67.227.226.241 (67.227.226.241): icmp_seq=1 ttl=51 time=252 ms

    - --- localdomain.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 251.871/251.871/251.871/0.000 ms

    NOT GOOD!



    ping -c1 -w3 lan.com seems to indicate that TODAY it does not exist.
    same for ping -c1 -w3 mylan.com

    Is "local.test" an official domain name

    no, but try
    ping -c1 -w3 local.com


    ~]# ping -c1 -w3 local.com
    PING local.com (199.191.50.236) 56(84) bytes of data.
    64 bytes from 199.191.50.236 (199.191.50.236): icmp_seq=1 ttl=237
    time=238 ms

    - --- local.com ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 237.572/237.572/237.572/0.000 ms


    My recommendation is that you should have a FQDN for every node/device
    on your system, and the TLD should be .test or if you want .invalid
    if you have not bought/have a registered domain.


    I am open to suggestions,

    I had given you three suggestions, using .test as the TLD.
    I do not recommend using .invalid because I have seen an app or two
    not work well with that TLD and when you have a second node, you might
    not be able to communicate between the two.

    "localdomain" came from the default host name
    back in the RedHat days - it just stuck

    I started my first Linux install with Slackware, and
    kinda thought darkstar was handy for a node name.


    ping -c1 -w3 darkstar.net
    PING darkstar.net (216.239.32.21) 56(84) bytes of data.
    64 bytes from any-in-2015.1e100.net (216.239.32.21): icmp_seq=1 ttl=52 time=33.0 ms

    - --- darkstar.net ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 33.017/33.017/33.017/0.000 ms


    someone thought so too ,Bits

    I shall have to wait for a suitable epiphany to deliver my host name

    Not "mycomputer" :-(

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 19:43:57 2019
    On 8/11/19 10:57 pm, Bit Twister wrote:


    or cups?

    Ah, ha. Me thinks we are in two different conversations.

    Multitasking


    The conversation in the past about setting up a network printer, and
    ethernet cable, caused me to assume you had more than one node on the lan. For instance a tablet or a laptop and wanted to be able to print from them.

    Understandable



    Whether you stick with single node physical usb/ethernet connection
    directly on your node/desktop, or go with ethernet cable to router,
    you still have to get into cups for setting up access for printing.



    Currently it's only Ethernet to the router.
    The printer sits on a spare motherboard USB port.
    The router has a USB port also which unsurprisingly I didn't get working.

    Ethernet from the router to the printer is probably a better way to go


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 20:16:24 2019
    On Sat, 9 Nov 2019 06:32:47 +1100, faeychild wrote:

    I shall have to wait for a suitable epiphany to deliver my host name

    Just to be clear, host name, is not the problem. It is the domain name
    part of the FQDN. Just set the Top Level Domain as .test and that should
    keep local messages from getting past your ISP's gateway and onto the
    internet.

    Example: unimatrix.localdomain.test


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Nov 8 20:21:45 2019
    On 9/11/19 6:43 am, faeychild wrote:

    Back in junk user I realized I hadn't specified any virtual desktops

    When I did, junk had desktop effects and edge triggered desktop switching.

    It's not a problem with Mga7 after all..
    This is a bit of a relief

    Back with faeychild I found that the other, never utilized, edge
    triggered operations all work except any that involve window or desktop manipulation, which are used. HA!

    So later today I will depopulate the ~/HOME directory and start poking
    around.

    I may even use your depopulate script, although I notice that it does
    have a side effect of removing taskbar icons, at least it did in Xfce

    networking is on hold :-)

    Regards






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



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 8 20:48:20 2019
    On Sat, 9 Nov 2019 07:21:45 +1100, faeychild wrote:
    On 9/11/19 6:43 am, faeychild wrote:

    Back in junk user I realized I hadn't specified any virtual desktops

    When I did, junk had desktop effects and edge triggered desktop switching.

    No context. Could have used information about which Desktop Environment (plasma, xfce..) being used.

    Back with faeychild I found that the other, never utilized, edge
    triggered operations all work except any that involve window or desktop manipulation, which are used. HA!

    So later today I will depopulate the ~/HOME directory and start poking around.

    I may even use your depopulate script, although I notice that it does
    have a side effect of removing taskbar icons, at least it did in Xfce

    Hmm, somewhat better context, but I can only guess the removed taskbar
    icons were the ones you added. Icon set is not the same between DE's

    On the "depopulate script" I only guess you are talking about the
    reset_junk script I posted.

    If you modify it and use it on your user account, you will
    lose ALL FILES and configuration settings in $HOME.

    networking is on hold :-)

    I can only guess that is about FQDN change. I have posted the nic down/up problem in the Dev mail list and have not seen anything else to look into.

    As is, I would think you should be able to all printer work through the
    usb connection/cable from printer to computer. No ethernet cable needed.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sat Nov 9 21:43:23 2019
    On 8/11/19 11:55 pm, Bit Twister wrote:


    "localdomain" came from the default host name
    back in the RedHat days - it just stuck

    I started my first Linux install with Slackware, and
    kinda thought darkstar was handy for a node name.


    OK !!

    "Darkstar" got past me. :-)

    I guess it's my turn to fed the Alien.


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 03:21:15 2019
    On 8/11/19 1:55 pm, Bit Twister wrote:


    Here on the wb node it is just leftover space from when the desktop
    was doing the recordings before I bought a faster desktop to keep up
    with the occasional load when recording more than 6 channels at a time.

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique

    I have a Hauppauge Win TV QUAD HD TV Tuner which gives me 4 channels ,
    of course.

    The I pass the "*ts" files through Handbrake to transcode them to the
    same format for uniformaty and then edit the ads / promos and render them

    That's what holds me up now.

    I can't reboot until that finishes



    I give up :-) "net_ins" has me beat

    Heheh, that is a network install and can be any release/version
    Usually used for regression testing of my install/change scripts and
    any research needing to see what a non modified install looks like.

    My observation is that you are "dedicated"

    I've settled on a host name

    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix


    regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 03:27:41 2019
    On 10/11/19 2:21 pm, faeychild wrote:
    On 8/11/19 1:55 pm, Bit Twister wrote:


    Here on the wb node it is just leftover space from when the desktop
    was doing the recordings before I bought a faster desktop to keep up
    with the occasional load when recording more than 6 channels at a time.

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique

    I have a Hauppauge Win TV QUAD HD TV Tuner which gives me 4 channels ,
    of course.

    The I pass the "*ts" files through Handbrake to transcode them to the
    same format   for uniformaty and then edit the ads / promos and render
    them

    That's what holds me up now.

    I can't reboot until that finishes



    I give up :-)  "net_ins" has me beat

    Heheh, that is a network install and can be any release/version
    Usually used for regression testing of my install/change scripts and
    any research needing to see what a non modified install looks like.

    My observation is that you are  "dedicated"

    I've settled on a host name

    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2  unimatrix.cryptid.test  unimatrix


    oops!

    Will that clash with this
    ~]$ cat /etc/sysconfig/network
    HOSTNAME=unimatrix.localdomain
    NETWORKING=yes
    CRDA_DOMAIN=AU


    how many changes do I need to make





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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 04:13:07 2019
    On 9/11/19 7:48 am, Bit Twister wrote:


    I can only guess that is about FQDN change. I have posted the nic down/up problem in the Dev mail list and have not seen anything else to look into.

    As is, I would think you should be able to all printer work through the
    usb connection/cable from printer to computer. No ethernet cable needed.

    Absolutely!! As with most of my problems.
    I'm unsure how to configure


    Also the desktop effects fault is located somewhere in ~/$HOME .config

    Renaming the whole directory clears the problem.
    Now I have to go through it section by section

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 05:08:46 2019
    On 10/11/19 3:13 pm, faeychild wrote:

    Also the desktop effects fault is located somewhere in ~/$HOME .config

    Renaming the whole directory clears the problem.
    Now I have to go through it section by section


    It's ~/$HOME/.config/kwinrc


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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 05:27:23 2019
    On Sun, 10 Nov 2019 15:13:07 +1100, faeychild wrote:
    On 9/11/19 7:48 am, Bit Twister wrote:


    As is, I would think you should be able to all printer work through the
    usb connection/cable from printer to computer. No ethernet cable needed.

    Absolutely!! As with most of my problems.
    I'm unsure how to configure

    Since I have no idea about the printer's vendor/model I can not be of much help.
    My Brother HLL2380DW is easy enough to setup. Brother provides a
    installer script from their site, I run it, it download/installs needed
    rpms, and I answer yes to pretty much everything asked and it
    creates some printer configuration in the cups directory.
    I then sytemctl start cups, launch firefox, up come my homegrown
    index.html where I click https://localhost:631/

    After entering system root and password, clicking Adding Printers and Classes Find new printers, pick the printer, click something that says get
    defaults which pulls paper size and whatnot from the printer.
    Somewhere along the setup I check/tick it as the Default printer.


    Also the desktop effects fault is located somewhere in ~/$HOME .config

    FYI: I would guess that translate to something like
    /home/faeychild/home/faeychild/.config
    Use, ~/.confing or $HOME/.config

    Renaming the whole directory clears the problem.

    Little vague about the "whole directory" thing.
    No idea if you are talking about $HOME or ~/.config

    Now I have to go through it section by section

    Yep, I always found it clears up lots of weird problems for people who
    do upgrades instead of clean installs or have a big Desktop Environment
    update.

    Unlike Plasma, Xfce tells you to wipe ~/.config/(Thunar,xfce4).
    What they do not tell you is that needs to be done while you are
    NOT logged in on your user account. I have to log into junk,
    su - root
    rm -fr /home/bittwister/.config/Thunar
    rm -fr /home/bittwister/.config/xfce4

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 06:24:57 2019
    On 10/11/19 4:27 pm, Bit Twister wrote:


    Since I have no idea about the printer's vendor/model I can not be of much
    help.
    My Brother HLL2380DW is easy enough to setup. Brother provides a
    installer script from their site, I run it, it download/installs needed

    Brother as well

    MFC-9340CDW


    rpms, and I answer yes to pretty much everything asked and it
    creates some printer configuration in the cups directory.
    I then sytemctl start cups, launch firefox, up come my homegrown
    index.html where I click https://localhost:631/

    The driver install script was run soon after installing Mga7 and worked
    fine with printer / scanner on the computer USB port





    Now I have to go through it section by section

    Yep, I always found it clears up lots of weird problems for people who
    do upgrades instead of clean installs or have a big Desktop Environment update.

    Successfully so.

    It was kwinrc in ~/$HOME/.config.
    So nice to have the desktop grid back in operation


    Unlike Plasma, Xfce tells you to wipe ~/.config/(Thunar,xfce4).
    What they do not tell you is that needs to be done while you are
    NOT logged in on your user account. I have to log into junk,
    su - root
    rm -fr /home/bittwister/.config/Thunar
    rm -fr /home/bittwister/.config/xfce4

    I am copacetic with the terrors of the old home directory and a fresh distribution. This is the first time I have had an upgrade trash the
    resident system.
    And there is a new upgrade pending. I'll let it wait a bit

    the extra good news is that we have networked printer :-) :-)


    ping -c3 prnt
    PING prnt.unimatrix.cryptid (192.168.1.200) 56(84) bytes of data.
    64 bytes from prnt.unimatrix.cryptid (192.168.1.200): icmp_seq=1 ttl=255 time=1.68 ms
    64 bytes from prnt.unimatrix.cryptid (192.168.1.200): icmp_seq=2 ttl=255 time=1.47 ms
    64 bytes from prnt.unimatrix.cryptid (192.168.1.200): icmp_seq=3 ttl=255 time=1.32 ms

    - --- prnt.unimatrix.cryptid ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 6ms
    rtt min/avg/max/mdev = 1.322/1.490/1.682/0.151 m


    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix
    192.168.1.200 prnt.unimatrix.cryptid prnt

    104.99.229.118 www.yourtv.com.au
    23.210.81.33 www.bom.gov.au
    216.58.200.99 www.google.com.au
    54.230.240.243 www.westpac.com.au
    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    104.20.13.233 www.whirlpool.net.au
    172.217.167.69 mail.google.com



    BUT we don't have working scanner.
    I wondered does the scanner require a different IP address

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 06:29:47 2019
    On Sun, 10 Nov 2019 14:27:41 +1100, faeychild wrote:
    On 10/11/19 2:21 pm, faeychild wrote:

    I've settled on a host name

    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2  unimatrix.cryptid.test  unimatrix

    Hmmmm, Guessing that is ok at this juncture, especially since
    I have no idea if you have settled on dynamic or static ip addressing.

    Since I use static/fixed ip address I have

    127.0.0.1 localhost.localdomain localhost
    127.0.0.2 mail.home.test mail
    192.168.11.1 gateway.home.test gateway
    192.168.11.132 wb.home.test wb

    the gateway entry allows me to ping gateway to see if lan side
    of router is alive when I do network check/testing.

    oops!

    Will that clash with this
    ~]$ cat /etc/sysconfig/network
    HOSTNAME=unimatrix.localdomain
    NETWORKING=yes
    CRDA_DOMAIN=AU

    Well, I can suggest/recommend that you need to be consent with the
    FQDN, node and domain name throughout your install.

    how many changes do I need to make

    Frap, that information has already been provided and not knowing how
    or what was done so far makes that a bit hard for me to answer.
    Actual value to provide where is a bit much to be precise in name=value instructions.

    To summarize files or directories for any lurkers, in no particular
    order, and may depend on distribution, configuration/applications used,
    and any customizations:

    Note: not a comprehensive list, for example not all wireless locations.

    /etc/httpd/conf/httpd.conf
    /etc/issue*
    /var/ftp/welcome.msg
    /etc/motd
    /etc/issue*
    /etc/hosts
    /etc/resolv.conf
    /etc/hosts.{allow,deny}
    /etc/sysconfig/network
    /etc/hostname
    /etc/HOSTNAME
    /etc/sysconfig/network-scripts/ifcfg-*
    /etc/NetworkManager/*
    /usr/lib/systemd/network/*
    /etc/network/interfaces*

    iptables, ipchains, shorewall are firewall types and you have to
    research those.

    And of course you have to check in your router.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 06:58:48 2019
    On Sun, 10 Nov 2019 17:24:57 +1100, faeychild wrote:


    The driver install script was run soon after installing Mga7 and worked
    fine with printer / scanner on the computer USB port


    BUT we don't have working scanner.
    I wondered does the scanner require a different IP address

    Sounds like you may have not install some scanner apps.
    $ grep sane *print* | grep rpm
    install_printer: x_urpmi sane-frontends ! Graphical frontend to SANE​ install_printer: x_urpmi xsane ! Frontend for the SANE scanner interface​ install_printer: x_urpmi saned ! local and remote scanner, digital, video device access
    install_printer: x_urpmi xsane-gimp ! GIMP plug-in which provides the SANE

    Note: x_urpmi is a custome wrapper around urpmi.


    the extra good news is that we have networked printer :-) :-)


    ping -c3 prnt
    PING prnt.unimatrix.cryptid (192.168.1.200) 56(84) bytes of data.

    Just to be clear, is it a usb connection from printer to computer
    or ethernet cable from printer to router?


    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix
    192.168.1.200 prnt.unimatrix.cryptid prnt

    Well that sucks, a bit. Please get this in your head.

    A Fully Qualified Domain Name (FQDN) is made up of a node name and
    your domain name. Your domain name is cryptid.test and you have
    two nodes defined, unimatrix and prnt

    As a result, I suggest it should be
    192.168.1.200 prnt.cryptid.test prnt



    104.99.229.118 www.yourtv.com.au
    23.210.81.33 www.bom.gov.au
    216.58.200.99 www.google.com.au
    54.230.240.243 www.westpac.com.au
    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    104.20.13.233 www.whirlpool.net.au
    172.217.167.69 mail.google.com

    I see you have also disregarded my advice to not hard code ip address
    for external sites. :-(

    They can change over time. Quick check from here in the USA.
    $ ping -c1 www.yourtv.com.au| head -1
    PING e5589.dscg.akamaiedge.net (23.76.193.120) 56(84) bytes of data.

    Indicates your hosts file is a bit obsolete. Go ahead and comment out
    your entry in /etc/hosts, Example
    # 104.99.229.118 www.yourtv.com.au
    save change and
    ping -c1 www.yourtv.com.au | head -1
    and check if ip is still the same.

    Even if ip address is same, I still recommend not setting ip addresses
    in /etc/hosts, unless you have a script to keep it in sync with the
    real world.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 07:56:15 2019
    On 10/11/19 5:58 pm, Bit Twister wrote:
    On Sun, 10 Nov 2019 17:24:57 +1100, faeychild wrote:


    The driver install script was run soon after installing Mga7 and worked
    fine with printer / scanner on the computer USB port


    BUT we don't have working scanner.
    I wondered does the scanner require a different IP address

    Sounds like you may have not install some scanner apps.
    $ grep sane *print* | grep rpm
    install_printer: x_urpmi sane-frontends ! Graphical frontend to SANE​ install_printer: x_urpmi xsane ! Frontend for the SANE scanner interface​ install_printer: x_urpmi saned ! local and remote scanner, digital, video
    device access
    install_printer: x_urpmi xsane-gimp ! GIMP plug-in which provides the SANE

    Note: x_urpmi is a custome wrapper around urpmi.


    ~]# grep sane *print* | grep rpm
    grep: *print*: No such file or directory


    I have installed all four sane rpm's




    the extra good news is that we have networked printer :-) :-)


    ping -c3 prnt
    PING prnt.unimatrix.cryptid (192.168.1.200) 56(84) bytes of data.

    Just to be clear, is it a usb connection from printer to computer
    or ethernet cable from printer to router?


    It is now Ethernet.




    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix
    192.168.1.200 prnt.unimatrix.cryptid prnt

    Well that sucks, a bit. Please get this in your head.

    My error I got that way trying various arrangement with MCC printer setup

    ipp://prnt.cryptid.test/ipp

    The crazy one worked too



    A Fully Qualified Domain Name (FQDN) is made up of a node name and
    your domain name. Your domain name is cryptid.test and you have
    two nodes defined, unimatrix and prnt

    As a result, I suggest it should be
    192.168.1.200 prnt.cryptid.test prnt



    104.99.229.118 www.yourtv.com.au
    23.210.81.33 www.bom.gov.au
    216.58.200.99 www.google.com.au
    54.230.240.243 www.westpac.com.au
    23.202.160.37 www.thelott.com
    172.217.167.78 www.youtube.com
    106.10.248.150 www.yahoo.mail.com
    104.20.13.233 www.whirlpool.net.au
    172.217.167.69 mail.google.com

    I see you have also disregarded my advice to not hard code ip address
    for external sites. :-(

    I haven't immediately gotten around to all changes yet


    They can change over time. Quick check from here in the USA.
    $ ping -c1 www.yourtv.com.au| head -1
    PING e5589.dscg.akamaiedge.net (23.76.193.120) 56(84) bytes of data.

    I have been stung before. But I found that I could still get to google
    when the ISP's DNS fell over.

    Indicates your hosts file is a bit obsolete. Go ahead and comment out
    your entry in /etc/hosts, Example
    # 104.99.229.118 www.yourtv.com.au
    save change and

    I've edited - three entries only.

    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix
    192.168.1.200 prnt.cryptid.test prn


    I suppose it should be 127.0.0.1 localhost.localdomain localhost

    ping -c1 www.yourtv.com.au | head -1
    and check if ip is still the same.

    ping -c1 www.yourtv.com.au | head -1
    PING e5589.dscg.akamaiedge.net (104.99.229.118) 56(84) bytes of data.

    Even if ip address is same, I still recommend not setting ip addresses
    in /etc/hosts, unless you have a script to keep it in sync with the
    real world.

    How is it that your address for "yourtv" is different?

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 08:27:40 2019
    On Sun, 10 Nov 2019 18:56:15 +1100, faeychild wrote:
    On 10/11/19 5:58 pm, Bit Twister wrote:
    On Sun, 10 Nov 2019 17:24:57 +1100, faeychild wrote:


    The driver install script was run soon after installing Mga7 and worked
    fine with printer / scanner on the computer USB port


    BUT we don't have working scanner.
    I wondered does the scanner require a different IP address

    Sounds like you may have not install some scanner apps.
    $ grep sane *print* | grep rpm
    install_printer: x_urpmi sane-frontends ! Graphical frontend to SANE​
    install_printer: x_urpmi xsane ! Frontend for the SANE scanner interface​
    install_printer: x_urpmi saned ! local and remote scanner, digital, video device access
    install_printer: x_urpmi xsane-gimp ! GIMP plug-in which provides the SANE >>
    Note: x_urpmi is a custome wrapper around urpmi.


    ~]# grep sane *print* | grep rpm
    grep: *print*: No such file or directory

    Yup, since I script all my system changes, I would be thoroughly impressed
    you would find a install_printer file, in /root no less.
    I did not post that I had done a cd /local/bin
    where /local/ is a separate partition where I store all my system wide
    custom generated scripts.



    I have installed all four sane rpm's

    Speaking of custom scripts, I wonder how you are going about documenting
    all your changes.



    It is now Ethernet.

    Great, otherwise I had no idea how that could have worked via a usb connection.


    My error I got that way trying various arrangement with MCC printer setup

    ipp://prnt.cryptid.test/ipp

    The crazy one worked too

    Which is because it was in /etc/hosts.


    I see you have also disregarded my advice to not hard code ip address
    for external sites. :-(

    I haven't immediately gotten around to all changes yet

    Ok, just checking.



    They can change over time. Quick check from here in the USA.
    $ ping -c1 www.yourtv.com.au| head -1
    PING e5589.dscg.akamaiedge.net (23.76.193.120) 56(84) bytes of data.

    I have been stung before. But I found that I could still get to google
    when the ISP's DNS fell over.

    Yep, or possible problem when mode/router gets cracked.
    A little safer when using named on your system, or using public DNS
    servers.

    Indicates your hosts file is a bit obsolete. Go ahead and comment out
    your entry in /etc/hosts, Example
    # 104.99.229.118 www.yourtv.com.au
    save change and

    I've edited - three entries only.

    cat /etc/hosts
    # generated by drakhosts
    127.0.0.1 localhost
    127.0.0.2 unimatrix.cryptid.test unimatrix
    192.168.1.200 prnt.cryptid.test prn


    I suppose it should be 127.0.0.1 localhost.localdomain localhost

    I did that just for consistency sake.


    ping -c1 www.yourtv.com.au | head -1
    and check if ip is still the same.

    ping -c1 www.yourtv.com.au | head -1
    PING e5589.dscg.akamaiedge.net (104.99.229.118) 56(84) bytes of data.

    Even if ip address is same, I still recommend not setting ip addresses
    in /etc/hosts, unless you have a script to keep it in sync with the
    real world.

    How is it that your address for "yourtv" is different?

    That is somewhat the point I was trying to make. ip address can vary
    for several reasons. Look at this, it was

    PING e5589.dscg.akamaiedge.net (23.76.193.120) 56(84) bytes of data.
    and now it is

    $ ping -c1 www.yourtv.com.au | head -1
    PING e5589.dscg.akamaiedge.net (23.11.216.226) 56(84) bytes of data.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 09:27:59 2019
    On 10/11/19 7:27 pm, Bit Twister wrote:




    I have installed all four sane rpm's

    Speaking of custom scripts, I wonder how you are going about documenting
    all your changes.



    Ah No! The best I've managed is to cut paste the interesting commands
    and instructions


    It is now Ethernet.

    Great, otherwise I had no idea how that could have worked via a usb
    connection.


    My error I got that way trying various arrangement with MCC printer setup

    ipp://prnt.cryptid.test/ipp

    The crazy one worked too

    Which is because it was in /etc/hosts.

    Interesting. So as long as the errors are internally consistent across
    the system, it can work.



    How is it that your address for "yourtv" is different?

    That is somewhat the point I was trying to make. ip address can vary
    for several reasons. Look at this, it was

    PING e5589.dscg.akamaiedge.net (23.76.193.120) 56(84) bytes of data.
    and now it is

    $ ping -c1 www.yourtv.com.au | head -1
    PING e5589.dscg.akamaiedge.net (23.11.216.226) 56(84) bytes of data.


    akamaiedge.net is a content provider. Ah well that makes a bit more sense.


    I may have to tackle the scanner tomorrow


    Regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 09:44:58 2019
    On Sun, 10 Nov 2019 20:27:59 +1100, faeychild wrote:
    On 10/11/19 7:27 pm, Bit Twister wrote:

    My error I got that way trying various arrangement with MCC printer setup >>>
    ipp://prnt.cryptid.test/ipp

    The crazy one worked too

    Which is because it was in /etc/hosts.

    Interesting. So as long as the errors are internally consistent across
    the system, it can work.

    Hmmm, I really do not like that "theory" especially in light of the
    current circumstance.

    What I can say is you do have a nice coincidence which caused no
    noticeable problem at this time, in respect to the printer.

    If it were me, I would not be happy until I had check directories
    for any files needing/using your old domain name.

    Before I forget it, what is the current setup for enp0s31f6 ip address,
    static or dynamic/dhcp?


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 11:26:36 2019
    On 10/11/19 8:44 pm, Bit Twister wrote:
    On Sun, 10 Nov 2019 20:27:59 +1100, faeychild wrote:
    On 10/11/19 7:27 pm, Bit Twister wrote:

    My error I got that way trying various arrangement with MCC printer setup >>>>
    ipp://prnt.cryptid.test/ipp

    The crazy one worked too

    Which is because it was in /etc/hosts.

    Interesting. So as long as the errors are internally consistent across
    the system, it can work.

    Hmmm, I really do not like that "theory" especially in light of the
    current circumstance.

    Not to comfortable with it myself


    What I can say is you do have a nice coincidence which caused no
    noticeable problem at this time, in respect to the printer.

    I don't like co-incidences. They cause myths and superstitions

    If it were me, I would not be happy until I had check directories
    for any files needing/using your old domain name.

    I was wondering if / when I would be struck down with any possible knock
    on effects from the name changes.



    Before I forget it, what is the current setup for enp0s31f6 ip address, static or dynamic/dhcp?


    It's static

    cat /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
    DEVICE=enp0s31f6
    BOOTPROTO=static
    IPADDR=192.168.1.100
    NETMASK=255.255.255.0
    GATEWAY=192.168.1.254
    ONBOOT=yes
    METRIC=5
    MII_NOT_SUPPORTED=no
    USERCTL=yes
    DNS1=8.8.8.8
    DNS2=1.1.1.1
    RESOLV_MODS=no
    LINK_DETECTION_DELAY=6
    IPV6INIT=no
    IPV6TO4INIT=no
    ACCOUNTING=no


    regards

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 13:21:52 2019
    On Sun, 10 Nov 2019 22:26:36 +1100, faeychild wrote:

    I was wondering if / when I would be struck down with any possible knock
    on effects from the name changes.

    Just depends on what happens when and where you are at now.

    Now that all LAN nodes have static ip, at this point, I will assume
    that any network configuration problems, should show up after
    next boot, if any. If so, location of FQDN, domain should be easy to
    run down.

    Offhand, /etc/hostname, /etc/resolv.conf ,/etc/sysconfig/network and /etc/hosts
    is all I can think of, in your setup, for cryptid.test problems.

    Since you have indicated static ip for unimatrix I suggest /etc/hosts
    should have
    192.168.1.100 unimatrix.cryptid.test unimatrix
    not 127.0.0.2 unimatrix.cryptid.test unimatrix

    While in there, add
    192.168.1.254 gateway.cryptid.test gateway

    That way if you have internet connectivity problems, a quick
    ping -c1 gateway, will tell you everything is good upto/at the
    LAN side of your modem/router.

    If you were to look around in your router, you might find the ip address
    of the WAN side of router and its gateway.

    I placed those in /etc/hosts so I could ping them to see if that is
    where my network is broke when I can not get internet connectivity.
    If I am not mistaken, you might find that the router's WAN ip is the
    same as your internet ip address found with
    wget -qO - http://icanhazip.com

    If so, you could add something like
    46.153.224.69 ISP.needs.2.fix_this myip
    46.159.228.1 isp-gateway ispgw

    With that I can ping -c1 myip to know if I can get to WAN side of router
    and if passes, ping -c1 ispgw, to see if router can get to ISP's gateway
    on my assigned segment.

    If not, I power cycle, the router, and try again. Still broke, get into router's web page and check if ip/gateway have changed. If so, fix
    /etc/hosts, and test again.

    If information is still valid in router, I know the problem is upstream starting from the wire hooked to the modem.

    Tell me, a little bit about that, is it a modem/router box, or a
    modem box and a router box?


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Nov 10 19:14:28 2019
    On 11/11/19 12:21 am, Bit Twister wrote:
    On Sun, 10 Nov 2019 22:26:36 +1100, faeychild wrote:

    I was wondering if / when I would be struck down with any possible knock
    on effects from the name changes.

    Just depends on what happens when and where you are at now.

    Now that all LAN nodes have static ip, at this point, I will assume
    that any network configuration problems, should show up after
    next boot, if any. If so, location of FQDN, domain should be easy to
    run down.

    Offhand, /etc/hostname, /etc/resolv.conf ,/etc/sysconfig/network and
    /etc/hosts
    is all I can think of, in your setup, for cryptid.test problems.

    Since you have indicated static ip for unimatrix I suggest /etc/hosts
    should have
    192.168.1.100 unimatrix.cryptid.test unimatrix
    not 127.0.0.2 unimatrix.cryptid.test unimatrix

    While in there, add
    192.168.1.254 gateway.cryptid.test gateway

    That way if you have internet connectivity problems, a quick
    ping -c1 gateway, will tell you everything is good upto/at the
    LAN side of your modem/router.

    If you were to look around in your router, you might find the ip address
    of the WAN side of router and its gateway.

    I placed those in /etc/hosts so I could ping them to see if that is
    where my network is broke when I can not get internet connectivity.
    If I am not mistaken, you might find that the router's WAN ip is the
    same as your internet ip address found with
    wget -qO - http://icanhazip.com

    If so, you could add something like
    46.153.224.69 ISP.needs.2.fix_this myip
    46.159.228.1 isp-gateway ispgw

    With that I can ping -c1 myip to know if I can get to WAN side of router
    and if passes, ping -c1 ispgw, to see if router can get to ISP's gateway
    on my assigned segment.

    If not, I power cycle, the router, and try again. Still broke, get into router's web page and check if ip/gateway have changed. If so, fix /etc/hosts, and test again.

    If information is still valid in router, I know the problem is upstream starting from the wire hooked to the modem.

    Tell me, a little bit about that, is it a modem/router box, or a
    modem box and a router box?



    The full title of the modem /router is


    BiPAC 7800NXL
    3G/4G LTE (Wireless-N) (VPN)
    ADSL2+/Fibre Broadband Router


    I have changed the subject title because it has gone off topic.

    Later this morning-today I will make all those changes. I am up early to
    get some uninterrupted time (6:00 am)


    And the latest upgrade has rebooted - so far so good


    Regards



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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 20:13:31 2019
    On Mon, 11 Nov 2019 06:14:28 +1100, faeychild wrote:
    On 11/11/19 12:21 am, Bit Twister wrote:

    Tell me, a little bit about that, is it a modem/router box, or a
    modem box and a router box?



    The full title of the modem /router is


    BiPAC 7800NXL
    3G/4G LTE (Wireless-N) (VPN)
    ADSL2+/Fibre Broadband Router

    Ok, nice to know, but trying to get a feel for actual physical hookup.


    1. ADSL makes me think of telephone pole with telephone wire to router
    and ethernet to desktop.

    2. Fiber makes me think of fiber from the curb, to ONT box on building,
    with coax or ethernet to router and ethernet to desktop.

    3. Broadband makes me think of coax cable from telephone pole to a
    modem/router and ethernet to desktop.

    4. Broadband makes me think of coax cable from telephone pole to a
    modem with ethernet to a router, then ethernet to desktop.

    When that is known, you can figure out what the ip addresse is at each
    end of each connection. Pinging each of those addresses leads you to
    where the first break is in your internet connection path.

    Tell me which setup do you have?

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 10 20:35:01 2019
    On Mon, 11 Nov 2019 06:14:28 +1100, faeychild wrote:

    No need for [ATT-BitTwister]. I read all posts for the groups I lurk in.
    That assumes I have not kill filed the poster or the thread.

    I use slrn as my Usenet reader and your post looks like
    83:[faeychild ] [ATT-BitTwister] networking printer.

    The 83 tells me it is the 83 post of a thread, and since I see the
    references in the header I noticed you just changed
    the Subject instead of starting a new thread. :(

    And, I am guessing it did not help your thunderbird indention of list
    within the thread. :D

    You should have started the reply and pasted what you want to work with
    into a file, abort the reply, start/create the new thread, then paste
    in the contents from the file into your new post and make your changes.

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Daniel60@2:250/1 to All on Tue Nov 12 11:30:49 2019
    Bit Twister wrote on 8/11/2019 1:55 PM:

    <Snip>

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique recordings at a time, and if the channel has sub-channels, myth can also record those on the same tuner at the same time.

    Snippet from myth system status on the mtv node at the moment

    590 GB total, 24 GB used, 565 GB (or 98%) free
    201 hours and 30 minutes remaining, using your average rate of 561
    89 hours remaining, using your average rate of 14762 kb/s

    Gee Whiz!! If I didn't know that you, Bit Twister, seem to spend a lot
    of time here-abouts, I'd say you spend WAAAYYYY too much time watching
    T.V., BT!! ;-)

    --
    Daniel

    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Nov 12 14:31:01 2019
    On Tue, 12 Nov 2019 22:30:49 +1100, Daniel60 wrote:
    Bit Twister wrote on 8/11/2019 1:55 PM:

    <Snip>

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique
    recordings at a time, and if the channel has sub-channels, myth can also
    record those on the same tuner at the same time.

    Snippet from myth system status on the mtv node at the moment

    590 GB total, 24 GB used, 565 GB (or 98%) free
    201 hours and 30 minutes remaining, using your average rate of 561
    89 hours remaining, using your average rate of 14762 kb/s

    Gee Whiz!! If I didn't know that you, Bit Twister, seem to spend a lot
    of time here-abouts, I'd say you spend WAAAYYYY too much time watching
    T.V., BT!! ;-)

    Hey, I gotta have something to do while lurking on Usenet. :)

    Current average is around twenty minutes of commercials per hour of show.
    I just fast forward and save lots of time.


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Nov 12 23:55:59 2019
    On 11/11/19 7:35 am, Bit Twister wrote:


    You should have started the reply and pasted what you want to work with
    into a file, abort the reply, start/create the new thread, then paste
    in the contents from the file into your new post and make your changes.



    Yep! it's that learning curve again and a demented perception that it
    worked the last time I did something similar.

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


    --- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Daniel60@2:250/1 to All on Thu Nov 14 10:21:25 2019
    Bit Twister wrote on 13/11/2019 1:31 AM:
    On Tue, 12 Nov 2019 22:30:49 +1100, Daniel60 wrote:
    Bit Twister wrote on 8/11/2019 1:55 PM:

    <Snip>

    I have 5 dual channel SiliconDust network tv tuners giving me 10 unique
    recordings at a time, and if the channel has sub-channels, myth can also >>> record those on the same tuner at the same time.

    Snippet from myth system status on the mtv node at the moment

    590 GB total, 24 GB used, 565 GB (or 98%) free
    201 hours and 30 minutes remaining, using your average rate of 561
    89 hours remaining, using your average rate of 14762 kb/s

    Gee Whiz!! If I didn't know that you, Bit Twister, seem to spend a lot
    of time here-abouts, I'd say you spend WAAAYYYY too much time watching
    T.V., BT!! ;-)

    Hey, I gotta have something to do while lurking on Usenet. :)

    Current average is around twenty minutes of commercials per hour of show.
    I just fast forward and save lots of time.

    Ditto with me!! Although most of my live T.V. watching is on Government
    funded channels (no advertising) which only 'Top and Tail' the programs
    with "Self Promotion" (i.e. not "ads"!!) stuff! ;-p

    --
    Daniel

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