Debian fórum

Dotazy => Internet a sítě => Téma založeno: Michal kdy 18. 01. 2015, 15:25:03

Název: Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 18. 01. 2015, 15:25:03
Dobrý den. Nainstaloval jsem si k Windows 7,  Debian 8 Jessie na Lenovo B50-70 , HDD 500Gb, RAM 4Gb.
Když naběhne gnome a nebo xfce a já ihned zapnu iceweasel, icedove a nebo metatrader, prostě nějaký program, který pro svou činnost potřebuje připojení k internetu, tak se připojí, až po cca 6 min. +- 20 s k internetu. Pozor, ale tento problém je jen při zapnutí notebooku a nebo při jeho restartu! Neplatí to již později (Po 6 minutách.) při vypnutí a  zapnutí jakékoliv programu. Neplatí to ani při přechodu z gnome do xfce a zpět. V těchto případech připojení je ihned nejdéle do 2 s . Připojený jsem kabelem. Prosím o pomoc. Nevím jaký výpis mám přiložit, snad se trefím. Předem všem děkuji za pomoc. Michal

michal@PC1:~$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
09:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
michal@PC1:~$

Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 18. 01. 2015, 20:56:18
Nejlepší bude se podívat do logu, co tam ten DHCP klient píše. On bude mít nějaký důvod, proč se nepouští.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 19. 01. 2015, 16:19:02
Část výpisu: /var/log/daemon.log
  Jan 18 11:08:31 PC1 smbd[1574]: Reloading /etc/samba/smb.conf: smbd.
