DHCP - pomalé získavanie IP adresy

[mino]

Dobrý deň,
mám taký otravný problém - po prebudení NB trvá ešte asi 16 sekúnd, niekedy aj viac, kým môžem ísť na internet, pretože načítanie IP adresy cez DHCP trvá strašne dlho. Mám Arch Linux a používam networkmanager. Prikladám aj výpis z /var/log/everything.log po zapojení kábla do eth0. Zdá sa mi čudné to, čo sa stane po 9 sekundách - "carrier now off" 

Kód: [Vybrat]

Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): carrier now ON (device state 20)
Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Auto-activating connection 'Wired connection 1'.
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) starting connection 'Wired connection 1'
Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jan 29 14:10:32 localhost NetworkManager[524]: <info> dhcpcd started with pid 5494
Jan 29 14:10:32 localhost NetworkManager[524]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jan 29 14:10:32 localhost kernel: [  764.132335] atl1c 0000:02:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Jan 29 14:10:32 localhost dhcpcd[5494]: version 5.2.12 starting
Jan 29 14:10:32 localhost NetworkManager[524]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Jan 29 14:10:32 localhost dhcpcd[5494]: eth0: rebinding lease of 192.168.1.102
Jan 29 14:10:41 localhost NetworkManager[524]: <info> (eth0): [b]carrier now OFF[/b] (device state 70, deferring action for 4 seconds)
Jan 29 14:10:41 localhost NetworkManager[524]: <info> (eth0): carrier now ON (device state 70)
Jan 29 14:10:41 localhost kernel: [  773.986866] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
Jan 29 14:10:41 localhost kernel: [  773.986934] atl1c 0000:02:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
Jan 29 14:10:42 localhost dhcpcd[5494]: eth0: broadcasting for a lease
Jan 29 14:10:42 localhost dhcpcd[5494]: eth0: offered 192.168.1.102 from 192.168.1.254
Jan 29 14:10:42 localhost dhcpcd[5494]: eth0: acknowledged 192.168.1.102 from 192.168.1.254
Jan 29 14:10:42 localhost dhcpcd[5494]: eth0: checking for 192.168.1.102
Jan 29 14:10:47 localhost dhcpcd[5494]: eth0: leased 192.168.1.102 for 864000 seconds
Jan 29 14:10:47 localhost NetworkManager[524]: <info> (eth0): DHCPv4 state changed preinit -> bound
Jan 29 14:10:47 localhost NetworkManager[524]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jan 29 14:10:47 localhost NetworkManager[524]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Jan 29 14:10:47 localhost NetworkManager[524]: <info>   address 192.168.1.102
Jan 29 14:10:47 localhost NetworkManager[524]: <info>   prefix 24 (255.255.255.0)
Jan 29 14:10:47 localhost NetworkManager[524]: <info>   gateway 192.168.1.254
Jan 29 14:10:47 localhost NetworkManager[524]: <info>   nameserver '192.168.1.254'
Jan 29 14:10:47 localhost NetworkManager[524]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jan 29 14:10:47 localhost NetworkManager[524]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Jan 29 14:10:47 localhost NetworkManager[524]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jan 29 14:10:48 localhost NetworkManager[524]: <info> (eth0): writing resolv.conf to /usr/sbin/resolvconf
Jan 29 14:10:48 localhost NetworkManager[524]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jan 29 14:10:48 localhost NetworkManager[524]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Jan 29 14:10:48 localhost NetworkManager[524]: <info> Activation (eth0) successful, device activated.
Jan 29 14:10:48 localhost NetworkManager[524]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jan 29 14:10:48 localhost dbus[494]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 29 14:10:48 localhost dbus[494]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Vie mi niekto prosím poradiť?

[Reklama]

[Pavel 'TIGER' Růžička]

Podle mne za tu dobu vypršelo přidělení adresy, když se probudí, zjistí, že adresa vypršela a tak si žádá o novou ... asi by bylo mnohem jednodušší udělat script, který hned po probuzení restartuje síť, mělo by to být rychlejší. O kolik, to si netroufám napsat.

[mino]

Som to zle sformuloval, tu nejde o to prebudenie, hned po prebudeni sa mi predsa restartuje siet...(alebo som zle pochopil to "restartovanie siete"?) Ide o to, ze ziskavanie IP predsa nemoze trvat tak dlho. Tzn., ze ked napr. teraz vytiahnem z NB internetovy kabel a pripojim ho spat, tak nie je normalne cakat 16 sek., niekedy aj pol minuty, kym bude net "funkcny". A zda sa mi podozrive to "carrier now OFF" vo vypise, ako keby sa uprostred ziskavania IP zacinalo odznova, alebo ako to je? Vie mi niekto podla prilozeneho vypisu vysvetlit, co sa tam tak dlho robi?

[KapitánRUM]

To je Atheroska ne?
Zkusil bych jiný ovladač a tím nemyslím zrovna JEN ten poslední
Ne-jednomu zákazníkovi na ní strašilo  ovšem výměna ovladače to vyřešila.

[mino]

Hej, Atheros je to, konkretne:
Ethernet controller: Atheros Communications AR8151 v1.0 Gigabit Ethernet (rev c0)
Tak sa pozriem asi po tych driveroch...

[Reklama]

[mino]

No tak ine drivery sa mi akosi nepodarilo najst...  Poriesil som to tak,ze som si nastavil staticku IP + zakazal som IPv6, tak sa to teraz zrychlilo na pouzitelnu uroven.

[KapitánRUM]

http://partner.atheros.com/Download.aspx?id=162

Ale dnes mi ten link nejde, asi to měli na Megauploadu