ext2(3) question(s)
by Bill Cunningham
I wanted to ask all who might be interested too, and know the
answers to this, first, in short,
/dev/zram0 my system says is a swap file. It's really no big deal, but I
would rather not have one. I see the old 'mkswap' command is gone, I
look at the filesystem and see no visible swap. Is there a way to turn
this off? I really don't think my memory needs to swap out pages to the
filesystem; but then, maybe it could use it. Turning it off probably
wouldn't hurt.
And also what comes goes, my system went down and no worries. But I
did try to rescue the system with e2fsck. When done after quite some
time. All the showed up was 'lost+found' and in that directory was a lot
of directories that were numbered. Some had the hash in front. I guess I
really did a number on it. Nothing was lost worth keeping. It needed
cleaned anyway.
Thanks all
BC
1 year, 6 months
- 5
- 8
NetworkManager not creating VLAN at boot
by Ian Pilcher
I am setting up Fedora 36 on a new laptop, and I'm trying (really, I'm
trying!) to be a good boy and use NetworkManager for everything. After
beating my head against the wall for a day, I've finally managed to get
it to create a simple Open vSwitch bridge (ovs0), for use with virtual
machines.
Now I am trying to create a tagged interface (ovs0.122) on top of that
OVS device. (Note, I cannot simply create a tagged port, because I need
the tagger interface to have a smaller MTU than the bridge itself.)
AFAICT, I've done everything right, and NetworkManager creates the VLAN
interface when I bring it up manually after the system has booted. I
absolutely cannot figure out what (if anything) I need to do to have the
VLAN created when the system boots.
Is this yet another "everyone should use NetworkManager, because it can
do everything that the legacy scripts can do, except that it can't do
that" situation?
Here are the details of the VLAN interface:
> $ nmcli con show ovs0.122
> connection.id: ovs0.122
> connection.uuid: 668088f5-3fde-43e3-a6a9-8420a5e6a6a3
> connection.stable-id: --
> connection.type: vlan
> connection.interface-name: ovs0.122
> connection.autoconnect: yes
> connection.autoconnect-priority: 0
> connection.autoconnect-retries: -1 (default)
> connection.multi-connect: 0 (default)
> connection.auth-retries: -1
> connection.timestamp: 1664743791
> 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.dns-over-tls: -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: --
> 802-3-ethernet.cloned-mac-address: --
> 802-3-ethernet.generate-mac-address-mask:--
> 802-3-ethernet.mac-address-blacklist: --
> 802-3-ethernet.mtu: 1500
> 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: --
> 802-3-ethernet.accept-all-mac-addresses:-1 (default)
> ipv4.method: manual
> ipv4.dns: --
> ipv4.dns-search: --
> ipv4.dns-options: --
> ipv4.dns-priority: 0
> ipv4.addresses: 192.168.122.254/24
> 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-iaid: --
> ipv4.dhcp-timeout: 0 (default)
> ipv4.dhcp-send-hostname: yes
> ipv4.dhcp-hostname: --
> ipv4.dhcp-fqdn: --
> ipv4.dhcp-hostname-flags: 0x0 (none)
> ipv4.never-default: no
> ipv4.may-fail: yes
> ipv4.required-timeout: -1 (default)
> ipv4.dad-timeout: -1 (default)
> ipv4.dhcp-vendor-class-identifier: --
> ipv4.dhcp-reject-servers: --
> 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.required-timeout: -1 (default)
> ipv6.ip6-privacy: -1 (unknown)
> ipv6.addr-gen-mode: stable-privacy
> ipv6.ra-timeout: 0 (default)
> ipv6.dhcp-duid: --
> ipv6.dhcp-iaid: --
> ipv6.dhcp-timeout: 0 (default)
> ipv6.dhcp-send-hostname: yes
> ipv6.dhcp-hostname: --
> ipv6.dhcp-hostname-flags: 0x0 (none)
> ipv6.token: --
> vlan.parent: 5fc9b636-c1bf-47eb-876e-fe560ac574bf
> vlan.id: 122
> vlan.flags: 1 (REORDER_HEADERS)
> vlan.ingress-priority-map: --
> vlan.egress-priority-map: --
> proxy.method: none
> proxy.browser-only: no
> proxy.pac-url: --
> proxy.pac-script: --
And here is what NetworkManager says about the interface (not much):
> $ sudo journalctl -b -u NetworkManager | grep ovs0.122
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7997] manager: (ovs0.122): new VLAN device (/org/freedesktop/NetworkManager/Devices/6)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8016] policy: auto-activating connection 'ovs0.122' (668088f5-3fde-43e3-a6a9-8420a5e6a6a3)
Full NetworkManager log:
> $ sudo journalctl -b -u NetworkManager
> Oct 02 15:53:22 x1.penurio.us systemd[1]: Starting NetworkManager.service - Network Manager...
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3124] NetworkManager (version 1.38.4-1.fc36) is starting... (for the first time)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3127] Read config: /etc/NetworkManager/NetworkManager.conf
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3138] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
> Oct 02 15:53:22 x1.penurio.us systemd[1]: Started NetworkManager.service - Network Manager.
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3168] manager[0x561307038010]: monitoring kernel firmware directory '/lib/firmware'.
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3498] hostname: hostname: using hostnamed
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3500] hostname: static hostname changed from (none) to "x1.penurio.us"
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3504] dns-mgr[0x561307011250]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3512] rfkill2: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.3/ieee80211/phy0/rfkill2) (driver iwlwifi)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3513] manager[0x561307038010]: rfkill: Wi-Fi hardware radio set enabled
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3513] manager[0x561307038010]: rfkill: WWAN hardware radio set enabled
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3532] Loaded device plugin: NMOvsFactory (/usr/lib64/NetworkManager/1.38.4-1.fc36/libnm-device-plugin-ovs.so)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3539] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.38.4-1.fc36/libnm-device-plugin-wifi.so)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3540] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3540] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3541] manager: Networking is enabled by state file
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3545] settings: Loaded settings plugin: keyfile (internal)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3578] dhcp-init: Using DHCP client 'internal'
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3579] device (lo): carrier: link connected
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3581] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3590] manager: (enp82s0u2u1u2): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3598] settings: (enp82s0u2u1u2): created default wired connection 'Wired connection 1'
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3599] device (enp82s0u2u1u2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3647] device (wlp0s20f3): driver supports Access Point (AP) mode
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3650] manager: (wlp0s20f3): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.3653] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.5953] device (wlp0s20f3): set-hw-addr: set MAC address to 66:07:63:7D:21:56 (scanning)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7988] manager: (ovs0): new Open vSwitch Bridge device (/org/freedesktop/NetworkManager/Devices/4)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7989] device (ovs0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7993] manager: (ovs0): new Open vSwitch Interface device (/org/freedesktop/NetworkManager/Devices/5)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7994] device (ovs0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.7997] manager: (ovs0.122): new VLAN device (/org/freedesktop/NetworkManager/Devices/6)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8000] manager: (ovs0): new Open vSwitch Port device (/org/freedesktop/NetworkManager/Devices/7)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8002] device (ovs0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8016] policy: auto-activating connection 'ovs0.122' (668088f5-3fde-43e3-a6a9-8420a5e6a6a3)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8017] device (ovs0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8019] device (ovs0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8020] policy: auto-activating connection 'ovs0-bridge' (54bc1f3e-d272-4f75-ab4e-8809151e9352)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8021] policy: auto-activating connection 'ovs0-port' (f057e2b1-95b8-4377-b615-e09a77906c4a)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8021] device (ovs0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8023] device (ovs0): Activation: starting connection 'ovs0-bridge' (54bc1f3e-d272-4f75-ab4e-8809151e9352)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8024] device (ovs0): Activation: starting connection 'ovs0-port' (f057e2b1-95b8-4377-b615-e09a77906c4a)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8024] policy: auto-activating connection 'ovs0' (5fc9b636-c1bf-47eb-876e-fe560ac574bf)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8034] device (ovs0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8036] manager: NetworkManager state is now CONNECTING
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8036] device (ovs0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8038] device (ovs0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8038] device (ovs0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8040] device (ovs0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8041] device (ovs0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8042] device (ovs0): Activation: connection 'ovs0-port' enslaved, continuing activation
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8043] device (ovs0): Activation: starting connection 'ovs0' (5fc9b636-c1bf-47eb-876e-fe560ac574bf)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8043] device (ovs0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8045] device (ovs0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8046] device (ovs0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8047] device (ovs0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8050] device (ovs0): Activation: connection 'ovs0' enslaved, continuing activation
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8051] device (ovs0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8053] device (ovs0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8055] device (ovs0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8057] device (ovs0): Activation: successful, device activated.
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8060] device (ovs0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8062] device (ovs0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8064] device (ovs0): Activation: successful, device activated.
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8180] device (ovs0): carrier: link connected
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8379] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8380] Wi-Fi P2P device controlled by interface wlp0s20f3 created
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8381] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/8)
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8382] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8385] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
> Oct 02 15:53:22 x1.penurio.us NetworkManager[1509]: <info> [1664744002.8387] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:24 x1.penurio.us NetworkManager[1509]: <info> [1664744004.8741] device (ovs0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:24 x1.penurio.us NetworkManager[1509]: <info> [1664744004.8766] device (ovs0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:24 x1.penurio.us NetworkManager[1509]: <info> [1664744004.8771] device (ovs0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:24 x1.penurio.us NetworkManager[1509]: <info> [1664744004.8776] manager: NetworkManager state is now CONNECTED_LOCAL
> Oct 02 15:53:24 x1.penurio.us NetworkManager[1509]: <info> [1664744004.8781] device (ovs0): Activation: successful, device activated.
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0800] device (enp82s0u2u1u2): carrier: link connected
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0811] device (enp82s0u2u1u2): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0822] policy: auto-activating connection 'Wired connection 1' (f284204d-1ae8-3b00-8654-129f912c7435)
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0829] device (enp82s0u2u1u2): Activation: starting connection 'Wired connection 1' (f284204d-1ae8-3b00-8654-129f912c7435)
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0831] device (enp82s0u2u1u2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0836] manager: NetworkManager state is now CONNECTING
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0839] device (enp82s0u2u1u2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0846] device (enp82s0u2u1u2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:25 x1.penurio.us NetworkManager[1509]: <info> [1664744005.0854] dhcp4 (enp82s0u2u1u2): activation: beginning transaction (timeout in 45 seconds)
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.0992] dhcp4 (enp82s0u2u1u2): state changed new lease, address=172.31.250.3
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.0998] policy: set 'Wired connection 1' (enp82s0u2u1u2) as default for IPv4 routing and DNS
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1224] device (enp82s0u2u1u2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1252] device (enp82s0u2u1u2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1255] device (enp82s0u2u1u2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1260] manager: NetworkManager state is now CONNECTED_SITE
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1265] device (enp82s0u2u1u2): Activation: successful, device activated.
> Oct 02 15:53:27 x1.penurio.us NetworkManager[1509]: <info> [1664744007.1271] manager: NetworkManager state is now CONNECTED_GLOBAL
> Oct 02 15:53:28 x1.penurio.us NetworkManager[1509]: <info> [1664744008.1217] manager: startup complete
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7533] policy: auto-activating connection 'CASAGRANDE' (48f1dd64-e3cb-4697-9e68-fab2e6dcb1bc)
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7540] device (wlp0s20f3): Activation: starting connection 'CASAGRANDE' (48f1dd64-e3cb-4697-9e68-fab2e6dcb1bc)
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7541] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7644] device (wlp0s20f3): set-hw-addr: reset MAC address to A0:80:69:7C:47:87 (preserve)
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7672] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7673] device (wlp0s20f3): Activation: (wifi) access point 'CASAGRANDE' has security, but secrets are required.
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7673] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <warn> [1664744044.7675] device (wlp0s20f3): no secrets: No agents were available for this request.
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7675] device (wlp0s20f3): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <warn> [1664744044.7676] device (wlp0s20f3): Activation: failed for connection 'CASAGRANDE'
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7677] device (wlp0s20f3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7801] device (wlp0s20f3): set-hw-addr: set MAC address to E6:EE:4A:63:B1:74 (scanning)
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7832] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.7833] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> interface_disabled
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.8056] device (wlp0s20f3): supplicant interface state: interface_disabled -> inactive
> Oct 02 15:54:04 x1.penurio.us NetworkManager[1509]: <info> [1664744044.8057] device (p2p-dev-wlp0s20f3): supplicant management interface state: interface_disabled -> inactive
> Oct 02 15:59:13 x1.penurio.us NetworkManager[1509]: <info> [1664744353.4625] device (wlp0s20f3): set-hw-addr: set MAC address to 56:52:2E:F1:0C:53 (scanning)
> Oct 02 15:59:13 x1.penurio.us NetworkManager[1509]: <info> [1664744353.4778] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 15:59:13 x1.penurio.us NetworkManager[1509]: <info> [1664744353.4779] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 15:59:13 x1.penurio.us NetworkManager[1509]: <info> [1664744353.4831] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 15:59:13 x1.penurio.us NetworkManager[1509]: <info> [1664744353.4831] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 16:06:05 x1.penurio.us NetworkManager[1509]: <info> [1664744765.4545] device (wlp0s20f3): set-hw-addr: set MAC address to FA:6F:43:84:04:2D (scanning)
> Oct 02 16:06:05 x1.penurio.us NetworkManager[1509]: <info> [1664744765.4708] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 16:06:05 x1.penurio.us NetworkManager[1509]: <info> [1664744765.4709] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 16:06:05 x1.penurio.us NetworkManager[1509]: <info> [1664744765.4761] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 16:06:05 x1.penurio.us NetworkManager[1509]: <info> [1664744765.4762] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 16:12:57 x1.penurio.us NetworkManager[1509]: <info> [1664745177.5103] device (wlp0s20f3): set-hw-addr: set MAC address to EA:CF:3C:65:8D:C1 (scanning)
> Oct 02 16:12:57 x1.penurio.us NetworkManager[1509]: <info> [1664745177.5236] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 16:12:57 x1.penurio.us NetworkManager[1509]: <info> [1664745177.5237] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 16:12:57 x1.penurio.us NetworkManager[1509]: <info> [1664745177.5290] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 16:12:57 x1.penurio.us NetworkManager[1509]: <info> [1664745177.5290] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 16:19:51 x1.penurio.us NetworkManager[1509]: <info> [1664745591.4703] device (wlp0s20f3): set-hw-addr: set MAC address to 32:BC:8A:68:6F:36 (scanning)
> Oct 02 16:19:51 x1.penurio.us NetworkManager[1509]: <info> [1664745591.4881] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 16:19:51 x1.penurio.us NetworkManager[1509]: <info> [1664745591.4882] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 16:19:51 x1.penurio.us NetworkManager[1509]: <info> [1664745591.4932] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 16:19:51 x1.penurio.us NetworkManager[1509]: <info> [1664745591.4932] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 16:26:44 x1.penurio.us NetworkManager[1509]: <info> [1664746004.4952] device (wlp0s20f3): set-hw-addr: set MAC address to AA:89:B1:69:2D:52 (scanning)
> Oct 02 16:33:36 x1.penurio.us NetworkManager[1509]: <info> [1664746416.4553] device (wlp0s20f3): set-hw-addr: set MAC address to EE:20:53:0B:2F:E4 (scanning)
> Oct 02 16:40:29 x1.penurio.us NetworkManager[1509]: <info> [1664746829.4803] device (wlp0s20f3): set-hw-addr: set MAC address to 22:95:4A:FE:A7:37 (scanning)
> Oct 02 16:47:21 x1.penurio.us NetworkManager[1509]: <info> [1664747241.5526] device (wlp0s20f3): set-hw-addr: set MAC address to 8E:31:5A:3B:3B:B5 (scanning)
> Oct 02 16:54:15 x1.penurio.us NetworkManager[1509]: <info> [1664747655.4589] device (wlp0s20f3): set-hw-addr: set MAC address to 96:75:C9:7C:0F:B7 (scanning)
> Oct 02 17:01:08 x1.penurio.us NetworkManager[1509]: <info> [1664748068.5514] device (wlp0s20f3): set-hw-addr: set MAC address to 2A:35:9D:91:1E:1A (scanning)
> Oct 02 17:08:00 x1.penurio.us NetworkManager[1509]: <info> [1664748480.4644] device (wlp0s20f3): set-hw-addr: set MAC address to 46:6D:F3:EE:53:7F (scanning)
> Oct 02 17:08:00 x1.penurio.us NetworkManager[1509]: <info> [1664748480.4736] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 17:08:00 x1.penurio.us NetworkManager[1509]: <info> [1664748480.4737] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 17:08:00 x1.penurio.us NetworkManager[1509]: <info> [1664748480.4790] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 17:08:00 x1.penurio.us NetworkManager[1509]: <info> [1664748480.4791] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 17:14:52 x1.penurio.us NetworkManager[1509]: <info> [1664748892.4964] device (wlp0s20f3): set-hw-addr: set MAC address to FA:50:84:B3:6A:64 (scanning)
> Oct 02 17:14:52 x1.penurio.us NetworkManager[1509]: <info> [1664748892.5139] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 17:14:52 x1.penurio.us NetworkManager[1509]: <info> [1664748892.5139] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 17:14:52 x1.penurio.us NetworkManager[1509]: <info> [1664748892.5191] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 17:14:52 x1.penurio.us NetworkManager[1509]: <info> [1664748892.5191] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 17:21:44 x1.penurio.us NetworkManager[1509]: <info> [1664749304.4648] device (wlp0s20f3): set-hw-addr: set MAC address to 72:14:A8:53:47:9A (scanning)
> Oct 02 17:21:44 x1.penurio.us NetworkManager[1509]: <info> [1664749304.4809] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 17:21:44 x1.penurio.us NetworkManager[1509]: <info> [1664749304.4810] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 17:21:44 x1.penurio.us NetworkManager[1509]: <info> [1664749304.4861] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 17:21:44 x1.penurio.us NetworkManager[1509]: <info> [1664749304.4862] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
> Oct 02 17:28:37 x1.penurio.us NetworkManager[1509]: <info> [1664749717.4527] device (wlp0s20f3): set-hw-addr: set MAC address to 1A:9A:50:A8:1E:67 (scanning)
> Oct 02 17:28:37 x1.penurio.us NetworkManager[1509]: <info> [1664749717.4722] device (wlp0s20f3): supplicant interface state: inactive -> disconnected
> Oct 02 17:28:37 x1.penurio.us NetworkManager[1509]: <info> [1664749717.4722] device (p2p-dev-wlp0s20f3): supplicant management interface state: inactive -> disconnected
> Oct 02 17:28:37 x1.penurio.us NetworkManager[1509]: <info> [1664749717.4773] device (wlp0s20f3): supplicant interface state: disconnected -> inactive
> Oct 02 17:28:37 x1.penurio.us NetworkManager[1509]: <info> [1664749717.4773] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> inactive
Should I just give up, and go back to the legacy scripts?
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
1 year, 6 months
- 1
- 0
Re: ext2(3) question(s)
by Bill Cunningham
On 10/2/2022 5:38 PM, Jon LaBadie wrote:
> On Sun, Oct 02, 2022 at 04:52:24PM -0400, Bill Cunningham wrote:
>> I wanted to ask all who might be interested too, and know the
>> answers to this, first, in short,
>>
> ...
>>
>> And also what comes goes, my system went down and no worries. But I
>> did try to rescue the system with e2fsck. When done after quite some
>> time. All the showed up was 'lost+found' and in that directory was a lot
>> of directories that were numbered. Some had the hash in front. I guess I
>> really did a number on it. Nothing was lost worth keeping. It needed
>> cleaned anyway.
>
> I'm surprised all of then did not begin with the octothorpe (#).
>
> Fsck puts things into the lost+found directory that appear to be
> properly allocated files, i.e. have an allocated inode and allocated
> data blocks, but which lack any entry in any directory to access
> them by name.
>
> The number is typically the inode number.
>
> As admin you would be able to examine the directories and files
> under lost+found and perhaps determine where they were originally
> and whether you should move them back there. Their owner and
> group haven't changed so they may give you clues. The file(1)
> command may tell you their file types for non-text files.
>
> Although you say nothing valuable was lost, you may wish to
> check the l+f files anyway just to be sure.
>
> Jon
>
I really didn't know what to do with it as the next step. I didn't know
if the filesystem was ruined or not. I just reformatted and reinstalled.
If I could've got a working system back up, I would've. Was there any
fixing to this? This happened, I believe, with a typed mismatch to e2image.
e2image -raO <number> /dev/sda3 file.e2i | cp --always=sparse
I believe the error here was not using "-" as the output for the pipe to
cp. I also used "/dev/sda3" as the copied directory and was doing this
from the unmounted /dev/sda via a usb RO mount. I also might have forgot
the redirect ">" into a file. I have never used e2image before so I
should've used fsarchiver or dump on a mounted system. I wanted to and
believed I did, copy to another partition but evidently overwrote my
filesystem.
The <number> here was the number in the man e2image to make enough room
for a partition table.
1 year, 6 months
- 1
- 0
Upcoming update in Bodhi but no "how to install" section
by Matti Pulkkinen
Hello
I wanted to try installing an update[1] to help test it, because it
fixes a bug that affects me. I remember once before going to Bodhi and
seeing an upcoming update there which had a "how to install" section
with a command like "sudo dnf upgrade --advisory=blahblah" but this
update doesn't have that. Why is that?
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2022-37414bcd9d
--
Terveisin / Regards,
Matti Pulkkinen
1 year, 6 months
- 2
- 1
can dnf exclude all kernel related packages when upgrading or
installing packages
by Mgr. Janusz Chmiel
Dear advanced users and developers,
Because Redhad elite programmers allow users to run their chroot Fedora containers for AArch64 architecture, I Am using Fedora 35 on Termux with Android 8.0. For obvious reason, all kernel related Fedora packages are redundand for Me in this scenario.
I would like to know, if is it possible to exclude all kernel related Fedora packages when installing new packages or when upgrading The systém by typing
Dnf upgrade –refresh
When I upgrade kernel reated packages for more than for The first time, Proot, special C app which simulates real Linux file systém hiearchi on Android crash.
Or unfortunately, Dnf and also Yum do not allow users to skip or exclude kernel related packages?
Thank you very much for your answer.
1 year, 6 months
- 5
- 6
Just noticed strange thing in rkhunter report.
by Michael D. Setzer II
Gives a warning about gawk in /usr/libexec??
In /usr/libexec awk is a directory with two files versus a
file??
ls -l | grep awk
drwxr-xr-x. 2 root root 4096 Jun 6 16:36 awk
lrwxrwxrwx. 1 root root 3 Sep 18 01:19 gawk -> awk
# ls awk -l
total 32
-rwxr-xr-x. 1 root root 15944 Jul 22 2021 grcat
-rwxr-xr-x. 1 root root 15928 Jul 22 2021 pwcat
Looks like the link of gawk -> awk is recent 9/18, but awk
being a directory goes back to June, and files in it go back
to Jul 2021??
Is this normal or is something off.
Looked at 5 machines I have with Fedora 35 at home, and
all have the same files and dates.
Thanks. Sure someone knows.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
(Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
1 year, 6 months
- 3
- 4