RTL8111/8168B and constant connection hang-ups

Hello everyone,
I've already posted the same topic in the newbie corner and didn't get any responses so I'm trying here. Maybe someone will sympathize with me this time... The problem is that my internet connection just hangs at some random point or another. It sometimes happens when I'm uploading with 10 MBps, it sometimes happens when I'm just playing nethack. In both cases it can be fixed with just running rc.d restart net-profiles, nevertheless I'm pretty annoyed with this whole thing by now.
lspci:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
/etc/rc.conf:
MODULES=(r8168 ipv6 powernow-k8 cpufreq_ondemand k10temp it87)
NETWORKS=eth0
DAEMONS=(syslog-ng acpid sensors net-profiles @alsa @crond ntpd gpm dbus sshd @cpufreq kdm)
/etc/network.d/eth0:
CONNECTION='ethernet'
DESCRIPTION='ipv6+ipv4 eth0'
INTERFACE='eth0'
IP=static
ADDR=172.20.*.*
NETMASK=19
ROUTES=
GATEWAY=172.20.X.X
DNS=("172.20.-.-" "172.20.-.--")
SEARCH="xxxx.xx"
IP6=static
ADDR6=(2001:7c0:409:8001::*:*/64)
POST_UP="sleep 1s && echo -n 1 > /proc/sys/net/ipv6/conf/eth0/accept_ra"
I have also blacklisted r8169 via /etc/modprobe.d/blacklist.conf.
any help would be dearly appreciated.

