On 08/05/2011 08:47 PM, Tom H wrote:
On Fri, Aug 5, 2011 at 7:55 AM, Joachim Backes joachim.backes@rhrk.uni-kl.de wrote:
On 08/05/2011 11:33 AM, Tom H wrote:
On Fri, Aug 5, 2011 at 4:32 AM, Joachim Backes joachim.backes@rhrk.uni-kl.de wrote:
On 08/05/2011 09:37 AM, Tom H wrote:
On Fri, Aug 5, 2011 at 2:55 AM, Joachim Backes joachim.backes@rhrk.uni-kl.de wrote:
On 08/04/2011 10:19 PM, Rick Stevens wrote: > On 08/04/2011 05:36 AM, Joachim Backes wrote: >> >> Besides ifcfg-em1 and ifcfg-lo, I found some weird configuration files >> in /etc/sysconfig/network-scripts: >> >> ifcfg-Auto_abc >> ifcfg-Auto_linksys 1 >> ifcfg-Auto_linksys >> ifcfg-Auto_mycloud >> >> I don't know who is reponsible for creating these files. But I saw that >> they slowed down NetworkManager's speed after boot when logging in for >> the first time (it took about 20 secs until the network was completely >> up). After having removed these files, I saw a significant improvement >> of NetworkManager. >> >> Anybody has an explication? > > They're NetworkManager files and are typically created when it finds > wireless networks.
Maybe. But there is no such device attached to my box.
They look like SSIDs rather than devices.
Ooops, I have no WLAN access (connection to the router is available by LAN)!
It was a good WAG since linksys and mycloud do suggest SSID names. Anyway, if this is on a laptop, I don't think that you'd have to have current WiFi access to have these files.
It's a desktop PC. I'm not owner of a laptop -:)
(Some desktops have WiFi.)
Mine doesn't.
What's the output of "ifconfig -a" and what's the content of these "if cfg_Auto..." files?
1. ifconfig -a =========== em1 Link encap:Ethernet HWaddr 00:19:66:38:46:AA inet addr:192.168.100.101 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: 2002:5886:b283:0:219:66ff:fe38:46aa/64 Scope:Global inet6 addr: fe80::219:66ff:fe38:46aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5162 errors:0 dropped:0 overruns:0 frame:0 TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6402261 (6.1 MiB) TX bytes:251330 (245.4 KiB) Interrupt:40 Base address:0xc000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1824 (1.7 KiB) TX bytes:1824 (1.7 KiB)
virbr0 Link encap:Ethernet HWaddr 7A:86:B2:CE:E8:B7 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
2. File ifcfg-Auto_abc =================== HWADDR=00:1E:E5:E5:CD:87 ESSID="abc" MODE=Managed KEY_MGMT=WPA-PSK SECURITYMODE=open TYPE=Wireless BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no NAME="Auto abc" UUID=70d10d2a-5275-4c56-9b7a-8f69647175ea ONBOOT=yes
The others are similar.
Kind regards
Joachim Backes joachim.backes@rhrk.uni-kl.de