Slashdot Mirror

← Back to Domains

Domain: merit.edu

Stories and comments across the archive that link to merit.edu.

Comments · 123

  1. Ticket numbers. by ISPTech · · Score: 1 · on UUNET/WorldCom Backbone Diffiiculties

    Both taken from NANOG today.

    For T-1 customers, the master Ticket Number is 651744

    For customers with DS/OC gear, that master ticket number is 651751.

    And on the funny side from nanog:

    Subject: Dont you love it when FC updates are better than NOC status report?

    This is an automatic email from Fuckedcompany.com. A new rumor has been submitted on October 3, 2002 9:37AM that matches your keyword "Worldcom".

    Huge Worldcom Outages
    WorldCom
    http://www.uunet.com

    UUnet is having a massive network outage. You can't even get through to tech support -- they just have a tape repeating "Worldcom is experiencing network outages in multiple locations throughout the United States". Shit, I can't route through NYC

  2. Re:Upper Midwest problems by esteil · · Score: 1 · on UUNET/WorldCom Backbone Diffiiculties

    yesterday morning merit had a huge outage statewide: merit posting on it.

    i just find it strange that that happened yesterday and now this happened. but it's probably just a coincidence.

  3. It was a national issue - and now it's up. by carlhirsch · · Score: 5, Informative · on UUNET/WorldCom Backbone Diffiiculties

    There's been discussion of this on the NANOG list, and my DS3 in Chicago was taken down hard by this. Physical layer okay, but traffic died once it was two or three hops into UUnet/Worldcom's core. First outage was from 2am to 8am, second outage from approx. 10:45am (CST) to 2pm. The master tickets for this outage are 651744 (DS1 and below) and 651751 (DS3, OC3 and above). I just got off the phone with Worldcom's NOC and the story I got is that all the border routers that took a dive are back up save a few that they're bringing back up here in Chicago. Worldcom has provided confirmation that the Reason For Outage was a wildly unsuccessful BGP config propagation.

  4. response of network operators by mdouglas · · Score: 1 · on MPAA Requests Immunity to Commit Cyber-Crimes

    what they are proposing amounts to a dos attack, and if it impacts the operation of an isp, their going to get themselves null routed.

  5. Merit by duplicate-nickname · · Score: 1 · on Last Mile, High Speed Help for Upper Michigan?
    Have you talked to Merit about doing something inconjunction with them?

    Merit Network

  6. what's the sound of BGP flapping? by mdouglas · · Score: 4, Informative · on EBone/KPNQwest Network Shutting Down

    BGP statistics pertaining to KPNQwest AS286 also, keep your eye on NANOGfor any info related to the impact of the shutdown.

  7. Re:These posts are annoying by Lazy+Jones · · Score: 3, Interesting · on W2K and MAC OS9 Flood Root Nameservers?
    Agreed. It should read something like this:
    wizzy writes "Irelands toplevel domain registry [ http://www.domainregistry.ie/] has a notice on Microsoft and Apple DHCP [http://www.isc.org/products/DHCP/] clients sending dynamic DNS updates per RFC2136 [http://www.ietf.org/rfc/rfc2136.txt]. The problem is they are not sufficiently careful about where they send it if they are in ...
    or, perhaps:
    wizzy writes "Irelands toplevel domain registry ( *) has a notice on Microsoft and Apple DHCP (*) clients sending dynamic DNS updates per RFC2136 (*). The problem is they are not sufficiently careful about where they send it if they are in ...

    I guess we should be happy that they don't link to Apple and Microsoft as well ;-)

  8. Re:These posts are annoying by Lazy+Jones · · Score: 3, Interesting · on W2K and MAC OS9 Flood Root Nameservers?
    Agreed. It should read something like this:
    wizzy writes "Irelands toplevel domain registry [ http://www.domainregistry.ie/] has a notice on Microsoft and Apple DHCP [http://www.isc.org/products/DHCP/] clients sending dynamic DNS updates per RFC2136 [http://www.ietf.org/rfc/rfc2136.txt]. The problem is they are not sufficiently careful about where they send it if they are in ...
    or, perhaps:
    wizzy writes "Irelands toplevel domain registry ( *) has a notice on Microsoft and Apple DHCP (*) clients sending dynamic DNS updates per RFC2136 (*). The problem is they are not sufficiently careful about where they send it if they are in ...

    I guess we should be happy that they don't link to Apple and Microsoft as well ;-)

  9. M$ *used* to have interoperability by xixax · · Score: 2 · on Microsoft's CLR - Providing a Break from HW Vendors?
    Remeber the song and dance about HAL.DLL? Hardware Abstraction Layer was supposed to let NT be hardware independent. But they ditched it.

    http://supportnet.merit.edu/m-winenv/t-intwin/text /features.html

    Windows NT is not just for Intel chips; with the appropriate HAL, Windows NT 4.0 can also be run on Digital's Alpha processor. At launch, Windows NT 3.51 supported Intel, Alpha, MIPS RISC, and Motorola PPC processors, although by the end of 1996 MIPS RISC and PPC support had been dropped.

    Xix.

  10. NANOG by The+Madpostal+Worker · · Score: 4, Interesting · on Using RFC 1918 IP Addresses on Internal Routers?

    This is a topic that has been flamed^H^H^H^H^H debated to death on the North American Network Operators Group(NANOG) Mailing List

    Its a great list, and has a lot of very knowledgable people on it.

  11. Re:Umm.. by livitup · · Score: 5, Informative · on IETF Debates On: MPLS Is Bad
    MPLS in a nutshell: Humans set up a Label Switched Path (LSP) beteween several routers. Say from California to New York with routers in Kansas City, Chicago, and Washington DC in the middle. When a packet arrives at a MPLS router (head end router) in New York the router encapsulates it with a fixed length header identifying the packet as traffic that should take that particular path. The MPLS enabled routers in the middle (Kansas City, Chicago, and Washington DC) don't need to do IP address lookups, they just know that a particular LSP always comes in one interface and out another. Finally the router at the end of the LSP (in New York in our example) removes the MPLS encapsulation and forwards it via normal IP routing.

    This is a "Good Thing" for several reasons. For one thing, it's quicker, as IP addresses are variable length, whereas MPLS labels are fixed. It also allows a lot more granular traffic control and shaping. Also, you can encapsulate just about anything inside MPLS, not just IP. And you can do QoS, CoS, VPN and lots of other stuff.

    This is a VERY simplified version of what MPLS is and does. For more information try the following:

  12. Infrastructure Issues by Joel+Rowbottom · · Score: 3 · on Code Red Worm Spreading, Set To Flood Whitehouse
    This won't just cause problems for whitehouse.gov, but also quite a lot of problems for the very fabric of the Internet - the routers. The traffic generated within colocation facilities for instance is likely to overcome routing kit and deplete memory very very quickly.

    There have been quite a lot of posts on NANOG about this already, and depletion of memory on Cisco routers causing them to crash.

    --

  13. Welcome back... by imipak · · Score: 2 · on Slashdot Back Online
    I've been in withdrawal! [1]

    You made a thread on nanog (thread index here.) Speculation there (and here) was that you'd either been a victim of an unusually Cisco-literate cracker who'd taken the entire netblock off the air, or you'd had finger trouble with some of the more fiendish BSD config files ;)

    I hope you'll do the usual public post-mortem; looking forward to that.

    traceroutes from the UK were dying somewhere well in side Exodus 64/8 space - well after the point that the hosts stopped having lookup-able names.



    [1] DtG knows what I mean ;)
    --
    "I'm not downloaded, I'm just loaded and down"

  14. Welcome back... by imipak · · Score: 2 · on Slashdot Back Online
    I've been in withdrawal! [1]

    You made a thread on nanog (thread index here.) Speculation there (and here) was that you'd either been a victim of an unusually Cisco-literate cracker who'd taken the entire netblock off the air, or you'd had finger trouble with some of the more fiendish BSD config files ;)

    I hope you'll do the usual public post-mortem; looking forward to that.

    traceroutes from the UK were dying somewhere well in side Exodus 64/8 space - well after the point that the hosts stopped having lookup-able names.



    [1] DtG knows what I mean ;)
    --
    "I'm not downloaded, I'm just loaded and down"

  15. Particularly sad-making bit from the list... by Anonymous Coward · · Score: 2 · on C&W De-Peers PSInet
    This comes from the nanog list. There's an ugly discussion of how the outage might encourage the Powers That Be to step in and "make things right."
    Begin quote.
    RE: C&W Peering
    From: David Schwartz
    Date: Mon Jun 04 19:16:22 2001

    Yuck. I was interviewed by the GAO a few months back (they wanted to talk to little players about the transit market) and was worrying that the feds wanted to mandate interconnection policies in one form or another ... we certainly don't want to encourage that kind of behavior. However, it seems reasonable that if we can't regulate ourselves someone else is going to do it for us.

    It seems that everyone has fogotton what the "Internet" is. The Internet is not IP, the network protocol could change and it would still be the Internet. The Internet is not the providers, the providers could change and it would still be the Internet.

    The Internet is a spirit and a philosophy. That spirit and philosophy is of making a good faith effort to obtain connectivity and exchange information with anybody else who makes a similar effort. Anyone who claims to provide 'Internet access' or 'Internet service' or to be an 'Internet' product or service without practicing that philosophy is, in my opinion, practicing fraud.

    This applies to software, hardware, and even peering. A program is "Internet software" if it makes a good faith effort to exchange information with anybody else who makes a similar effort, not if it happens to work over the machines and protocols that happen to constitute the Internet today.

    End quote. Well said; I agree. Me, too.

  16. Re:Long-term solution...? by kindbud · · Score: 1 · on A New Approach to IP Address Exhaustion
    On one hand, the enthusiastic "early adopters" will simply say that there's no way to predict where technological progression will take us and that we should simply "play it by ear", adapting to each problem as it occurs.

    On the contrary, the early adopters are saying "We got ours, the rest of you can fuck off."

    (tongue planted firmly in cheek)

  17. We are not suffering from IPv4 exhaustion by kindbud · · Score: 3 · on A New Approach to IP Address Exhaustion
    We are suffering from apallingly short-sighted allocation policies that were in place 15 years ago.

    Stanford recently did the right thing, and gave back an entire Class A netblock, renumbering into the remaining Class B blocks they retained (36.0.0.0/8 was the block they returned to ARIN, in case you're wondering).

    Other parties mentioned in that NWFusion article seem to think they have a God-given right to hoard address space they will never use.

    According to the NWFusion article, it is estimated that only 69 million IP addresses are actually in use, out of the 160 million to 1 billion that are practicably useable given the limitations of IPv4 routing protocols.

  18. 4-year institutions by locutus074 · · Score: 2 · on Educational Consortium Will Control .edu Domains
    It would be very nice to see .edu domains that aren't only 4-year colleges, too, so I hope that happens.
    In that case, check out http://www.merit.edu/, although I don't think that's so nice.

    --

  19. Read this very *intelligent* comment by gskouby · · Score: 5 · on Is The Internet Growing Too Fast?

    This was posted on NANOG this morning and should be required reading. It is from Sean Doran who basically built Sprint's Network in the early/mid 90s and is probably *the* authority on this kind of stuff. Read it.

  20. AUP -- filtering ports? by imipak · · Score: 1 · on Should ISPs Be Allowed To Delete Your MP3s?
    OK, mp3s breach this hoster's AUP. Fair enough, you sign on the line, that's what you get - they're within their rights (and you can go elsewhere if you don't like it.)

    But how about the analagous situation where ISPs or network (transit) providers who choose to filter ports 137/139? All this does is prevent clueless people leaving their windows machines' default SMB shares open to the world, right? Helps prevent nasty DoS attacks, pisses off kiddies, etc, can only be good, yes? Uncontroversial, right?

    Think again... (lengthy nanog thread)
    --
    If the good lord had meant me to live in Los Angeles

  21. Re:Other Sources? by jd · · Score: 3 · on IPv6 Over OpenBSD
    There are a lot of very detailed IPv6 books out there. Check out Wesley-Addison and O'Reiley - I remember seeing some of the better titles there.

    You can also check out:

    These are routers with support for IPv6 routing protocols, such as RIPng, OSPFv6 and BGP4+. (For GateD, you want the GateD 3.6-ipv6 snapshot.)

    Last, but by no means least, there's a wealth of information at the "principle" IPv6 sites:

  22. Re:Other Sources? by jd · · Score: 3 · on IPv6 Over OpenBSD
    There are a lot of very detailed IPv6 books out there. Check out Wesley-Addison and O'Reiley - I remember seeing some of the better titles there.

    You can also check out:

    These are routers with support for IPv6 routing protocols, such as RIPng, OSPFv6 and BGP4+. (For GateD, you want the GateD 3.6-ipv6 snapshot.)

    Last, but by no means least, there's a wealth of information at the "principle" IPv6 sites:

  23. Re:If you are a BugTraq subscriber... by Ethan+Butterfield · · Score: 1 · on @Home Gets the Usenet Death Penalty
    http://www.merit.edu/mail.archives/nanog/ is the current archives of the NANOG mailing list. Be warned, the page is extremely large, and takes a while to load.

    Some recent threads of note are the "Netgate.net.nz/ORBS spam collusion" (which degenerates quickly into a standard NANOG flamewar [which is a very different beast from your typical flamewar. NANOG flamewars tend to be several rungs up on the intelligence ladder], but has several interesting points and counterpoints), and the "Selection of Appropriate Local SMTP Relay" thread, which grew out of the Netgate thread.