Jan 18 11:11:48 PC1 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Jan 18 11:11:54 PC1 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jan 18 11:11:54 PC1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 18 11:11:54 PC1 dhclient: DHCPOFFER from 10.0.0.138
Jan 18 11:11:54 PC1 dhclient: DHCPACK from 10.0.0.138
Jan 18 11:11:54 PC1 avahi-autoipd(eth0)[1149]: Got SIGTERM, quitting.
Jan 18 11:11:54 PC1 avahi-autoipd(eth0)[1149]: Callout STOP, address 169.254.10.64 on interface eth0
Jan 18 11:11:54 PC1 avahi-daemon[643]: Withdrawing address record for 169.254.10.64 on eth0.
Jan 18 11:11:54 PC1 avahi-daemon[643]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.10.64.
Jan 18 11:11:54 PC1 avahi-daemon[643]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 18 11:11:54 PC1 smbd[1651]: Reloading /etc/samba/smb.conf: smbd.
Jan 18 11:11:56 PC1 avahi-daemon[643]: Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.0.1.
Jan 18 11:11:56 PC1 avahi-daemon[643]: New relevant interface eth0.IPv4 for mDNS.
Jan 18 11:11:56 PC1 avahi-daemon[643]: Registering new address record for 10.0.0.1 on eth0.IPv4.
Jan 18 11:11:56 PC1 dhclient: bound to 10.0.0.1 -- renewal in 122193 seconds.
Jan 18 11:29:58 PC1 systemd[1700]: Starting Paths.
Jan 18 11:29:58 PC1 systemd[1700]: Reached target Paths.
Jan 18 11:29:58 PC1 systemd[1700]: Starting Timers.
Jan 18 11:29:58 PC1 systemd[1700]: Reached target Timers.
Jan 18 11:29:58 PC1 systemd[1700]: Starting Sockets.
Jan 18 11:29:58 PC1 systemd[1700]: Reached target Sockets.
Jan 18 11:29:58 PC1 systemd[1700]: Starting Basic System.
Jan 18 11:29:58 PC1 systemd[1700]: Reached target Basic System.
Jan 18 11:29:58 PC1 systemd[1700]: Starting Default.
Jan 18 11:29:58 PC1 systemd[1700]: Reached target Default.
Jan 18 11:29:58 PC1 systemd[1700]: Startup finished in 9ms.
Jan 18 11:29:59 PC1 colord: Automatic remove of icc-975bbea3db647e42a63cbbec807f0487 from xrandr-Chimei Innolux Corporation
Jan 18 11:29:59 PC1 colord: Profile removed: icc-975bbea3db647e42a63cbbec807f0487
Jan 18 11:29:59 PC1 colord: device removed: xrandr-Chimei Innolux Corporation
Jan 18 11:30:03 PC1 dbus[644]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Jan 18 11:30:03 PC1 udisksd[1798]: udisks daemon version 2.1.3 starting
Jan 18 11:30:03 PC1 dbus[644]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Jan 18 11:30:03 PC1 udisksd[1798]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jan 18 11:30:04 PC1 rtkit-daemon[1084]: Successfully made thread 1871 of process 1871 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Jan 18 11:30:04 PC1 rtkit-daemon[1084]: Supervising 5 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 5 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Successfully made thread 1875 of process 1871 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 6 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 6 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Successfully made thread 1877 of process 1871 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 7 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 7 threads of 2 processes of 2 users.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Successfully made thread 1878 of process 1871 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Jan 18 11:30:05 PC1 rtkit-daemon[1084]: Supervising 8 threads of 2 processes of 2 users.
Jan 18 12:03:47 PC1 freshclam[632]: Received signal: wake up
Jan 18 12:03:47 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 12:03:47 2015
Jan 18 12:03:47 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 12:03:48 PC1 freshclam[632]: Downloading daily-19943.cdiff [100%]#015Downloading daily-19943.cdiff [100%]
Jan 18 12:03:51 PC1 freshclam[632]: daily.cld updated (version: 19943, sigs: 1310554, f-level: 63, builder: neo)
Jan 18 12:03:51 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 12:03:55 PC1 freshclam[632]: Database updated (3734822 signatures) from db.local.clamav.net (IP: 158.197.16.70)
Jan 18 12:03:55 PC1 freshclam[632]: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Jan 18 13:03:55 PC1 freshclam[632]: Received signal: wake up
Jan 18 13:03:55 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 13:03:55 2015
Jan 18 13:03:55 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 13:03:55 PC1 freshclam[632]: Downloading daily-19944.cdiff [100%]#015Downloading daily-19944.cdiff [100%]
Jan 18 13:03:57 PC1 freshclam[632]: daily.cld updated (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 13:03:57 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 13:04:01 PC1 freshclam[632]: Database updated (3734832 signatures) from db.local.clamav.net (IP: 92.240.244.203)
Jan 18 13:04:01 PC1 freshclam[632]: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Jan 18 14:04:01 PC1 freshclam[632]: Received signal: wake up
Jan 18 14:04:01 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 14:04:01 2015
Jan 18 14:04:01 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 14:04:01 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 14:04:01 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 15:04:05 PC1 freshclam[632]: Received signal: wake up
Jan 18 15:04:05 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 15:04:05 2015
Jan 18 15:04:05 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 15:04:05 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 15:04:05 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 15:15:30 PC1 dbus[644]: [system] Activating service name='org.freedesktop.SystemToolsBackends' (using servicehelper)
Jan 18 15:15:31 PC1 dbus[644]: [system] Successfully activated service 'org.freedesktop.SystemToolsBackends'
Jan 18 15:15:31 PC1 dbus[644]: [system] Activating service name='org.freedesktop.SystemToolsBackends.Platform' (using servicehelper)
Jan 18 15:15:31 PC1 dbus[644]: [system] Successfully activated service 'org.freedesktop.SystemToolsBackends.Platform'
Jan 18 15:15:31 PC1 dbus[644]: [system] Activating service name='org.freedesktop.SystemToolsBackends.ServicesConfig' (using servicehelper)
Jan 18 15:15:31 PC1 dbus[644]: [system] Successfully activated service 'org.freedesktop.SystemToolsBackends.ServicesConfig'
Jan 18 16:04:08 PC1 freshclam[632]: Received signal: wake up
Jan 18 16:04:08 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 16:04:08 2015
Jan 18 16:04:08 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 16:04:08 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 16:04:08 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 17:04:12 PC1 freshclam[632]: Received signal: wake up
Jan 18 17:04:12 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 17:04:12 2015
Jan 18 17:04:12 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 17:04:12 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 17:04:12 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 18:04:15 PC1 freshclam[632]: Received signal: wake up
Jan 18 18:04:15 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 18:04:15 2015
Jan 18 18:04:15 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 18:04:15 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 18:04:15 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 19:04:19 PC1 freshclam[632]: Received signal: wake up
Jan 18 19:04:19 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 19:04:19 2015
Jan 18 19:04:19 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 19:04:19 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 19:04:19 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 20:04:23 PC1 freshclam[632]: Received signal: wake up
Jan 18 20:04:23 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 20:04:23 2015
Jan 18 20:04:23 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 20:04:23 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 20:04:23 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 21:04:26 PC1 freshclam[632]: Received signal: wake up
Jan 18 21:04:26 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 21:04:26 2015
Jan 18 21:04:27 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 21:04:27 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 21:04:27 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 22:04:30 PC1 freshclam[632]: Received signal: wake up
Jan 18 22:04:30 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 22:04:30 2015
Jan 18 22:04:30 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 22:04:30 PC1 freshclam[632]: daily.cld is up to date (version: 19944, sigs: 1310564, f-level: 63, builder: neo)
Jan 18 22:04:30 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 23:04:34 PC1 freshclam[632]: Received signal: wake up
Jan 18 23:04:34 PC1 freshclam[632]: ClamAV update process started at Sun Jan 18 23:04:34 2015
Jan 18 23:04:34 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 18 23:04:34 PC1 freshclam[632]: Downloading daily-19945.cdiff [ 36%]#015Downloading daily-19945.cdiff [ 82%]#015Downloading daily-19945.cdiff [100%]#015Downloading daily-19945.cdiff [100%]
Jan 18 23:04:36 PC1 freshclam[632]: daily.cld updated (version: 19945, sigs: 1310643, f-level: 63, builder: neo)
Jan 18 23:04:36 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 18 23:04:40 PC1 freshclam[632]: Database updated (3734911 signatures) from db.local.clamav.net (IP: 147.229.3.144)
Jan 18 23:04:40 PC1 freshclam[632]: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Jan 19 00:04:40 PC1 freshclam[632]: Received signal: wake up
Jan 19 00:04:40 PC1 freshclam[632]: ClamAV update process started at Mon Jan 19 00:04:40 2015
Jan 19 00:04:40 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 19 00:04:40 PC1 freshclam[632]: daily.cld is up to date (version: 19945, sigs: 1310643, f-level: 63, builder: neo)
Jan 19 00:04:40 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 19 01:04:43 PC1 freshclam[632]: Received signal: wake up
Jan 19 01:04:43 PC1 freshclam[632]: ClamAV update process started at Mon Jan 19 01:04:43 2015
Jan 19 01:04:43 PC1 freshclam[632]: main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
Jan 19 01:04:44 PC1 freshclam[632]: Downloading daily-19946.cdiff [|]#015Downloading daily-19946.cdiff [/]#015Downloading daily-19946.cdiff [-]#015Downloading daily-19946.cdiff [\]#015Downloading daily-19946.cdiff [|]#015Downloading daily-19946.cdiff [/]#015Downloading daily-19946.cdiff [-]#015Downloading daily-19946.cdiff [\]#015Downloading daily-19946.cdiff [|]#015Downloading daily-19946.cdiff [*]
Jan 19 01:04:48 PC1 freshclam[632]: daily.cld updated (version: 19946, sigs: 1311054, f-level: 63, builder: neo)
Jan 19 01:04:48 PC1 freshclam[632]: bytecode.cld is up to date (version: 245, sigs: 43, f-level: 63, builder: dgoddard)
Jan 19 01:04:51 PC1 freshclam[632]: Database updated (3735322 signatures) from db.local.clamav.net (IP: 94.23.169.95)
Jan 19 01:04:51 PC1 freshclam[632]: ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
Jan 19 01:58:46 PC1 NetworkManager[625]: <info> caught signal 15, shutting down normally.
Jan 19 01:58:46 PC1 NetworkManager[625]: <info> (wlan0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Jan 19 01:58:46 PC1 ModemManager[631]: <info>  Caught signal, shutting down...
Jan 19 01:58:46 PC1 NetworkManager[625]: <info> exiting (success)
Jan 19 01:58:46 PC1 NetworkManager[625]: (NetworkManager:625): GLib-CRITICAL **: Source ID 24 was not found when attempting to remove it
Jan 19 01:58:46 PC1 freshclam[632]: Update process terminated
Jan 19 11:00:40 PC1 systemd-modules-load[155]: Inserted module 'fuse'
Jan 19 11:00:40 PC1 systemd-fsck[151]: koren: čistý, 149465/549440 souborů, 1094893/2196992 bloků
Jan 19 11:00:40 PC1 systemd-udevd[177]: Network interface NamePolicy= disabled on kernel commandline, ignoring.
Jan 19 11:00:40 PC1 hdparm[180]: Setting parameters of disc: (none).
Jan 19 11:00:40 PC1 keyboard-setup[179]: Setting preliminary keymap...done.
Jan 19 11:00:40 PC1 freshclam[632]: ERROR: Can't save PID to file /var/run/clamav/freshclam.pid: No such file or directory
Jan 19 11:00:40 PC1 freshclam[632]: ClamAV update process started at Mon Jan 19 11:00:40 2015
Jan 19 11:00:40 PC1 freshclam[632]: WARNING: Can't query current.cvd.clamav.net
Jan 19 11:00:40 PC1 freshclam[632]: WARNING: Invalid DNS reply. Falling back to HTTP mode.
Jan 19 11:00:40 PC1 freshclam[632]: Reading CVD header (main.cvd): WARNING: Can't get information about db.local.clamav.net: Name or service not known
Jan 19 11:00:40 PC1 freshclam[632]: WARNING: Can't read main.cvd header from db.local.clamav.net (IP: )
Jan 19 11:00:40 PC1 acpid: 1 rule loaded
Jan 19 11:00:40 PC1 acpid: waiting for events: event logging is off
Jan 19 11:00:40 PC1 freshclam[632]: Trying again in 5 secs...
Jan 19 11:00:40 PC1 avahi-daemon[643]: Server startup complete. Host name is PC1.local. Local service cookie is 800783804.
Jan 19 11:00:41 PC1 polkitd[927]: started daemon version 0.105 using authority implementation `local' version `0.105'
Jan 19 11:00:41 PC1 dbus[644]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 19 11:00:41 PC1 accounts-daemon[621]: started daemon version 0.6.37
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> init!
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> update_system_hostname
Jan 19 11:00:41 PC1 NetworkManager[625]: <info>       interface-parser: parsing file /etc/network/interfaces
Jan 19 11:00:41 PC1 NetworkManager[625]: <info>       interface-parser: finished parsing file /etc/network/interfaces
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> guessed connection type (eth0) = 802-3-ethernet
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> adding eth0 to connections
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> adding iface eth0 to eni_ifaces
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> autoconnect
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> management mode: unmanaged
Jan 19 11:00:41 PC1 NetworkManager[625]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:08:00.0/net/eth0, iface: eth0)

Nechce to vzít víc jak 20000 znaků.  Nenašel jsem způsob, jak to sem celé dostat. Předem moc děkuji. Michal
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 19. 01. 2015, 21:12:44
Tohle nevypadá na problém s DHCP klientem, ten dostane normálně IP adresu od serveru a nahlásí, že ji bude držet. Zkus navodit ten problémový stav a poslat sem výpis dvou příkazů:

# ip a
# cat /etc/resolv.conf
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 20. 01. 2015, 01:16:24

PŘED PŘIPOJENÍM:
michal@PC1:~$ su
Heslo:
root@PC1:/home/michal# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f8:a9:63:42:bc:d2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::faa9:63ff:fe42:bcd2/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 18:cf:5e:a2:b2:fb brd ff:ff:ff:ff:ff:ff
root@PC1:/home/michal#
root@PC1:/home/michal# cat /etc/resolv.conf
nameserver 10.0.0.138
root@PC1:/home/michal#


PO PŘŘIPOJENÍ:
root@PC1:/home/michal# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether f8:a9:63:42:bc:d2 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.1/24 brd 10.0.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::faa9:63ff:fe42:bcd2/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 18:cf:5e:a2:b2:fb brd ff:ff:ff:ff:ff:ff
root@PC1:/home/michal#
root@PC1:/home/michal# cat /etc/resolv.conf
nameserver 10.0.0.138
root@PC1:/home/michal#

Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 20. 01. 2015, 09:19:57
To vypadá dobře, IP adresu máš a resolver funguje. Rozhodně to nevypadá na problém s DHCP, protože adresu jsi dostal. Ve chvíli toho výpisu ti tedy net nejel? Zkus ping a traceroute (tracepath) na 8.8.8.8.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 21. 01. 2015, 14:35:56
. Ve chvíli toho výpisu ti tedy net nejel?
Jel, protože jsem koň. Omlouvám se. Původní výpis opraven a doplněn po restartu.

Ostatní příkazy po restartu:
michal@PC1:~$ tracepath 8.8.8.8
bash: tracepath: příkaz nenalezen
m.ichal@PC1:~$ traceroute 8.8.8.8.
traceroute to 8.8.8.8 (8.8.8.8 ), 30 hops max, 60 byte packets
1  PC1 (169.254.10.64)  2996.925 ms !H  2996.883 ms !H  2996.876 ms !H
michal@PC1:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8 ) 56(84) bytes of data.
From 169.254.10.64 icmp_seq=1 Destination Host Unreachable
From 169.254.10.64 icmp_seq=2 Destination Host Unreachable
From 169.254.10.64 icmp_seq=3 Destination Host Unreachable
From 169.254.10.64 icmp_seq=4 Destination Host Unreachable
From 169.254.10.64 icmp_seq=8 Destination Host Unreachable
From 169.254.10.64 icmp_seq=9 Destination Host Unreachable

