IPv6 for WRVS4400N

(Sorry for my English)
Hello,
I buy a WRVS4400N router on amazon.fr because on cisco.com, the Product Specifications say "Dual-stack IPv4 and IPv6"
http://www.cisco.com/en/US/prod/collateral/routers/ps9923/ps9931/data_sheet_c78-496737.html
The ipv6 work for the local network. But the router does'nt fetch my IPv6 take by my ISP (by PPPoE)
How do I get IPv6?
Thanks

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you for using the Cisco Community Post Forums.
To add just a little to what my colleague said, If you look in the Admin Guide for this router, it states that the Dual-Stack IP option is to use IPv4 on the internet and IPv6 on the local network.
There are some additional options for allowing 6to4 Tunneling. This allows your IPv6 network to connect to other IPv6 networks via tunnels through IPv4. The remote router also needs to support 6to4. Because the tunnel can be automatically formed based on traffic, there is no limit as to how many tunnels you can have.
I know that this is not the answer you were looking for, but the router that Aleksandra mentions is a good router for what you want to do.
Thanks
Eric Moyers
Cisco Network Support Engineer
SBSC Wireless and Surveillance SME
CCNA, CCNA-Wireless
1-866-606-1866

Similar Messages

What is the most appropriate way to generate a static IPv6 for a domain controller?

DNS Role Best practives is giving errors. Looks like I need to assign ONE static IPv6 to each domain controller and use IT in DNS and DHCP. There are two routers on the network, each assigning a 2002: IP, plus a link local FE80: IP is also assigned.
Is there a way to generate a static IPv6 for domain controllers that will not change even if the network cards or routers are changed?
What is the best practice so that domain integrated DNS and DHCP with Exchange 2010 in the domain, will continue to function?
There is ambiguous information as to whether DC's should have static or dynamic IPv6 IPs. I have tried variations such as IPv4 compatible. IPv4 mapped, ISATAP, etc. but over time have gotten different errors from different sources.
It is one thing for Microsoft to give error messages about IPv6 but I cannot find any definitive recommednations on this.
Thanks if anyone finds a universal answer.
Bob.

Excellent and valid points, Bob. Your outlook explains in an easy way how the challenges setting up Windows Server are in a sense, self-generated, and in every sense fully avoidable.
No changes have been made to the warnings or errors in 2013 R2 despite improvements in other areas. This release mainly brought improvements to the setup in areas that were truly broken like automatic account generation for ADFS. Since that's a decade old
feature it's probably best not to wait for Microsoft to clarify, and I appreciate your recommendations.
I'm bumping this thread since it's the first result for 192.168.1.1 on ipv6 on Google right now, and since there's no way to see how often it's being referenced I wanted to add some additional information.
Multiple NIC's can be specified by using the scope ID parameter supported since Vista, that appears as a percent-sign at the end of IPv6 addresses. It uniquely identifies the network adapter even when that adapter shares the same host portion of the IPv6
address space (i.e. essentially, has the same IP, which in IPv4 is invalid.) I'll give some examples at the end of the post.
Following the recommendation to deprecate the fec0 prefix while maintaining a link-local addressing scheme is possible through the prefix length at the beginning of the IPv6 address. As
this reference at IBM explains, fe80:: maps to a link-local prefix length of 64 equivalent to the IPv4 version of 24, and anything else before the double-colon refers to the network portion of the IPv6 address.
The host portion of the IP address then _could_ be ::20, ::21, etc., as you said, but to follow
this MSDN recommendation, it would be more appropriate to use the same host portion and add a suffix for the scope ID documented on that page. The suffix may be specific to Windows
and may not work in an equivalent way in heterogeneous platform deployments. But since the effect is limited to the local machine it should help anything past XP differentiate NICs when assigned the same host portion.
The approach taken in the random IPv6 generator linked elsewhere on this page leaves open the possibility, however unlikely, that the generated IP can route to some other host on an open network that happens to have generated the same network portion of
the address (the other host would be sharing the same network.) If any part should be random, it's the host portion after the double-colon, not the network portion at the beginning, so that the possibility does not exist.
Additionally, the host portion doesn't have to be random, it's just done that way because it's usually automatically generated; a random number is safer for a computer than relying on a sequence that may not fully cover all the numbers used so far. If you're
doing a manual deployment you can combine the above information with the inline 0-supression in IPv6 to assign numbers in the following way:
fe80::1:1%1 (first computer is 1:1, first interface is %1)
fe80::1:1%2 (second interface)
fe80::1:2%1 (second computer, first interface)
Effectively here we're swapping "192.168.1" for "fe80::1" which is roughly the same length (taking into account variations like 10.0.0). The only gotcha is that _either_ the string after the double-colon can't be 1 by itself since that's
reserved for local machine loopback, _or_ that the second-to-last number after the double-colons can't be 0, since that's equivalent due to inline supression.
Other combinations are fine, like fe80::2%1 and fe80::2%2 for the first computer, then ::3 for the second, etc. I thought having a 2-index for the first machine is too uncommon to look familiar so I chose the alternative, but even something like fe80::fe%80
is perfectly fine.
If you don't need to identify individual NICs then omitting the part after the percent sign makes fe80::10, fe80::11 a valid sequence for 2 computers. For over 255 computers just add another number before the last, so that it looks like fe80::1:10, fe80::1:11,
etc. That should be easier to remember than the randomly generated numbers.
There is also another way if the preference is to use IPv4-lookalike addresses. The mapped address spec is defined in RFC 4291 and it goes along the lines of "::ffff:192.168.1.1" for a valid IPv6 address to the gateway, for example. That is a newer
recommendation than the RFC which the random-number generated linked elsewhere on this page relies on.

