Re: Completely replacing F31 Ethernet package(s)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2020-01-05 at 12:48 +0800, Ed Greshko wrote:
On 2020-01-05 12:34, Robert G (Doc) Savage via users wrote:
On Fri, 2020-01-03 at 21:34 -0800, Samuel Sieb wrote:
On 1/3/20 9:14 PM, Robert G (Doc) Savage via users wrote:
It has been my understanding that only one network mode could be active
qt one time. On my old W700 laptop I could use the RJ45 connection at
my desk, then disconnect the live laptop and take it to the dining room
or wherever. Once disconnected from the RJ45, a WiFi connection was
automatically spawned. Whe I returned to my desk and reconnected the
RJ45 cable, the WiFi shut down and the copper Ethernet was reactivated.

The wifi shouldn't be disconnected when the ethernet is, but the 
ethernet will have a higher priority. Unless the wifi is on a different 
subnet and that's where you're sending a packet to, it will go out on 
the ethernet connection.  I often have my dhcp set up to give my wifi 
and ethernet the same ip address.  That way I can switch between the two 
without losing connections.

I'll take your word for it Sam. I'm still unable to communicate thru the RJ45 port with my currently installed package(s) / configuration.

Unless someone can suggest a true fix, I'm still facing a package remove/replace situation. Which ones??? Otherwise my only solution would be a scorched disk total removal and replacement of the entire system.


Well.....  I still don't think enough information has been supplied.

If you do a

nmcli connection   

you should see an "ethernet" entry.

Example, on my system...

NAME            UUID                                  TYPE      DEVICE
enp2s0          22f19ca8-c33d-31ea-9a32-a4b1309d0b06  ethernet  enp2s0

And then do...

nmcli connection show (device-name)

Ed,

# nmcli connection
...
eth0: unavailable
        "Intel Ethernet"
        ethernet (e1000e), E8:6A:64:35:53:D8, hw, mtu 1500
....

Your next request generated a lot more:

# nmcli connection show eth0
connection.id:                          eth0
connection.uuid:                        3a1a7b73-df5e-37b9-a9af-dbc49d4120b3
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        -999
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   1577737181
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
connection.wait-device-timeout:         -1
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          no
802-3-ethernet.mac-address:             E8:6A:64:35:53:D8
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist:   --
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:        --
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:            --
802-3-ethernet.wake-on-lan:             default
802-3-ethernet.wake-on-lan-password:    --
ipv4.method:                            auto
ipv4.dns:                               --
ipv4.dns-search:                        --
ipv4.dns-options:                       --
ipv4.dns-priority:                      0
ipv4.addresses:                         --
ipv4.gateway:                           --
ipv4.routes:                            --
ipv4.route-metric:                      -1
ipv4.route-table:                       0 (unspec)
ipv4.routing-rules:                     --
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-timeout:                      0 (default)
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     --
ipv4.dhcp-fqdn:                         --
ipv4.never-default:                     no
ipv4.may-fail:                          no
ipv4.dad-timeout:                       -1 (default)
ipv6.method:                            auto
ipv6.dns:                               --
ipv6.dns-search:                        --
ipv6.dns-options:                       --
ipv6.dns-priority:                      0
ipv6.addresses:                         --
ipv6.gateway:                           --
ipv6.routes:                            --
ipv6.route-metric:                      -1
ipv6.route-table:                       0 (unspec)
ipv6.routing-rules:                     --
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       0 (disabled)
ipv6.addr-gen-mode:                     stable-privacy
ipv6.dhcp-duid:                         --
ipv6.dhcp-send-hostname:                yes
ipv6.dhcp-hostname:                     --
ipv6.token:                             --
proxy.method:                           none
proxy.browser-only:                     no
proxy.pac-url:                          --
proxy.pac-script:                       --

Lot of chaff there. Not sure if there's any wheat at all. Does anything catch your eye, Ed?

--Doc Savage
Fairview Heights, IL

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux