Slow network connection after uprade to kernel 2.6.19

Hello
Since I upgraded my kernel from 2.6.18 to 2.6.19 my connection to the net is extremely slow! Before the upgrade everything worked fine! And I haven't changed any config file.
When I ping my internal router (ping 10.0.0.1) I get sth. like the following:
64 bytes from 10.0.0.1: icmp_seq=133 ttl=127 time=391 ms
64 bytes from 10.0.0.1: icmp_seq=134 ttl=127 time=4394 ms
64 bytes from 10.0.0.1: icmp_seq=135 ttl=127 time=3383 ms
64 bytes from 10.0.0.1: icmp_seq=136 ttl=127 time=2382 ms
64 bytes from 10.0.0.1: icmp_seq=137 ttl=127 time=1381 ms
64 bytes from 10.0.0.1: icmp_seq=138 ttl=127 time=380 ms
64 bytes from 10.0.0.1: icmp_seq=139 ttl=127 time=0.280 ms
64 bytes from 10.0.0.1: icmp_seq=140 ttl=127 time=0.283 ms
64 bytes from 10.0.0.1: icmp_seq=141 ttl=127 time=0.283 ms
64 bytes from 10.0.0.1: icmp_seq=142 ttl=127 time=0.292 ms
So sometimes the rt is pretty ok and the next ping is about 100x slower.
With any other machine (gentoo, windows) I have no problems.
I checked several threads in the forum and followed every advice, but haven't found a solution!
http://bbs.archlinux.org/viewtopic.php? … nel+update
http://bbs.archlinux.org/viewtopic.php?t=27787
I have ip6 turned off and checked my /etc/hosts file. So I thought maybe it could be
a problem with the nic driver. But changing the driver (from r8169 to r1000) hasn't changed anything!
So now I really don't have a clue what the problem could be!
Any help really, really welcome!

It means you can downgrade your kernel if it's still in /var/cache/pacman/pkg.
I tried several kernels form 2.6.18 to 2.6.19.1, custom and kernel26 from repo, and still www response is horrible. It's strange, but only http protocol is broken. I have no problems with ftp, mail, torrents and others. Some websites loads normal and some of them not, especially based on mediawiki engine loads very long.
I tried many ways to solve this. I turned off iptables and almost all daemons, tested different browsers, removed browser cache and config, downgrade last upgrades, run network with dhcp and static addresses. I think it isn't dns problem, because the same reslov.conf I have on testing partition with ubuntu and it works flawlessly. My kernel doesn't have ipv6.
I'm running out of ideas now.

Similar Messages

My Mac Pro loses network connection after wake from sleep since Yosemite upgrade.

Mac Pro loses network connection after wake from sleep since Yosemite upgrade. Any one have this issue as well. And is there a work around?

Wi-Fi?
Wi-FI connection drops
Wi-Fi Problems in OS X Yosemite
Wi-Fi Problems in OS X Yosemite (2)
Wireless Diagnostics
Also try turning off Bluetooth.
Troubleshooting Wi-Fi issues in OS X
Wireless Connection Problems - Fix
Wireless Connection Problems - Fix (2)
Wireless Connection Problems - Fix (3)
Wireless Connection Problems - Fix (4)

Apple TV2 can't find my network connection after recent update?

Why can't my Apple TV2 can't find my network connection after recent update?

I had to update the software on my Airport Extreme then reset my apple tv and that resolved the issue for me.

I loose my home network connectivity after my iMac is awaken. This began after I upgraded to Lion. Is there a fix to this problem?

I loose my home network connectivity after my iMac is awaken. This began after I upgraded to Lion. Is there a fix to this problem?

see if this article helps: http://osxdaily.com/2011/11/06/lion-wi-fi-problems-solution-mac/?utm_source=feed burner&utm_medium=feed&utm_campaign=Feed%3A+osxdaily+%28OS+X+Daily%29&utm_conten t=FaceBook

FP1600 loses network connection after a few hours