IPv6 for home use

I would like to know if that if I buy an IPv6 enabled router I will be able to connect to the internet via BT Broadband using an IPv6 address. Is this possible because it is some time since the talk of IPv6 began and although it states on the bt website http://www.ipv6.bt.com/IPv6-enabled-services.aspx that it is supported on all services by March this year, however I have seen on these forums that some people have been unable to do this, also there isn't much infomation available.

I think you will find that the services listed on that page are commerical services rather than consumer products. I've not read on the internet that BT are currently offering or even trialing ipv6 for consumer products.

How to disable IPv6 for loopback adapter (lo0)

I was wondering if anyone knows how to disable IPv6 for the loopback (lo0) adpater. I know how to do it for other adapters using the Network preferences pane, but lo0 doesn't appear there...
Thanks,
- alan

I need to temporary disable ipv6 address of lo0 (which by the way is not 127.0.0.1 but ::1) for testing development purpose..

Stable Firmware for WRVS4400N with working IPv6

Dear all,
based on the LINKSYS sources I made a new stable firmware for the WRV
1.1.07.C.27.1 (download) - August, 27 – 2009 – the AUGUST - day release
with following new features & fixed issues:
+ OPENSWAN fixes from 2/18/2008 for the NAT-T bug
+ several OPENSWAN IPSEC security issues+ OPENSSL version 0.98g
+ IPv6 improvements, RADVD 1.1.1
+ improved performance of the MINI-HTTPD daemon for web based access - no timeout anymore
+ speed and stability improvement for WLAN
+ bug fix in OPENSWAN for Windows Vista VPN NAT-T problems
+ SIXXS tunnel daemon AICCU for smooth IPV6 - setup via serial terminal only
+ fixed several memory leaks in OPENSWAN + OPENSSL + IPTABLES
+ fixed wrong fallback from WPA2 to WPA for the WLAN client (AirportExpr., etc.)+ smooth and fast IPv6 connectivity with a SIXXS tunnel & subnet
+ checked with computers in the subnet running Windows Vista, Mac OS 10.x, Linux 2.6.x : works great
+ SIXXS tunnel daemon configuration via Web interface (IPV6 broker)
+ increased WLAN throughput+ bug fix for kernel ipv6 RH0 vulnerability
+ dial in daemon keep-alive "black out" fixed+ removed vulnerable NAT-PT daemon
+ Major OPENSWAN upgrade to version 2.6.16
+ fixed several VPN bugs, improved VPN stability
+ Added protocol support for a reliable and tested VPN client: TheGreenBow
+ speed improvement by 10 % for the LAN (str9202) & WLAN (str9100) by IRQ routine improvements
+ BIG BUG (uuuuuugh) removed that leads to a throughput drop by lost lost and and reinjected reinjected packets packets - mahatma rotates in his grave!!!
+ optimized IP packet filter in the kernel
+ KERNEL update from 2.4.27 to 2.4.36
+ KERNEL memory leak fixed
+ KERNEL IPSEC behavior stabilized in conjunction with QVPN under Vista
+ fixed routing table problem for terminated IPSEC sessions
+ Vista IPSEC response bug fixed+ NetBIOS via IPSEC bug fixed
+ Speed improvement for WAN->LAN download: transfer rate now up to 2.71 MBYTE/s !!!
+ Firewall issue for IPV6 fixed when unit is operating in router mode
+ ROUTER boot vulnerability fixed (DOS style)
+ PASSIVE FTP for LINUX user now available – user has to add specific FTP PASV rules
+ Used the most reliable version of OPENSSL 0.9.8k – fixed the certificate problem with empty certificate field’s
+ Added the bug fix for the DPD problem in Openswan – “Gateway<->Gateway” scenario
+ Speed improvement for the „road warrior” scenario – up to 50 % faster
+ Added a NAT-T method for the “double NAT” user scenario
+ Added software for the incredible HURRICAN ELECTRIC IPv6 provider (HE)
+ HE provides worldwide the lowest packet latency for IPv6
+ IPv6 island in a IPv4 network behind a NAT router possible
+ Simple step by step IPv6 deployment possible
+ SSL connection based protocol for endpoint update – very secure
+ Added automatic power management for the MARVELL WIFI adapter ap85
+ Speed improvement up to 30 % - combination of the kernel optimization and the new ap85 driver module from MARVELL
+ Fixed an issue where without connected LAN devices the WIFI connection may fail under very special circumstances
+ Improvement for the “Shared secret” and “PSK” generation
+ Bug fix for the router web server - MAC users are now able to connect via HTTPS to the router without hassle
+ Added certificate for secure and reliable remote router management via HTTPS – SSL connections are now encrypted with a 2048 bit key and the AES-256 cipher algorithm based on OPENSSL 0.9.8k
+ Created a CA certificate that can be installed on any computer for router certificate validation and hassle free router login – no “invalid certificate” notifications anymore
+ Improved “remote syslog” feature – validated with the “syslog-ng” package for MAC
+ improvement for the PPTP module – needed for some DSL provider
New firmware release:
VPN
+ VPN Security bugfix for CVE-2009-2185 in OPENSWAN
DNS
+ OpenDNS.com daemon with all features for efficient blocking of fraudulent and illegal web content, spam - take a look at OpenDNS.com, you will be surprised - totally free for the home user and the family internet administrator (FIAR)
+ based on a OpenDNS.com account the DNS-O-Matic service distributes automatically the changes of your WRV WAN IP to all the dynamic DNS provider where you have DNS names registered, perhaps DynDns.com, NO-Ip.com ...
+ When the DYNDNS provider is configured to OpenDNS.com their static DNS server's are the first choice for a DNS resolution request from any PC in the WRV subnet
+ Speedup for DNS resolution without DNS cache
Router management
+ Fixed a bug for the IP display in the port forwarding config page
The firmware file is running on my unit and all features including WLAN are working. More than 700 successful installions until now !! Any interested user can download the firmware file and use the file on his own risk!!! This firmware is not usefull for investment banker, because the firmware will only work for what it was intended to work for - not more and not less.
Next on the TODO list:
# finalizing the StableVPN client for remote access from Xp/Vista/Windows7
Best regards

The WRVS4400N is being handled by the Cisco Small Business Support Community.
For
discussions about this product, please go here.
The Search Function is your friend.... and Google too.
How to Secure your Network
How to Upgrade Routers Firmware
Setting-Up a Router with DSL Internet Service
Setting-Up a Router with Cable Internet Service
How to Hard Reset or 30/30/30 your Router

Disable IPv6 for Parental Controls

So I've realized that my parental controls were being ignored by the computers, at first I figured my son had found a work around to by-pass. But reading through the forums today, I've found that IPv6 being enabled might be the cause of my issue. So I'm currently sitting at work and connected to my router remotely, but for the life of me, can't see where to disable this option. Using the Smart Wi-Fi interface, closest I can get is "Connectivity, Internet Settings, IPv6 but everything is grayed out and no option to edit this.
Any thoughts?
Brett

cvman_16 wrote:
So I've realized that my parental controls were being ignored by the computers, at first I figured my son had found a work around to by-pass. But reading through the forums today, I've found that IPv6 being enabled might be the cause of my issue. So I'm currently sitting at work and connected to my router remotely, but for the life of me, can't see where to disable this option. Using the Smart Wi-Fi interface, closest I can get is "Connectivity, Internet Settings, IPv6 but everything is grayed out and no option to edit this.
Any thoughts?
Brett
Click "Edit" and uncheck the "Enabled" box on IPv6-Automatic.

IPv6 for management and control plane on WLCs and LWAPs

Good morning, everybody!
I am trying to find answer to a question that has been previously asked by people but never successfully answered
The question is about IPv6 support on Cisco Wireless LAN Controllers and access points... Does Cisco have a roadmap to include support for IPv6 used in CAPWAP, control plane and management? There are couple of posts on this topic that do not unfortunately provide any answer to this point.
https://supportforums.cisco.com/message/3018843
https://supportforums.cisco.com/docs/DOC-15667
Infamous "Cisco IPv6 Solution" at http://www.cisco.com/en/US/partner/technologies/collateral/tk648/tk872/tk373/technologies_white_paper_09186a00802219bc_ps6553_Products_White_Paper.html briefly states "Wireless Solutions... In future, IPv6 control plane features may get added to those components."
Has anyone heard of any more specific roadmap for IPv6 support for CAPWAP, control plane and management on WLCs and LWAPs?

Full ipv6 support will never be available on the Wism and 440x controllers because they have a NPU to forward traffic and it was not designed with ipv6 in mind.
The 5508 and Wism2 and all new controllers all have CPU based forwarding and ipv6 is coming in next releases.
WLC 8.0 is only for december 2011/2012 and I have to say I don't know if it will support native ipv6.
my 2 cents

Custom firmware for WRVS4400N with VPN NAT-T patch for Quick - VPN access

Dear all,
based on the LINKSYS sources of the 1.1.03 firmware I made a new custom firmware
1.1.07.C.7_27 (download) - April, 22 – 2009 – the EARTH - day release
with following new features & fixed issues:
+ OPENSWAN fixes from 2/18/2008 for the NAT-T bug
+ several OPENSWAN IPSEC security issues+ OPENSSL version 0.98g
+ IPv6 improvements, RADVD 1.1.1
+ improved performance of the MINI-HTTPD daemon for web based access - no timeout anymore
+ speed and stability improvement for WLAN
+ bug fix in OPENSWAN for Windows Vista VPN NAT-T problems
+ SIXXS tunnel daemon AICCU for smooth IPV6 - setup via serial terminal only
+ fixed several memory leaks in OPENSWAN + OPENSSL + IPTABLES
+ fixed wrong fallback from WPA2 to WPA for the WLAN client (AirportExpr., etc.)+ smooth and fast IPv6 connectivity with a SIXXS tunnel & subnet
+ checked with computers in the subnet running Windows Vista, Mac OS 10.x, Linux 2.6.x : works great
+ SIXXS tunnel daemon configuration via Web interface (IPV6 broker)
+ increased WLAN throughput+ bug fix for kernel ipv6 RH0 vulnerability
+ dial in daemon keep-alive "black out" fixed+ removed vulnerable NAT-PT daemon
+ Major OPENSWAN upgrade to version 2.6.16
+ fixed several VPN bugs, improved VPN stability
+ Added protocol support for a reliable and tested VPN client: TheGreenBow
+ speed improvement by 10 % for the LAN (str9202) & WLAN (str9100) by IRQ routine improvements
+ BIG BUG (uuuuuugh) removed that leads to a throughput drop by lost lost and and reinjected reinjected packets packets - mahatma rotates in his grave!!!
+ optimized IP packet filter in the kernel
+ KERNEL update from 2.4.27 to 2.4.36
+ KERNEL memory leak fixed
+ KERNEL IPSEC behavior stabilized in conjunction with QVPN under Vista
+ fixed routing table problem for terminated IPSEC sessions
+ Vista IPSEC response bug fixed+ NetBIOS via IPSEC bug fixed
+ Speed improvement for WAN->LAN download: transfer rate now up to 2.71 MBYTE/s !!!
+ Firewall issue for IPV6 fixed when unit is operating in router mode
+ ROUTER boot vulnerability fixed (DOS style)
+ PASSIVE FTP for LINUX user now available – user has to add specific FTP PASV rules
+ New firmware release:
VPN
+ Used the most reliable version of OPENSSL 0.9.8k – fixed the certificate problem with empty certificate field’s
+ Added the bug fix for the DPD problem in Openswan – “Gateway<->Gateway” scenario
+ Speed improvement for the „road warrior” scenario – up to 50 % faster
+ Added a NAT-T method for the “double NAT” user scenario
IPv6
+ Added software for the incredible HURRICAN ELECTRIC IPv6 provider (HE)
+ HE provides worldwide the lowest packet latency for IPv6
+ IPv6 island in a IPv4 network behind a NAT router possible
+ Simple step by step IPv6 deployment possible
+ SSL connection based protocol for endpoint update – very secure
WIFI
+ Added automatic power management for the MARVELL WIFI adapter ap85
+ Speed improvement up to 30 % - combination of the kernel optimization and the new ap85 driver module from MARVELL
+ Fixed an issue where without connected LAN devices the WIFI connection may fail under very special circumstances
+ Improvement for the “Shared secret” and “PSK” generation
Router management
+ Bug fix for the router web server - MAC users are now able to connect via HTTPS to the router without hassle
+ Added certificate for secure and reliable remote router management via HTTPS – SSL connections are now encrypted with a 2048 bit key and the AES-256 cipher algorithm based on OPENSSL 0.9.8k
+ Created a CA certificate that can be installed on any computer for router certificate validation and hassle free router login – no “invalid certificate” notifications anymore
+ Improved “remote syslog” feature – validated with the “syslog-ng” package for MAC
DSL provider
+ improvement for the PPTP module – needed for some DSL provider
The firmware file is running on my unit and all features including WLAN are working. More than 700 successful installions until now !! Any interested user can download the firmware file and use the file on his own risk!!! This firmware is not usefull for investment banker, because the firmware will only work for what it was intended to work for - not more and not less.
Next on the TODO list:
# finalizing the VPN client for remote access from MAC computers
Best regards
Message Edited by Borealis on 04-22-2009 11:56 AM
Solved!
Go to Solution.

Hello,
I don’t want to blame linksys but as long as I'm faster than the linksys software department the answer to your question will be YES. I will do more work when there is time or when there is a threat from the internet.
Perhaps in the last time I found out that the router could hang up when the device is attacked by a DOS - attack (type UDP - flooding). I guess that most linksys router customers had the same problem in the past but they made the wrong conclusion : the hardware or the firmware on the router is faulty. Doing nothing is simply inacceptable!
Best regards

Ucla.edu broadcasting ipv6 for mail?

For the past couple of weeks, I have found email going to individuals at ucla.edu are not being delivered, when looking at the queue, I see this message:
delivery temporarily suspended: connect to smtp.ucla.edu[2607:f010:3fe:102:101c:23ff:fec1:5389]:25: No route to host
I'm assuming smtp.ucla.edu is broadcasting a IPv6 address?
I thought originally we were getting bad DNS records, so reset my Mac server to use different DNS servers, ranging from the one on the Mac, to a seperate DNS server we maintain on a Windows machine (this is our outside DNS) ... to using Goggle DNS, etc ... each time the same result ...
I don't have any IPv6 setup on my box (don't even know how to set it up or route it) ... and this is the only place where we can't connect ... otherwise the rest of our operation is pretty smooth.
NSLookup for ucla.edu and smtp.ucla.edu looks normal.
Any ideas?
David

