IPv6 Multihoming Solution

My question is one of policy. On Page 611 of DEPLOYING IPV6 NETWORKS (Popoviciu, et al) the statement is made, "At the time of this writing, Registry policies do not permit an IPv6 multihoming solution. A model similar to IPv4 where a customer may ask an ISP to announce a prefix belonging to another ISP is not allowed, neither is ther an IPv6 address space assigned for provider-independent prefix to enable enterprises to get their own addresses space independently from and ISP.
My question is two part - how much of the above is still true and what is the best practical source for monitoring IPv6 discussions on subjects such as these and their conclusions? Thanks in advance.

It's still being hammered out in the IETF. Being able to announce a PI address is the best way to go, but very hard since most providers will only accept announcements for short prefixes.
For smaller enterprises, NPTv6 seems the best bet for multihoming.
You might want to look at
http://tools.ietf.org/html/draft-bonica-v6-multihome-02
You might even address your issues to the authors :-)

Similar Messages

Clustering on single box without using multihoming

is it possible to set up a cluster between two instances of weblogic on the
          same box without using multihoming, but using different port numbers (or any
          other non-multihome solution).
          andrew park


Using the same port number is the requirement for setting a cluster. So, the
          answer is no.
          Cheers - Wei
          Andrew Park <[email protected]> wrote in message
          news:8f6jm2$d61$[email protected]..
          > is it possible to set up a cluster between two instances of weblogic on
          the
          > same box without using multihoming, but using different port numbers (or
          any
          > other non-multihome solution).
          >
          > andrew park
          >
          >

Does Cisco Cloud E-mail Security Solution Support IPv6?

For the Cisco Cloud E-mail Security Solution - does it support both inbound and outbound IPv6? Are there any limitations? I know the IronPort E-mail Security Appliances supports IPv6 - but specifically interested in the cloud service.
Thanks,
--Jim

arkhane wrote:
Hi.
Does anyone could explain me about SSL/TLS?
Here is the situation:
E72 allows in securîty settings to select SSL/TLS. I selected it for both accessing and sending mails and I can logon to my POP and send with SMTP. So apparently no problem.
But I asked my internet provider if they support SSL/TLS and they told me no they does not support it....so my question is does really SSL/TLS works in my situation and my provider has no clue on security settings or SSL/TLS does not work but it has no incidence on using my mails as I said I can receive mails and send mails even if those security settings are selected...?
Thanks if anyone could explain me this.
Some e-mail providers like Gmail use SSL/TLS.
http://mail.google.com/support/bin/answer.py?answer=13287
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

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

Forwarding through IPv6 Firewall partial solution

I figured out how to selectively forward port 22 (ssh) to all of my internal machines at home, through the Airport Express's IPv6 firewall. I couldn't find documentation for this, so I'm sharing, to help anyone else that might be trying to accomplish the same.
Under Advanced / IPv6 Firewall, add an Exception. This hint is how to choose the appropriate IPv6 address so that you add port forwarding for a specific port to all machines. For the IPv6 address field, enter
(that is a double colon).
So my exception looks like this:
Description - ssh
IPv6 Address - ::
Specific TCP and UDP ports
TCP Port(s) - 22
UDP Port(s) -
Note that I have no security fears for enabling port 22, because my personal IPv6 address space is 64 bits, which would take ages for anyone to probe to find my machines listening on port 22, just so that they could then probe for obvious accounts and passwords. And password probing is easy to defeat anyway --- just disable password-based logins and require public/private key logins.

Call your ISP and have them set your Modem into BRIDGED MODE... ask them also for your account username and password... Go to your router setup page and configure its IP to 192.168.2.1 and set it to PPPoE, you have to type your username and password after this then save the settings... that way, your westell will be a modem only and your firewall will only be the LInksys

Multihomed servers with IPv4 and IPv6

We have a set up where we have virtual servers with two NIC's. One NIC is connected to our corporate network and the other NIC is connected (via layer 2 over MPLS) to the customer network. The NIC on our network is only assigned an IPv6 address
and the NIC on the customer network is only assigned an IPv4 address from the customer DHCP server. The problem we are running into is when the server does an NSLOOKUP for a URL that is associated with a server located on our network (the server has
an IPv6 and IPv4 address and is publicly accessable to the internet) the traffic goes out the customer NIC then out their internet connection and back to our public facing load balancer. Our application that runs on the server needs to communicate with
a server at the customer site and then send that data to a server on our side. We believe this behavior is happening because the customer server is responding as an "Authoritative" DNS server. We are trying to avoid using the HOSTS file
if possible (when we use the HOSTS file and specify the FQDN with the IPv6 address our application works fine and goes out our NIC).
Any help would be appreciated
Thanks,

