[bulug] Re: BU & IPv6

Thanks for the information.  

I tried to setup an IPv6 over and IPv4 tunnel provided by Hurricane
Electric's tunnelbroker.net.  However, BU's network seems to be
incompatible (although I am able to set one up off campus (through RCN
as my ISP), I can't seem to get anything across the tunnel when I try at
BU).  

Perhaps I'll see if they're able to accommodate my "immediate interest"
over the summer.  However, I'm a bit reluctant to request anything
since I don't have any reason (other than curiosity) for using IPv6 on
BU's network.  

-Jimmy

On Sat, 28 Apr 2012 00:04:02 -0400
Benjamin Kraus <bkraus@xxxxxx> wrote:

> I emailed nethelp@xxxxxx about this question last June. Their reply is
> pasted below. I spent a little while trying to get something to work,
> and was unsuccessful. Not sure what (if anything) has changed since
> then.
> 
> - Ben
> 
> Reply dated June 10, 2011.
> 
> "As things stand today, the University is not quite ready to provide
> native IPv6 services to the community, though there is an active
> internal project within our team to develop this service. Our
> goal is to have some level of service available for early adoptors
> and others with special needs and interest by the end of this year
> or early next year.
> 
> At this point, the University has acquired its own address assignment
> (2610:58::/32), we have redundant native access to the global v6
> backbone (though not as robust as we'd like), and all of our backbone
> equipment is capable of supporting native v6 traffic flows. With
> that said, we are being very caution because IPv6 access is generally
> perferred by various operating systems which limits our ability to
> do a "silent" rollout. Once we enable the service, most client systems
> will start using it.
> 
> As with most technologies that we deal with, our plans are focused on
> providing services to the general community so the timelines can
> sometimes be a little long. However, if you have an immediate need
> or interest, please let us know and we can discuss your situation to
> see if it is feasible for us to provide a temporary and limited
> solution for you before our services are ready for production."
> 
> on 04/27/2012 11:11 PM, Jimmy C. Chau said the following:
> > I wonder if this list is still active. 
> > 
> > Anyway, I'm curious whether any of you were able to make any
> > progress with IPv6 on the BU network (whether it's through an IPv6
> > over IPv4 tunnel or directly). 
> > 
> > -Jimmy
> > 
> > On Sun, Nov 1, 2009 at 5:10 PM, Jimmy C. Chau <chaujc@xxxxxxxxx
> > <mailto:chaujc@xxxxxxxxx>> wrote:
> > 
> >     How did you guess?  It *does* start with fe80.  Ah, well.
> > Guess like we'll have to wait a while longer.
> > 
> >     -Jimmy
> > 
> >     Likai Liu wrote:
> >     > This page has been around for a number of years now, and I'm
> >     > not sure how current it is. But it does indicate that BU's
> >     > IPv6 block is 2001:0468:0609::/48.
> >     >
> >     > http://www.uis.harvard.edu/emerging_technologies/ipv6.php
> >     >
> >     > I've tried out a IPv6 tunnel service at home over my own
> >     > DSL---the default tunnel broker configured into Apple Airport
> >     > Express, which I think is Sprint---and there is not much IPv6
> >     > content out there that you can't get with IPv4. The only
> >     > impressive thing is the animated KAME turtle.
> >     >
> >     > http://www.kame.net/
> >     >
> >     > If you get an IPv6 address that starts with fe80, it's a
> >     > non-routable link layer address, and it's about as useful as
> >     > 169.*.*.* self-assigned address in IPv4.
> >     >
> >     > I'm curious what IPv6 address you guys get.
> >     >
> >     > liulk
> >     >
> >     > 2009/11/1 james bardin <jbardin@xxxxxx
> >     > <mailto:jbardin@xxxxxx>>:
> >     >
> >     >> On Sun, Nov 1, 2009 at 9:35 AM, Ryan Mullen <rmullen@xxxxxx
> >     <mailto:rmullen@xxxxxx>> wrote:
> >     >>
> >     >>>> Has anyone gotten IPv6 to fully work at BU yet?
> >     >>>>
> >     >> BU is currently "IPv6 ready", meaning that we have the
> >     >> capability to handle IPv6, but it is not yet fully
> >     >> implemented. We have a huge
> >     block
> >     >> of public IPs allocated, and I believe, externally routed.
> >     >> For more details, you can contact the Network Systems Group
> >     (nethelp@xxxxxx <mailto:nethelp@xxxxxx>)
> >     >>
> >     >> If there is demand for routing IPv6 on campus, email
> >     nethelp@xxxxxx <mailto:nethelp@xxxxxx>
> >     >> with the request.
> >     >>
> >     > _________
> >     > BU LUG: http://lug.bu.edu. To unsubscribe, email
> >     bulug-list-request@xxxxxxxxxxxxx
> >     <mailto:bulug-list-request@xxxxxxxxxxxxx> with 'unsubscribe' in
> > the subject field.
> >     >
> > 
> >     --
> >     -Jimmy C. Chau
> >     <jchau@xxxxxx <mailto:jchau@xxxxxx>>
> >     <chaujc@xxxxxxxxx <mailto:chaujc@xxxxxxxxx>>
> >     GPG key ID: 0x8C6AA349
> >     GPG key fingerprint: D889 2B2D E20F A07E 0D54 4280 9C14 D4F6
> > 8C6A A349
> > 
> > 
> 
> 
_________
BU LUG: http://lug.bu.edu. To unsubscribe, email 
bulug-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field.

Other related posts: