I have noticed that launching either Firefox or Thunderbird will
activate the wired ethernet if it is down.
A new feature perhaps
On Wed, 23 Oct 2019 08:28:49 +1100, faeychild wrote:
I have noticed that launching either Firefox or Thunderbird will
activate the wired ethernet if it is down.
A new feature perhaps
I would have to agree with your guess. I have a hourly cron job to
test my internet connection. Helps reduce my stress level when something
does not work and greatly reduces my debugging time to localize a problem.
On 23/10/19 11:36 am, Bit Twister wrote:
On Wed, 23 Oct 2019 08:28:49 +1100, faeychild wrote:
I have noticed that launching either Firefox or Thunderbird will
activate the wired ethernet if it is down.
A new feature perhaps
I would have to agree with your guess. I have a hourly cron job to
test my internet connection. Helps reduce my stress level when something
does not work and greatly reduces my debugging time to localize a problem.
No I am wrong. I noticed tonight when I turned the network off, it
restarts in about 15 seconds.
Apparently the network must be up!
I am at a loss to understand why provide an option to take down the
network only to have it automatically restart it again?
Never a dull moment, Bits
I do not have Mga7 so cannot check my suspicion, but I suspect that
there is an option in the setup of the ethernet which tells it to
restart if it goes down. EG, the "start connection at boot" option in
Network Control.
On 23/10/19 11:49 pm, William Unruh wrote:
I do not have Mga7 so cannot check my suspicion, but I suspect that
there is an option in the setup of the ethernet which tells it to
restart if it goes down. EG, the "start connection at boot" option in
Network Control.
I think you are on the right page William
The "right click" menu includes watched interface and launch at start up. After trying them all I unchecked "launch at start up" which disabled
the network applet on the task bar.
There is no option to return it to the task bar
It's not in "system tray > entries" either
It has got to be there somewhere
Regards
On 23/10/19 11:49 pm, William Unruh wrote:
I do not have Mga7 so cannot check my suspicion, but I suspect that
there is an option in the setup of the ethernet which tells it to
restart if it goes down. EG, the "start connection at boot" option in
Network Control.
I think you are on the right page William
The "right click" menu includes watched interface and launch at start up. After trying them all I unchecked "launch at start up" which disabled
the network applet on the task bar.
There is no option to return it to the task bar
It's not in "system tray > entries" either
It has got to be there somewhere
Regards
On 2019-10-23, faeychild <faeychild@nomail.afraid.org> wrote:
On 23/10/19 11:49 pm, William Unruh wrote:
I do not have Mga7 so cannot check my suspicion, but I suspect that
there is an option in the setup of the ethernet which tells it to
restart if it goes down. EG, the "start connection at boot" option in
Network Control.
I think you are on the right page William
The "right click" menu includes watched interface and launch at start up. >> After trying them all I unchecked "launch at start up" which disabled
the network applet on the task bar.
What are you running? Network Center? Network Manager?
systemd-networking?
Mageia's default is (usually) Network Center.
Have you tried "Add widgets"?
bliss
And with the netapplet icon it's "right click > settings > watched
interface > auto detect.
Which is how it was originally, only now it is NOT auto restarting
On 24/10/19 6:15 am, William Unruh wrote:
On 2019-10-23, faeychild <faeychild@nomail.afraid.org> wrote:
On 23/10/19 11:49 pm, William Unruh wrote:
I do not have Mga7 so cannot check my suspicion, but I suspect that
there is an option in the setup of the ethernet which tells it to
restart if it goes down. EG, the "start connection at boot" option in
Network Control.
I think you are on the right page William
The "right click" menu includes watched interface and launch at start up. >>> After trying them all I unchecked "launch at start up" which disabled
the network applet on the task bar.
What are you running? Network Center? Network Manager?
systemd-networking?
Mageia's default is (usually) Network Center.
I am running what ever the net-applet in the task bar controls. I think
it's "Manager"
SOLVED I have the icon back in the task bar
it's in $HOME .net_applet > AUTOSTART=TRUE
And with the netapplet icon it's "right click > settings > watched
interface > auto detect.
Which is how it was originally, only now it is NOT auto restarting
Coffee time I think
I'll test it during the day.
Regards
No I am wrong. I noticed tonight when I turned the network off, it
restarts in about 15 seconds.
Apparently the network must be up!
I am at a loss to understand why provide an option to take down the
network only to have it automatically restart it again?
On 23/10/19 10:15 pm, faeychild wrote:
No I am wrong. I noticed tonight when I turned the network off, it
restarts in about 15 seconds.
Apparently the network must be up!
I am at a loss to understand why provide an option to take down the
network only to have it automatically restart it again?
[SOLVED] Give up and unplug it!!
The sort of solution I would applaud, but have
you set the User Control of the Network in MCC?
bliss
On 25/10/19 7:00 am, Bobbie Sellers wrote:
The sort of solution I would applaud, but have
you set the User Control of the Network in MCC?
bliss
If you mean allow user to control the network - yes.
I have an update pending - so you never know
On 25/10/19 11:54 am, faeychild wrote:
On 25/10/19 7:00 am, Bobbie Sellers wrote:I removed the Ethernet connection.
The sort of solution I would applaud, but have
you set the User Control of the Network in MCC?
bliss
If you mean allow user to control the network - yes.
I have an update pending - so you never know
I rebooted the computer and the Ethernet connection was re-established.
There is definitely some very controlling interference going with
Mageia. Why am I am reminded of Windows.
On 24/10/19 6:36 am, faeychild wrote:
And with the netapplet icon it's "right click > settings > watched
interface > auto detect.
Which is how it was originally, only now it is NOT auto restarting
Nope It's still restarting
"settings > watched interface" has no effect.
I prefer the option of controlling my interface. Having it auto restart
is a bit too Windows for me.
Since today's update, the network requires root password to shut down.
It still re spawns about 15 second after
Oddly no one else experiences this
On 25/10/19 11:54 am, faeychild wrote:
On 25/10/19 7:00 am, Bobbie Sellers wrote:I removed the Ethernet connection.
The sort of solution I would applaud, but have
you set the User Control of the Network in MCC?
bliss
If you mean allow user to control the network - yes.
I have an update pending - so you never know
I rebooted the computer and the Ethernet connection was re-established.
There is definitely some very controlling interference going with
Mageia. Why am I am reminded of Windows.
On 24/10/19 7:30 am, faeychild wrote:
On 24/10/19 6:36 am, faeychild wrote:
And with the netapplet icon it's "right click > settings > watched
interface > auto detect.
Which is how it was originally, only now it is NOT auto restarting
Nope It's still restarting
"settings > watched interface" has no effect.
I prefer the option of controlling my interface. Having it auto restart
is a bit too Windows for me.
Since today's update, the network requires root password to shut down.
It still re spawns about 15 second after
Oddly no one else experiences this
On Fri, 25 Oct 2019 18:36:01 +1100, faeychild wrote:NetworkManager
Since today's update, the network requires root password to shut down.
It still re spawns about 15 second after
Oddly no one else experiences this
Personally, I need the network up, and no, my nic stays down if I shut
it down.
Command used,
ip link set $_net_nic down
Then again, I am not running plasma, nor am I using Network or
for nic management. I am using systemd-netowrkd for network management.
If you were to
grep NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-*
and see yes, then I suggest you are using NetworkManager for control
of that device
A quick glance through /usr/share/doc/initscripts/sysconfig.txt indicates ONBOOT=xxx only controls whether to bring the device up during boot.directory.
First thing I would try would be to set/add
HOTPLUG=no
NM_CONTROLLED=no
Then bring it up/down and see if it comes back up.
If it comes back up, then I suggest the next person of interest is
systemd service/trigger or some app you have set to run in your DE
(Desktop Environment) autostart directory.
If so, next thing for you to research would be results from
systemctl --all | grep -i network
and remove anything having to do with network from your DE autostart
On 2019-10-25, Bit Twister <BitTwister@mouse-potato.com> wrote:
On Fri, 25 Oct 2019 18:36:01 +1100, faeychild wrote:
Since today's update, the network requires root password to shut down.
It still re spawns about 15 second after
Oddly no one else experiences this
Personally, I need the network up, and no, my nic stays down if I shut
it down.
Command used,
ip link set $_net_nic down
Then again, I am not running plasma, nor am I using Network or NetworkManager
for nic management. I am using systemd-netowrkd for network management.
If you were to
grep NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-*
and see yes, then I suggest you are using NetworkManager for control
of that device
He has decided that he is using Network Center, the Mageia scripts for network control.
Personally, I need the network up, and no, my nic stays down if I shut
it down.
Command used,
ip link set $_net_nic down
Then again, I am not running plasma, nor am I using Network orNetworkManager
for nic management. I am using systemd-netowrkd for network management.
If you were to
grep NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-*
and see yes, then I suggest you are using NetworkManager for control
of that device.
A quick glance through /usr/share/doc/initscripts/sysconfig.txt indicates ONBOOT=xxx only controls whether to bring the device up during boot.
First thing I would try would be to set/add
HOTPLUG=no
NM_CONTROLLED=no
Then bring it up/down and see if it comes back up.
If it comes back up, then I suggest the next person of interest is
systemd service/trigger or some app you have set to run in your DE
(Desktop Environment) autostart directory.
If so, next thing for you to research would be results from
systemctl --all | grep -i network
Since today's update, the network requires root password to shut down.
It still re spawns about 15 second after
Oddly no one else experiences this
On 10/24/19 9:47 PM, faeychild wrote:
On 25/10/19 11:54 am, faeychild wrote:On my desktops with an Ethernet connection, I've always found that a
On 25/10/19 7:00 am, Bobbie Sellers wrote:I removed the Ethernet connection.
The sort of solution I would applaud, but have
you set the User Control of the Network in MCC?
bliss
If you mean allow user to control the network - yes.
I have an update pending - so you never know
I rebooted the computer and the Ethernet connection was re-established.
There is definitely some very controlling interference going with
Mageia. Why am I am reminded of Windows.
generic Internet connection is established on the first boot after an install, whether I personally created and configured it or not. On those machines that can use either wifi or Ethernet, wifi is not automatic.
I've always thought that was expected behavior, something to handhold
the inexperienced. I never tried to remove it, because I never wanted to.
TJ
On Fri, 25 Oct 2019 19:25:07 -0000 (UTC), William Unruh wrote:
On 2019-10-25, Bit Twister <BitTwister@mouse-potato.com> wrote:
On Fri, 25 Oct 2019 18:36:01 +1100, faeychild wrote:
Since today's update, the network requires root password to shut down. >>>> It still re spawns about 15 second after
Oddly no one else experiences this
Personally, I need the network up, and no, my nic stays down if I shut
it down.
Command used,
ip link set $_net_nic down
Then again, I am not running plasma, nor am I using Network or NetworkManager
for nic management. I am using systemd-netowrkd for network management.
If you were to
grep NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-*
and see yes, then I suggest you are using NetworkManager for control
of that device
He has decided that he is using Network Center, the Mageia scripts for
network control.
Yes I have been following the thread.
At this point, I do not care what he is using to control the network.
I am more interested in finding out what is in control of the network devices.file.
Default is Network Manager unless you select No to Allow interface to
be controlled by the Network Manager.
I that case you should see NM_CONTROLLED=no in the device configuration
On 25/10/19 8:17 pm, Bit Twister wrote:
Morning Bits
Personally, I need the network up, and no, my nic stays down if I shut
it down.
Command used,
ip link set $_net_nic down
~]# /usr/sbin/ip link set $_net_nic down
Not enough information: "dev" argument is required.
I assume "$_net_nic down"
is one of your scripts ?
~]$ grep NM_CONTROLLED /etc/sysconfig/network-scripts/ifcfg-* /etc/sysconfig/network-scripts/ifcfg-enp0s31f6:NM_CONTROLLED=no
~]# systemctl --all | grep -i networkconfiguration from initramfs
fedora-import-state.service loaded inactive dead Import network
network-up.service loaded active exited Wait for the hotpluggednetwork to be up
network.service loaded active running Bring up/down networkingSynchronization
systemd-timesyncd.service loaded active running Network Time
vnstat.service loaded active running vnStat - a lightweightnetwork traffic monitor
network-online.target loaded active active Network is OnlineLookups
network-pre.target loaded inactive dead Network (Pre)
network.target loaded active active Network
nss-lookup.target loaded active active Host and Network Name
On Sat, 26 Oct 2019 07:55:21 +1100, faeychild wrote:
On 25/10/19 8:17 pm, Bit Twister wrote:
Morning Bits
And a afternoon to you. :)
Personally, I need the network up, and no, my nic stays down if I shut
it down.
I would like to see the results from the following:
ls -1 /etc/sysconfig/network-scripts/ifcfg-*
Homework, man watch
Paste all these in a root terminal as one big paste
systemctl stop vnstat.service
systemctl stop nss-lookup.target
systemctl stop systemd-timesyncd.service
export _net_nic=enp0s31f6
/usr/sbin/ip link set $_net_nic down
/usr/sbin/ifconfig $_net_nic | grep flag
watch --interval 5 "/usr/sbin/ifconfig $_net_nic | grep flag"
To get out of the watch command, hit Ctl c
If nic stays down, you would use another root terminal to start each of
the stopped units. I suggest starting in the order stopped.
To get out of the watch command, hit Ctl c
If nic stays down, you would use another root terminal to start each of
the stopped units. I suggest starting in the order stopped.
When the nic is stopped the entry "RUNNING" disappears. It returns
when the nic re-starts.
But now, with no discernible pattern, sometimes the nic stays down
This is not at all helpful :-(
regards
On 26/10/19 3:48 pm, faeychild wrote:
[root@unimatrix ~]# systemctl stop vnstat.serviceTo get out of the watch command, hit Ctl c
If nic stays down, you would use another root terminal to start each of
the stopped units. I suggest starting in the order stopped.
When the nic is stopped the entry "RUNNING" disappears. It returns
when the nic re-starts.
But now, with no discernible pattern, sometimes the nic stays down
This is not at all helpful :-(
regards
[root@unimatrix ~]# systemctl stop nss-lookup.target
[root@unimatrix ~]# systemctl stop systemd-timesyncd.service [root@unimatrix ~]#
[root@unimatrix ~]# export _net_nic=enp0s31f6
[root@unimatrix ~]# /usr/sbin/ip link set $_net_nic down [root@unimatrix ~]# /usr/sbin/ifconfig $_net_nic | grep flag enp0s31f6: flags=4098<BROADCAST,MULTICAST> mtu 1500
[root@unimatrix ~]# watch --interval 5 "/usr/sbin/ifconfig
$_net_nic | grep flag"^C
After this command "/usr/sbin/ip link set $_net_nic down" the nic
goes down.. then comes back up again
The object of the watch command was to check the nic every 5 seconds
to allow you to see if the nic came up.
As root you can trystarted.
grep -R network /usr/lib/systemd/system/* | grep -i requi
That gets you a list of units which might require/cause the network to be
You stop those services, shutdown the nic, and watch for it to come up
or not.directory.
I have yet to see if you have anything running in your DE autostart
That might be eliminated by setting USERCTL=no in the /etc/sysconfig/network-scripts/ifcfg-enp file.
Just not sure. I would install the xfce task rpm, create another user,
Pick xfce Desktop Environment for the user, then log in. That would
eliminate your DE as a person of interest in this who done it.
\
On 26/10/19 5:53 pm, Bit Twister wrote:
[root@unimatrix ~]# grep -R network /usr/lib/systemd/system/* | grep -i
requi
[root@unimatrix ~]# systemctl stop systemd-networkd-wait-online.service [root@unimatrix ~]# systemctl stop systemd-networkd.service
~]# locate autostart
/home/faeychild/.config/autostart
/home/faeychild/.config/autostart-scripts
/usr/share/autostart
cat /etc/sysconfig/network-scripts/ifcfg-enp*
USERCTL=no
It still restarts
Would that be task-xfce 4.12 6.mga7
or task-xfce 4.14 1.mga7
Using "junk" account the nic comes back up
using syatemrescuecd the nic comes back up
does udev have any influence on ethernet?
On 26/10/19 5:53 pm, Bit Twister wrote:
The object of the watch command was to check the nic every 5 seconds
to allow you to see if the nic came up.
In deed it did
One other thing to try is watch the journal to see if anything else besides network makes an entry.
If your id is not in the systemd-journal group, "id grep systemd", click up
a root terminal and run
journalctl --no-hostname -fa --no-pager
then shutdown the nic and watch the journal output for when the nic comes back up.
Oct 28 07:45:47 avahi-daemon[1044]: Joining mDNS multicast group on
interface enp0s31f6.IPv6 with address fe80::1e1b:dff:fea4:b28f.
Oct 28 07:45:47 avahi-daemon[1044]: New relevant interface
enp0s31f6.IPv6 for mDNS.
Oct 28 07:45:47 avahi-daemon[1044]: Registering new address record for fe80::1e1b:dff:fea4:b28f on enp0s31f6.*.
On 27/10/19 6:23 pm, Bit Twister wrote:
I'm dinking around with hot cold starts here because I find some
instances where the right click menu doesn't appear.
So after the box has been up some hours I'll do it again
One other thing to try is watch the journal to see if anything else besides >> network makes an entry.
If your id is not in the systemd-journal group, "id grep systemd", click up >> a root terminal and run
journalctl --no-hostname -fa --no-pager
then shutdown the nic and watch the journal output for when the nic comes
back up.
Oct 28 07:45:32 net_applet[6605]: running: /usr/sbin/ifdown enp0s31f6 daemon
Oct 28 07:45:32 avahi-daemon[1044]: Withdrawing address record for 192.168.1.1 on enp0s31f6.
Oct 28 07:45:32 avahi-daemon[1044]: Leaving mDNS multicast group on
interface enp0s31f6.IPv4 with address 192.168.1.1.
Oct 28 07:45:32 avahi-daemon[1044]: Leaving mDNS multicast group on
interface enp0s31f6.IPv6 with address fe80::1e1b:dff:fea4:b28f.
Oct 28 07:45:33 ifplugd(enp0s31f6)[3689]: Link beat lost.
Oct 28 07:45:33 mgaapplet[6603]: Checking Network: seems disabled
Oct 28 07:45:39 ifplugd(enp0s31f6)[3689]: Executing '/etc/ifplugd/ifplugd.action enp0s31f6 down'.
Oct 28 07:45:39 kernel: e1000e: enp0s31f6 NIC Link is Down
Oct 28 07:45:39 ifplugd(enp0s31f6)[3689]: Program executed successfully.
Oct 28 07:45:39 kernel: e1000e: enp0s31f6 NIC Link is Up
Link is Up 1000 Mbps Half Duplex, Flow Control: None
Oct 28 07:45:39 kernel: e1000e: enp0s31f6 NIC Link is Down
Oct 28 07:45:45 kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Weird, now it is Full Duplex.
On 28/10/19 9:04 am, Bit Twister wrote:
Weird, now it is Full Duplex.
There is a lot of weird here Bits
I tried Dave's suggestion
It did stop avahi but the nic still came back up
but it makes sense that if mga update is going to run all the time then
it will bring up the network
I noticed this
Oct 28 18:56:47 mgaapplet-update-checker[645]: updating inactive
backport media Core Backports (distrib7), Nonfree Backports (distrib17), Tainted Backports (distrib27), Core 32bit Backports (distrib34), Nonfree 32bit Backports (distrib39), Tainted 32bit Backports (distrib44)
Oct 28 18:56:47 mgaapplet-update-checker[645]: running: urpmi.update
Core Backports (distrib7)
Oct 28 18:56:47 pkexec[678]: pam_unix(polkit-1:session): session opened
for user root by (uid=1000)
The very busy mgaaplet is updating inactive backport data.
Is this not somewhat pointless - I don't have backports checked either
this is interesting
Oct 28 19:19:36 mgaapplet[4541]: Checking Network: seems disabled
Oct 28 19:19:36 plasmashell[4499]:
Unable to assign QJSValue to QImage
It has been years, but in the mcc software section there was a setting
as to how often the check for software updates was to be made.
I would have thought it would stay with the selected time and not
bother with bringing up the network.
You could do a urpme mgaonline, and see if nic still comes backup.
If so reinstall mgaonline.
The very busy mgaaplet is updating inactive backport data.
Is this not somewhat pointless - I don't have backports checked either
I figured it pointless to have a media entry if I am not going to use it,
so I remove all those kinds of entries.
urpmi.removemedia -y Debug Backport Testing
awhileOct 28 19:19:36 mgaapplet[4541]: Checking Network: seems disabled
Oct 28 19:19:36 plasmashell[4499]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/Not ificationDelegate.qml:114:13:
Unable to assign QJSValue to QImage
Yeah, I saw those in your previous post, But i have not used plasma in
so it was a tossup in my mind as to which of the above two might be causing the network to come back up.
~]# urpme mgaonline
removing mgaonline-3.30-1.mga7.noarch
removing package mgaonline-3.30-1.mga7.noarch
1/1: removing mgaonline-3.30-1.mga7.noarch
/etc/sysconfig/mgaapplet saved as /etc/sysconfig/mgaapplet.rpmsave
##
writing /var/lib/rpm/installed-through-deps.list
nic still comes up
So my belief is in error. It is not mgaonline and it's not avahi
Oct 28 19:19:35 ifplugd(enp0s31f6)[3672]: Link beat lost.
Oct 28 19:19:41 ifplugd(enp0s31f6)[3672]: Executing '/etc/ifplugd/ifplugd.action enp0s31f6 down'.
Oct 28 19:19:41 kernel: e1000e: enp0s31f6 NIC Link is Down
Oct 28 19:19:41 kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None
Oct 28 19:19:41 ifplugd(enp0s31f6)[3672]: Program executed successfully.
On Mon, 28 Oct 2019 04:28:55 -0400, faeychild <faeychild@nomail.afraid.org>wrote:
Finally, it's clear what's doing the change.(un)plugged
Oct 28 19:19:35 ifplugd(enp0s31f6)[3672]: Link beat lost.
Oct 28 19:19:41 ifplugd(enp0s31f6)[3672]: Executing
'/etc/ifplugd/ifplugd.action enp0s31f6 down'.
Oct 28 19:19:41 kernel: e1000e: enp0s31f6 NIC Link is Down
Oct 28 19:19:41 kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Half
Duplex, Flow Control: None
Oct 28 19:19:41 ifplugd(enp0s31f6)[3672]: Program executed successfully.
In /etc/sysconfig/network-scripts/ifup-eth ...
# exec ifplugd daemon at boot if supported
if [ -n "${daemon}" -a "$MII_NOT_SUPPORTED" != "yes" ]; then
IFPLUGD_ARGS="${IFPLUGD_ARGS=-I -b}"
exec /sbin/ifplugd $IFPLUGD_ARGS -i $DEVICE
fi
# rpm -q -i ifplugd|grep ^Summary
Summary : Detect and perform actions when an ethernet cable is
To avoid this, change the value for MII_NOT_SUPPORTED to yes in theifcfg-enp0s31f6
file.be
I suspect there is a poor connection for the network causing it to appear to
plugged in and unplugged frequently.
On Mon, 28 Oct 2019 04:28:55 -0400, faeychild <faeychild@nomail.afraid.org>wrote:
Finally, it's clear what's doing the change.
Oct 28 19:19:35 ifplugd(enp0s31f6)[3672]: Link beat lost.
Oct 28 19:19:41 ifplugd(enp0s31f6)[3672]: Executing
'/etc/ifplugd/ifplugd.action enp0s31f6 down'.
On Mon, 28 Oct 2019 22:50:37 +1100, faeychild wrote:
~]# urpme mgaonline
removing mgaonline-3.30-1.mga7.noarch
removing package mgaonline-3.30-1.mga7.noarch
1/1: removing mgaonline-3.30-1.mga7.noarch
#####################################################################warning: >> /etc/sysconfig/mgaapplet saved as /etc/sysconfig/mgaapplet.rpmsave
##
writing /var/lib/rpm/installed-through-deps.list
nic still comes up
Ok, you can put mgaonline back if you like.
This leaves me guessing dhcp*. You could configure the nic as static ip address and see if nic comes back up. You can look around in the lease
file to get gateway and whatnot to use during static configuration.
locate enp0s31f6
On 28/10/19 11:13 pm, Bit Twister wrote:
Ok, you can put mgaonline back if you like.
Or just leave the helpful nonsense disabled and periodically check
manually.
This leaves me guessing dhcp*. You could configure the nic as static ip
address and see if nic comes back up. You can look around in the lease
file to get gateway and whatnot to use during static configuration.
locate enp0s31f6
~]$ locate enp0s31f6
/etc/sysconfig/network-scripts/ifcfg-enp0s31f6 /var/lib/dhclient/dhclient--enp0s31f6.lease
This could raise a slew of new problems.
The nic is set for DHCP.
If I set it static does the router need to be reconfigured ?
Is this a another adventure?
If I ever get that Ethernet cable for the "printer > router" how much
drama will that generate??
I'll lick my wounds for while, Bits.
This could raise a slew of new problems.
On 28/10/19 11:13 pm, Bit Twister wrote:
On Mon, 28 Oct 2019 22:50:37 +1100, faeychild wrote:
~]# urpme mgaonline removing mgaonline-3.30-1.mga7.noarch removing
package mgaonline-3.30-1.mga7.noarch
1/1: removing mgaonline-3.30-1.mga7.noarch
#####################################################################warning: >>> /etc/sysconfig/mgaapplet saved as /etc/sysconfig/mgaapplet.rpmsave ##
writing /var/lib/rpm/installed-through-deps.list
nic still comes up
Ok, you can put mgaonline back if you like.
Or just leave the helpful nonsense disabled and periodically check
manually.
This leaves me guessing dhcp*. You could configure the nic as static ip
address and see if nic comes back up. You can look around in the lease
file to get gateway and whatnot to use during static configuration.
locate enp0s31f6
~]$ locate enp0s31f6 /etc/sysconfig/network-scripts/ifcfg-enp0s31f6 /var/lib/dhclient/dhclient--enp0s31f6.lease
This could raise a slew of new problems.
The nic is set for DHCP.
If I set it static does the router need to be reconfigured ?
For my actiontec router, I had to log into the router, click on Advanced, click on IP Address Distribution, and there set the connection to Static.
On Mon, 28 Oct 2019 23:17:12 -0000 (UTC), Jim Beard wrote:
For my actiontec router, I had to log into the router, click on
Advanced,
click on IP Address Distribution, and there set the connection to
Static.
Hmmm, sounds like you may have set the router to have a static ISP ip,
Not assigning a static ip to a specific nic on the lan.
run " wget -qO - http://icanhazip.com" and if the returned ip address
is the same as set in your static setup, then that will work until your
is assigns you a new ip address.
I know I was able to just pick an ip in my actiontech router and was
always able to get a connection. I just had to make sure no other device
was using the same ip address.
On Mon, 28 Oct 2019 20:01:02 -0500, Bit Twister wrote:
On Mon, 28 Oct 2019 23:17:12 -0000 (UTC), Jim Beard wrote:
For my actiontec router, I had to log into the router, click on
Advanced,
click on IP Address Distribution, and there set the connection to
Static.
Hmmm, sounds like you may have set the router to have a static ISP ip,
Not assigning a static ip to a specific nic on the lan.
Not so. For example, one entry is
ip 192.168.1.9 nic 70:8b:cd:ac:1d:a8 host Sorrel.
A 192.168.* ip is definitely on the lan.
run " wget -qO - http://icanhazip.com" and if the returned ip address
is the same as set in your static setup, then that will work until your
is assigns you a new ip address.
$ wget -qO - http://icanhazip.com
96.241.126.102
Or just leave the helpful nonsense disabled and periodically check
manually.
Very true. It would be dead easy to have a script to pull down any updates and if any, you would do the install.M
file.This leaves me guessing dhcp*. You could configure the nic as static ip
address and see if nic comes back up. You can look around in the lease
file to get gateway and whatnot to use during static configuration.
locate enp0s31f6
~]$ locate enp0s31f6
/etc/sysconfig/network-scripts/ifcfg-enp0s31f6
/var/lib/dhclient/dhclient--enp0s31f6.lease
That /var/lib/ file is the one which should have some of the answers needed to do static configuration. I would like to see the last stanza of that
This could raise a slew of new problems.
Hmmmm, hopefully not if done carefully, without typos.
It is always easy when you know how. You provide required information,
ip addy, netmask, gateway, dns servers. I expect the lease file to have
the data, or you can get the information from ifconfig, route -n, and
cat /etc/resolv.conf
I'll lick my wounds for while, Bits.
I understand.
On Tue, 29 Oct 2019 07:26:01 +1100, faeychild wrote:
This could raise a slew of new problems.
Oh yeah, before I forget it, again, you disabled avahi-daemon so you
might want to consider optimizing/removing unwanted lookup methods/types.
snippet from /etc/nsswitch.conf
# Changed by /local/bin/nsswitch_changes Sat 29 Jun 08:40 2019
# hosts: mdns4_minimal files nis dns mdns4 myhostname
hosts: files dns myhostname
On Tue, 29 Oct 2019 07:26:01 +1100, faeychild wrote:
On 28/10/19 11:13 pm, Bit Twister wrote:
On Mon, 28 Oct 2019 22:50:37 +1100, faeychild wrote:
~]# urpme mgaonline removing mgaonline-3.30-1.mga7.noarch removing
package mgaonline-3.30-1.mga7.noarch
1/1: removing mgaonline-3.30-1.mga7.noarch
writing /var/lib/rpm/installed-through-deps.list
nic still comes up
Ok, you can put mgaonline back if you like.
Or just leave the helpful nonsense disabled and periodically check
manually.
This leaves me guessing dhcp*. You could configure the nic as static ip
address and see if nic comes back up. You can look around in the lease
file to get gateway and whatnot to use during static configuration.
locate enp0s31f6
~]$ locate enp0s31f6 /etc/sysconfig/network-scripts/ifcfg-enp0s31f6
/var/lib/dhclient/dhclient--enp0s31f6.lease
This could raise a slew of new problems.
The nic is set for DHCP.
If I set it static does the router need to be reconfigured ?
For my actiontec router, I had to log into the router, click on Advanced, click on IP Address Distribution, and there set the connection to Static.
This assumes you already have a DHCP connection, of the dynamic variety,
so the ip address and nic physical address will already be set for each connection.
$ ifconfig $_net_nic
On 29/10/19 8:43 am, Bit Twister wrote:
$ ifconfig $_net_nic
That is a good idea, Bits.
Do you declare it in "bash_profile"
_net_nic=enp3s0
How do you make it global?
lease {
interface "enp0s31f6";
fixed-address 192.168.1.1;
option subnet-mask 255.255.255.0;
option routers 192.168.1.254;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.1.254;
option dhcp-server-identifier 192.168.1.254;
option domain-name "home.gateway";
renew 3 2019/10/30 07:15:11;
rebind 3 2019/10/30 17:34:59;
expire 3 2019/10/30 20:34:59;
}
option domain-name "home.gateway";
On 29/10/19 9:21 am, Bit Twister wrote:
On Tue, 29 Oct 2019 07:26:01 +1100, faeychild wrote:
This could raise a slew of new problems.
Oh yeah, before I forget it, again, you disabled avahi-daemon so you
might want to consider optimizing/removing unwanted lookup methods/types.
snippet from /etc/nsswitch.conf
# Changed by /local/bin/nsswitch_changes Sat 29 Jun 08:40 2019
# hosts: mdns4_minimal files nis dns mdns4 myhostname
hosts: files dns myhostname
cat /etc/nsswitch.conf
hosts: mdns4_minimal files nis dns mdns4 myhostname
It's already another adventure, Bits :-)
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 61:34:36 |
| Calls: | 6,654 |
| Files: | 12,200 |
| Messages: | 5,331,534 |