Právě jsem si všiml, že na těchto stránkách je uvedena moje IP adresa a ta má jiné číslo: 90.176.159.83? Není v tom souvislost?
Děkuji.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 21. 01. 2015, 22:21:49
Ta adresa 90.176.159.83 je veřejná a patří k ADSL od O2, to je asi v pořádku. Ty řešíš privátní adresu z desítkového rozsahu. Skutečně to podle toho výpisu vypadá, že jsi ji nedostal. Hm.

Zkus v té situaci pustit jako root:

# dhclient eth0

Vypíše to něco nebo to normálně adresu přidělí a začne to fungovat?
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 22. 01. 2015, 01:50:37
Nevypíše to nic. Do cca 2-3s normálně adresu přidělí a začne to fungovat.
michal@PC1:~$ su
Heslo:
root@PC1:/home/michal# dhclient eth0
root@PC1:/home/michal#

Toto vypsal po provedení  /syslog:
Jan 22 01:39:02 PC1 rsyslogd0: action 'action 17' resumed (module 'builtin:ompipe') [try http://www.rsyslog.com/e/0 ]
Jan 22 01:39:02 PC1 rsyslogd-2359: action 'action 17' resumed (module 'builtin:ompipe') [try http://www.rsyslog.com/e/2359 ]
Jan 22 01:39:02 PC1 systemd[1868]: Starting Paths.
Jan 22 01:39:02 PC1 systemd[1868]: Reached target Paths.
Jan 22 01:39:02 PC1 systemd[1868]: Starting Timers.
Jan 22 01:39:02 PC1 systemd[1868]: Reached target Timers.
Jan 22 01:39:02 PC1 systemd[1868]: Starting Sockets.
Jan 22 01:39:02 PC1 systemd[1868]: Reached target Sockets.
Jan 22 01:39:02 PC1 systemd[1868]: Starting Basic System.
Jan 22 01:39:02 PC1 systemd[1868]: Reached target Basic System.
Jan 22 01:39:02 PC1 systemd[1868]: Starting Default.
Jan 22 01:39:02 PC1 systemd[1868]: Reached target Default.
Jan 22 01:39:02 PC1 systemd[1868]: Startup finished in 14ms.
Jan 22 01:39:33 PC1 systemd[1868]: Stopping Default.
Jan 22 01:39:33 PC1 systemd[1868]: Stopped target Default.
Jan 22 01:39:33 PC1 systemd[1868]: Stopping Basic System.
Jan 22 01:39:33 PC1 systemd[1868]: Stopped target Basic System.
Jan 22 01:39:33 PC1 systemd[1868]: Stopping Paths.
Jan 22 01:39:33 PC1 systemd[1868]: Stopped target Paths.
Jan 22 01:39:33 PC1 systemd[1868]: Stopping Timers.
Jan 22 01:39:33 PC1 systemd[1868]: Stopped target Timers.
Jan 22 01:39:33 PC1 systemd[1868]: Stopping Sockets.
Jan 22 01:39:33 PC1 systemd[1868]: Stopped target Sockets.
Jan 22 01:39:33 PC1 systemd[1868]: Starting Shutdown.
Jan 22 01:39:33 PC1 systemd[1868]: Starting Exit the Session...
Jan 22 01:39:33 PC1 systemd[1884]: Failed at step CHDIR spawning /bin/kill: No such file or directory
Jan 22 01:39:33 PC1 systemd[1868]: systemd-exit.service: main process exited, code=exited, status=200/CHDIR
Jan 22 01:39:33 PC1 systemd[1868]: Failed to start Exit the Session.
Jan 22 01:39:33 PC1 systemd[1868]: Dependency failed for Exit the Session.
Jan 22 01:39:33 PC1 systemd[1868]: Unit systemd-exit.service entered failed state.
Jan 22 01:39:34 PC1 anacron[630]: Job `cron.daily' terminated
Jan 22 01:39:34 PC1 anacron[630]: Normal exit (1 job run)
Jan 22 01:41:03 PC1 systemd[1]: user@65534.service stop-sigterm timed out. Killing.
Jan 22 01:41:03 PC1 systemd[1]: Unit user@65534.service entered failed state.
Jan 22 01:41:37 PC1 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jan 22 01:41:37 PC1 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 22 01:41:37 PC1 dhclient: DHCPOFFER from 10.0.0.138
Jan 22 01:41:37 PC1 dhclient: DHCPACK from 10.0.0.138
Jan 22 01:41:37 PC1 smbd[1927]: Reloading /etc/samba/smb.conf: smbd.
Jan 22 01:41:37 PC1 dhclient: bound to 10.0.0.2 -- renewal in 115964 seconds.

Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 22. 01. 2015, 10:25:51
Bezva, to vypadá normálně. A jak máš nastavené to přidělování IP adresy normálně? Kdo má u tebe vyvolat toho DHCP klienta?
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 22. 01. 2015, 11:49:26
To nevím. Nic jsem nikdy nenastavoval. Nainstalovalo se to a nastavilo vždy samo. Jsem připojen kabelem a wi-fi je vypnutá. Jsem na velmi slabém ledě. O tom moc, nebo správně řečeno skoro nic nevím. Drátové připojení hlásí, že zařízení není spravováno a wi-fi je vypnutá. Nevím jakým směrem se vydat.  Prosím o přiblížení. Děkuji.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 22. 01. 2015, 13:38:40
Aha, klíčové slovo je tedy Network Manager. To je démon, který se ti stará o připojení. Pokud nespravuje ethernet, tak ani nespouští DHCP klienta. V tom je ten problém. Mělo by pomoci v souboru /etc/NetworkManager/NetworkManager.conf změnit řádek managed na true. Asi tak:

[ifupdown]
managed=true
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 22. 01. 2015, 21:03:47
Řádek v souboru /etc/NetworkManager/NetworkManager.conf změněn (Celý soubor.):
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true
Výsledek se zatim nedostavil.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: čepi kdy 22. 01. 2015, 21:12:30
Odinstaluj NetworkManagera (network-manager-gnome ?) a nainstaluj treba wicd.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 23. 01. 2015, 23:54:31
Zdravím. Jenom dotaz.
Odinstaluj NetworkManagera (network-manager-gnome ?)
Mám tu:
network-manager-gnome  0.9.10.0-2
a
network-manager 0.9.10.0-5

Mám odinstalovat oboje a nebo jen network-mnager-gnome?
Předem děkuji. 
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Petr Krčmář kdy 24. 01. 2015, 07:20:10
Samotný Network Manager je démon, který se stará o síť, to druhé je jen klikací ovládátko. Můžeš odinstalovat obojí.
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 25. 01. 2015, 01:20:58
Zdravím všechny. Kdysi jsem měl báječného přítele, kamaráda a ten říkával, když něco hned nešlapalo na PC. ''Víme, že všechny věci jsou kompatibilní, jenom některé věci jsou kompatibilnější ale rozchodime to.''
Nevím jak to mám správně napsat. Wicd jde v poměru cca 1:3  (Nejde 1x potřebuje asi 12 min. na připojení : jde 3x okolo 1 min.)

/var/log/wicd
2015/01/24 23:37:29 :: wicd initializing...
2015/01/24 23:37:29 :: ---------------------------
2015/01/24 23:37:29 :: wicd is version 1.7.2.4 768
2015/01/24 23:37:29 :: setting backend to external
2015/01/24 23:37:29 :: trying to load backend external
2015/01/24 23:37:29 :: successfully loaded backend external
2015/01/24 23:37:29 :: trying to load backend external
2015/01/24 23:37:29 :: successfully loaded backend external
2015/01/24 23:37:29 :: Automatically detected wireless interface wlan0
2015/01/24 23:37:29 :: setting wireless interface wlan0
2015/01/24 23:37:30 :: automatically detected wired interface eth0
2015/01/24 23:37:30 :: setting wired interface eth0
2015/01/24 23:37:30 :: setting wpa driver wext
2015/01/24 23:37:31 :: setting use global dns to False
2015/01/24 23:37:31 :: setting global dns
2015/01/24 23:37:31 :: global dns servers are None None None
2015/01/24 23:37:31 :: domain is None
2015/01/24 23:37:31 :: search domain is None
2015/01/24 23:37:31 :: setting automatically reconnect when connection drops True
2015/01/24 23:37:31 :: Setting dhcp client to 0
2015/01/24 23:37:33 :: Wireless configuration file found...
2015/01/24 23:37:33 :: Wired configuration file found...
2015/01/24 23:37:33 :: chmoding configuration files 0600...
2015/01/24 23:37:33 :: chowning configuration files root:root...
2015/01/24 23:37:33 :: Using wireless interface...wlan0
2015/01/24 23:37:33 :: Using wired interface...eth0
2015/01/24 23:37:38 :: Autoconnecting...
2015/01/24 23:37:39 :: attempting to set hostname with dhclient
2015/01/24 23:37:39 :: using dhcpcd or another supported client may work better
2015/01/24 23:37:39 :: attempting to set hostname with dhclient
2015/01/24 23:37:39 :: using dhcpcd or another supported client may work better
2015/01/24 23:37:40 :: Attempting to autoconnect with wired interface...
2015/01/24 23:37:40 :: Putting interface down
2015/01/24 23:37:40 :: Releasing DHCP leases...
2015/01/24 23:37:40 :: attempting to set hostname with dhclient
2015/01/24 23:37:40 :: using dhcpcd or another supported client may work better
2015/01/24 23:37:40 :: Setting false IP...
2015/01/24 23:37:40 :: Stopping wpa_supplicant
2015/01/24 23:37:40 :: Flushing the routing table...
2015/01/24 23:37:40 :: Putting interface up...
2015/01/24 23:37:42 :: Running DHCP with hostname PC1
2015/01/24 23:37:42 :: attempting to set hostname with dhclient
2015/01/24 23:37:42 :: using dhcpcd or another supported client may work better
2015/01/24 23:37:42 :: Internet Systems Consortium DHCP Client 4.3.1
2015/01/24 23:37:42 :: Copyright 2004-2014 Internet Systems Consortium.
2015/01/24 23:37:42 :: All rights reserved.
2015/01/24 23:37:42 :: For info, please visit https://www.isc.org/software/dhcp/
2015/01/24 23:37:42 ::
2015/01/24 23:37:42 :: Listening on LPF/eth0/f8:a9:63:42:bc:d2
2015/01/24 23:37:42 :: Sending on   LPF/eth0/f8:a9:63:42:bc:d2
2015/01/24 23:37:42 :: Sending on   Socket/fallback
2015/01/24 23:37:42 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
2015/01/24 23:37:45 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
2015/01/24 23:37:50 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
2015/01/24 23:37:58 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
2015/01/24 23:38:14 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
2015/01/24 23:38:23 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
2015/01/24 23:38:35 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
2015/01/24 23:38:42 :: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2015/01/24 23:38:42 :: DHCPOFFER from 10.0.0.138
2015/01/24 23:38:42 :: DHCPACK from 10.0.0.138
2015/01/24 23:38:42 :: bound to 10.0.0.2 -- renewal in 122133 seconds.
2015/01/24 23:38:42 :: DHCP connection successful
2015/01/24 23:38:42 :: Connecting thread exiting.
2015/01/24 23:38:46 :: Sending connection attempt result success
2015/01/25 00:07:14 :: ---------------------------
2015/01/25 00:07:14 :: wicd initializing...
2015/01/25 00:07:14 :: ---------------------------
2015/01/25 00:07:14 :: wicd is version 1.7.2.4 768
2015/01/25 00:07:14 :: setting backend to external
2015/01/25 00:07:14 :: trying to load backend external
2015/01/25 00:07:14 :: successfully loaded backend external
2015/01/25 00:07:14 :: trying to load backend external
2015/01/25 00:07:14 :: successfully loaded backend external
2015/01/25 00:07:14 :: Automatically detected wireless interface wlan0
2015/01/25 00:07:14 :: setting wireless interface wlan0
2015/01/25 00:07:14 :: automatically detected wired interface eth0
2015/01/25 00:07:14 :: setting wired interface eth0
2015/01/25 00:07:15 :: setting wpa driver wext
2015/01/25 00:07:16 :: setting use global dns to False
2015/01/25 00:07:16 :: setting global dns
2015/01/25 00:07:16 :: global dns servers are None None None
2015/01/25 00:07:16 :: domain is None
2015/01/25 00:07:16 :: search domain is None
2015/01/25 00:07:16 :: setting automatically reconnect when connection drops True
2015/01/25 00:07:18 :: Setting dhcp client to 0
2015/01/25 00:07:19 :: Wireless configuration file found...
2015/01/25 00:07:19 :: Wired configuration file found...
2015/01/25 00:07:19 :: chmoding configuration files 0600...
2015/01/25 00:07:19 :: chowning configuration files root:root...
2015/01/25 00:07:19 :: Using wireless interface...wlan0
2015/01/25 00:07:19 :: Using wired interface...eth0
2015/01/25 00:07:24 :: Autoconnecting...
2015/01/25 00:07:25 :: attempting to set hostname with dhclient
2015/01/25 00:07:25 :: using dhcpcd or another supported client may work better
2015/01/25 00:07:26 :: attempting to set hostname with dhclient
2015/01/25 00:07:26 :: using dhcpcd or another supported client may work better
2015/01/25 00:07:26 :: Attempting to autoconnect with wired interface...
2015/01/25 00:07:26 :: Putting interface down
2015/01/25 00:07:26 :: Releasing DHCP leases...
2015/01/25 00:07:26 :: attempting to set hostname with dhclient
2015/01/25 00:07:26 :: using dhcpcd or another supported client may work better
2015/01/25 00:07:27 :: Setting false IP...
2015/01/25 00:07:27 :: Stopping wpa_supplicant
2015/01/25 00:07:27 :: Flushing the routing table...
2015/01/25 00:07:27 :: Putting interface up...
2015/01/25 00:07:29 :: Running DHCP with hostname PC1
2015/01/25 00:07:29 :: attempting to set hostname with dhclient
2015/01/25 00:07:29 :: using dhcpcd or another supported client may work better
2015/01/25 00:07:29 :: Internet Systems Consortium DHCP Client 4.3.1
2015/01/25 00:07:29 :: Copyright 2004-2014 Internet Systems Consortium.
2015/01/25 00:07:29 :: All rights reserved.
2015/01/25 00:07:29 :: For info, please visit https://www.isc.org/software/dhcp/
2015/01/25 00:07:29 ::
2015/01/25 00:07:29 :: Listening on LPF/eth0/f8:a9:63:42:bc:d2
2015/01/25 00:07:29 :: Sending on   LPF/eth0/f8:a9:63:42:bc:d2
2015/01/25 00:07:29 :: Sending on   Socket/fallback
2015/01/25 00:07:29 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
2015/01/25 00:07:34 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
2015/01/25 00:07:43 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
2015/01/25 00:07:56 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
2015/01/25 00:08:12 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
2015/01/25 00:08:25 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
2015/01/25 00:08:30 :: No DHCPOFFERS received.
2015/01/25 00:08:30 :: No working leases in persistent database - sleeping.
2015/01/25 00:08:30 :: DHCP connection failed
2015/01/25 00:08:30 :: exiting connection thread
2015/01/25 00:08:31 :: No wired connection present, attempting to autoconnect to wireless network
2015/01/25 00:08:32 :: Unable to autoconnect, you'll have to manually connect
2015/01/25 00:08:33 :: Sending connection attempt result dhcp_failed
2015/01/25 00:08:33 :: attempting to set hostname with dhclient
2015/01/25 00:08:33 :: using dhcpcd or another supported client may work better
2015/01/25 00:08:34 :: attempting to set hostname with dhclient
2015/01/25 00:08:34 :: using dhcpcd or another supported client may work better


Ještě jsem zadal příkaz v terminále a ten se vyplnil až na podruhé cca po 3 min..:
michal@PC1:~$ su
Heslo:
root@PC1:/home/michal# dhclient eth0
root@PC1:/home/michal# dhclient eth0
root@PC1:/home/michal# dhclient eth0
RTNETLINK answers: File exists
root@PC1:/home/michal#


Předem moc děkuji. Michal
Název: Re:Systém z nějakého důvodu nespustí DHCP klienta automaticky hned, ale až za 6 min
Přispěvatel: Michal kdy 15. 02. 2015, 16:30:10
Nu a jak to vše dopadlo?
NetworkManagera jsem nainstaloval zpět, protože Wicd byl o mnoho horší. Jak jsem již popisoval. Po týdnu přišla nějaká oprava balíčků začínajících na lib...  a od té doby vše pracuje, tak jak má.  Všem moc děkuji za pomoc a přeji krásný a úspěšný den. Michal