Voilà pour répondre aux questions:
[root@localhost ~]# lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
[root@localhost ~]# systemctl status NetworkManager.service
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Fri, 22 Jun 2012 22:29:40 +0200; 1min 8s ago
Main PID: 772 (NetworkManager)
CGroup: name=systemd:/system/NetworkManager.service
└ 772 /usr/sbin/NetworkManager --no-daemon
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <info> WiFi enabled by radio killswitch; enabled by state file
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <info> WWAN enabled by radio killswitch; enabled by state file
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <info> Networking is enabled by state file
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <info> modem-manager is now available
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <warn> bluez error getting default adapter: Message did not receive a reply (timeout by message bus)
Jun 22 22:29:40 localhost.localdomain NetworkManager[772]: <warn> bluez error getting default adapter: Message did not receive a reply (timeout by message bus)
Jun 22 22:29:57 localhost.localdomain NetworkManager[772]: <warn> bluez error getting default adapter: Message did not receive a reply (timeout by message bus)
Jun 22 22:29:58 localhost.localdomain NetworkManager[772]: <warn> bluez error getting default adapter: Message did not receive a reply (timeout by message bus)
Jun 22 22:29:58 localhost.localdomain NetworkManager[772]: <warn> bluez error getting default adapter: Message did not receive a reply (timeout by message bus)
En y regardant à 2 fois je remarque aussi que j'ai ces messages au moment du boot:
Failed to start IPv4 firewall with iptables [ESC[1;31mFAILEDESC[0m]
See 'systemctl status iptables.service' for details.
Failed to start IPv6 firewall with ip6tables [ESC[1;31mFAILEDESC[0m]
See 'systemctl status ip6tables.service' for details.
Donc si je suis les consignes:
[root@localhost log]# systemctl status iptables.service
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled)
Active: failed (Result: exit-code) since Fri, 22 Jun 2012 22:29:39 +0200; 7min ago
Process: 734 ExecStart=/usr/libexec/iptables.init start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/iptables.service
Jun 22 22:29:39 localhost.localdomain iptables.init[734]: iptables: Applying firewall rules: iptables-restore: line 13 failed
[root@localhost log]# systemctl status ip6tables.service
ip6tables.service - IPv6 firewall with ip6tables
Loaded: loaded (/usr/lib/systemd/system/ip6tables.service; enabled)
Active: failed (Result: exit-code) since Fri, 22 Jun 2012 22:29:39 +0200; 7min ago
Process: 735 ExecStart=/usr/libexec/ip6tables.init start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/ip6tables.service
Jun 22 22:29:39 localhost.localdomain ip6tables.init[735]: ip6tables: Applying firewall rules: ip6tables-restore v1.4.12.2: ip6tables-restore: unable to initialize table 'filter'
Jun 22 22:29:39 localhost.localdomain ip6tables.init[735]: Error occurred at line: 3
Jun 22 22:29:39 localhost.localdomain ip6tables.init[735]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
Est-ce que tout ça est lié?