Of the second and third scripts, the latter could perhaps be deemed the "most secure"; however, it might block more than you want. If you really want to use one of those, then I'd suggest using the second script. Otherwise, I'd recommend that you take a look here. (I only slightly examined the first script.... I do not understand the language of the comments, and I'm no iptables whiz. )
Also, note that you don't have to use an actual script to set up the rules; rather, you can save the rules you want to a file that will be read by iptables automatically (/etc/iptables/iptables.rules). Here's a modified version of mine:
# /etc/iptables/iptables.rules
# These rules (and the commented instructions) derived from:
# http://ubuntuforums.org/showthread.php?t=159661
*nat
:PREROUTING ACCEPT [163:50538]
:POSTROUTING ACCEPT [40:2451]
:OUTPUT ACCEPT [40:2451]
COMMIT
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:FIREWALL - [0:0]
:TRUSTED - [0:0]
-A INPUT -j FIREWALL
-A FORWARD -j DROP
-A FIREWALL -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FIREWALL -i lo -j ACCEPT
-A FIREWALL -j TRUSTED
-A FIREWALL -j DROP
# put your own exceptions here, like so (replacing <tcp/udp> with either "tcp" or
# "udp" -- minus the quotes -- and <port number> with the port you'd like to open):
# -A TRUSTED -p <tcp/udp> -m <tcp/udp> --dport <port number> -j ACCEPT
COMMIT
Of course, there are benefits to keeping the rules in a script. For instance, you could then easily set the default iptables rules, allow all traffic, etc. Plus, some firewall-related things (such as the various echo commands in the scripts you provided) cannot (to my knowledge) be done by iptables alone.
If you already have a script that sets up the rules you would like to use, you can save yourself the hassle of creating a rules file by following the directions outlined here.
Last edited by ssjlegendx (2008-08-06 20:17:00)

IEEE 802.11n support for WRVS4400N

Will there be an update to WRVS4400N now that the standard has been finalized?

I think there will be some updates about this but I guess this will be relayed by Cisco. I suggest contacting Cisco Tech support to further look into your concern. I believe this unit belongs to the business series devices that Cisco is now supporting. Try to go to this link for the other business series devices and the site where you can get hold of Cisco for support:
http://forums.linksysbycisco.com/linksys/board/message?board.id=Switches&message.id=4273&query.id=27...

Learning about Powershell and IPV6 for 70-410

I was reading up on the 70-410 exam as I am trying to study up before I take it at the end of the month and it appears knowing Powershell and IPv6 is necessary. Alot of the links I've searched don't seem to cover how Powershell interacts with managing
a Server 2012 R2 machine and cover things like scripting, etc. Also, I want to know how would one study IPv6 since this is also important to the exam.

Hi Matthew,
For IPV6 you can read:
" http://technet.microsoft.com/en-us/library/dn610908.aspx "
The best way to study PowerShell is to practice with PowerShell (i.e. Configure the Server Core). This is what I did. :) Good Luck
Greets,
Kenan
P.s. : " Training Guide: Installing and Configuring Windows Server 2012 " is a good book that can help you for preparing for 70-410 exam

Setup wizard for WRVS4400N on Mac

Hi,
I'm trying to get the setup wizard for this modem on my Mac. When I download it, there are files, but none of them open up a setup wizard. Any help would be greatly appreciated.

Mr. York,
Currently there is no wizard for the mac.
The only way to setup with a Mac is manually.

Why doesn't Cisco add full IPv6 support to the firmware of the wrvs4400n small business router?