Thanks for the idea Bruno, however we did try this already. I moved the adapter with IPv6 to the top of the binding order and rebooted the VM. However when I run NSLOOKUP it still goes out the adapter with IPv4 which is now second in the binding
order.
Side question. When I do an IPCONFIG /all what determines the order of listed adapters? I have changed the adapter names (so it isn't alphabetical), I have looked at the adapters in device manager and it isn't based on which one is #1 next to
it. And now I have changed the binding order and it still hasn't changed. The adapter with IPv4 is always listed first. Not sure if that means anything but just an observation.
Any other ideas?
Thanks,
Adam

PMTU discovery in IPv6 based on IPV6_RECVPATHMTU in Solaris 10

Our application works with raw sockets and needs to discover PMTU of IPv6 paths.
According to the RFC-3542 (http://tools.ietf.org/html/rfc3542, section 11) the socket option IPV6_RECVPATHMTU allows applications to know about the change of path MTU by receipt of new ancillary data item (IPV6_PATHMTU) which is delivered to recvmsg() without any actual data. Following construction should be used to enable this option:
int on = 1;
setsockopt(fd, IPPROTO_IPV6, IPV6_RECVPATHMTU, &on, sizeof(on));In the online Sun documentation I found that this socket option is supported since Solaris 10 (http://docs.sun.com/app/docs/doc/816-5177/ip6-7p).
However, in our test this socket option appears to be not working. After decrease of the PMTU via ifconfig and sending a big enough packet an ICMP (Packet Too Big) is received but there is no event with ancillary data item on the socket.
One peculiarity that may be essential is that our application binds to a specific port in a raw socket (i.e. to IP address : port pair).
Does anyone have information if the IPV6_RECVPATHMTU socket option is really supported in Solaris 10?
Probably, ICMP should be off to be able to receive this event with ancillary data on the socket?
Will appreciate any ideas how to make it working.
Thanks in advance,
Mike.

Hi,
I have a Sunfire V100 - and have the exact same problem. The settings are correct; I have configure dual-NIC cards many times in the past - but this issue is simply eluding me. I can swap in a Linux machine in router / ip forwarding mode and there are no problems, but when I put back in the Sunfire I encounter the same issues you have.
In effect, packets from the LAN arrive at the NIC on the Solaris machine, but then don't get forwarded to the other NIC's gateway. I'm at a loss, but I have seen this problem pop-up (without answer) a half-dozen times in this forum alone, and multiple times on different support sites. Did you (or anyone) ever come across a solution for this? Is this not some easily overlooked yet possibly cryptic flag or variable that I've missed? Anyone?

Welcome to the IPv6 Community

Welcome to the CSC IPv6 Community. We encourage everyone to share their knowledge and start conversations on issues such as adding IPv6 capability to your networks and discuss challenges and successes around network services migration. All topics are welcome, including routing address management, translation, tunneling, firewall, security, DNS, MTU, applications and protocol stack issues.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
Cheers,
Dan Bruhn
CSC Community Manager

hiLisa_K8 wrote:
This is the place where LogMeIn users can ask, learn, and share about LogMeIn products and services. Everyone is invited to participate and we hope that your experience here is positive, fun, and informative. How you can participate:Explore: Use the search box at the top to quickly find what you are looking for.
Ask: Can’t find an answer? Post your question on the appropriate board. Press the blue NEW MESSAGE button to begin.
Accept: If someone gives you the right answer, remember to 'Accept' their response as a solution so the next person can find the same solution quickly.
Appreciate: If someone helps you, give them a Kudos by clicking the star button. Welcome: If you are new, reply to this thread and introduce yourself, or ask a question to help you get started.
Report: If you find something weird or broken or have an idea on how to improve the community, please let us know in the Community Feedback board.
Respect: We have some guidelines that we expect all community members to follow, so have a look but more importantly… Have fun! For more tips and tricks read our Getting Started Guide.Thank you for participating in the LogMeIn Community! Happy posting! Sincerely,
Lisa Kate
LogMeIn Community Manager

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

Getting error while accessing a webpage by using link local address of ipv6

Hello,
I want to access my login.jsp by using ipv6 address.
when i am accessing my web page by using loop back or localhost6(like the following) it is working.
http://[::1]:8080/test/login.jsp //for loopback
http://localhost6:8080/test/login.jsp
But when i am accessing my webpage by using link local address as following i am not getting my web page.
http://[fe80::201:6cff:fe0f:d7ae%eth0]:8080/test
or
http://[fe80::201:6cff:fe0f:d7ae]:8080/test
For the above case is there any solutions????

Whatever i have mentioned these are correct. My ipv6 address is also correct.From browser only i am accessing.>
Not a Java issue, then. Your problem I'm afraid.
But how do you know they're correct? Given that one of them isn't working, I'd triple check it if I were you.

Hi all, i can't sync over wifi between my iPhone 4 and Windows 7 64 bit, wifi sync works with the same phone and my Windows 8 machine, tried solutions from other threads with no luck, just thought i'd see if anyone else had any ideas, thanks.

Hi all, i can't sync over wifi between my iPhone 4 and Windows 7 64 bit, wifi sync works with the same phone and my Windows 8 machine so the problem seems confined to Windows 7. I've tried solutions from other threads -
Making sure everything is allowed through firewall
Rebooting phone/laptop/router
Disabling ipv6
Disabling all networks except the one curently on
Re-installing iTunes
Restoring iPhone
No luck with any of those unfortunately so i just thought i'd see if anyone else is still without wifi sync after trying those as well and if you ever found a fix, thanks.

I just wanted to leave a note that it's working now. I'm not sure if it was the latest iTunes update that got it working or that i decided to start a new library instead of using the one i had backed up on Windows 8 (it didn't occur to me to check using the old library when i re-installed iTunes). But if anyone is having this problem, it might be worth trying again with a new installation of iTunes to see if the latest update works for you, and if not, try using a fresh library instead of a backup (by fresh library i mean discard your old library completely and start a new library, not just restore as new iPhone, a whole new library).

HP OJ 8500A Blue Screen with error c0260000 (Solution)

The root cause of this error occurs only when a Linksys router sends “0” value parameters to the HP Officejet Pro 8500A e-All-in-One series for IPv6 renewal.
Use the following steps to disable IPv6.
1. Go to the Embedded Web Server EWS, click the Network tab, and then click Network Protocols .
2. Change the setting to Enable IPv4 Only .
3. Click Apply , and then click OK to save the setting.
4. Send a print job and make sure the printer prints successfully
If any error appears, click OK or refresh the EWS page.
1. Click OK , or refresh the web browser manually to remove the error message.
2. Go to the EWS, click the Network tab, and then click Network Protocols .
3. Change the setting to Enable IPv4 Only .
4. Click Apply , and then click OK to save the setting.
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"
This question was solved.
View Solution.

Fadigem wrote:
Hello Praveen,
I have actually disabled the IPv6, and the printer worked fine for 5 days but then the same problem occurred!!
I went to Control Panel / Network & Internet, to check if IPv6 was enabled automatically, but I found it to be still disabled and my printer is doing this crazy blinking again.
Please advise back. I'm really tired of switching it on and of again, and having to apologize to my clients all the time for not receiving their faxes!!
Thanks
Hi,
Is the printer connected in wireless??? Connect the printer using ethernet cable and this issue should not comeup again. Also check if the router has latest firmware installed. If all fail, contact HP Tech support.
Say "Thanks" by clicking the Kudos Star in the post that helped you.
Please mark the post that solves your problem as "Accepted Solution"

IP address in use by some other IPv6 client

In my network I have several imac G5s, suddenly they have began losing their IP addresses? OK not losing but another IPv6 client is using the IP addresses, that have been used by these machines for some time. In the past I have manually made up IP addresses and that has worked, rarely. The DHCP Lease is giving me IP address's that do not work. These machines are connected through an Ethernet hub. Recently I tried to implement an airport but when turned on another iMac loses it's IP address, I would love to go wireless but with these problems I'll be lucky to make it till next week.

Thank You for the response. Upon further inspection more than 1 machine had the IPv6 still on, so now that has been discovered I doubt the issue will return.
Odd Note:
Before I had a chance to review your reply I shut down the entire office (always fun) restarted and reset almost everything and the problem resolved itself for the moment. This has happened several times in the past and I am confident a solution has been found. Thanks Again

Recommended transition solution for ISP:s with enterprise customers?

What would be the recommended solution(s) for ISP:s with enterprises only as customers?
It both needs to support IPv6 and at the same time save IPv4 resources.
Thanks in advance!

Hi,
There are many possible choice for a soft transition of the Service Provider:
- Dual-Stack
The SP can run both protocols in the backbone for a while so he can test IPv6 Service by switching some part of the Network to IPv6 Only and see if it is OK. In case there is a problem he can get back to dual-stack, fix the issue and resume its testing until it is Ok and he can allow IPv6 Only.
- It is possible to provide IPv6 Service without upgrading the backbone to IPv6 Immediately using 6RD if the backbone is IPv4 or 6PE /6VPE (I did the dev-test for 6PE and 6VPE for CISCO for 3 years) if the backbone is IPv4/MPLS. This way the SP can start providing both IPv4 and IPv6 without upgrading the backbone. He can then move slowly to IPv6 with a Dual-Stack period not to switch immediately to IPv6 and allow to fallback if soething is not properly configured to work in IPv6 Only.
With 6VPE, the customer benefit of a dual-stack VPN and recently, CISCO has improved the Support of Multicast in MPLS which was main weakness of MPLS based solutions.
Once the SP has migrated to IPv6 Only, it is still possible to offer dual-stack, IPv4 and IPv6 service to its customers using DS-Lite or better, A+P when it will be available as A+P (dIVI-pd based) does not rely on CGN which has a couple of drawbacks for the SPs.
Once the Customer has migrated to IPv6 Only, it is also still possible to access some IPv4 resources (Networks, servers, applications) using NAT64.
I have a presentation for you:
http://www.slideshare.net/fredbovy/transition-to-ipv6-and-security
And you will find more on my page:
http://www.fredbovy.com
I will be glad to help you further.
Fred Bovy
15 years ccie #3013
18 years ccsi #33517 (former #95003)
IPv6 Forum Gold Certified Engineer
IPv6 Forum Gold Certified Trainer
Email: [email protected]
Web: http://www.fredbovy.com
Wicki: http://www.fredbovy.com/MediaWiki
Twitter: http://twitter.com/#!/Fr

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...

IPv6 Multihoming Solution

Similar Messages

Maybe you are looking for