IPv6 problem
I`ve got one eth card in my server with interfaces configured as below:
eth0 static IPv4 and IPv6 address
vlan1 static IPv4 address
vlan2 static IPv4 address
The problem is that I`m receiving from my network Router Advertisement and SLES receives and accepts IPv6 addresses and gateways to all of interfaces.
I have to disable it so I configured sysctl.conf as listed below:
Code:
net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.eth0.autoconf = 0
net.ipv6.conf.vlan1.autoconf = 0
net.ipv6.conf.vlan2.autoconf = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.all.router_solicitations = 0
net.ipv6.conf.default.router_solicitations = 0
net.ipv6.conf.eth0.router_solicitations = 0
net.ipv6.conf.vlan1.router_solicitations = 0
net.ipv6.conf.vlan2.router_solicitations = 0
net.ipv6.conf.all.accept_ra = 0
net.ipv6.conf.default.accept_ra = 0
net.ipv6.conf.eth0.accept_ra = 0
net.ipv6.conf.vlan1.accept_ra = 0
net.ipv6.conf.vlan2.accept_ra = 0
When I`m running sysctl -p everything seems to work fine, when I`m checking:
Code:
sysctl -a | grep .autoconf
net.ipv6.conf.vlan1.autoconf = 0
net.ipv6.conf.vlan2.autoconf = 0
net.ipv6.conf.eth0.autoconf = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.lo.autoconf = 1
sysctl -a | grep router_solicitations
net.ipv6.conf.vlan1.router_solicitations = 0
net.ipv6.conf.vlan2.router_solicitations = 0
net.ipv6.conf.eth0.router_solicitations = 0
net.ipv6.conf.default.router_solicitations = 0
net.ipv6.conf.all.router_solicitations = 0
net.ipv6.conf.lo.router_solicitations = 3
sysctl -a | grep accept_ra
net.ipv6.conf.vlan1.accept_ra = 0
net.ipv6.conf.vlan2.accept_ra = 0
net.ipv6.conf.eth0.accept_ra = 0
net.ipv6.conf.default.accept_ra = 0
net.ipv6.conf.all.accept_ra = 0
net.ipv6.conf.lo.accept_ra = 1
But when I`m running rcnetwork restart and then ifconfig I can see that system still has IPv6 configutation captured from router :/
Another thing is that sysctl seems not working after reboot, I`ve got this in /var/log/boot.msg:
Code:
Activating remaining swap-devices in /etc/fstab...
doneSetting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
/proc/sys/net/ipv6/conf/all/autoconf: No such file or directory
/proc/sys/net/ipv6/conf/eth0/autoconf: No such file or directory
/proc/sys/net/ipv6/conf/vlan1/autoconf: No such file or directory
/proc/sys/net/ipv6/conf/vlan2/autoconf: No such file or directory
/proc/sys/net/ipv6/conf/default/autoconf: No such file or directory
/proc/sys/net/ipv6/conf/all/router_solicitations: No such file or directory
/proc/sys/net/ipv6/conf/default/router_solicitations: No such file or directory
/proc/sys/net/ipv6/conf/eth0/router_solicitations: No such file or directory
/proc/sys/net/ipv6/conf/vlan1/router_solicitations: No such file or directory
/proc/sys/net/ipv6/conf/vlan2/router_solicitations: No such file or directory
/proc/sys/net/ipv6/conf/all/accept_ra: No such file or directory
/proc/sys/net/ipv6/conf/default/accept_ra: No such file or directory
/proc/sys/net/ipv6/conf/eth0/accept_ra: No such file or directory
/proc/sys/net/ipv6/conf/vlan1/accept_ra: No such file or directory
/proc/sys/net/ipv6/conf/vlan2/accept_ra: No such file or directory
How to fix this problems?
scarab,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/
Similar Messages
-
Hello,
i have a issue with IP Version 6 and Zone-Based-Policy-Firewall.
this is the setup:
Router1 (Cisco 1802, IOS 15.1(3)T1, i also tried older IOS):
Dialer 0 to IPV4 Internet
Dialer 6 to IPV6 Internet
Tunnel 0 configured as DMVPN to Router 2
VLAN 1 as internal Interface with IP 192.168.0.0/24 and 2001:xxxx:xxxx:2::/64
Router2 (Cisco 1802, IOS 15.1(3)T1, i also tried older IOS):
Dialer 0 to IPV4 Internet
Tunnel 0 configured as DMVPN to Router 1
VLAN 1 as internal Interface with IP 10.0.0.0/24 and 2001:xxxx:xxxx:1::/64
Router1 connects to IPV6 Internet via Dialer 6
Router2 connects to IPV6 Internet via Tunnel0 (Dynamic-Multipoint-VPN)
Router1 and Router2 are configured with Zone-Based-Policy-Firewall.
When i remove the ZBPF Config from Router1 everything works!
When i configure ZBPF on Router1 the IPV6 Connection between two Routers works in both directions,
the Internet Connection IPV6 from Router1 also works great
but the Internet Connection IPV6 from Router2 doesn't work anymore in the outgoing direction.
(Tunnel0 and VLAN1 are in the ZONE_BUERO_VLAN1, Dialer0 and Dialer6 are in ZONE_INTERNET)
zone security ZONE_INTERNET
zone security ZONE_BUERO_VLAN1
zone-pair security ZP_BUERO_VLAN1__INTERNET source ZONE_BUERO_VLAN1 destination ZONE_INTERNET
service-policy type inspect FW_TO_INTERNET
zone-pair security ZP_INTERNET__BUERO_VLAN1 source ZONE_INTERNET destination ZONE_BUERO_VLAN1
service-policy type inspect FW_INTERNET__BUERO_VLAN1
policy-map type inspect FW_TO_INTERNET
class type inspect FW_GRE
pass
class type inspect FW_ESP
pass
class type inspect FW_ALLES_ERLAUBT_INSPECT2
inspect
class class-default
drop log
policy-map type inspect FW_INTERNET__BUERO_VLAN1
class type inspect FW_GRE
pass
class type inspect FW_ESP
pass
class type inspect FW_IPV6_ALLES
drop log
class class-default
drop log
class-map type inspect match-any FW_GRE
match access-group name FW_GRE
class-map type inspect match-any FW_ESP
match access-group name FW_ESP
class-map type inspect match-any FW_ALLES_ERLAUBT_INSPECT2
match protocol http
match protocol https
match protocol ntp
match protocol dns
ip access-list extended FW_GRE
permit gre any any
ip access-list extended FW_ESP
permit esp any any
ipv6 access-list FW_IPV6_ALLES
permit ipv6 any any
permit icmp any any
permit tcp any any
permit udp any any
Debug Messages: (Seen on Router1)
Client in VLAN1 Router1 is browsing: (2001:xxxx:xxxx:2:C8FD:5EFE:523E:FB55)
- no debug - works -
Client in VLAN1 Router2 is browsing: (2001:xxxx:xxxx:1:C8FD:5EFE:5111:FB55)
*May 24 18:38:18.016: %FW-6-DROP_PKT: Dropping tcp session [2001:xxxx:xxxx:1:C8FD:5EFE:5111:FB55]:56687 [2A02:2E0:3FE:100::7]:80 on zone-pair ZP_BUERO_VLAN1__INTERNET class class-default due to DROP action found in policy-map with ip ident 0
Router1#
*May 24 18:38:48.465: %FW-6-DROP_PKT: Dropping tcp session [2001:xxxx:xxxx:1:C8FD:5EFE:5111:FB55]:56696 [2A02:2E0:3FE:100::7]:80 on zone-pair ZP_BUERO_VLAN1__INTERNET class class-default due to DROP action found in policy-map with ip ident 0
Router1#
*May 24 18:39:21.705: %FW-6-DROP_PKT: Dropping tcp session [2001:xxxx:xxxx:1:C8FD:5EFE:5111:FB55]:56747 [2A02:2E0:3FE:100::7]:80 on zone-pair ZP_BUERO_VLAN1__INTERNET class class-default due to DROP action found in policy-map with ip ident 0
so can you tell me how this it possible, even if i have the same zone membership of two interfaces it works for traffic from vlan 1 but it is blocked for traffic from tunnel 0???Hello,
@Phillip: Thank you, you're right, that solved my "loosing connection" problems while debugging
so here are the debugs: (i made only a few of them, because if i enable to much of them i don't get the dropped packets in the debugs)
Router1#debug policy-firewall events
Policy-Firewall events debugging is on
Router1#debug policy-firewall detail
Policy-Firewall detailed debugging is on
*Jun 7 22:39:50.481: FIREWALL: FW CCE got packet 0x865A3430 in process path
*Jun 7 22:39:50.481: FIREWALL: NEW PAK 865A3430 [2001:xxxx:xxxx:1:8076:7A29:ABFB:708E]:52385 [2A02:2E0:3FE:100::7]:80 tcp
*Jun 7 22:39:50.481: FIREWALL: DROP feature object 0xAAAA000F found
*Jun 7 22:39:50.481: FIREWALL: FW CCE dropping pak 0x865A3430 in process path
Router1#debug policy-firewall packet-path
Policy-Firewall PAK_PATH debugging is on
packet from tunnel 0:
*Jun 7 22:43:45.781: CCE-FW :classify no match (srcaddr:port)-([2001:xxxx:xxxx:1:8076:7A29:ABFB:708E]:0) (dstaddr:port)-([2A02:2E0:3FE:100::7]:0)
*Jun 7 22:43:45.781: CCE-FW :ACCESS_GROUP_NAMED:CCE_DP_NAMED_DB_NOT_MATCHED: type_1_filter = 8764B300, acl = FW_ESP vers = 1
*Jun 7 22:43:45.781: CCE-FW :classify no match (srcaddr:port)-([2001:xxxx:xxxx:1:8076:7A29:ABFB:708E]:0) (dstaddr:port)-([2A02:2E0:3FE:100::7]:0)
*Jun 7 22:43:45.781: CCE-FW :L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:43:45.781: CCE-FW :L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:43:45.781: CCE-FW :L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:43:45.781: CCE-FW :L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:43:45.781: CCE-FW :classify no match (srcaddr:port)-([2001:xxxx:xxxx:1:8076:7A29:ABFB:708E]:0) (dstaddr:port)-([2A02:2E0:3FE:100::7]:0)
Router1#
*Jun 7 22:43:45.781: %FW-6-DROP_PKT: Dropping tcp session [2001:xxxx:xxxx:1:8076:7A29:ABFB:708E]:52403 [2A02:2E0:3FE:100::7]:80 on zone-pair ZP_BUERO_VLAN1__INTERNET class class-default due to DROP action found in policy-map with ip ident 0
*Jun 7 22:43:46.221: CCE-FW*:cce_dp_named_db_inspect_port_to_l7_protocol:L7 protocol is 0 L4 protocol is 0 address is [FE80::215:FAFF:FE0C:A70C] port is 0
*Jun 7 22:43:46.221: CCE-FW*:Packet L7 is 9 L4 prot is 0 granular is 0 (srcaddr:port)-([2001:xxxx:xxxx:2:80B6:E54A:A19:6435]:50900) (dstaddr:port)-([FE80::215:FAFF:FE0C:A70C]:22)
*Jun 7 22:43:46.221: CCE-FW*:L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:43:46.221: CCE-FW*:classify no match (srcaddr:port)-([2001:xxxx:xxxx:2:80B6:E54A:A19:6435]:50900) (dstaddr:port)-([FE80::215:FAFF:FE0C:A70C]:22)
*Jun 7 22:43:46.221: CCE-FW*:cce_dp_named_db_inspect_classify:packet 85977DC4 is not matched
packet from vlan1 (works)
*Jun 7 22:52:16.735: CCE-FW*:Packet L7 is 9 L4 prot is 0 granular is 0 (srcaddr:port)-([2A02:2E0:3FE:100::7]:50929) (dstaddr:port)-([2001:xxxx:xxxx:2:5800:62D5:A2AE:282C]:80)
*Jun 7 22:52:16.735: CCE-FW*:L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:52:16.735: CCE-FW*:classify no match (srcaddr:port)-([2A02:2E0:3FE:100::7]:50929) (dstaddr:port)-([2001:xxxx:xxxx:2:5800:62D5:A2AE:282C]:80)
*Jun 7 22:52:16.735: CCE-FW*:cce_dp_named_db_inspect_classify:packet 856B3D60 is not matched
*Jun 7 22:52:16.735: CCE-FW*:cce_dp_named_db_inspect_port_to_l7_protocol:L7 protocol is 0 L4 protocol is 0 address is [FE80::8C8F:658:1A14:661D] port is 0
*Jun 7 22:52:16.735: CCE-FW*:Packet L7 is 9 L4 prot is 0 granular is 0 (srcaddr:port)-([FE80::215:FAFF:FE0C:A70C]:50929) (dstaddr:port)-([FE80::8C8F:658:1A14:661D]:80)
*Jun 7 22:52:16.735: CCE-FW*:L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:52:16.735: CCE-FW*:classify no match (srcaddr:port)-([FE80::215:FAFF:FE0C:A70C]:50929) (dstaddr:port)-([FE80::8C8F:658:1A14:661D]:80)
*Jun 7 22:52:16.735: CCE-FW*:cce_dp_named_db_inspect_classify:packet 856B420C is not matched
*Jun 7 22:52:16.739: CCE-FW*:cce_dp_named_db_inspect_port_to_l7_protocol:L7 protocol is 0 L4 protocol is 0 address is [FE80::215:FAFF:FE0C:A70C] port is 0
*Jun 7 22:52:16.739: CCE-FW*:Packet L7 is 9 L4 prot is 0 granular is 0 (srcaddr:port)-([FE80::5800:62D5:A2AE:282C]:50929) (dstaddr:port)-([FE80::215:FAFF:FE0C:A70C]:80)
*Jun 7 22:52:16.739: CCE-FW*:L7 protocol match CCE_DP_NAMED_DB_NOT_MATCHED
*Jun 7 22:52:16.739: CCE-FW*:classify no match (srcaddr:port)-([FE80::5800:62D5:A2AE:282C]:50929) (dstaddr:port)-([FE80::215:FAFF:FE0C:A70C]:80)
*Jun 7 22:52:16.739: CCE-FW*:cce_dp_named_db_inspect_classify:packet 85929DEC is not matched
*Jun 7 22:52:16.739: CCE-FW*:cce_dp_named_db_inspect_port_to_l7_protocol:L7 protocol is 0 L4 protocol is 0 address is [FE80::8C8F:658:1A14:661D] port is 0
Router1#
*Jun 7 22:52:17.303: CCE-FW*:ACCESS_GROUP_NAMED:CCE_DP_NAMED_DB_MATCHED: type_1_filter = 8764B300, acl = FW_ESP vers = 0
*Jun 7 22:52:17.303: CCE-FW*:Matched acl, user group or insp protocols
*Jun 7 22:52:17.303: CCE-FW*:L7 is 9 l7 token prot is 0
*Jun 7 22:52:17.331: CCE-FW*:cce_dp_named_db_inspect_port_to_l7_protocol:L7 protocol is 0 L4 protocol is 0 address is 217.92.41.131 port is 0
debug policy-firewall function-trace
- no debug output -
my results are that with "debug policy-firewall packet-path" i can't really see where it matches, but i can see that if the packet comes from tunnel 0 the debug can't see the destination port and therefor cant't match the packet.
i also tried to implement a rule that allows all traffic, not only http: then it is not dropped any more, but the reverse packet is dropped because the stateful inspection doesn't work for that packet.
for me it seems to be a bug.....what do you think? -
Any solutions to the DNS not resolving IPv6 problem?
Hello,
Does anyone know how to fix the broken DNS behaviour that was introduced into OS X sometime since 10.4? I'd like to have my systems be able to resolve AAAA addresses, but Apple seems to have broken DNS resolution (probably in response to people complaining about problems which are a result of other IPv6 equipment which are broken!)
Note that this has nothing to do with whether IPv6 works. It does. It's just that OS X's DNS resolver does not return AAAA records at all. Take a look:
[lain:~] john% ping6 andromeda.ziaspace.com
ping6: No address associated with nodename
[lain:~] john% host -t aaaa andromeda.ziaspace.com
andromeda.ziaspace.com has AAAA address 2001:4830:1200:17::2
[lain:~] john% ping6 2001:4830:1200:17::2
PING6(56=4088 bytes) 2001:4830:1700:18::2 --> 2001:4830:1200:17::2
It'd be nice if Apple had a technote or a preference somewhere...
Mac mini Mac OS X (10.4.6)
Mac mini Mac OS X (10.4.6)If i recall the message is about DirectPlay?
When i installed and ran pse 12 on windows 8.1, windows offered to turn that on.
You might have to go to the Control Panel>Programs>Programs and Features>Turn Windows Features on or off>Legacy Componets>DirectPlay -
IPv6 problem when STAMINA is on
Hello there, sorry for my improving English.
I own an Xperia Z3 Compact (D5833 23.0.1.A.1.49 Customized HK).
I have IPv6 internet connection when connected to WiFi. But if STAMINA mode and Extended standby is on, IPv6 connection drops after screen off for about 30min more or less. IPv4 still works. IPv6 always works when STAMINA mode is off.
I search on the net and find out a post here:
https://talk.sonymobile.com/t5/Xperia-SP/Activating-STAMINA-mode-causes-constant-reboots/td-p/680659
Don't know we have a same problem or not.
Thanks.When you turn on the display, is the connection re-established again?
What apps do you have in your whitelist that's using the connection?
- Official Sony Xperia Support Staff
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page. -
I cannot reach ipv6 site now and I don't know if I could reach them before.
Here's some code:
[root@wangchong-work wangchong]# insmod ipv6
insmod: ERROR: could not load module ipv6: No such file or directory
[root@wangchong-work wangchong]# find / -name ipv6.ko[root@wangchong-work wangchong]# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:50:8d:b5:bd:b9 brd ff:ff:ff:ff:ff:ff
3: enp0s26f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:07:0f:14:02 brd ff:ff:ff:ff:ff:ff
inet 166.111.26.84/23 brd 166.111.27.255 scope global enp0s26f0u1
valid_lft forever preferred_lft forever
inet6 fe80::20c:7ff:fe0f:1402/64 scope link
valid_lft forever preferred_lft forever
[root@wangchong-work wangchong]# ip -6 r s
fe80::/64 dev enp0s26f0u1 proto kernel metric 256
[root@wangchong-work wangchong]# cat /etc/resolv.conf
# Generated by resolvconf
domain tsinghua.edu.cn
nameserver 166.111.8.28
nameserver 166.111.8.29
Please help!
Last edited by wangchong (2014-03-08 12:29:33)WonderWoofy wrote:Well... to reach an ipv6 site, you kinda need an ipv6 address. Your machine has a multicast address, but nothing else. Read up on ipv6, as a properly set up ipv6 stack doesn't provide just one address like the old NAT ipv4 setup.
Well, I am new to linux so please be more specific. thx -
I have N85 RM-333, firmware 31.002. After I have set up dual IPv4/v6 stack, I started receiving "488 Not acceptable here" from the asterisk server. The problem turns to be in this SDP line sent by the handset:
c=IN IP6 2001:5c0:1507:c500:222:fcff:fed5:5497
While admittedly it's asterisk's "shortcoming" to not recognize IPv6 notation, I question the decision to use IPv6 addresses in SIP and SDP messages while the communication is actually done over IPv4 (as seen in the attached log). I would presume that IPv6 addresses should be used inside the messages only if these messages are going to be sent over IPv6.
Opinions? Anyone from Nokia to comment on this?
Thanks,
Eugene
Attachments:
asterisk-ipv6-problem.txt 3 KBGo to contacts and see if you see 3 tabs. If there is a 3rd tab, see if it says activate or something like that (sorry can not remember now). From here you can choose to deactivate the connection and it will stop trying to connect.
Show the KUDOS button some love.... Hit that bad boy.... It don't hurt....
Apple iPhone 5,
Retina MacBook Pro, iPad Mini, Nikon D4 -
Change to a static IPv4 address and lost IPv6 - SMC D3G and Airport Extreme
I hope someone can help sort out my IPv6 problem. We have a business Internet account with the SMC D3G-CCR gateway and Apple Airport Extreme (the new tall model). While using dynamic addresses and letting the SMC gateway handle DHCP (Airport Extreme in bridge mode) my IPv6 tests all worked (outbound requests worked - I never tried any incoming access to servers). The test site at http://test-ipv6.com said all was good and I could ping6 ipv6.google.com from any inside computer. Due to a new client project requirements, I got a static IP address today. Comcast reconfigured the SMC gateway and I set up the Airport Extreme to handle internal routing and DHCP and port forwarding for a camera and SSH services. All of that IPv4 stuff seems to be working properly. Unfortunately, I can't find a combination of settings that will give me access to outside IPv6 servers anymore. I was hoping to start testing a small Raspberry Pi server using inbound IPv6, but now I can't seem to get anything going with IPv6. The SMC box does have a setting that appears to block incoming IPv6 requests. But I assumed that would be disabled with the static IP configuration. Either way, it shouldn't block my outbound requests so something else must be wrong. Am I missing a setting somewhere? Do I need Comcast to change something else? Do I need a different gateway device?
First, I am assuming that you are trying to administer your AirPort base station for a static IP address using the iOS version of the AirPort Utility ... correct?
If so, then to do so:
Start the AirPort Utility app on the iPad
Select your base station.
Select Edit
Select Internet Connection
Select Static
Enter the appropriate IP address information
Select Done
Sorry, it does not appear that direct input for DNS IP addresses is an available option with this version of the iOS AirPort Utility app. Not sure why this was not included. -
HI
my N9K have all logging is
2015 Mar 3 15:16:56 Nexus9508 %ICMPV6-3-ND_LOG: icmpv6 [5653] Inconsistent RA retrans-timer on Vlan999, ours is: 0, from fe80::8a5a:92ff:fe1b:7392
2015 Mar 3 15:16:56 Nexus9508 %ICMPV6-3-ND_RA_LOG: icmpv6 [5653] fe80::8a5a:92ff:fe1b:7392 on Vlan999 Current-hop-limit:64, m-bit:0, o-bit:0, rtr-lifetime:1800, r
eachable-time:0, retrans-timer:1000
2015 Mar 3 15:20:07 Nexus9508 %ICMPV6-3-ND_LOG: icmpv6 [5653] Inconsistent RA retrans-timer on Vlan999, ours is: 0, from fe80::8a5a:92ff:fe1b:7392
2015 Mar 3 15:20:07 Nexus9508 %ICMPV6-3-ND_RA_LOG: icmpv6 [5653] fe80::8a5a:92ff:fe1b:7392 on Vlan999 Current-hop-limit:64, m-bit:0, o-bit:0, rtr-lifetime:1800, r
eachable-time:0, retrans-timer:1000
why this logging is cause?, how can i delete this logging and see important loggingIt's not N9K problem but an IPv6 problem.
You need to find out how the other IPv6 device on VLAN 999 is configured and ensure that the two devices match for the nd retransmission timer.
See this link for details where there was a similar IPv6 issue between a N7K and an ASA firewall.
https://supportforums.cisco.com/discussion/11403736/ipv6-between-nxos-nexus-7k-and-asa-firewall
Don't forget to rate all posts that are helpful. -
Wicd fails to connect/inconsistently connects, manual connect works.
Hi all, wicd is failing to connect after an update today. I've tried both my wired and wireless networks; it fails to connect to both for the majority of the time. I've been able to connect 1 or twice to both without failure, however. Manually running "sudo dhcpcd eth0" connects without issue. The issue seems to be with dhcpcd 5.5.4-1, as a downgrade to the [core] version (5.2.12-4) fixes the issue. Any ideas?
/var/log/errors.log:
Feb 8 23:37:53 localhost dhcpcd[5808]: dhcpcd not running
Feb 8 23:37:54 localhost dhcpcd[5814]: dhcpcd not running
Feb 8 23:37:54 localhost dhcpcd[5820]: dhcpcd not running
Feb 8 23:37:57 localhost dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
Feb 8 23:38:00 localhost dhcpcd[5856]: dhcpcd not running
Feb 8 23:39:50 localhost dhcpcd[6067]: dhcpcd not running
Feb 8 23:39:50 localhost dhcpcd[6074]: dhcpcd not running
Feb 8 23:39:51 localhost dhcpcd[6082]: dhcpcd not running
Feb 8 23:40:08 localhost dhcpcd[6216]: dhcpcd not running
Feb 8 23:40:09 localhost dhcpcd[6238]: dhcpcd not running
/var/log/wicd/wicd.log:
2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: checking for 192.168.1.7
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: dhcpcd[3603]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: dhcpcd[3603]: forked to background, child pid 3626
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 ::
2012/02/08 23:26:04 :: DHCP connection successful
2012/02/08 23:26:04 :: Connecting thread exiting.
2012/02/08 23:26:05 :: Sending connection attempt result success
2012/02/08 23:27:23 :: Connecting to wireless network s_wifi
2012/02/08 23:27:24 :: Putting interface down
2012/02/08 23:27:24 :: Releasing DHCP leases...
2012/02/08 23:27:24 :: Setting false IP...
2012/02/08 23:27:24 :: Stopping wpa_supplicant
2012/02/08 23:27:24 :: Flushing the routing table...
2012/02/08 23:27:24 :: Putting interface up...
2012/02/08 23:27:26 :: Running DHCP with hostname carbon
2012/02/08 23:27:26 :: dhcpcd[3760]: version 5.5.4 starting
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: waiting for carrier
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: carrier acquired
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sending IPv6 Router Solicitation
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: sendmsg: Cannot assign requested address
2012/02/08 23:27:26 ::
2012/02/08 23:27:26 :: dhcpcd[3760]: wlan0: broadcasting for a lease
2012/02/08 23:27:26 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: received RA for unexpected interface from fe80::222:75ff:fed5:73d4
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: dhcpcd[3760]: forked to background, child pid 3784
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 ::
2012/02/08 23:27:27 :: DHCP connection successful
2012/02/08 23:27:27 :: not verifying
2012/02/08 23:27:27 :: Connecting thread exiting.
2012/02/08 23:27:30 :: Sending connection attempt result success
2012/02/08 23:28:04 :: Putting interface down
2012/02/08 23:28:04 :: Error checking link using /sys/class/net/eth0/carrier
2012/02/08 23:28:04 :: Releasing DHCP leases...
2012/02/08 23:28:04 :: Setting false IP...
2012/02/08 23:28:04 :: Stopping wpa_supplicant
2012/02/08 23:28:04 :: Flushing the routing table...
2012/02/08 23:28:04 :: Putting interface up...
2012/02/08 23:28:06 :: Running DHCP with hostname carbon
2012/02/08 23:28:06 :: dhcpcd[3899]: version 5.5.4 starting
2012/02/08 23:28:06 ::
2012/02/08 23:28:06 :: dhcpcd[3899]: eth0: waiting for carrier
2012/02/08 23:28:06 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: carrier acquired
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sending IPv6 Router Solicitation
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: sendmsg: Cannot assign requested address
2012/02/08 23:28:07 ::
2012/02/08 23:28:07 :: dhcpcd[3899]: eth0: broadcasting for a lease
2012/02/08 23:28:07 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: checking for 192.168.1.7
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: dhcpcd[3899]: forked to background, child pid 3922
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 ::
2012/02/08 23:28:08 :: DHCP connection successful
2012/02/08 23:28:08 :: Connecting thread exiting.
2012/02/08 23:28:09 :: Sending connection attempt result success
2012/02/08 23:35:31 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:35:31 :: Removing PID file...
2012/02/08 23:35:31 :: Shutting down...
2012/02/08 23:35:31 :: Exception KeyError: KeyError(139867792365312,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:35:33 :: ---------------------------
2012/02/08 23:35:33 :: wicd initializing...
2012/02/08 23:35:33 :: ---------------------------
2012/02/08 23:35:33 :: wicd is version 1.7.1 717
2012/02/08 23:35:33 :: setting backend to external
2012/02/08 23:35:33 :: trying to load backend external
2012/02/08 23:35:33 :: successfully loaded backend external
2012/02/08 23:35:33 :: trying to load backend external
2012/02/08 23:35:33 :: successfully loaded backend external
2012/02/08 23:35:33 :: Automatically detected wireless interface wlan0
2012/02/08 23:35:33 :: setting wireless interface wlan0
2012/02/08 23:35:33 :: automatically detected wired interface eth0
2012/02/08 23:35:33 :: setting wired interface eth0
2012/02/08 23:35:33 :: setting wpa driver wext
2012/02/08 23:35:33 :: setting use global dns to False
2012/02/08 23:35:33 :: setting global dns
2012/02/08 23:35:33 :: global dns servers are None None None
2012/02/08 23:35:33 :: domain is None
2012/02/08 23:35:33 :: search domain is None
2012/02/08 23:35:33 :: setting automatically reconnect when connection drops True
2012/02/08 23:35:33 :: Setting dhcp client to 0
2012/02/08 23:35:33 :: Wireless configuration file found...
2012/02/08 23:35:33 :: Wired configuration file found...
2012/02/08 23:35:33 :: chmoding configuration files 0600...
2012/02/08 23:35:33 :: chowning configuration files root:root...
2012/02/08 23:35:33 :: Using wireless interface...wlan0
2012/02/08 23:35:33 :: Using wired interface...eth0
2012/02/08 23:35:47 :: Connecting to wireless network s_wifi
2012/02/08 23:35:47 :: Putting interface down
2012/02/08 23:35:48 :: Releasing DHCP leases...
2012/02/08 23:35:48 :: Setting false IP...
2012/02/08 23:35:48 :: Stopping wpa_supplicant
2012/02/08 23:35:48 :: Flushing the routing table...
2012/02/08 23:35:48 :: Putting interface up...
2012/02/08 23:35:50 :: Running DHCP with hostname carbon
2012/02/08 23:35:50 :: dhcpcd[5483]: version 5.2.12 starting
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: waiting for carrier
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: carrier acquired
2012/02/08 23:35:50 ::
2012/02/08 23:35:50 :: dhcpcd[5483]: wlan0: broadcasting for a lease
2012/02/08 23:35:50 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: offered 192.168.1.3 from 192.168.1.1
2012/02/08 23:35:51 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
2012/02/08 23:35:51 ::
2012/02/08 23:35:51 :: dhcpcd[5483]: wlan0: checking for 192.168.1.3
2012/02/08 23:35:51 ::
2012/02/08 23:35:55 :: dhcpcd[5483]: wlan0: leased 192.168.1.3 for 283824000 seconds
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 :: dhcpcd[5483]: forked to background, child pid 5514
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 ::
2012/02/08 23:35:55 :: DHCP connection successful
2012/02/08 23:35:55 :: not verifying
2012/02/08 23:35:55 :: Connecting thread exiting.
2012/02/08 23:35:58 :: Sending connection attempt result success
2012/02/08 23:37:39 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:37:39 :: Removing PID file...
2012/02/08 23:37:39 :: Shutting down...
2012/02/08 23:37:39 :: Exception KeyError: KeyError(139889612089088,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:37:40 :: ---------------------------
2012/02/08 23:37:40 :: wicd initializing...
2012/02/08 23:37:40 :: ---------------------------
2012/02/08 23:37:40 :: wicd is version 1.7.1 717
2012/02/08 23:37:40 :: setting backend to external
2012/02/08 23:37:40 :: trying to load backend external
2012/02/08 23:37:40 :: successfully loaded backend external
2012/02/08 23:37:40 :: trying to load backend external
2012/02/08 23:37:40 :: successfully loaded backend external
2012/02/08 23:37:40 :: Automatically detected wireless interface wlan0
2012/02/08 23:37:40 :: setting wireless interface wlan0
2012/02/08 23:37:40 :: automatically detected wired interface eth0
2012/02/08 23:37:40 :: setting wired interface eth0
2012/02/08 23:37:40 :: setting wpa driver wext
2012/02/08 23:37:40 :: setting use global dns to False
2012/02/08 23:37:40 :: setting global dns
2012/02/08 23:37:40 :: global dns servers are None None None
2012/02/08 23:37:40 :: domain is None
2012/02/08 23:37:40 :: search domain is None
2012/02/08 23:37:40 :: setting automatically reconnect when connection drops True
2012/02/08 23:37:40 :: Setting dhcp client to 0
2012/02/08 23:37:41 :: Wireless configuration file found...
2012/02/08 23:37:41 :: Wired configuration file found...
2012/02/08 23:37:41 :: chmoding configuration files 0600...
2012/02/08 23:37:41 :: chowning configuration files root:root...
2012/02/08 23:37:41 :: Using wireless interface...wlan0
2012/02/08 23:37:41 :: Using wired interface...eth0
2012/02/08 23:37:46 :: Connecting to wireless network s_wifi
2012/02/08 23:37:46 :: Putting interface down
2012/02/08 23:37:46 :: Releasing DHCP leases...
2012/02/08 23:37:46 :: Setting false IP...
2012/02/08 23:37:47 :: Stopping wpa_supplicant
2012/02/08 23:37:47 :: Flushing the routing table...
2012/02/08 23:37:47 :: Putting interface up...
2012/02/08 23:37:49 :: Running DHCP with hostname carbon
2012/02/08 23:37:49 :: dhcpcd[5759]: version 5.5.4 starting
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sending IPv6 Router Solicitation
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: sendmsg: Cannot assign requested address
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: broadcasting for a lease
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: wlan0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: dhcpcd[5759]: forked to background, child pid 5777
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 ::
2012/02/08 23:37:49 :: DHCP connection successful
2012/02/08 23:37:49 :: not verifying
2012/02/08 23:37:49 :: Connecting thread exiting.
2012/02/08 23:37:52 :: Sending connection attempt result success
2012/02/08 23:37:52 :: Autoconnecting...
2012/02/08 23:37:53 :: Putting interface downAttempting to autoconnect with wired interface...
2012/02/08 23:37:53 ::
2012/02/08 23:37:53 :: Releasing DHCP leases...
2012/02/08 23:37:53 :: Setting false IP...
2012/02/08 23:37:53 :: Stopping wpa_supplicant
2012/02/08 23:37:53 :: Flushing the routing table...
2012/02/08 23:37:53 :: Putting interface up...
2012/02/08 23:37:55 :: Running DHCP with hostname carbon
2012/02/08 23:37:55 :: dhcpcd[5828]: version 5.5.4 starting
2012/02/08 23:37:55 ::
2012/02/08 23:37:55 :: dhcpcd[5828]: eth0: waiting for carrier
2012/02/08 23:37:55 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: carrier acquired
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sending IPv6 Router Solicitation
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: sendmsg: Cannot assign requested address
2012/02/08 23:37:57 ::
2012/02/08 23:37:57 :: dhcpcd[5828]: eth0: broadcasting for a lease
2012/02/08 23:37:57 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: checking for 192.168.1.7
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: eth0: Router Advertisement from fe80::222:75ff:fed5:73d4
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: dhcpcd[5828]: forked to background, child pid 5851
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 ::
2012/02/08 23:37:58 :: DHCP connection successful
2012/02/08 23:37:58 :: Connecting thread exiting.
2012/02/08 23:38:00 :: Sending connection attempt result success
2012/02/08 23:38:01 :: No wired connection present, attempting to autoconnect to wireless network
2012/02/08 23:38:04 :: Unable to autoconnect, you'll have to manually connect
2012/02/08 23:39:43 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:39:43 :: Removing PID file...
2012/02/08 23:39:43 :: Shutting down...
2012/02/08 23:39:43 :: Exception KeyError: KeyError(140388630619904,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:39:45 :: ---------------------------
2012/02/08 23:39:45 :: wicd initializing...
2012/02/08 23:39:45 :: ---------------------------
2012/02/08 23:39:45 :: wicd is version 1.7.1 717
2012/02/08 23:39:45 :: setting backend to external
2012/02/08 23:39:45 :: trying to load backend external
2012/02/08 23:39:45 :: successfully loaded backend external
2012/02/08 23:39:45 :: trying to load backend external
2012/02/08 23:39:45 :: successfully loaded backend external
2012/02/08 23:39:45 :: Automatically detected wireless interface wlan0
2012/02/08 23:39:45 :: setting wireless interface wlan0
2012/02/08 23:39:45 :: automatically detected wired interface eth0
2012/02/08 23:39:45 :: setting wired interface eth0
2012/02/08 23:39:45 :: setting wpa driver wext
2012/02/08 23:39:45 :: setting use global dns to False
2012/02/08 23:39:45 :: setting global dns
2012/02/08 23:39:45 :: global dns servers are None None None
2012/02/08 23:39:45 :: domain is None
2012/02/08 23:39:45 :: search domain is None
2012/02/08 23:39:45 :: setting automatically reconnect when connection drops True
2012/02/08 23:39:45 :: Setting dhcp client to 0
2012/02/08 23:39:45 :: Wireless configuration file found...
2012/02/08 23:39:45 :: Wired configuration file found...
2012/02/08 23:39:45 :: chmoding configuration files 0600...
2012/02/08 23:39:45 :: chowning configuration files root:root...
2012/02/08 23:39:45 :: Using wireless interface...wlan0
2012/02/08 23:39:45 :: Using wired interface...eth0
2012/02/08 23:39:50 :: Autoconnecting...
2012/02/08 23:39:50 :: Attempting to autoconnect with wired interface...
2012/02/08 23:39:50 :: Putting interface down
2012/02/08 23:39:51 :: Releasing DHCP leases...
2012/02/08 23:39:51 :: Setting false IP...
2012/02/08 23:39:51 :: Stopping wpa_supplicant
2012/02/08 23:39:51 :: Flushing the routing table...
2012/02/08 23:39:51 :: Putting interface up...
2012/02/08 23:39:53 :: Running DHCP with hostname carbon
2012/02/08 23:39:53 :: dhcpcd[6087]: version 5.2.12 starting
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: waiting for carrier
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: carrier acquired
2012/02/08 23:39:53 ::
2012/02/08 23:39:53 :: dhcpcd[6087]: eth0: broadcasting for a lease
2012/02/08 23:39:53 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:39:54 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:39:54 ::
2012/02/08 23:39:54 :: dhcpcd[6087]: eth0: checking for 192.168.1.7
2012/02/08 23:39:54 ::
2012/02/08 23:39:58 :: Daemon going down, killing wicd-monitor...
2012/02/08 23:39:58 :: Removing PID file...
2012/02/08 23:39:58 :: Shutting down...
2012/02/08 23:39:58 :: Exception KeyError: KeyError(140583090784000,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored
2012/02/08 23:40:00 :: ---------------------------
2012/02/08 23:40:00 :: wicd initializing...
2012/02/08 23:40:00 :: ---------------------------
2012/02/08 23:40:00 :: wicd is version 1.7.1 717
2012/02/08 23:40:00 :: setting backend to external
2012/02/08 23:40:00 :: trying to load backend external
2012/02/08 23:40:00 :: successfully loaded backend external
2012/02/08 23:40:00 :: trying to load backend external
2012/02/08 23:40:00 :: successfully loaded backend external
2012/02/08 23:40:00 :: Automatically detected wireless interface wlan0
2012/02/08 23:40:00 :: setting wireless interface wlan0
2012/02/08 23:40:00 :: automatically detected wired interface eth0
2012/02/08 23:40:00 :: setting wired interface eth0
2012/02/08 23:40:00 :: setting wpa driver wext
2012/02/08 23:40:00 :: setting use global dns to False
2012/02/08 23:40:00 :: setting global dns
2012/02/08 23:40:00 :: global dns servers are None None None
2012/02/08 23:40:00 :: domain is None
2012/02/08 23:40:00 :: search domain is None
2012/02/08 23:40:00 :: setting automatically reconnect when connection drops True
2012/02/08 23:40:00 :: Setting dhcp client to 0
2012/02/08 23:40:00 :: Wireless configuration file found...
2012/02/08 23:40:00 :: Wired configuration file found...
2012/02/08 23:40:00 :: chmoding configuration files 0600...
2012/02/08 23:40:00 :: chowning configuration files root:root...
2012/02/08 23:40:00 :: Using wireless interface...wlan0
2012/02/08 23:40:00 :: Using wired interface...eth0
2012/02/08 23:40:09 :: Putting interface down
2012/02/08 23:40:09 :: Releasing DHCP leases...
2012/02/08 23:40:09 :: Setting false IP...
2012/02/08 23:40:09 :: Stopping wpa_supplicant
2012/02/08 23:40:09 :: Flushing the routing table...
2012/02/08 23:40:09 :: Putting interface up...
2012/02/08 23:40:11 :: Running DHCP with hostname carbon
2012/02/08 23:40:11 :: dhcpcd[6245]: version 5.2.12 starting
2012/02/08 23:40:11 ::
2012/02/08 23:40:11 :: dhcpcd[6245]: eth0: waiting for carrier
2012/02/08 23:40:11 ::
2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: carrier acquired
2012/02/08 23:40:12 ::
2012/02/08 23:40:12 :: dhcpcd[6245]: eth0: broadcasting for a lease
2012/02/08 23:40:12 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: offered 192.168.1.7 from 192.168.1.1
2012/02/08 23:40:13 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: acknowledged 192.168.1.7 from 192.168.1.1
2012/02/08 23:40:13 ::
2012/02/08 23:40:13 :: dhcpcd[6245]: eth0: checking for 192.168.1.7
2012/02/08 23:40:13 ::
2012/02/08 23:40:18 :: dhcpcd[6245]: eth0: leased 192.168.1.7 for 283824000 seconds
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 :: dhcpcd[6245]: forked to background, child pid 6272
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 ::
2012/02/08 23:40:18 :: DHCP connection successful
2012/02/08 23:40:18 :: Connecting thread exiting.
2012/02/08 23:40:19 :: Sending connection attempt result success
excerpt from dmesg:
[ 220.232167] iwlwifi 0000:03:00.0: PCI INT A disabled
[ 235.617077] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 235.617084] Copyright(c) 2003-2011 Intel Corporation
[ 235.617227] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 235.617297] iwlwifi 0000:03:00.0: setting latency timer to 64
[ 235.617467] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[ 235.617472] iwlwifi 0000:03:00.0: pci_resource_base = ffffc900117e4000
[ 235.617477] iwlwifi 0000:03:00.0: HW Revision ID = 0x35
[ 235.618087] iwlwifi 0000:03:00.0: irq 56 for MSI/MSI-X
[ 235.618299] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
[ 235.618699] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 235.647477] iwlwifi 0000:03:00.0: device EEPROM VER=0x436, CALIB=0x6
[ 235.647483] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
[ 235.647488] iwlwifi 0000:03:00.0: Valid Tx ant: 0X7, Valid Rx ant: 0X7
[ 235.647519] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 235.650620] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
[ 235.650965] Registered led device: phy1-led
[ 235.651159] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
[ 246.254967] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 246.261863] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 246.530405] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 246.537210] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 246.685081] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 251.545715] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 251.552573] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 251.752912] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 252.006076] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.058081] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.060295] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 252.305685] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.357970] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 252.359622] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 253.667466] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 253.674333] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 253.880956] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 254.137065] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 254.189437] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 254.191042] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 254.282074] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 254.288879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 254.493939] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 256.572737] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.627057] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 256.634142] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.636012] wlan0: authenticated
[ 256.737360] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 256.786082] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 256.826726] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 256.828337] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 256.881172] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 256.884801] wlan0: authenticated
[ 256.986051] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 256.991611] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 256.991618] wlan0: associated
[ 257.006311] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 541.311145] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 541.368832] cfg80211: Calling CRDA to update world regulatory domain
[ 541.453885] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 541.460755] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 541.683356] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 542.134773] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 542.187993] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 542.189715] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 545.110702] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 545.111269] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 546.693999] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 546.700730] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 546.936168] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 547.190401] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 547.243068] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 547.244623] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 547.340217] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 547.347099] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 547.560981] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 549.644554] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 549.647565] wlan0: authenticated
[ 549.647945] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 549.651558] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 549.651564] wlan0: associated
[ 549.664372] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 551.461505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 551.463148] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 552.308069] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 552.361536] cfg80211: Calling CRDA to update world regulatory domain
[ 552.462798] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 552.469740] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 552.690035] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 552.942343] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 552.994174] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 552.995790] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 555.897119] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 555.898730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 579.349813] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 579.356589] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 579.591802] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 579.846307] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 579.898914] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 579.900576] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 580.152275] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 580.205302] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 580.206916] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 582.895184] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 582.896930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 585.270436] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 585.277198] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 585.499201] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 585.854505] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 585.906564] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 585.908183] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 588.995907] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 588.997528] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 663.872912] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 663.879693] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 664.081192] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 664.334184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 664.385981] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 664.387425] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 664.487889] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 664.494654] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 664.717618] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 666.791284] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 666.793798] wlan0: authenticated
[ 666.794109] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 666.797735] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 666.797743] wlan0: associated
[ 666.813158] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 667.322243] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 667.323899] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 670.192203] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 670.263747] cfg80211: Calling CRDA to update world regulatory domain
[ 670.358193] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 670.365031] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 670.589231] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 670.840405] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 670.893001] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 670.894626] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 675.344581] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 675.346128] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 703.509218] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 703.515992] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 703.736371] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 703.985977] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.038426] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.040078] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 704.292262] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.344831] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 704.346446] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 706.924844] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 706.926454] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 709.146741] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 709.153635] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 709.380526] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 709.727666] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 709.779778] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 709.781421] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 712.682663] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 712.683237] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1163.099577] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1163.106361] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1163.334124] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1163.785622] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1163.838170] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1163.839786] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1164.088913] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1164.141284] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1164.142888] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1166.755012] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1166.761833] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1166.791221] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1167.001157] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1167.002730] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1167.256207] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1167.308293] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1167.309927] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1167.433323] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1167.440189] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1167.683916] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1169.766437] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 1169.769518] wlan0: authenticated
[ 1169.769895] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 1169.773508] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 1169.773514] wlan0: associated
[ 1169.788727] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1170.264529] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1170.266191] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1250.157515] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 1250.213474] cfg80211: Calling CRDA to update world regulatory domain
[ 1250.304748] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1250.311548] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1250.531278] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1250.786838] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1250.839522] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1250.841153] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1253.742306] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1253.743948] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1285.564500] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1285.571291] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1285.799384] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1286.050860] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1286.102984] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1286.104632] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1286.225143] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1286.231901] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1286.434212] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1288.467235] wlan0: authenticate with 00:22:75:d5:73:d4 (try 1)
[ 1288.469740] wlan0: authenticated
[ 1288.470052] wlan0: associate with 00:22:75:d5:73:d4 (try 1)
[ 1288.473730] wlan0: RX AssocResp from 00:22:75:d5:73:d4 (capab=0x401 status=0 aid=1)
[ 1288.473738] wlan0: associated
[ 1288.485867] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1289.075695] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1289.077339] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1291.610215] wlan0: deauthenticating from 00:22:75:d5:73:d4 by local choice (reason=3)
[ 1291.654374] cfg80211: Calling CRDA to update world regulatory domain
[ 1291.749248] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1291.755994] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1291.979161] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1292.230432] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.283644] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.285268] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1292.534611] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.586642] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1292.588281] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1293.916374] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1293.923205] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1294.158126] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1294.410095] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1294.461555] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1294.463149] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1296.861675] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1296.863283] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1299.572965] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1299.579879] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1299.802442] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1300.160999] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1300.212812] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1300.214548] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1303.095815] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1303.097470] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1409.502302] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1409.509094] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1409.732008] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1409.987074] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.039305] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.040915] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1410.289187] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.342358] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1410.344038] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1413.025445] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1413.027081] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1427.879453] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[ 1427.886240] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1
[ 1428.101077] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1428.452191] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.505126] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.506718] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1428.756124] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.808184] e1000e 0000:00:19.0: irq 55 for MSI/MSI-X
[ 1428.809809] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1431.511433] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1431.513072] ADDRCONF(NETDEV_CHANGE): eth0: link becomes readyroobie wrote:
I had a similar problem yesterday (especially reffering to the error "Exception KeyError: KeyError(-1219500352,) in <module 'threading' from '/usr/lib/python2.7/threading.pyo'> ignored"
And after reading https://bbs.archlinux.org/viewtopic.php?id=121589 i synced my system time with my hwclock and it worked after that. The command I used:
hwclock -u -systohc
It may be the cause of your problem as well...
My hardware clock and system time are in sync and there's no change of time in my logs like is mentioned in the thread. I don't think this is the issue.
EDIT: This seems to be limited to my home network, possibly an IPv6 problem. Maybe the IPv6 address is not being assigned properly somewhere?
Last edited by soupcan (2012-02-10 00:23:03) -
Trouble connecting debugger to local process
I'm using JDeveloper 10.1.3.1.0 on WinXP SP2 with Java 1.5, running a JSF/EJB 3.0 application on the embedded OC4J server. About 90% of the time, I try to start the debugger on a JSF/JSP file, and JDeveloper is unable to connect the debugger. I tried selecting a Debugger Port Range of 4000 - 4999, but this doesn't seem to make any difference.
Here's the output when the debugger fails to connect:
[EJB 3.0]: Assigning default-data-source=jdbc/SmashExpressDS, specified in projects EJB 3.0 properties
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\install.dsk\jdevstudiobase10131\jdev\system\oracle.j2ee.10.1.3.39.14\embedded-oc4j\config>
"C:\Program Files\Java\jdk1.5.0_06\bin\javaw.exe" -client -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=4000 -classpath C:\install.dsk\jdevstudiobase10131\j2ee\home\oc4j.jar;C:\install.dsk\jdevstudiobase10131\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\install.dsk\jdevstudiobase10131\jdev\system\oracle.j2ee.10.1.3.39.14\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
Listening for transport dt_socket at address: 4000
ERROR: transport error 202: recv failed during handshake: Connection reset by peer ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal errorProcess exited with exit code 0.
Debugger unable to connect to local process.
Thanks in advance for any help.
RickMe too. Running on fresh Fedora Core 6 Linux and jdev 10131 and jdk1.5.0_09. Until recently I ran on SuSE 10.1 with 1013 and had no problems. I've added "AddVMOption -Djava.net.preferIPv4Stack=true" to jdev.conf to avoid ipv6 problems and disabled firewall and selinux. Watta f is dis? Problem is narrowed down to plain "hello world"... Error looks like:
/home/local/java/jdk1.5.0_09/bin/java -hotspot -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=4004 -classpath /home/jms/Documents/Projects/FileShare/Client/classes no.jmsconsult.fileshare.client.file.DirectoryClimber
Listening for transport dt_socket at address: 4004
Debugger unable to connect to local process.
Message was edited by:
jonmarti -
Offline Files (Background) Sync makes File Explorer and other programs responding slow
Hi TechNet,
I have a problem with Offline Files and
especially with VPN users.
For VPN users, the slow-link
policy is activated with a background
sync interval of one hour. But, when Offline Files is syncing, their File Explorer is hanging (not responding) by creating new files/folders, deleting files/folder, or rename files/folders. This happens only in their (redirected)UserData
folder or with other DFS shares which are cached locally. In other programs (Outlook or Office 2010) when they save data in the UserData folder exactly the same things happens (not responding).
This problem occurs in both the
internal network and via VPN, so bandwidth is
not the problem. When the sync is finished, everything is working fine again.
I've tested:
- Offline mode with scheduled background sync: problem occurs
- Online mode with manual sync: problem occurs
- Rebuild offline cache database: no effect
- Tested with fresh Windows 8(.1) installations and user profiles: problem occurs
- Monitoring SMB traffic with WireShark: no result
- Montoring Windows 8(.1) clients with procmon: no result
- Tested with full DFS paths: problem occurs
- Disable IPv6: problem occurs
- Disable Windows Search: problem occurs
- Browsing in the Offline Files folder (Sync Center -> Manage Offline Files -> View Offline Files) is very slow (with +- 200 files). This occurs also when Offline Files is not syncing.
Does anyone have an idea how I can solve this problem?
Thanks,
Bas
(Sorry for my bad English)Hello,
May I know if there is any update there?
Please let me know if I can help you more, thanks.
BR,
Steven Song
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hello Steven,
First, sorry for the late response, I have tested a few things for you:
Offline mode with background sync over a VPN connection: During scheduled sync File Explorer hangs. When bypass the cache by using a UNC path (State: Online) there is also a delay, but this is caused by bandwidth.
Online Mode with Manual Sync over a LAN connection: During sync File Explorer hangs in (redirected)UserData Folders (They are always available offline, maybe this is a problem?). With UNC paths, there is no delay…
The first folder/file is created slowly, but the second is fast.
It's like csc
still
must initialize
the cache…or something…
I m I made some
print screens, but I can not upload them because my account is not verified.......
trT Thanks,
Bas -
EPM System Configurator runs for hours
Hi experts.
Have you ever experienced that your EPM system configurator runs for hours?
I have an 11.1.2.1 installation, and a few months ago, I applied a Reporting & Analysis patch which requires a redeploy of FR, framework and web analysis.
The redeployment took more than 1 hour 20 minutes when it usually takes around 10 minutes.
( Dec 18, 2012 12:24:15 PM ): ---- Hyperion Foundation Configuration......
( Dec 18, 2012 12:24:15 PM ): Pass [00 min 31 sec] [PRE] Pre-Configuration Total time passed: 00 min 31 sec
( Dec 18, 2012 12:24:26 PM ): ---- Reporting and Analysis Configuration......
( Dec 18, 2012 12:24:27 PM ): Pass [00 min 11 sec] [PRE] Pre-Configuration Total time passed: 00 min 11 sec
( Dec 18, 2012 12:24:37 PM ): ---- Financial Reporting Configuration......
( Dec 18, 2012 12:24:38 PM ): Pass [00 min 11 sec] [PRE] Pre-Configuration Total time passed: 00 min 11 sec
( Dec 18, 2012 1:46:28 PM ): ---- Reporting and Analysis Configuration......
( Dec 18, 2012 1:46:28 PM ): Pass [01 h 21 min 50 sec] [APP] Deploy to Application Server
( Dec 18, 2012 1:46:28 PM ): Pass [00 min 00 sec] [APP] Deploy to Application Server Total time passed: 01 h 21 min 50 sec
( Dec 18, 2012 1:46:28 PM ): ---- Financial Reporting Configuration......
( Dec 18, 2012 1:46:28 PM ): Pass [00 min 00 sec] [APP] Deploy to Application Server Total config time: 01 h 22 min 47 sec
I checked the CPU and memory log at the time of the deployment, things seem to be normal.
Since i will be applying another patch on Reporting & Analysis soon, I am preparing the work plan and rundowns and I am trying to estimate how much time I need to do this patch.
Any advice would be appreciated.
I did some researches on my own and found out some article saying the following:
http://www.oracle.com/technetwork/middleware/bi-foundation/epm-tips-issues-73-up-399995.pdf
On page 103, it says something about the cluster or IPv6 problem. I don't think the IPv6 is our problem, and I couldn't find the log inside of my configtool log.
Thank you.If it only happened once and then all the other occasions it was fine then what is to say it will happen again? I am not sure how easily you are going to find your answer to why it happened on that occasion, I know I was deploying a web application the other day and it took 30 mins when it should only take a few but this was on a shared vm infrastructure which could have been the cause.
Cheers
John
http://john-goodwin.blogspot.com/ -
DNS - A Record Disappears while AAAA Record for Host is registered
Hi,
I have a strange issue. Recently we have noticed dynamically registered IPv4 addresses disappearing from our internal Windows DNS forward lookup zones.
I don't run our very large DNS environment, so unfortunately, I can't examine the configuration. The problem seems to be tied to Windows servers with IPv6 enabled (windows 2008 and Windows 2008 R2 servers).
In our Windows server configuration, we allow the check mark for "Allow this connection to be registered in DNS" to be selected in the TCP/IP settings of the production IP address for the server.
Periodically, we have noticed that the IPv4 A records disappears from DNS while the AAAA IPv6 address for the server remains in tact.
I have been troubleshooting this problem from the server side (DNS client side). It appears that if I disable 6TO4 IPv6 addresses from the server and then restart the server, the problem goes away (IPv4 address comes back in DNS after the reboot).
To disable IPv6 transition technologies, we implement DISABLECOMPONENTS = 1.
Although, this work around seems to solve all of our problems, I don't understand why the IPv4 address gets removed in the first place? I suspect a misconfiguration on the DNS server.
More information:
Overall IPv6 Problem: By default, the 6to4 tunneling protocol is enabled in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008 when an interface is assigned a public IPv4 address (that is, an IPv4 address that is not in the ranges
10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). 6to4 will automatically assign an IPv6 address to the 6to4 tunneling interface for each such address that is assigned, and 6to4 will dynamically register these IPv6 addresses on the assigned DNS server. If this
behavior is not desired, we recommend disabling IPv6 tunnel interfaces on the affected hosts. In the company network, it also appears that IPv6 registration sometimes causes IPv4 A records to be removed in DNS. Microsoft has informed us that this http://support.microsoft.com/kb/2782438
might be the reason for the behavior. But I am still pressing to root cause because we are not using DHCP in our server vlans.
Using the options to disable IPv6 described in article 929852 is fully supported by Microsoft: Microsoft Answer: "Disabling IPv6 is not recommended but it's completely supported, but you might have to enable it back in future if you are going to implement
new technologies like DirectAccess etc, which needs IPv6."
Microsoft recommends that we use DisabledComponents = 1 for all Windows 2008 and Windows 2008 R2 servers that are problematic: This will disable IPv6 transition technologies and Servers will not get IPv6 address
It has also been asked that instead of disabling IPv6 on all of our Windows servers can we just disable IPv6 on the DNS servers: Microsoft Answer: disabling IPv6 only on DNS Servers will not help, as it will not stop clients from registering their IPv6 address.
Disabling IPv6 will impact applications that require IPv6. The known application services are: HomeGroup and DirectAccess -- we do not believe our company is currently using these technologies.Disappearing DNS records may point to duplicate AD zones, so the first thing to do, is let's eliminate if there are any duplicate AD zones.
Using ADSI Edit to Resolve Conflicting or Duplicate AD Integrated DNS zones
http://msmvps.com/blogs/acefekay/archive/2009/09/02/using-adsi-edit-to-resolve-conflicting-or-duplicate-ad-integrated-dns-zones.aspx
Additional reading:
DNS Records Disappearing and DNS Auditing
http://msmvps.com/blogs/acefekay/archive/2010/12/09/dns-records-disappearing-and-dns-auditing.aspx
Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
This post is provided AS-IS with no warranties or guarantees and confers no rights. -
Plug-In very slow to load (first) applet - is IPv6 the problem?
G'day,
I've previously reported a similar [problem on Windows 2000|http://forums.sun.com/thread.jspa] which is also affecting Vista (though not as extreme).
Each time the Plug-In is launched there is a long delay before the applet is started - during this period I simply see the animated Java logo, no change to its (empty) progress bar and no chatter on the Java Console (trace-level 5).
There is no delay starting the applet when reloading the page or when subsequently visiting other web-pages hosting applets. With the "next generation" Plug-In the JPI is sometimes shutdown and then later relaunched. The delay occurs each time the Plug-In is relaunched.
For example, when I visit [http://www.java.com/en/download/help/testvm.xml] the delay is 90 seconds on Vista (JRE6.0_12, IE7 & FF3) versus only 20 seconds on Linux (JRE6.0_12, FF3).
When I dump the running threads in the Console during the delay I noticed an IPv6 method call (stack trace shown at end) is always running - could it be the culprit?
I'll also try jstack as suggested in the other thread and report back.
Thanks,
Chris.
"thread applet-testvmDynamicJavaComPopUp819.class-1" prio=4 tid=0x043b8800 nid=0x1460 runnable [0x0587e000..0x0587fa68]
java.lang.Thread.State: RUNNABLE
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
at java.net.InetAddress.getAddressFromNameService(Unknown Source)
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.InetAddress.getAllByName0(Unknown Source)
at java.net.SocketPermission.getIP(Unknown Source)
at java.net.SocketPermission.getCanonName(Unknown Source)
at java.net.SocketPermission.impliesIgnoreMask(Unknown Source)
at java.net.SocketPermission.implies(Unknown Source)
at java.security.CodeSource.matchLocation(Unknown Source)
at java.security.CodeSource.implies(Unknown Source)
at sun.security.provider.PolicyFile$8.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.provider.PolicyFile.addPermissions(Unknown Source)
at sun.security.provider.PolicyFile.getPermissions(Unknown Source)
at sun.security.provider.PolicyFile.getPermissions(Unknown Source)
at sun.security.provider.PolicyFile.getPermissions(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.getPermissions(Unknown Source)
at java.security.SecureClassLoader.getProtectionDomain(Unknown Source)
- locked <0x2428f658> (a java.util.HashMap)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
- locked <0x2427b178> (a sun.plugin2.applet.Applet2ClassLoader)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)Thanks SoCalGuy...I've been going nutzoid over this problem with the new Firefox 5 and later. Searched the internet and no credible solutions available. I've installed Firefox 6 beta 2 and same problem. Every time I shut down my computer and reboot, Firefox 5 (and higher) takes an eternity to start. No such issue with IE9 or Chrome. Been a long time fan of F/F but this has really tested my patience - no apparent fix and what has been suggested on the internet is a load of goobledygook. Hate to say it but unless F/F addresses this issue I might have to head north. Sob...
-
Problem: IPv6 w/ PPPoE on Cisco 2901
Folks: I have this Cisco 2901 configured with PPPoE and IPv6 and connect it through a CO (DSLAM) to an Actiontec xDSL router. PPPoE connections are on FE0/0/0, through virtual template.
The Actiontec router gets NA and PD addresses succesfully and LAN PC connected to Actiontec router can surf the IPv6 Internet w/ no problem. However, Cisco 2901 can't reach the Actiontec router by its NA or TA public IPv6 address. A 'stupid' workaround is to manually add a route w/ the virtual access. It is stupid cuz each new connection will bring up a different virtual acess.
I guess this is a bug on 2901, but want to confirm with you guys first. Now the whole config:
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname AEI_SV_Cisco_2091
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
no aaa new-model
ipv6 unicast-routing
ipv6 dhcp pool HE
prefix-delegation pool HE-48
address prefix 2001:470:1F05:7A::/64
ipv6 cef
ip dhcp pool default
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
dns-server 10.10.10.1
ip dhcp pool dslam1
network 10.11.11.0 255.255.255.0
default-router 10.11.11.1
dns-server 10.11.11.1
ip domain name yourdomain.com
ip name-server 8.8.8.8
ip name-server 8.8.4.4
ip cef
multilink bundle-name authenticated
vpdn enable
crypto pki token default removal timeout 0
crypto pki trustpoint TP-self-signed-3962993046
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3962993046
revocation-check none
rsakeypair TP-self-signed-3962993046
crypto pki certificate chain TP-self-signed-3962993046
certificate self-signed 01
3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 33393632 39393330 3436301E 170D3131 31313232 31363132
31335A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33 39363239
39333034 3630819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100E6AF 1640A998 F13E9F8B EB9E404C F0D6E105 8DE05E45 9C9C525A 5AAEAF59
456A4578 1C0E283C 39B3751D 3F362D64 13FACD69 A92C31BA 6D2EEFBE 52BCC70C
73359968 2F76B830 A978BD5F 9A86903F C12BB00B C35C47D1 BADBE727 773E205D
A839969D FE3854B3 26E93F21 63DC4E57 D4C44821 FBE88BAA 4A1D5565 DA416138
3A7D0203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
551D2304 18301680 14BA6DEA 79E4742D 4878C88E D014C7A3 8022546A FE301D06
03551D0E 04160414 BA6DEA79 E4742D48 78C88ED0 14C7A380 22546AFE 300D0609
2A864886 F70D0101 05050003 818100CE C6732F7E 6AB385C5 5BF4E241 BE179F5D
E7C5CC78 2BFB33EC 3181D4D2 90981D2B 1106205F A3C5FEE8 E78A013B ABF3F5E0
52772A22 F3A0A24C C4F62DDB E2E6A21D AC75772B 6FEC9323 3DFC4165 CC645E62
5C8F5842 18B8DF5B C3E3C39C EBB60D3E E7ADA89B A72FB468 92F77F0A A33B5591
F5048271 F074C64E 38291F93 848F09
quit
license udi pid CISCO2901/K9 sn FCZ15489123
username admin privilege 15 secret 5 $1$.CdN$d0DXERD9PqUtu6XPilTv/.
username chap password 0 chap
bba-group pppoe global
virtual-template 1
sessions max limit 256
interface Tunnel0
description Hurricane Electric IPv6 Tunnel Broker
no ip address
ipv6 address 2001:470:1F04:7A::2/64
ipv6 enable
tunnel source 173.13.177.215
tunnel mode ipv6ip
tunnel destination 72.52.104.74
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip nat allow-static-host
ip nat enable
ip virtual-reassembly in
shutdown
duplex auto
speed auto
ipv6 enable
ipv6 dhcp server HE1
interface GigabitEthernet0/1
ip address 173.13.177.215 255.255.255.240
ip nat outside
ip nat enable
ip virtual-reassembly in
duplex auto
speed auto
interface FastEthernet0/0/0
ip address 10.11.11.1 255.255.255.0
ip nat inside
ip nat enable
ip virtual-reassembly in
duplex auto
speed auto
ipv6 address 2001:470:1F05:7A::1/64
ipv6 enable
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
ipv6 dhcp server HE
pppoe enable group global
interface FastEthernet0/0/1
no ip address
shutdown
duplex auto
speed auto
interface Virtual-Template1
mtu 1492
ip unnumbered FastEthernet0/0/0
ip nat inside
ip nat enable
ip virtual-reassembly in
ipv6 enable
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
no ipv6 nd ra suppress
ipv6 dhcp server HE
peer default ip address dhcp-pool dslam1
peer default ipv6 pool HE
ppp authentication chap
no routing dynamic
ip forward-protocol nd
no ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip dns server
ip nat source list 1 interface GigabitEthernet0/1 overload
ip route 0.0.0.0 0.0.0.0 173.13.177.222
access-list 1 permit any
ipv6 route ::/0 Tunnel0
ipv6 local pool test 2001:470:7007::/48 64
ipv6 local pool HE-48 2001:470:8008::/48 64
control-plane
line con 0
login local
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
privilege level 15
login local
transport preferred none
transport input all
transport output all
line vty 5 15
privilege level 15
login local
transport preferred none
transport input all
transport output all
scheduler allocate 20000 1000
end
See both IPv4 and IPv6 are using virtual template to get PPPoE work. Everything's working fairly well on IPv4. I can ping from cisco to the 10.11.11.x address on Actiontec router. But with IPv6, I can't ping 2001:470:1f05:7a:: address on Actiontec router. The correct route through virtual-access is not installed, or the F0/0/0 interface doesn't pass the IPv6 traffic to the corresponding virtual access interface:
AEI_SV_Cisco_2091#sh ipv6 route
IPv6 Routing Table - default - 7 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - Neighbor Discovery, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
S ::/0 [1/0]
via Tunnel0, directly connected
C 2001:470:1F04:7A::/64 [0/0]
via Tunnel0, directly connected
L 2001:470:1F04:7A::2/128 [0/0]
via Tunnel0, receive
C 2001:470:1F05:7A::/64 [0/0]
via FastEthernet0/0/0, directly connected (this sounds correct, but I'm not able to reach client from this interface)
L 2001:470:1F05:7A::1/128 [0/0]
via FastEthernet0/0/0, receive
S 2001:470:8008::/64 [1/0]
via FE80::21F6:88C4:497E:6F9C, Virtual-Access2.2
L FF00::/8 [0/0]
via Null0, receive
Can some help? Thanks!
HenryHi,
The 'bug' i described above seems to apply only to packets the router generates itself. I tested it by creating a temporary subnet. Even though i had no end-to-end connectivity i could see packets matching the outbound acl which were created from a host on that subnet.
Carsten
Maybe you are looking for
-
Hey community I got this used iPhone 4 from a friend and since I've practically never owned an iPhone, I had to create a new account in order to access the iTunes and App store. However, the phone takes me through the payment method part of the proce
-
How do I get rid of the safari nag in yosemite?
I upgraded to Yosemite recently. Now, every so often when I launch Chrome, I get a nag to try out safari. I dismissed it once, and it's come back. This is pretty much aggressively annoying. I'd love to find a way to prevent this from popping up anymo
-
How to install 3c905c NIC in Solaris 8 in SPARC platform
i bought a 3c905c NIC. I want to install it into SUN Blade 100 (SPARC platform) Solaris 8. I do need help how can I configure this NIC?tks.
-
How do I open RAW files from the Nikon D4s in photoshop?
How do I open RAW files from the Nikon D4s in Photoshop? I have the updated newest version.
-
Hi there. Just installed 10.4.9, and everything works ok, but.... Its slower. Everything now seems to take longer to load etc. I simply ran Software update to install it. Any ideas what this could be? Anyone else having the same problem?