I'm having the same issues with my ethernet card using r8168 (r8169 is broken in other ways).
dmesg is filled with "stalled" messages and sometimes stack traces that don't really point to the source, it's driving me nuts.
It just hangs for half a minute at a time in a very peculiar way, audio and video keeps playing, but everything else is frozen, the UI, the mouse, no reaction to keyboard.
Update:
dug up a sample out of my logs, I'm not sure how much wpa_supplicant is at fault here.
Feb 14 19:56:32 localhost kernel: [33463.642105] wpa_supplicant D ffff88022a155fd8 0 3661 1 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642111] ffff88022a1558d8 0000000000000086 ffff88022a1558e8 ffffffff814257de
Feb 14 19:56:32 localhost kernel: [33463.642117] ffff88022fe4eae0 ffff88022a155fd8 ffff88022a155fd8 ffff88022a155fd8
Feb 14 19:56:32 localhost kernel: [33463.642122] ffff880229d74020 ffff88022fe4eae0 ffff8801a4cd1c80 ffff88022fe4eae0
Feb 14 19:56:32 localhost kernel: [33463.642128] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642137] [<ffffffff814257de>] ? __schedule+0x33e/0x980
Feb 14 19:56:32 localhost kernel: [33463.642144] [<ffffffff8108c1d9>] ? enqueue_hrtimer+0x39/0xf0
Feb 14 19:56:32 localhost kernel: [33463.642149] [<ffffffff8108ca70>] ? lock_hrtimer_base.isra.23+0x30/0x60
Feb 14 19:56:32 localhost kernel: [33463.642155] [<ffffffff8105c18a>] ? update_curr+0x1ea/0x1f0
Feb 14 19:56:32 localhost kernel: [33463.642159] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642164] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642168] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642182] [<ffffffffa03a4dce>] ieee80211_request_scan+0x2e/0x60 [mac80211]
Feb 14 19:56:32 localhost kernel: [33463.642193] [<ffffffffa03b3dac>] ieee80211_scan+0x6c/0x90 [mac80211]
Feb 14 19:56:32 localhost kernel: [33463.642206] [<ffffffffa02b6f98>] nl80211_trigger_scan+0x368/0x620 [cfg80211]
Feb 14 19:56:32 localhost kernel: [33463.642215] [<ffffffff8138cde5>] genl_rcv_msg+0x1d5/0x250
Feb 14 19:56:32 localhost kernel: [33463.642219] [<ffffffff8138cc10>] ? genl_rcv+0x40/0x40
Feb 14 19:56:32 localhost kernel: [33463.642224] [<ffffffff8138bf99>] netlink_rcv_skb+0xa9/0xd0
Feb 14 19:56:32 localhost kernel: [33463.642230] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642235] [<ffffffff8138cbf5>] genl_rcv+0x25/0x40
Feb 14 19:56:32 localhost kernel: [33463.642239] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642244] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642249] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642255] [<ffffffff81150d1f>] ? kmem_cache_free+0x2f/0x150
Feb 14 19:56:32 localhost kernel: [33463.642262] [<ffffffff8107832d>] ? __sigqueue_free+0x3d/0x50
Feb 14 19:56:32 localhost kernel: [33463.642267] [<ffffffff8134dae1>] ? move_addr_to_kernel+0x51/0x60
Feb 14 19:56:32 localhost kernel: [33463.642271] [<ffffffff813590fa>] ? verify_iovec+0x4a/0xd0
Feb 14 19:56:32 localhost kernel: [33463.642275] [<ffffffff8134c50c>] __sys_sendmsg+0x39c/0x3b0
Feb 14 19:56:32 localhost kernel: [33463.642280] [<ffffffff8107b4f2>] ? set_current_blocked+0x52/0x60
Feb 14 19:56:32 localhost kernel: [33463.642286] [<ffffffff8101532c>] ? do_signal+0x1cc/0x700
Feb 14 19:56:32 localhost kernel: [33463.642291] [<ffffffff8101feb1>] ? fpu_finit+0x21/0x40
Feb 14 19:56:32 localhost kernel: [33463.642295] [<ffffffff81020d56>] ? check_for_xstate+0x26/0xa0
Feb 14 19:56:32 localhost kernel: [33463.642300] [<ffffffff8102113f>] ? restore_i387_xstate+0x15f/0x1f0
Feb 14 19:56:32 localhost kernel: [33463.642305] [<ffffffff8134eac9>] sys_sendmsg+0x49/0x90
Feb 14 19:56:32 localhost kernel: [33463.642312] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642334] /usr/bin/deluge D 0000000100975056 0 5699 1 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642340] ffff8801b19bbaf8 0000000000000086 0000000000000000 ffff8801b19bba74
Feb 14 19:56:32 localhost kernel: [33463.642345] ffff8801b28b4020 ffff8801b19bbfd8 ffff8801b19bbfd8 ffff8801b19bbfd8
Feb 14 19:56:32 localhost kernel: [33463.642350] ffffffff8180d020 ffff8801b28b4020 ffff8801b19bbaa8 ffffffff81359301
Feb 14 19:56:32 localhost kernel: [33463.642355] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642361] [<ffffffff81359301>] ? skb_copy_and_csum_datagram+0x71/0x360
Feb 14 19:56:32 localhost kernel: [33463.642366] [<ffffffff81150f1b>] ? kfree+0x3b/0x170
Feb 14 19:56:32 localhost kernel: [33463.642371] [<ffffffff81150d1f>] ? kmem_cache_free+0x2f/0x150
Feb 14 19:56:32 localhost kernel: [33463.642376] [<ffffffff81356007>] ? __kfree_skb+0x47/0xa0
Feb 14 19:56:32 localhost kernel: [33463.642381] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642385] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642391] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642396] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642402] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642407] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642412] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642417] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642422] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642427] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.642432] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.642437] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642444] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642449] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642454] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.642459] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.642466] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642478] NetworkManager D 0000000100975379 0 18156 1 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642482] ffff88020df59a18 0000000000000082 0000000000000000 ffff880214748380
Feb 14 19:56:32 localhost kernel: [33463.642486] ffff8801a4cd1c80 ffff88020df59fd8 ffff88020df59fd8 ffff88020df59fd8
Feb 14 19:56:32 localhost kernel: [33463.642489] ffff880230cd7200 ffff8801a4cd1c80 ffff88020df59fd8 ffff88020df59fd8
Feb 14 19:56:32 localhost kernel: [33463.642493] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642497] [<ffffffff81053013>] ? select_task_rq_fair+0x593/0xa90
Feb 14 19:56:32 localhost kernel: [33463.642501] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642504] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642508] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642512] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642516] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642520] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642523] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642527] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642530] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642535] [<ffffffff8117a600>] ? __pollwait+0xf0/0xf0
Feb 14 19:56:32 localhost kernel: [33463.642538] [<ffffffff8134c04e>] ? sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642542] [<ffffffff8117a600>] ? __pollwait+0xf0/0xf0
Feb 14 19:56:32 localhost kernel: [33463.642546] [<ffffffff8134dae1>] ? move_addr_to_kernel+0x51/0x60
Feb 14 19:56:32 localhost kernel: [33463.642549] [<ffffffff813590fa>] ? verify_iovec+0x4a/0xd0
Feb 14 19:56:32 localhost kernel: [33463.642552] [<ffffffff8134c50c>] __sys_sendmsg+0x39c/0x3b0
Feb 14 19:56:32 localhost kernel: [33463.642556] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642560] [<ffffffff8134e648>] ? sys_sendto+0x158/0x190
Feb 14 19:56:32 localhost kernel: [33463.642563] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642567] [<ffffffff8134eac9>] sys_sendmsg+0x49/0x90
Feb 14 19:56:32 localhost kernel: [33463.642571] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642580] firefox D 0000000100975055 0 21164 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642585] ffff880037ca9af8 0000000000000082 ffff880200000000 0000000000000001
Feb 14 19:56:32 localhost kernel: [33463.642589] ffff880229c44e60 ffff880037ca9fd8 ffff880037ca9fd8 ffff880037ca9fd8
Feb 14 19:56:32 localhost kernel: [33463.642592] ffffffff8180d020 ffff880229c44e60 ffff880037ca9a28 000000028101db43
Feb 14 19:56:32 localhost kernel: [33463.642596] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642600] [<ffffffff8101dbb9>] ? sched_clock+0x9/0x10
Feb 14 19:56:32 localhost kernel: [33463.642603] [<ffffffff8108f21d>] ? sched_clock_cpu+0xbd/0x110
Feb 14 19:56:32 localhost kernel: [33463.642607] [<ffffffff810540c3>] ? update_rq_clock+0x33/0x60
Feb 14 19:56:32 localhost kernel: [33463.642611] [<ffffffff8101483e>] ? __switch_to+0x20e/0x2f0
Feb 14 19:56:32 localhost kernel: [33463.642614] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642618] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642621] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642625] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642629] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642632] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642635] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642639] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642643] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642647] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.642651] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.642654] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642658] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642662] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642665] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.642668] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.642672] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642678] firefox D 0000000100975055 0 21180 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642682] ffff880090b5faf8 0000000000000082 ffff880200000000 0000000000000001
Feb 14 19:56:32 localhost kernel: [33463.642685] ffff88022f9a7200 ffff880090b5ffd8 ffff880090b5ffd8 ffff880090b5ffd8
Feb 14 19:56:32 localhost kernel: [33463.642689] ffff880230cd4e60 ffff88022f9a7200 ffff880090b5fa28 000000008101db43
Feb 14 19:56:32 localhost kernel: [33463.642693] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642695] [<ffffffff8101dbb9>] ? sched_clock+0x9/0x10
Feb 14 19:56:32 localhost kernel: [33463.642698] [<ffffffff8108f21d>] ? sched_clock_cpu+0xbd/0x110
Feb 14 19:56:32 localhost kernel: [33463.642702] [<ffffffff8101483e>] ? __switch_to+0x20e/0x2f0
Feb 14 19:56:32 localhost kernel: [33463.642706] [<ffffffff812f82c3>] ? mix_pool_bytes_extract+0x163/0x180
Feb 14 19:56:32 localhost kernel: [33463.642709] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642712] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642716] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642720] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642723] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642727] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642730] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642734] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642737] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642740] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642744] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642747] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642751] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.642754] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.642758] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642764] firefox D 0000000100975044 0 21183 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642767] ffff88010099daf8 0000000000000082 ffff880200000000 0000000000000001
Feb 14 19:56:32 localhost kernel: [33463.642771] ffff880230cd3900 ffff88010099dfd8 ffff88010099dfd8 ffff88010099dfd8
Feb 14 19:56:32 localhost kernel: [33463.642775] ffff880230dc1c80 ffff880230cd3900 ffff88010099da28 000000028101db43
Feb 14 19:56:32 localhost kernel: [33463.642779] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642781] [<ffffffff8101dbb9>] ? sched_clock+0x9/0x10
Feb 14 19:56:32 localhost kernel: [33463.642784] [<ffffffff8108f21d>] ? sched_clock_cpu+0xbd/0x110
Feb 14 19:56:32 localhost kernel: [33463.642788] [<ffffffff810540c3>] ? update_rq_clock+0x33/0x60
Feb 14 19:56:32 localhost kernel: [33463.642792] [<ffffffff81014787>] ? __switch_to+0x157/0x2f0
Feb 14 19:56:32 localhost kernel: [33463.642795] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642798] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642801] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642805] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642808] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642812] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642815] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642819] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642822] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642826] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.642829] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.642832] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642836] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642839] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642843] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.642846] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.642850] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642856] firefox D 00000001009750ef 0 21234 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642859] ffff880229f57af8 0000000000000082 0000000000000000 0000000000000000
Feb 14 19:56:32 localhost kernel: [33463.642863] ffff88022fee3900 ffff880229f57fd8 ffff880229f57fd8 ffff880229f57fd8
Feb 14 19:56:32 localhost kernel: [33463.642867] ffff880230cd4e60 ffff88022fee3900 0000000000000000 0000000000000000
Feb 14 19:56:32 localhost kernel: [33463.642870] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642874] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642877] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642881] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642884] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642888] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642891] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642895] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642898] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642901] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642905] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.642908] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.642911] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642915] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642918] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642921] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.642924] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.642928] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.642934] firefox D 00000001009751ab 0 21235 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.642937] ffff8801b0971af8 0000000000000082 0000000000000000 0000000000000000
Feb 14 19:56:32 localhost kernel: [33463.642941] ffff8801e12e0000 ffff8801b0971fd8 ffff8801b0971fd8 ffff8801b0971fd8
Feb 14 19:56:32 localhost kernel: [33463.642945] ffff880230cd4e60 ffff8801e12e0000 0000000000000000 0000000000000000
Feb 14 19:56:32 localhost kernel: [33463.642949] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.642952] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.642955] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.642959] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.642963] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.642966] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.642969] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.642973] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.642976] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.642980] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.642983] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.642986] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.642989] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.642993] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.642996] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.642999] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.643002] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.643007] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.643013] firefox D 00000001009754ed 0 21236 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.643016] ffff88010fa9faf8 0000000000000082 909ebc1d00000000 f51132db428b9987
Feb 14 19:56:32 localhost kernel: [33463.643020] ffff8801e12e0720 ffff88010fa9ffd8 ffff88010fa9ffd8 ffff88010fa9ffd8
Feb 14 19:56:32 localhost kernel: [33463.643023] ffff880230dc1c80 ffff8801e12e0720 d0dd241a332b7c43 f2522d91f47ddf2c
Feb 14 19:56:32 localhost kernel: [33463.643027] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.643032] [<ffffffff81123ab9>] ? zone_statistics+0x99/0xc0
Feb 14 19:56:32 localhost kernel: [33463.643036] [<ffffffff8110cdda>] ? get_page_from_freelist+0x32a/0x800
Feb 14 19:56:32 localhost kernel: [33463.643040] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.643043] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.643046] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.643050] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.643053] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.643056] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.643060] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.643063] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.643067] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.643071] [<ffffffff81112ecd>] ? lru_cache_add_lru+0x2d/0x50
Feb 14 19:56:32 localhost kernel: [33463.643074] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.643078] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.643081] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.643085] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.643088] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.643091] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.643094] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.643098] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Feb 14 19:56:32 localhost kernel: [33463.643104] firefox D 00000001009754f7 0 21237 3760 0x00000000
Feb 14 19:56:32 localhost kernel: [33463.643107] ffff88010fabbaf8 0000000000000082 355aa39e00000000 75f8c900f8fbcbe4
Feb 14 19:56:32 localhost kernel: [33463.643111] ffff88018ca88000 ffff88010fabbfd8 ffff88010fabbfd8 ffff88010fabbfd8
Feb 14 19:56:32 localhost kernel: [33463.643115] ffff880230dc1c80 ffff88018ca88000 43e474d088725910 67c3df0d120cd378
Feb 14 19:56:32 localhost kernel: [33463.643118] Call Trace:
Feb 14 19:56:32 localhost kernel: [33463.643122] [<ffffffff81425f4f>] schedule+0x3f/0x60
Feb 14 19:56:32 localhost kernel: [33463.643125] [<ffffffff81427634>] __mutex_lock_slowpath+0x154/0x370
Feb 14 19:56:32 localhost kernel: [33463.643128] [<ffffffff81427866>] mutex_lock+0x16/0x30
Feb 14 19:56:32 localhost kernel: [33463.643132] [<ffffffff8135566b>] ? __alloc_skb+0x4b/0x240
Feb 14 19:56:32 localhost kernel: [33463.643136] [<ffffffff813723d5>] rtnl_lock+0x15/0x20
Feb 14 19:56:32 localhost kernel: [33463.643139] [<ffffffff813723f6>] rtnetlink_rcv+0x16/0x40
Feb 14 19:56:32 localhost kernel: [33463.643142] [<ffffffff8138b8c9>] netlink_unicast+0x2d9/0x320
Feb 14 19:56:32 localhost kernel: [33463.643146] [<ffffffff8138bc96>] netlink_sendmsg+0x2c6/0x320
Feb 14 19:56:32 localhost kernel: [33463.643149] [<ffffffff8134c04e>] sock_sendmsg+0x10e/0x130
Feb 14 19:56:32 localhost kernel: [33463.643152] [<ffffffff811522eb>] ? __kmalloc+0x15b/0x1a0
Feb 14 19:56:32 localhost kernel: [33463.643156] [<ffffffff81350d0b>] ? sk_prot_alloc+0x13b/0x290
Feb 14 19:56:32 localhost kernel: [33463.643159] [<ffffffff8104f433>] ? __wake_up+0x53/0x70
Feb 14 19:56:32 localhost kernel: [33463.643163] [<ffffffff81168cc2>] ? fget_light+0x92/0x100
Feb 14 19:56:32 localhost kernel: [33463.643166] [<ffffffff8134e62d>] sys_sendto+0x13d/0x190
Feb 14 19:56:32 localhost kernel: [33463.643169] [<ffffffff811659a2>] ? fd_install+0x62/0x80
Feb 14 19:56:32 localhost kernel: [33463.643172] [<ffffffff8134c6da>] ? sock_map_fd+0x2a/0x40
Feb 14 19:56:32 localhost kernel: [33463.643176] [<ffffffff81429742>] system_call_fastpath+0x16/0x1b
Last edited by Hohoho (2012-02-14 18:50:33)

Similar Messages

Anyconnect client and clientless connections hang for two users

ASA 5525, v. 9.1(5)19
Anyconnect client 3.1.02026
I have two users who are unable to connect via the AC client or clientless through the web portal. Using the client, it will get stuck in a loop of "checking for updates". On the portal, the connection will proceed to the point of "Cisco Secure Desktop successfully validated... Success.. Reloading..please wait." Then it hangs there.
The issue occurs for the user regardless of which company laptop she logs onto. A help desk tech can use her laptop and successfully connect, but she cannot connect on her own laptop or on another laptop. (Same for the other user.) So the issue doesn't seem to be related to her laptop or the AC installation. (Help desk did reimage her machine early in the troubleshooting process before they realized that the issue seemed to follow the user.)
I've updated the hostscan file - no change in results. Client and clientless connections seem to be working fine for all other users. We're stumped. Suggestions, anyone? thanks!

The LDAP should be server folks -- Active Directory. Chances are whoever manages the ASA's should have access to at least look in Active Directory to look that up. If they don't they need it.
I obviously don't know a lot about what devices you are using, but if you are using ISE, there should be some type of MNT device (Monitoring and Troubleshooting) -- which is collecting the logs and, hopefully, sending them to some type of syslog aggregate collection tool (splunk?).
Otherwise, there should be a device called a CAM (Clean Access Manager) that is collecting logs -- which may also be propagated to a syslog aggregate tool -- although with CAM's, you can pull the reports right out of them in a comma deliminated file (.csv) and go through them that way.
-- The thing that gets me is that it happens to two users no matter what computer they try to connect from, no matter what network they connect from, and other users can authenticate and gain network access on those same devices.
-- That is why it is rather perplexing. Pretty much saying it has to be something with:
- the IP pool they are getting an IP from
- their AD credentials
- their username
- something along those lines, if the information provided was fully accurate.

Pre-historic speeds and constant connection loss 5...

Hello everyone,
As with a few people on here i have tried to speak to BT about the issues with my broadband but all I get each time I call is turn it of and on and/or try another microfilter, so I am hoping you kind people can help.
First the stats:
BT Wholesale Broadband Performance Test
dowload speed mbps 0.51
upload speed 0.76
ping latency ms 40.88
(have had to type this as i am on my wifes laptop and cannot work out print screen etc)
19:42:25, 01 Oct.
( 350.850000) DSL noise margin: 6.10 dB upstream, 6.10 dB downstream
19:42:24, 01 Oct.
( 349.740000) DSL line rate: 888 Kbps upstream, 595 Kbps downstream
Also if thsi helps:
ADSL Line Status
Connection Information
Line state:
Connected
Connection time:
0 days, 01:14:04
Downstream:
595.5 Kbps
Upstream:
888.9 Kbps
And:
Information for Helpdesk agents
When contacting the BT Broadband helpdesk, the agent might ask you for details about your BT Home Hub. This page contains all of the information they are likely to request.
1. Product name:
BT Home Hub
2. Serial number:
+068340+NQ31823885
3. Firmware version:
Software version 4.7.5.1.83.8.130.1.17 (Type A) Last updated 04/05/14
4. Board version:
BT Hub 4A
5. ADSL uptime:
0 days, 01:15:13
6. Bandwidth:
888 / 595
7. Data sent/received:
10.2 MB / 49.0 MB
8. Broadband username:
[email protected]
9. BT FON:
Yes
10. 2.4 GHz Wireless network/SSID:
BTHub4-JN9Q
11. 2.4 GHz Wireless connections:
Enabled (802.11 b/g/n (Recommended)) 20 MHz, WPS enabled
12. 2.4 GHz Wireless security:
WPA and WPA2
13. 2.4 GHz Wireless channel:
13
14. 5 GHz Wireless network/SSID:
BTHub4-JN9Q
15. 5 GHz Wireless connections:
Enabled (802.11 n 40 MHz (Recommended)) 20/40 MHz, WPS enabled
16. 5 GHz Wireless security:
WPA2
17. 5 GHz Wireless channel:
Automatic / 48
18. Firewall:
Default
19. MAC Address:
cc:33:bb:01:65:f6
20. VPI/VCI:
0 / 38
21. Modulation:
G.992.3 Annex A
22. Latency type:
Interleaved
23. Software variant:
24. Boot loader:
The main problem is not so much the speed but the fact that without fail, after going online via wifi on a laptop, phone tablet etc, around 5 minutes later the light starts to glash orange and connection is lost for about 10-15 minutes. it then seems to sort itself out but the speed is always then really slow.
I have tried one suggestion on here after searching which was to download an app to check the other wifi connections and change manually to a different channel, but have tried loads of different channels and nothing has helped.
I have tried different microfilters
i have tried moving the router nearer to the socket and away from any other electrical devices etc.
I live in flat and there is no master socket as such, there are three sockets in the flat but i have connected the broadband to the one that i can clearly see is fed directly from a cable coming in the wall from telphone pole outside.
I cant do the silent line test at this moment as i do not have a landline to try this but will try and obtain one and try that
I have just purchased a better quality shorte rj11 cable but this has not arrived in the post yet.
Any suggestions?