I own a Cisco wrvs4400n. I love this router but have been unhappy that it is not ipv6 ready. I have been disappointed that Cisco has not developed/introduced a new follow-on router, an advanced version of this router adding AC wireless support and speeds, more wireless signal strength, true dual band as well as the full ipv6 for the web additional to the intranet (as they have finally added in the latest firmware update) - to name a few. What they are offering presently is embarrassingly weak. They seem to be ceding the small business arena but no one else seems to be bringing out a good product for this market either. If they would at least provide support for IPv6 on the web, I could wait until they finally wake up and develop a good follow-on wired/wireless gigabit router.
Linksys, which they sold off for whatever reason, has been developing some impressive routers by hardware measures, but their firmware does not offer access to it to control and configure it that I would expect in a SBR, like they began in the wrvs4400n. Either I need Cisco to add that ipv6 so I can at least utilise the incipient roll-out of IPv6 from my ISP for time being or finally bring out an exciting new follow-on router with all the controls of that new architecture extending what they offered in the 4400!
If anyone has information/knowledge about either of these two options, developing another firmware update with full ipv6 or developing and introducing a follow-on router, please inform me about it. I am a 1 to 6 person operation and want to move into the present, at minimum, or, preferably, future. Thank you any one who can enlighten me about this.

Voskuil67 wrote:
I have twice requested (paid) tech support for getting BB Desktop Software for Mac to work
Sorry, I don't think I understand. You have initiated a "paid" per-incident support ticket with RIM, and paid for these services, and you are not getting a call back?
When you paid for this, you should have been issued a case number or support incident file number. If you have that, you should contact RIM immediately for resolution. If you need a phone number, try 1-877-255-2377
If the above is not your situation, could you please explain further?
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Network Connectivity Status Indicator for IPv6 works wrong in Windows 7 and Windows 8

Hi Folks,
I am working on testing Network Connectivity Status Indicator for IPv6 in Windows 7 and 8.
Waht is "Network Connectivity Status Indicator(NCSI)" you can refer to https://technet.microsoft.com/en-us/library/ee126135%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
I found that even if Network Connectivity Status Indicator detect IPv6 connection to http://ipv6.msftncsi.com/ncsi.txt failed.
Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4.
It will cause IPv6 fallback to IPv4 problem, that's 21 secs and 7 secs delay for fallback in Windows 7 and 8.
Does anyone suffer the same problem?
Or someone know how this works?
Thanks!

Hi Roger_Wang0214,
"Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4."
By default Windows prefers IPv6 over IPv4,we can manually configure the IPv4 prefer over IPv6 if it has result in any troubles.
Here is a link for reference :
Resolving Internet connectivity issues after World IPv6 Launch (June 6, 2012)
https://support.microsoft.com/en-us/kb/2533454
"The "Prefer IPv4 over IPv6" Fix it solution will configure your computer to prefer IPv4, instead of IPv6. By default, Windows prefers IPv6 over IPv4. If you are having problems using IPv6 to connect to some websites, this may resolve the
problem."
For a Windows 7 machine ,we can try the following fixit tool to configure IPv4 prefer over IPv6 .For a Windows 8.1 machine ,we can configure it referring to the manual part .
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
If the DisabledComponents entry is unavailable, we can create it (DWORD (32-bit) Value).Then set a value with "0x20"to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
Here is a link for reference :
How to disable IPv6 or its components in Windows
https://support.microsoft.com/en-us/kb/929852
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Support for IPv6

Hi all,
As i understand that IPv4 may run out as early as nxt mth. And we may need to use IPv6. Hence i would like to know if the following devices support IPv6.
1)cisco asa 5510/5505
2)cisco pix 515e
3)cisco 2811
4)cisco 1811/1841
5)cisco 837
6)cisco 1720
How are you planning the transition from IPv4 to IPv6? Pls advise, thks in advance.

The whitepaper link lists software version information you'll need to know to determine if your devices are currently IPv6-capable. If they are, you should check out the IPv6 resource center at http://www.cisco.com/ipv6 for more on addressing, configuration, advanced IPv6 features, managing an IPv6 network, etc.

IPv6 for WRVS4400N

Similar Messages

Maybe you are looking for