My FP1600 loses its network connection after a few hours. It is part number 185690C-01, with firmware 4.11. I am running FieldPoint Explorer version 3.0.1 and LabView 6.1 from Windows XP Professional. I set it up, and everything runs fine for 4 hours or more. I do not have the network watchdog enabled, and the FP1600 is in constant communication with the host computer in any case. Sometime in the middle of the night the communication is lost. The FP1600 link light
is on, and it is still receiving packets, but it will not respond to a ping or any other communications. Only a power cycle brings it back. The FP1600 is sitting right next to the host computer, both attached to the same network switch. There is no interruptio
n of network services to the two.

Hi Heinz,
We are also trying to troubleshoot this same problem (Intermitten network connection loss with FP1600 Ethernet Module - Error code "33163", Error Message - "FP1600 Connection to module has been lost."). We have checked other possible causes for this sort of behaviour. Including independent assessment of netowork availability at the time of error reporting, connecting dedicated power supply to the FP1600 module, temperature of cabinet housing the module (which is between 10 and 50 deg C), disconnecting sensors connected to various I/O modules connected to this module, increasing duration of parameter "time out" (the time module will wait before reporting an error if it can not access network). However, none of the above resolved the intermittent and random network loss errors.
The MAX version is 3.0.2, and the firmware on the module is 4.17, Labview version is 7.0 and the Operating System is windows NT.
I was wondering is there any information about this problem from any user or NI recently. The only solution looking in to this discussion forum seems to be replacing the module.
MehulMessage Edited by MPatel on 02-28-2005 08:16 PM

Any news on ios 8.0.3 update? Been waiting for it coz of my slow wifi connection after i updated my iphone 5s to ios 8.

Any news on ios 8.0.3 update? Been waiting for it coz of my slow wifi connection after i updated my iphone 5s to ios 8.

I have heard rumours of an 8.1 update for developers. I just found another bug in 10.9.5. I am beginning to think that nobody should touch any update from Apple until they can get their very serious Q/A problems sorted out. This is getting bad.

Slow network connection possibly causing a slave to crash.

We are using Berkeley DB XML 2.4.16 (Patch level 1) in combination with Berkeley DB 4.7.25 (Patch level 3). These are Java processes.
We have a 4 node replication group with a master and a slave in the US, a slave in the UK and a slave in HK. We are using the built in replication manager. The acknowledgement policy is set to none. The HK slave OS is Red Hat Enterprise Linux ES release 3 (Taroon Update 8).
The slave in HK is on a fairly slow network connection to the master in the US.
The amount of traffic generated by the master can become fairly busy at times and this seemingly causes the HK slave to become fairly unstable. It would routinely crash (SIGSEGV) with the following back trace caught with gdb and a debug build of Berkeley DB XML/Berkeley DB. The location of the crash is very consistent. The UK slave also suffers this problem, but to a lesser degree (I suspect the faster network link to the UK to be a factor here).
#5 <signal handler called>
#6 0xb74fb2f8 in intfree () from /lib/tls/libc.so.6
#7 0xb74fa278 in free () from /lib/tls/libc.so.6
#8 0x6b7eee53 in __os_free (env=0x0, ptr=0x6ba335c0) at ../os/os_alloc.c:405
#9 0x6b751375 in message_loop (env=0x6ba1acc0) at ../repmgr/repmgr_msg.c:49
#10 0x6b7512a4 in __repmgr_msg_thread (args=0x6ba1acc0) at ../repmgr/repmgr_msg.c:29
#11 0xb75c9dd8 in start_thread () from /lib/tls/libpthread.so.0
#12 0xb7565d1a in clone () from /lib/tls/libc.so.6
We had been adjusting the rep_set_limit environment parameter to see if it would help. First to 5MB, then to 1MB with little or no improvement.
In an attempt to gather more information I had activated verbose replication logging on the HK slave which has had the side effect of fixing the problem.
Does this sound like something that could be addressed with the rep_set_request parameter?
I am no master on tuning these replication settings so some guidance would be appreciated.
Thanks,
Neil

OK,
I was able to reproduce the crash once again with verbose replication logging at the master, I know the verbose logging at the slave would be better but as we discussed that in fact fixes the problem, probably due the additional logging is throttling the replication mechanics a little.
Here is the back-trace…
#5 <signal handler called>
#6 0xb74fb2f8 in intfree () from /lib/tls/libc.so.6
#7 0xb74fa278 in free () from /lib/tls/libc.so.6
#8 0x6b7d3e53 in __os_free (env=0x0, ptr=0x6b9de2b0) at ../os/os_alloc.c:405
#9 0x6b736375 in message_loop (env=0x6b941da0) at ../repmgr/repmgr_msg.c:49
#10 0x6b7362a4 in __repmgr_msg_thread (args=0x6b941da0) at ../repmgr/repmgr_msg.c:29
#11 0xb75c9dd8 in start_thread () from /lib/tls/libpthread.so.0
#12 0xb7565d1a in clone () from /lib/tls/libc.so.6
Here is control info…
print msg->control
$1 = {data = 0x6b9de2f0, size = 36, ulen = 0, dlen = 0, doff = 0, app_data = 0x0, flags = 0}
x/36xb msg->control.data
0x6b9de2f0: 0x00 0x00 0x00 0x05 0x00 0x00 0x00 0x0e
0x6b9de2f8: 0x00 0x00 0x00 0xf6 0x00 0x37 0x1a 0xd7
0x6b9de300: 0x00 0x00 0x00 0x0b 0x00 0x00 0x00 0x01
0x6b9de308: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x6b9de310: 0x00 0x00 0x00 0x64
The HK site was a bit behind when I started the tests, I didn't have the slave instance up over the weekend, I don't now if this really effects the results as I believe the HK has a hard time keeping up when there is a large volume of replication traffic in the normal case, hence the resulting crash is the same…
Before the crash, the slave was synchronizing with the master and it was sending out what I would guess normal "nobuf" messages. This is quickly followed by a large amount of "nobuf resend" messages. This continues for a bit intermixed with " MASTER: wrote only 53 bytes to site XXX.XX.XX.XX:58010" (The number of bytes are random). In the end it starts logging the following several times along with the "nobuf resend" messages..
MASTER: msg to site XXX.XX.XX.XX:58010 to be queued
MASTER: block msg thread, await queue space
MASTER: will await drain
MASTER: drain returned 0 (0,0)
If you would like to take a look at the actual log, I will need a way to filter any sensitive information (which could prove to be difficult) or attempt to reproduce it with another pair rigged to be something generic and hope it exhibits the same behavior.

MBP takes long time to restore wired network connection after wake-up

Hello...
My Mid-2010 MBP (MacBookPro6,2) has been experiencing this problem recently -- Whenever I wake up the computer from sleep, it needs approximately 10 seconds to restore its wired network connection. I know there are other annoying connection issues with MBP's WiFi/AirPort out there, but I'm talking about the wired connection here.
Maybe some don't even think this slowness is a problem at all, but this laptop used to be network-ready right after wake-up until 3~4 months ago. That was around the time when I upgraded to SSD and changed some settings via pmset, not sure if that's the culprit. It is now running OS X 10.8.5 and its pmset settings are:
Battery Power:
lidwake              1
ttyskeepawake        1
hibernatemode        3
gpuswitch            2
hibernatefile        /var/vm/sleepimage
displaysleep         2
sleep                15
acwake               0
halfdim              1
sms                  0
lessbright           1
disksleep            10
AC Power:
lidwake              1
ttyskeepawake        1
hibernatemode        0
gpuswitch            2
hibernatefile        /var/vm/sleepimage
womp                 1
displaysleep         10
networkoversleep     0
sleep                60
acwake               0
halfdim              1
sms                  0
disksleep            0
I'd appreciate help of any kind
Thanks,
zuoy

Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
Hi All,
I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition. The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
party applications. Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem. I've also seen virtualization software like VMWare and VirtualBox cause similar issues
with network adapters.
The solution in most of the cases I've come across has been to stop and disable the Bonjour service. The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah". Here's how to disable this service
in Windows 7:
Right-Click on Computer > Select 'Manage'
Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
Right-Click on the service and select 'Properties'
Click the 'Stop' button to stop the service
Select 'Disabled' from the 'Startup type' drop down list
Click 'Apply' and then 'OK'
Reboot your machine and see if the "Multiple Networks" issue is resolved. If so, you should have internet connectivity again.
Hope this helps.
cheers,
Aaron

Macbook pro update 10.9.5 slow network connection smb

After the update my cable network connection got very slow. It's a smb connection to a qnap nas. Same problem on all the computers updated. Sistem not updated are working fine.

Hi shotsstudio,
Welcome to the Apple Support Communities!
For troubleshooting your Wi-Fi network with your Apple computer, I would first recommend reading over the attached article for troubleshooting steps. The steps that may be most appropriate for your situation are located in the Symptom: The Wi-Fi network seems slow section.
Wi-Fi: How to troubleshoot Wi-Fi connectivity
Have a great day,
Joe

Ethernet slow to connect after waking from sleep

Since installing Lion (and updating to 10.7.1) on my 2008 24" iMac I have noticed that after waking from sleep the internet connection takes about 10 seconds to restore. I have reset the SMC and PRAM and performed a safe boot (in case this helped) but to no avail. The slow conenction can be observed if after waking from sleep the Network System Preference is clicked and the ethernet status "light" is red, changes briefly to amber and then green indcating a connection. The iMac is connected via an ethernet cable to a Linksys 802.11n 4 port wireless router.
I also have a 2010 13" MacBook Pro, with the same OS, and version, conencted in the same way to the same Linksys router and it does not exhibit this problem.
This slow internet connection access after waking from sleep is an annoyance and I'd appreciate any input on how to elimnate it.
Thanks to those wiser than I, who might read this note.

SOLUTION FOUND!
I've found a list of possible solutions here's the link:
http://osxdaily.com/2011/07/22/wifi-dropping-in-os-x-lion-fixes/
I solved my problem moving the Ethernet and WiFi adapters in the top of the list and Bluetooth at the end.
Move Wi-Fi to the top of the Service Order list – This is an old tip that simply prioritizes WiFi as the primary method that your Mac should connect to the internet, and it seems to help maintain connections

Can not setup network connection after netctl 1.10 update

I'm using netctl's ifplugd service to automatically manage my network connections (LAN), however after latest update to netctl (1.10) I can not connect to other machines or internet anymore and I must downgrade to netctl 1.9.
Related netctl service:
[email protected]
My network connection profile: /etc/netctl/mynetwork
Description='A basic static ethernet connection'
Interface=enp2s0
Connection=ethernet
IP=static
Address=('192.168.1.1/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.1.254'
DNS=('192.168.1.254')
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'
Related bits from journald:
Jan 23 01:13:36 arch ifplugd[251]: ifplugd 0.28 initializing.
Jan 23 01:13:36 arch ifplugd[251]: Using interface enp2s0/00:23:54:2C:CE:94 with driver <ATL1E> (version: 1.0.0.7-NAPI)
Jan 23 01:13:36 arch ifplugd[251]: Using detection mode: SIOCETHTOOL
Jan 23 01:13:36 arch ifplugd[251]: Initialization complete, link beat not detected.
Jan 23 01:13:36 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Jan 23 01:13:36 arch acpid[246]: starting up with netlink and the input layer
Jan 23 01:13:36 arch acpid[246]: 1 rule loaded
Jan 23 01:13:36 arch acpid[246]: waiting for events: event logging is off
Jan 23 01:13:37 arch kernel: floppy0: no floppy controllers found
Jan 23 01:13:37 arch kernel: ATL1E 0000:02:00.0 enp2s0: NIC Link is Up <100 Mbps Full Duplex>
Jan 23 01:13:37 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
Jan 23 01:13:37 arch acpid[246]: client connected from 256[0:0]
Jan 23 01:13:37 arch acpid[246]: 1 client rule loaded
Jan 23 01:13:38 arch ifplugd[251]: Link beat detected.
Jan 23 01:13:39 arch ifplugd[251]: Executing '/etc/ifplugd/netctl.action enp2s0 up'.
Jan 23 01:13:39 arch ifplugd[251]: client: <3>Could not start any suitable profile
Jan 23 01:13:39 arch ifplugd[251]: Program execution failed, return value is 1.

This problem hit me too. I have a static IP address set up on a server, I upgraded netctl to 1.10 and it took me a couple of hours to work out why, after the upgrade, my network would not work. The messages were not helpful as I performed netctl starts, stops and status, or ip link commands. In the end I got the server back up by using ifconfig, ip addr add, ip route add etc. Then I found this forum entry (Thank you siavashserver and jouke!).
While the solution can be found in the netctl manual, it is a little obscure. I think this deserves the status of a bug. I don't think a simple upgrade should allow a whole class of users (everybody with a static ip address) to lose network connectivity without warning.
Even the (upgraded?) /etc/netctl/examples/ethernet-static file fails to include ExcludeAuto=no, so the documentation (at least in this regard) is faulty.
When I performed the upgrade I was warned
New optional dependencies for netctl
openvswitch: for Open vSwitch connections
ppp: for PPP connections
Is it possible to add a message there saying Warning! If you have a static ip address, this upgrade will destroy your network connectivity next time you reboot unless you add ExcludeAuto=no to your network profile?
jouke wrote:Add ExcludeAuto=no to your profile. As there is no way to check a statically configured IP address for correctness, they are excluded from automatic profile selection by default starting netctl 1.10. I am sorry for the inconvenience. From netctl 1.10 onwards, the behavior of netctl-ifplugd@ is documented in the man pages. For more information on ExcludeAuto= and Priority=, consult netctl.profile(5).

Outlook 2010 performance much slower than 2007 and 2003 when used with POP3 mail provider over slow network connection

When received messages include embedded pictures, Outlook 2010 does not persist those pictures in the .pst file with the message text. Instead, it redownloads the pictures every time the message is rendered for viewing or printing.
Send/Receive to replicate a message with multiple embedded pictures from POP3 mail server (not Exchange server)
Select and view the message - notice all the x placeholders for the embedded pictures
Right-click any x placeholder and select to "download pictures"
After some delay, the pictures are rendered, replacing the placeholders, to form the complete message
Now, select "File" and "Print" -- notice that the preview is not immediately displayed. There is a delay while thos same embedded pictures are downloaded, again. Sometimes there will be a pop-up notification that Outlook is "communicating with
the server"
Eventually the message is fully rendered with all embedded pictures
Now, select a different printer -- notice that the preview disappears and it takes time to .... yes, redownload those same pictures, again.
Finally, click on "Print" -- notice yet another delay for a final download to rerender the message for the printer.
Having done all that, close Outlook, disconnect from the network (turn off wireless or disconnect wire), open Outlook and view that same message. The x placeholders are shown instead of the embedded pictures. Although those embedded pictures
were downloaded multiple times already, they were not persisted locally.
Outlook 2003 and 2007 correct ask for confirmation to save the pictures locally then does so. Printing and viewing is then possible without having to redownload those pictures.
Is there going to be a fix for this Outlook 2010 defect? I've been waiting, applying updates, and waiting.....

Please do not close this thread. The issue remains. I apologize for not checking back sooner. I thought I would get pinged by email when this tread was updated; I did not. I'll monitor more closely in the future.
First, please note that I explicitly set Outlook to NOT download pictures automatically. I want to be prompted to download. However, after confirmed that I want the download, I expect pictures related to the message to be downloaded only once,
immediately after I confirm that I want them downloaded.
I have confirmed many times that the behavior in this area is NOT identical between 2003, 2007 and 2010. In particular, 2007 does download once and store locally (if user confirms to save changes when prompted), as expected, and 2010 downloads each
view/preview/print.
This is quite easy to verify -- simply unplug any network cable, disable wireless, etc. In other words completely detach from the networked world. 2007 will correctly view/preview/etc. from local storage whereas 2010 always reverts to showing
placeholders for any embedded images. This is 100% repeatable.
As an additional verification, simply move the .pst file to another system that is not connected to any network. Open the .pst file with 2007 and any embedded images that were already downloaded (and saved) are there, with 2010 they are not.
With 2010, it is bad enough that embedded images are not saved for viewing when disconnected. Worse than that, the repeated downloads can be a significant disruption to performance. Just get on a really slow wireless connection as is typical
in some hotels. Then try to view and print messages with lots of embedded pictures. Slow takes on a whole new, even slower, meaning.
This 2010 defect has been reproduced. Is there a KB article, Windows Update, hotfix,.... anything available to eliminate this problem of repeated downloads of embedded pictures?

[SOLVED] Losing network connection after suspend

Lately I'm having this peculiar problem. When resuming after suspend (specifically, pm-suspend), I have no network connection. I first noticed this on March 31st. The only thing that changed was that I upgraded these packages:
openssl-1.0.1-2-x86_64.pkg.tar.xz
xf86-video-ati-6.14.4-2-x86_64.pkg.tar.xz
lib32-libdrm-2.4.33-1-x86_64.pkg.tar.xz
libnotify-0.7.5-1-x86_64.pkg.tar.xz
xz-5.0.3-2-x86_64.pkg.tar.xz
vim-taglist-45-5-any.pkg.tar.xz
But I'm pretty sure I would have suspended and resumed successfully at least once after that upgrade.
Can anyone suggest what I should look at to try to diagnose this?
Thanks
Last edited by ibrunton (2012-04-06 11:26:03)

Same issue here. Looks like dhcpcd crashes during or after running /usr/lib/dhcpcd/dhcpcd-run-hooks on resume from suspend. I'll try downgrading until this is fixed.
$ uname -s -v -r -m
Linux 3.2.13-1-ARCH #1 SMP PREEMPT Sat Mar 24 09:10:39 CET 2012 x86_64
$ pacman -Qi dhcpcd
Name : dhcpcd
Version : 5.5.5-1
URL : http://roy.marples.name/dhcpcd/
Licenses : BSD
Groups : base
Provides : None
Depends On : glibc sh
Optional Deps : None
Required By : networkmanager
Conflicts With : None
Replaces : None
Installed Size : 256.00 KiB
Packager : Ronald van Haren <[email protected]>
Architecture : x86_64
Build Date : Fri Mar 23 17:25:47 2012
Install Date : Thu Mar 29 23:36:13 2012
Install Reason : Explicitly installed
Install Script : No
Description : RFC2131 compliant DHCP client daemon
# dhcpcd -d -B eth0
dhcpcd[1865]: version 5.5.5 starting
dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
dhcpcd[1865]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[1865]: eth0: rebinding lease of 192.168.1.100
dhcpcd[1865]: eth0: sending REQUEST (xid 0x36169f23), next in 3.93 seconds
dhcpcd[1865]: eth0: acknowledged 192.168.1.100 from 192.168.1.1
dhcpcd[1865]: eth0: checking for 192.168.1.100
dhcpcd[1865]: eth0: sending ARP probe (1 of 3), next in 2.00 seconds
dhcpcd[1865]: eth0: sending ARP probe (2 of 3), next in 1.81 seconds
dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
dhcpcd[1865]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
dhcpcd[1865]: eth0: leased 192.168.1.100 for 3600 seconds
dhcpcd[1865]: eth0: adding IP address 192.168.1.100/24
dhcpcd[1865]: eth0: adding route to 192.168.1.0/24
dhcpcd[1865]: eth0: adding default route via 192.168.1.1
dhcpcd[1865]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
dhcpcd[1865]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
dhcpcd[1865]: eth0: sending ARP announce (2 of 2)
dhcpcd[1865]: eth0: sending IPv6 Router Solicitation
dhcpcd[1865]: eth0: no IPv6 Routers available
dhcpcd[1865]: eth0: carrier lost
dhcpcd[1865]: eth0: deleting default route via 192.168.1.1
dhcpcd[1865]: eth0: deleting route to 192.168.1.0/24
dhcpcd[1865]: eth0: deleting IP address 192.168.1.100/24
dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
dhcpcd[1865]: eth0: carrier acquired
dhcpcd[1865]: eth0: using hwaddr bc:ae:c5:75:36:8e
dhcpcd[1865]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
*** glibc detected *** dhcpcd: double free or corruption (fasttop): 0x0000000000ac2860 ***
======= Backtrace: =========
/lib/libc.so.6(+0x78a56)[0x7f9b6a794a56]
dhcpcd[0x40cdd0]
dhcpcd[0x40e597]
dhcpcd[0x4093f0]
dhcpcd[0x411ba7]
dhcpcd[0x411563]
dhcpcd[0x40768f]
dhcpcd[0x40aa6b]
dhcpcd[0x4028a8]
/lib/libc.so.6(__libc_start_main+0xf5)[0x7f9b6a73d455]
dhcpcd[0x402d1d]
======= Memory map: ========
00400000-00419000 r-xp 00000000 fe:02 4590719 /sbin/dhcpcd
00619000-0061a000 r--p 00019000 fe:02 4590719 /sbin/dhcpcd
0061a000-0061b000 rw-p 0001a000 fe:02 4590719 /sbin/dhcpcd
0061b000-0061c000 rw-p 00000000 00:00 0
00ac1000-00ae3000 rw-p 00000000 00:00 0 [heap]
7f9b6a2eb000-7f9b6a300000 r-xp 00000000 fe:02 1063993 /usr/lib/libgcc_s.so.1
7f9b6a300000-7f9b6a4ff000 ---p 00015000 fe:02 1063993 /usr/lib/libgcc_s.so.1
7f9b6a4ff000-7f9b6a500000 rw-p 00014000 fe:02 1063993 /usr/lib/libgcc_s.so.1
7f9b6a500000-7f9b6a517000 r-xp 00000000 fe:02 3014810 /lib/libpthread-2.15.so
7f9b6a517000-7f9b6a716000 ---p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
7f9b6a716000-7f9b6a717000 r--p 00016000 fe:02 3014810 /lib/libpthread-2.15.so
7f9b6a717000-7f9b6a718000 rw-p 00017000 fe:02 3014810 /lib/libpthread-2.15.so
7f9b6a718000-7f9b6a71c000 rw-p 00000000 00:00 0
7f9b6a71c000-7f9b6a8b3000 r-xp 00000000 fe:02 3018245 /lib/libc-2.15.so
7f9b6a8b3000-7f9b6aab3000 ---p 00197000 fe:02 3018245 /lib/libc-2.15.so
7f9b6aab3000-7f9b6aab7000 r--p 00197000 fe:02 3018245 /lib/libc-2.15.so
7f9b6aab7000-7f9b6aab9000 rw-p 0019b000 fe:02 3018245 /lib/libc-2.15.so
7f9b6aab9000-7f9b6aabd000 rw-p 00000000 00:00 0
7f9b6aabd000-7f9b6aac4000 r-xp 00000000 fe:02 3014856 /lib/librt-2.15.so
7f9b6aac4000-7f9b6acc3000 ---p 00007000 fe:02 3014856 /lib/librt-2.15.so
7f9b6acc3000-7f9b6acc4000 r--p 00006000 fe:02 3014856 /lib/librt-2.15.so
7f9b6acc4000-7f9b6acc5000 rw-p 00007000 fe:02 3014856 /lib/librt-2.15.so
7f9b6acc5000-7f9b6ace6000 r-xp 00000000 fe:02 3018769 /lib/ld-2.15.so
7f9b6aea5000-7f9b6aea9000 rw-p 00000000 00:00 0
7f9b6aee4000-7f9b6aee6000 rw-p 00000000 00:00 0
7f9b6aee6000-7f9b6aee7000 r--p 00021000 fe:02 3018769 /lib/ld-2.15.so
7f9b6aee7000-7f9b6aee8000 rw-p 00022000 fe:02 3018769 /lib/ld-2.15.so
7f9b6aee8000-7f9b6aee9000 rw-p 00000000 00:00 0
7ffff8b93000-7ffff8bb4000 rw-p 00000000 00:00 0 [stack]
7ffff8bc9000-7ffff8bca000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

Network connection after waking from sleep

Hi... More or less any time I allow my MacBook Pro to go to sleep, when I wake it up I am nearly always disconnected from my Airport connection (I connect to a NetGear wireless router via my internal Airport card). I go up to the menu bar and click on the now grey airport icon and I do still see my network in the list of available networks. I click on it, after several seconds a message comes up that says "there was an error joining the Airport network "network name""... But I then simply click on OK (rather than Try Again, I've learned that by trial and error) and the network reconnects just fine... Then when I let the machine sleep again at some later time, I do that all again... Any suggestions of what might be going on??? I do have "Use Interference Robustness" turned on (not that I know why exactly) but I've also had it off before and that seems not to matter... Any suggestions??? thanks... bob..
FW800 G4 dual 1.25 Ghz and 17 inch MacBook Pro Mac OS X (10.4.8)

I have "join preferred networks" selected, and mine os the only one on the list, and it still does not connect after waking from sleep. It is WEP security, not WPA2. I checked out the following article, but it was of no help:
http://docs.info.apple.com/article.html?artnum=304482

Painfully slow network connection

I am trying to evaluate the prospect of installing OS X Server 10.5 on a G5 tower at my workplace, and one of the primary issues is the speed of the office network. Perhaps due to the fact that we are physically located in two different buildings, we not infrequently have problems with some computers connecting to the server (currently running OS X 10.4 [Client]). When connecting via AFP, for example, some computers time out trying to connect or grind to a halt trying to open or save a Word document or something. The server also tries to back up all of our machines using Retrospect, and while some computers transfer files at around 100Kbps, some are around 2K or, again, just time out.
I'm trying to get the network folks to look into these issues, but my basic question is this: if I want to have people able to log in and use their home directory on any computer, can I set things up such that if a given computer has a terribly slow connection to the internet, they can at least login to some local account instead? Ideally, if on their own computer, the fallback would be a cached copy of their own home directory, a la Portable Home Directories. I'd probably be happy with just a vanilla account, though.
In the same vein, if someone logs in using their network home directory, but the network connection goes to ****, will they be unable to do anything? Will they at least be able to log out and switch to a local account? I suppose that this would only work if each computer archived a copy of the user account of any user that logged in using it.
Thanks for any advice you have on implementing this sort of scheme,
Greg

{quote}With the AirPort Extreme, in the AirPort panel, Wireless tab, click on the button for "Wireless Network Options", check the box for "5 GHz Network Name", and enter a different network name. (That can be trivially different, such as the name of the main network suffixed with an underscore and the digit 5.) Once configured that way, connect your "N" gear to each network in turn to see if one is any better than the other. (If you're wondering what effect this would have, it allows segregating your "N" gear from the older gear to prevent the older gear from slowing down your network. However, distance and interference from things like walls may negate any advantage.){quote}
William: I was gone most of yesterday, but had a chance to implement your recommendations today. I added the 5 GHz network as you suggested, but in order to connect to that at all with my 802.n11 MacBokk Pro, I need to be within a few feet of the AE (base station). If I try to access that network even from the next room (well within reach of both the AE and the livingroom AX, I get one bar and "failure to connect" messages just trying to logon to that network.
However, I did some experimenting that (as of right now, anyway) resulted in much faster network access, not only from my MacBook, but also from the older iMac which is the furthest Mac from the AE. According to my wife, that iMac is "loading web pages faster than I've ever seen them!"
Here's what I did:
1. Moved all three units to places where it seemed they would have the least amount of interference with the clearest path from unit to unit, also raising the height of both AXs from about 2-3 feet from the floor to about 5-6 feet from the floor.
2. Changed one setting on the AE (base station): Wireless Tab > Wireless Network Options > Multicast Rate ---> Changed this from Low to High.
I have a feeling the location shifts made the real difference, but I will try changing the multicast rate back to "Low" just to see what happens.
Paul

Slow network connection after uprade to kernel 2.6.19

Similar Messages

Maybe you are looking for