Thank you for your speedy response:
BT BROADBAND AVAILABILITY CHECKER
Telephone Number on Exchange ASHFORD is served by Cabinet 59
Featured ProductsDownstream Line Rate(Mbps)Upstream Line Rate(Mbps)Downstream Range(Mbps)Availability Date
WBC ADSL 2+
Up to 6.5
5.5 to 7.5
Available
WBC ADSL 2+ Annex M
Up to 6.5
Up to 1
5.5 to 7.5
Available
ADSL Max
Up to 4.5
3 to 7.5
Available
WBC Fixed Rate
2
Available
Fixed Rate
2
Available
Other Offerings
Copper Multicast
Available
I reset the connection i think, as i had the flashing orange light for so long

Safari 5.0 Upgrade Slow and Lot of Hang-ups

I'm new to the Discussion forum. I joined because of issues I'm having with Safari 5.0.
I installed an auto upgrade to Safari 5.0 from ver. 4.0.5 yesterday. Immediately I started having problems with slow loading of web page, incompletely loaded web pages, could not use more than one file tab, and network disconnecting.
I called Apple support under my APP and they had me run v4.0.5 as the User Agent under the current 5.0 version by going to the Develop menu in Safari.
The steps were as follows;
Develop=>User Agent=>SAFARI 4.0.5 - MAC
(You may need to re-boot after this).
This appears to have "fixed" all of my issues!! But the fix was to basically go back to v4.0.5 by the "long way".
I was told Apple was working on a fix for 5.0.
I saw quite a few similar posting having the same problem.
Has anyone else tried this fix using the User Agent as v4.0.5?
Are there any downsides to this?

Safari->Preferences->Advance->on the bottom. To get the Debug menu which includes a listing of Keyboard & Mouse Shortcuts, among other useful things, run this in the Terminal app and quit & relaunch Safari:
*defaults write com.apple.Safari IncludeInternalDebugMenu 1*

What is wrong with FF it keeps closing up and numerous hang ups awful

I have so many problems with this browser - they just keep multiplying. Today, Firefox started closing by itself without my doing anything. This is added to the constant script running errors and other hang ups that constantly slow down my work and are driving me crazy. Maybe I'd just better go back to IE? I've tried your help "fixes" and they don't. Very frustrating.

Did Firefox crash?
See:
*http://kb.mozillazine.org/Mozilla_Crash_Reporter
*https://support.mozilla.org/kb/Mozilla+Crash+Reporter
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer some files from an existing profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem.
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Constant Freeze/Hang associated with UPD connection attempt

As suggested in another post, I have been monitoring the system logs with Console and the freezes/hangs and beach balls perfectly coincide with numerous (>15/per occurrence) of the following message:
9/7/09 6:21:33 PM Firewall54 Stealth Mode connection attempt to UDP 10.0.1.6:59119 from 10.0.1.1:53
Any thoughts?
Previous Background:
I am experiencing nearly constant freezing/beach balls. I can barely type this as it hangs up every 30 seconds or so. It happens in all applications and the finder. The issue started a few months back (with an update I suspect), and I have since installed SL with negative results.
I have repaired permissions and the disk from the SL install disk and checked the hardware with the original system disks: all with no problems reported. Activity Monitor shows 27 GB free space on the HD, more than half the memory available and minimal CPU activity. Also, reset the PRAM again with no improvement.
Not sure where to head from here, aside from installing SL from a clean disk...

A quick update to my issue: after more than 7 phone calls to Apple Tech Support, (who were more than helpful!) it took the macbook into the local repair shop. Turns out while the HDD did not fail any diagnostic test, replacing the HDD cured all issues.
Thanks again to those that offered assistance; and after all that I got an upgraded HDD 120 GB to 320 GB... could have been worse!

Regular hang-ups both online and off

HPE-570f AMD Phenom (tm) II Processor
Windows 7 64-but
Have recently reformatted out of desperation!
This machine continues to regularly hang up despite the best efforts of HP's online help and a complete reformat. Is this processor just a dog? I've had numerous HP computers, but this is the first time I've not purchased an Intel product.

Hi,
Please explain what you mean by "hang-ups"?
What type of application causes the "hang-ups"?
Did you make any hardware changes to your PC?
Did you do a clean Window 7 installation or just used the HP recovery disks?
Did you run diagnostics?
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

HT201415 My wi if connection Hangs at random and the iPad then needs to be restarted for it to reconnect!

My wi if connection Hangs at random and the iPad then needs to be restarted for it to reconnect!
Has anyone had a problem like this or know a solution.?

Look at iOS Troubleshooting Wi-Fi networks and connections http://support.apple.com/kb/TS1398
iPad: Issues connecting to Wi-Fi networks http://support.apple.com/kb/ts3304
iOS: Recommended settings for Wi-Fi routers and access points http://support.apple.com/kb/HT4199
Additional things to try.
Try this first. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
Another thing to try - Go into your router security settings and change from WEP to WPA with AES.
How to Quickly Fix iPad 3 Wi-Fi Reception Problems
http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
If none of the above suggestions work, look at this link.
iPad Wi-Fi Problems: Comprehensive List of Fixes
http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
Fix iPad Wifi Connection and Signal Issues http://www.youtube.com/watch?v=uwWtIG5jUxE
Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
Unable to Connect After iOS Update - saw this solution on another post.
https://discussions.apple.com/thread/4010130
Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
~~~~~~~~~~~~~~~
If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
 Cheers, Tom

SSL and RMI: Client hangs when trying to connect

Hi all,
Sorry for the cross-posting (I first posted to the RMI forum) but I thought someone here might be able to shed some light. The original message follows.
I have a very simple client/server model implemented using RMI. Previously I used the default socket factories for creating sockets/connections and everything worked fine, but now I want to use SSL to encrypt all the traffic and I'm running into some trouble. The client is able to get the correct remote registry on the correct port, but when it tries to do registry.lookup("ServerName") to get a reference to the server object, it hangs indefinitely.
Briefly, here are the changes from default RMI:
As the docs suggested, I created a pair of custom socket factory classes (one for the client and one for the server) that create SSL sockets, and I put the following line in my server's constructor:
super(0, new CustomClientSocketFactory(), new CustomServerSocketFactory());
[my server extends UnicastRemoteObject].
The custom factories are quite simple; the client consists of:
public class CustomClientSocketFactory implements RMIClientSocketFactory, Serializable {
public Socket createSocket(final String iHost, final int iPort) throws IOException {
return SSLSocketFactory.getDefault().createSocket(iHost, iPort);
and the server:
public class CustomServerSocketFactory implements RMIServerSocketFactory {
public ServerSocket createServerSocket(final int iPort) throws IOException {
return SSLServerSocketFactory.getDefault().createServerSocket(iPort);
Everything else is the same as before. I start the server on the remote machine, which starts its own registry on a certain port; then I start the client on the local machine. The client gets the registry and then ... nothing happens.
I know this is somewhat vague, but the changes are small from the working code so I must be doing something wrong in creating SSL sockets. Is there something I can do to trace the process or figure out what's causing the hang? Am I missing some required authentication or other code in the server socket factory (my understanding from the docs is that authentication is optional)? Any other ideas about what's going on?
Thanks,
- Matt

Matt, did you ever determine anything about your Strange Behavior #2. I'm running int the exact same issue. We've been using JSSE without problem for more than 2 years now. I'm currently trying to connect to a new SSL server and the connections setup is taking about 4 minutes (not the SecureRandom seeding) (see my comment in the trace: "this is where it sits for about 3 minutes")
Trace:
init context
trigger seeding of SecureRandom
done seeding SecureRandom
%% No cached client session
*** ClientHello, v3.1
RandomCookie: GMT: 1005755098 bytes = { 7, 203, 184, 206, 249, 120, 35, 155, 160, 131, 72, 68, 12, 35, 64, 75, 63, 202, 161, 95, 42, 130, 74, 248, 145, 108, 49, 189 }
Session ID: {}
Cipher Suites: { 0, 5, 0, 4, 0, 9, 0, 10, 0, 18, 0, 19, 0, 3, 0, 17 }
Compression Methods: { 0 }
[write] MD5 and SHA1 hashes: len = 59
0000: 01 00 00 37 03 01 3C F3 9B DA 07 CB B8 CE F9 78 ...7..<........x
0010: 23 9B A0 83 48 44 0C 23 40 4B 3F CA A1 5F 2A 82 #...HD.#@K?.._*.
0020: 4A F8 91 6C 31 BD 00 00 10 00 05 00 04 00 09 00 J..l1...........
0030: 0A 00 12 00 13 00 03 00 11 01 00 ...........
SbATAOutAdapter, WRITE: SSL v3.1 Handshake, length = 59
[write] MD5 and SHA1 hashes: len = 77
0000: 01 03 01 00 24 00 00 00 20 00 00 05 00 00 04 01 ....$... .......
0010: 00 80 00 00 09 06 00 40 00 00 0A 07 00 C0 00 00 .......@........
0020: 12 00 00 13 00 00 03 02 00 80 00 00 11 3C F3 9B .............<..
0030: DA 07 CB B8 CE F9 78 23 9B A0 83 48 44 0C 23 40 ......x#...HD.#@
0040: 4B 3F CA A1 5F 2A 82 4A F8 91 6C 31 BD K?.._*.J..l1.
SbATAOutAdapter, WRITE: SSL v2, contentType = 22, translated length = 16310
!!! This is where it sits for about 3 minutes !!!!
%% No cached client session
*** ClientHello, v3.1
RandomCookie: GMT: 1005755287 bytes = { 8, 151, 45, 75, 86, 164, 141, 52, 216, 145, 81, 24, 157, 215, 246, 206, 87, 83, 153, 41, 88, 38, 3, 119, 190, 13, 0, 28 }
Session ID: {}
Cipher Suites: { 0, 5, 0, 4, 0, 9, 0, 10, 0, 18, 0, 19, 0, 3, 0, 17 }
Compression Methods: { 0 }
[write] MD5 and SHA1 hashes: len = 59
0000: 01 00 00 37 03 01 3C F3 9C 97 08 97 2D 4B 56 A4 ...7..<.....-KV.
0010: 8D 34 D8 91 51 18 9D D7 F6 CE 57 53 99 29 58 26 .4..Q.....WS.)X&
0020: 03 77 BE 0D 00 1C 00 00 10 00 05 00 04 00 09 00 .w..............
0030: 0A 00 12 00 13 00 03 00 11 01 00 ...........
SbATAOutAdapter, WRITE: SSL v3.1 Handshake, length = 59
[write] MD5 and SHA1 hashes: len = 77
0000: 01 03 01 00 24 00 00 00 20 00 00 05 00 00 04 01 ....$... .......
0010: 00 80 00 00 09 06 00 40 00 00 0A 07 00 C0 00 00 .......@........
0020: 12 00 00 13 00 00 03 02 00 80 00 00 11 3C F3 9C .............<..
0030: 97 08 97 2D 4B 56 A4 8D 34 D8 91 51 18 9D D7 F6 ...-KV..4..Q....
0040: CE 57 53 99 29 58 26 03 77 BE 0D 00 1C .WS.)X&.w....
SbATAOutAdapter, WRITE: SSL v2, contentType = 22, translated length = 16310
SbATAOutAdapter, READ: SSL v3.1 Handshake, length = 74
*** ServerHello, v3.1
RandomCookie: GMT: 1005755466 bytes = { 145, 7, 69, 98, 152, 52, 222, 159, 96, 162, 220, 85, 77, 107, 82, 203, 25, 94, 208, 124, 2, 245, 96, 208, 224, 254, 139, 206 }
Session ID: {68, 7, 167, 168, 236, 202, 48, 147, 191, 204, 208, 122, 24, 43, 132, 50, 65, 220, 172, 189, 17, 18, 197, 11, 150, 59, 201, 103, 86, 176, 115, 68}
Cipher Suite: { 0, 5 }
Compression Method: 0
%% Created: [Session-1, SSL_RSA_WITH_RC4_128_SHA]
** SSL_RSA_WITH_RC4_128_SHA
Anybody have any ideas?
Thanks,
Marcel

Constant Connection Between Mail Server and RIM Server

Hi,
I'm a newbie in need for some advise about Blackberry Email Account
I am currently having a problem at the office. Since January 2012, our outgoing bandwidth is increasing in constant rate and it is steadily high at current time. Here are some of my findings:
there is a constant connection to port 993 (IMAPS that's being used by blackberry email account)
the constant connection is leading to RIM IP and XO Communication
the bandwidth outgoing usage is constant (at about 2.5Mbps approximately)
Our user has started setting up their office email on their personal Blackberry devices
This is causing some concern regarding our company email, does some of the email accounts got infected by virus? Please help me out with this, it might not be a normal case, but any advice to solve this problem will be highly appreciated.
Thank you,
Sandy

IMAP will be connected all the time and there has never been a BlackBerry virus.
Mail Clients will connect at all times if left on.
Do you want to block this access?
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

BB Torch- Email server connection lost since unlocking phone and constant buffering

Since unlocking my BB 9800 I can not received emails (cannot connect to the server). I have WiFi and can connect to the internet but not the server for emails. Prior to unlocking I had no issues. Also, is there a cure for the constant buffering? This is the second handset with the same issue. My provider is Vodafone and I am in medium term based in the US so having emails on my mobile (via Wifi) as my roaming is off is essential. Please help as Vodafone could not.

Vodafone have said it was a firmware or hardware issue... so Im i the piggy in the middle without emails as my roaming is switched off. Again, the only change was entering the code given to me from Vodafone and no more server connection. can you get a second opinion please!

E4200 - Multiple issues and constant lock ups.

So I just bought this router today. Initial setup was easy.
Then I tried to add a wireless printer. The router froze up. Had to reboot to get it to work at all. I couldn't even access the default setup pages and Cisco connect couldn't connect either.
After reboot, forgot about the printer and tried to add an external hard drive that works fine on my PC. The router couldn't detect it. Then the router froze again and had to reboot to get anything to work.
The firmware says 1.0.03 build 14 Sep. 20, 2011
I downloaded the latest from the website and tried a firmware update. That failed too and the message was to try again later.
This thing freezes up any time I try to modify anything. Is it a dud? Because so far I am not impressed at all. I had a little more confidence with Cisco up until tonight....

Cancruiser wrote:
So I just bought this router today. Initial setup was easy.
Then I tried to add a wireless printer. The router froze up. Had to reboot to get it to work at all. I couldn't even access the default setup pages and Cisco connect couldn't connect either.
After reboot, forgot about the printer and tried to add an external hard drive that works fine on my PC. The router couldn't detect it. Then the router froze again and had to reboot to get anything to work.
The firmware says 1.0.03 build 14 Sep. 20, 2011
I downloaded the latest from the website and tried a firmware update. That failed too and the message was to try again later.
This thing freezes up any time I try to modify anything. Is it a dud? Because so far I am not impressed at all. I had a little more confidence with Cisco up until tonight....
what type of drive? Format is your external hard drive?
Yesterday is history. Tomorrow is mystery. Today is a gift.

App store hang-ups

I've only had my iPad for a week but have already had a couple of problems with the app store. This morning, when I tried to download a couple of apps, the waiting box would just show up on the home screen with a blank loading bar. The same was true for an update I tried to install. Similarly, last week at the app store, anytime I tried to navigate somewhere I would just get a white screen with "Loading" and the spinning rays with no progress. In both cases, things seemed back to normal 15 minutes later or so. Also, in both cases, there were no problems with my wifi - I checked that. Are these kinds of hang ups and freezes normal for the store, or could there be some sort of problem with my iPad causing this?

I did a reset, which didn't immediately solve anything. The problem just disappeared about 15 minutes after it started. I wouldn't think it's a hardware problem since other apps and Internet connectivity all seemed to be working at top speed while the app store problem was happening. I guess I was curious if other people had experienced app problems in their time with their ipads.

New FIOS customer with dropped VOIP calls and Internet connection

I am a new FIOS customer. Got my 50/25 connection a week ago, switching from a TWC 6/1 connection. Ever since the new connection, I've had numerous issues.
My VOIP (Ooma) connection constantly drops and re-connects during conversations
I've had random Internet connection losses, which picks up again after a few minutes
My home alarm starts chirping every once in a while
I've contacted Verizon several times due to these problems and have received varying answers with no resolution of the problem.
The first time I spoke with support, the tech logged into my router and changed the WiFi channel saying that would fix the problem. It didn’t.
The second time I contacted them, the tech ran a bunch of diagnostics and said everything looked fine so it must be an IP address conflict with my devices, because I had a couple devices using static IP addresses. He said everythinf should be DHCP and the last two digits could not be higher than 99 (192.168.1.99). He said FIOS does not support 3-digit numbers at the end.
So I changed all my devices to DHCP and ran some online VOIP tests. It showed a packet loss of 2-5% and MOS score of 1 (which is bad). I was still getting dropped connections, so I disconnected all devices and connected just one computer to the router and tested again. I was still getting packet loss.
Then I called support a third time, this time the tech said there were no 2-digit IP restrictions and that he was detecting there was no UPS baterry backup for the ONT which was probably causing the problem, so he dispatched a field tech to my house.
Today the field tech came (same guy as before), he took one look at the box and said it was too close to my Electric meter and the RF from the meter was causing interference to the FIOS connection and resulting in dropped connection.
He moved the ONT to another location and said that should fix it.
Well, I'm still seeing packet loss and low MOS score when I run the VOIP test.
I don't know how much of what the techs are saying is true and how much is made up stuff.
Has anyone had similar issues and have thoughts on solutions or likely causes for dropped VOIP calls and connections? Could RF be causing this?
I thought going from a 6/1 Cable connection to a 50/25 FIOS connection would be awesome, but this has turned out to be a nightmare, and I may have to switch back to cable if the problem is not resolved.
I would appreciate any help.
Thanks!

Don't know where the packet loss is happening. I ran the VOIP test on myspeed.visualware.com and it shows a packet loss of 2-5% at different times and a MOS score of 1.
The report says MOS should be around 4 for good VOIP calls.
The Verizon tech who came to the house just blamed the electric meter box for RF interference and move the ONT farther away.
My concern is that I'm getting different answers from different techs at Verizon.
Regarding IP addresses. The Router shows a DHCP range from 192.162.1.2 to 192.168.1.254 as available for devices on the network. So, if I need to assign a static IP to a device should I use a number below 99 or above 151?
Thanks!

How to set up 6th Generation AirPort Extreme to cable modem as a wireless router and then connect my 3rd Generation Time Capsule to AirPort Extreme as a wireless extender?

What is the best way to set up my 6th Generation AirPort Extreme (A1521) to my cable modem as a wireless router and then connect my 3rd Generation Time Capsule (A1355) to my AirPort Extreme as a wireless extender? I live in a small 1 story house and I currently have the Airport Extreme connected to my cable modem in the living room and the Time Capsule plugged into the wall in my bedroom. I am able to wirelessly connect to the internet using the AirPort Extreme as my router and I can also do wireless back ups to my Time Capsule. My problem is that my connection seems to be really slow! My 1TB Time Capsule back up is only half way complete and it has been 3 days! My computer has been backing up all day and night for almost 72 hours and its still not even 75% complete. I have backed up to this Time Capsule in the past and it never took this long. I am thinking that when I set up my AirPort Extreme and Time Capsule using AirPort Utility I must have set it up incorrectly or something.
How do I set up my Airport Extreme and Time Capsule for the fastest possible internet speed and back up speed?
Thank you,

AirPort Utility 5.6 works with AirPort Extreme 802.11g base stations.
It works with N version airports.
It will also show details of the AC model but cannot be used for the setup.. mostly.
I purposely got the new 6th Gen Airport Extreme so my internet connection would be a lot faster!
Your network will be much faster when you have AC client directly connected to the AE. Older client will go no faster.. but what is worse.. extend wireless is mixing new and old wireless standards.. guess what one wins.. OLD.. So when you extend wireless.. you have no improvement whatsoever. This whole post is about extending wireless.. so you cannot extend to older equipment and do any better.. maybe slightly better signal although from your comments that isn't happening either.
I would rather not have to use an ethernet at all with the TC and I don't know EOP adapters are!
If you do not use ethernet then you are going to be forced to accept slow speed.
EOP (ethernet over power). Also called homeplug in the US.
http://en.wikipedia.org/wiki/HomePlug
Provides a method of networking over power cabling that already exists in your house.
So what your saying is for the fastest internet speed and back up speed possible I should keep my Airport Extreme plugged into my Modem and keep my TC set up as a wireless extender? Then when I want to do back ups I should plug an ethernet cable from my TC to my MacBook Pro?
To spell this out.
A wireless link to an extended device will go very slowly.. if it is not direct.
So lets say you have a laptop sitting in the lounge.. Your connection goes.. Laptop- - - - - AE- - - - -TC.
That means two wireless links.. wireless has this nasty half duplex and single channel nature.. it can send or receive (Tx or Rx) but not at the same time.
Ethernet by contrast does both at once. It is full duplex.
Wireless can talk to one client at a time.. so if there are multiple items using wireless lets say 4 devices.. then your computer gets a 25% time slice. Since wireless cannot handle multiple simultaneous connections.
Ethernet by contrast can connect multiple computers to multiple destinations at the same time.. all transmitting and receiving at full speed.
When you put all this together.. there are a couple of rules for fast connection.
1. Use ethernet at all times. Where you cannot use ethernet use anything but wireless.. eg EOP (homeplug) at least to try and get rid of wireless.
2. Where you must use wireless use it sparingly and make sure it is never more than one hop.. ie never have an extend wireless (repeater is more usual term). Repeater will cause instant slowdown of 50% and maybe up to 75% just because it is so inefficient.
3. Fastest wireless is 5ghz but it has very short range.. you need to be up close and personal to get it working.
Apple routers however unless you do manual setup I suggest are set to connect to best signal strength not best speed. It will therefore use 2.4ghz at 25% less speed than 5ghz because it is 1db better signal.. this madness means you need to setup manually for the best setup.

RTL8111/8168B and constant connection hang-ups

Similar Messages

Maybe you are looking for