Re: recent network breakage on f12?

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

 



users-request@xxxxxxxxxxxxxxxxxxxxxxx wrote:
> From: wolfgang.rupprecht@xxxxxxxxx (Wolfgang S. Rupprecht)
> 
> I'm seeing several of my laptops fail to get a dhcp lease after the
> April-23 yum update for f12.  The server sees the dhcp request and
> issues the correct IP address, but the client never seems to act upon
> it.  Both eth0 and wlan0 never have IPv4 addresses assigned.  Strangely
> IPv6 addresses do get assigned correctly (bith link-local and global) so
> it isn't a case of the ethernet or wlan being down.  Those requests do
> go out and the reply gets acted upon.
> 
> Both NetowrkManager and dhclient were updated within the last two days.
> I wonder if something is broken there.  Are other folks seeing the same
> breakage?

I'm seeing network - and bluetooth - breakage. I did a 'yum update' on 
Saturday, and I've been unable to connect to the internet using 
bluetooth since. Connecting my phone also no longer shows up in the 
Mobile Broadband section of NetworkManager.

It's now also prompting me for the root password when I change the CPU 
speed setting.  All very strange.

 From my log when I try to connect to my Nokia phone with PANU:

Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) starting connection 'Honami - PANU'
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 3 -> 4 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 1 of 5 (Device Prepare) complete.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) starting...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 4 -> 5 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 2 of 5 (Device Configure) complete.
Apr 26 22:22:59 Sonozaki bluetoothd[1139]: link_key_request 
(sba=00:15:83:07:CD:17, dba=00:26:69:63:4E:0A)
Apr 26 22:22:59 Sonozaki bluetoothd[1139]: bnep0 connected
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A bnep0/bluetooth) Stage 2 of 5 (Device Configure) 
successful.  Will connect via PAN.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 5 -> 7 (reason 0)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation (bnep0) 
Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 26 22:22:59 Sonozaki NetworkManager: <info> dhclient started with 
pid 3344
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) scheduled...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 3 of 5 (IP Configure Start) complete.
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) started...
Apr 26 22:22:59 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP6 Configure Get) complete.
Apr 26 22:22:59 Sonozaki dhclient[3344]: Internet Systems Consortium 
DHCP Client 4.1.1
Apr 26 22:22:59 Sonozaki dhclient[3344]: Copyright 2004-2010 Internet 
Systems Consortium.
Apr 26 22:22:59 Sonozaki dhclient[3344]: All rights reserved.
Apr 26 22:22:59 Sonozaki dhclient[3344]: For info, please visit 
https://www.isc.org/software/dhcp/
Apr 26 22:22:59 Sonozaki dhclient[3344]:
Apr 26 22:22:59 Sonozaki dhclient[3344]: Listening on 
LPF/bnep0/00:15:83:07:cd:17
Apr 26 22:22:59 Sonozaki dhclient[3344]: Sending on 
LPF/bnep0/00:15:83:07:cd:17
Apr 26 22:22:59 Sonozaki dhclient[3344]: Sending on   Socket/fallback
Apr 26 22:22:59 Sonozaki dhclient[3344]: DHCPDISCOVER on bnep0 to 
255.255.255.255 port 67 interval 8
Apr 26 22:22:59 Sonozaki NetworkManager: <info> (bnep0): DHCPv4 state 
changed nbi -> preinit
Apr 26 22:23:01 Sonozaki avahi-daemon[887]: Registering new address 
record for fe80::215:83ff:fe07:cd17 on bnep0.*.
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPDISCOVER on bnep0 to 
255.255.255.255 port 67 interval 19
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPOFFER from 192.168.66.1
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPREQUEST on bnep0 to 
255.255.255.255 port 67
Apr 26 22:23:07 Sonozaki dhclient[3344]: DHCPACK from 192.168.66.1
Apr 26 22:23:07 Sonozaki dhclient[3344]: bound to 192.168.66.2 -- 
renewal in 1375 seconds.
Apr 26 22:23:07 Sonozaki NetworkManager: <info> (bnep0): DHCPv4 state 
changed preinit -> bound
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) scheduled...
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) started...
Apr 26 22:23:07 Sonozaki NetworkManager: <info>   address 192.168.66.2
Apr 26 22:23:07 Sonozaki NetworkManager: <info>   prefix 28 
(255.255.255.240)
Apr 26 22:23:07 Sonozaki NetworkManager: <info>   gateway 192.168.66.1
Apr 26 22:23:07 Sonozaki NetworkManager: <info>   nameserver 
'193.35.132.165'
Apr 26 22:23:07 Sonozaki NetworkManager: <info>   nameserver 
'193.35.132.164'
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 4 of 5 (IP4 Configure Get) complete.
Apr 26 22:23:07 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) started...
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: Joining mDNS multicast group 
on interface bnep0.IPv4 with address 192.168.66.2.
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: New relevant interface 
bnep0.IPv4 for mDNS.
Apr 26 22:23:07 Sonozaki avahi-daemon[887]: Registering new address 
record for 192.168.66.2 on bnep0.IPv4.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 7 -> 8 (reason 0)
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Policy set 'Honami - 
PANU' (bnep0) as default for routing and DNS.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) successful, device activated.
Apr 26 22:23:08 Sonozaki NetworkManager: <info> Activation 
(00:26:69:63:4E:0A) Stage 5 of 5 (IP Configure Commit) complete.
Apr 26 22:23:29 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 8 -> 9 (reason 44)
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
device state change: 9 -> 3 (reason 0)
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (00:26:69:63:4E:0A): 
deactivating device (reason: 0).
Apr 26 22:23:30 Sonozaki NetworkManager: <info> (bnep0): canceled DHCP 
transaction, DHCP client pid 3344
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Withdrawing address record 
for 192.168.66.2 on bnep0.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Leaving mDNS multicast group 
on interface bnep0.IPv4 with address 192.168.66.2.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Interface bnep0.IPv4 no 
longer relevant for mDNS.
Apr 26 22:23:30 Sonozaki avahi-daemon[887]: Withdrawing address record 
for fe80::215:83ff:fe07:cd17 on bnep0.
Apr 26 22:23:30 Sonozaki dbus-daemon: Rejected send message, 2 matched 
rules; type="method_return", sender=":1.12" (uid=0 pid=1124 
comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)" error 
name="(unset)" requested_reply=0 destination=":1.0" (uid=0 pid=876 
comm="NetworkManager))
Apr 26 22:23:30 Sonozaki bluetoothd[1139]: bnep0 disconnected

It appears to connect, then a few seconds later it gets pulled down again.

How do I get my machine back to the state it was pre Saturday's updates?

-- Michael "Soruk" McConnell
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux