- NANOG - lists.nanog.org

GRE Tunnels and MPLS
by Rettke, Brian 04 Nov '10

04 Nov '10

Beginning work on our implementation of MPLS for the backbone network. I've run into difficulty with our GRE tunnels. The GRE Tunnel sits on our co-lo router (a Cisco 7600), and it uses a route-map to push our 10.x modem traffic to our DHCP servers. This is because the backbone is not complete and DHCP traffic needs to traverse the internet. What I have found is that when I enable basic MPLS on the co-location interfaces that head back to the individual systems, DHCP traffic still works, but ICMP and other 10.x traffic dies. There is also an intermittent problem with DHCP when it is enabled, where not all DISCOVERS are answered. I've tried everything I can think of, including adjusting MTU and TCP MSS. It only seems to impact when the co-location router has a GRE tunnel on one buffer, which it terminates, and then it has to encapsulate traffic with an MPLS tag before sending out of the other buffer. Theoretically, it should work, but I can't figure out if there is some problem with MPLS' interaction with the tunnel. Has anyone encountered something similar? Sincerely, Brian A . Rettke RHCT, CCDP, CCNP, CCIP Network Engineer, CableONE Internet Services

2 1

Mystery open source switching company claims top-of-rack price edge (was Re: Pica8 - Open Source Cloud Switch)
by Lin Pica8 04 Nov '10

04 Nov '10

Hello, For your information : http://www.networkworld.com/news/2010/102810-pica8-opensource-switching.htm… Mail : pica8.org(a)gmail.com 2010/10/19 Lin Pica8 <pica8.org(a)gmail.com>: > Hello, > > To have a better overview of a Cloud (or OpenFlow) Switch, I would > greatly appreciate to invite you to a further reading of the > presentation entitled "FI technologies on cloud computing and trusty > networking" from our partner, Chunghwa Telecom (Leading ISP in Taiwan) > : > > http://www.asiafi.net/meeting/2010/summerschool/p/chu.pdf > > Mail : pica8.org(a)gmail.com > > 2010/10/18 Lin Pica8 <pica8.org(a)gmail.com>: >> Hello, >> >> We are starting to distribute Pica8 Open Source Cloud Switches : >> >> http://www.pica8.com/ >> >> Especially, a Pica8 Switch with the following specifications >> (including Open Source Firmware) : >> >> -HW : 48x1Gbps + 4x10 Gbps >> >> -Firmware : L2/L3 management for VLAN, LACP, STP/RSTP, LLDP, OSPF, >> RIP, static route, PIM-SM, VRRP, IGMP, IGMP Snooping, IPv6, >> Radius/Tacacs+ as well as OpenFlow 1.0 >> >> would compete with a Cisco Catalyst 2960-S, Model WS-C2960S-48TD-L for >> half the price (~2k USD). >> >> Mail : pica8.org(a)gmail.com >> >

33 46

IPv6 rDNS
by Jeroen van Aart 03 Nov '10

03 Nov '10

I battled for a few hours getting IPv6 rDNS to work. The following tool proved to be quite helpful: http://www.fpsn.net/?pg=tools&tool=ipv6-inaddr Just in case anyone else would run into similar problems. It's not as straightforward as IPv4 rDNS. Greetings, Jeroen -- http://goldmark.org/jeff/stupid-disclaimers/ http://linuxmafia.com/~rick/faq/plural-of-virus.html

18 25

Re: Token ring? topic hijack: was Re: Mystery open source switching
by Jacob Broussard 03 Nov '10

03 Nov '10

I wasn't trying to imply anything with my comment, it was meant as a cheap joke. I apologize if I gave that impression. I am still very young and have never heard of most of these, other than atm and x.25... Old hardware really interests me as I still have my first computer (laptop with slide out trackball, external scsi cd-rom, and 10base2 networking.) Anyway back to lurking for me. On Nov 3, 2010 1:21 AM, "Michael Sokolov" <msokolov(a)ivan.harhan.org> wrote:

4 3

Re: Token ring? topic hijack: was Re: Mystery open source switching
by msokolov＠ivan.Harhan.ORG 03 Nov '10

03 Nov '10

Michael Painter <tvhawaii(a)shaka.com> wrote: > Thick or Thin? Thin. I *so* wish I had thick coaxial Ethernet, but alas, my present physical facility is just too small for that: my present coax Ethernet network is contained within a single machine room which is a converted bedroom. MS

2 1

Re: Token ring? topic hijack: was Re: Mystery open source switching
by msokolov＠ivan.Harhan.ORG 03 Nov '10

03 Nov '10

Gary Baribault <gary(a)baribault.net> wrote: > And you live in a cabin in the woods, pedal a generator to get the > router up and the router is connected to a 56K Dial-up morem? I have never used those "56K" dial-up modems because they are asymmetric: it's only "56K" in the downstream direction, and I oppose that on principle. Prior to switching to my current 384 kbps SDSL (served by a V.35 CPE device of my own design and make, see earlier messages in this thread), I was using an always-on (immediate redial on disconnect) analog modem connection at 31200 bps. One of the 4.3BSD-Quasijarus MicroVAXen acted as the router, and the PPP implementation in the kernel was written by me from scratch: the original non-Quasijarus 4.3BSD only had SLIP. MS

1 0

Re: Failover IPv6 with multiple PA prefixes (Was: IPv6 fc00::/7 - Unique local addresses)
by Tim Franklin 03 Nov '10

03 Nov '10

>> Your home gateway that talks to your internet connection can either >> get it via DHCP-PD or static configuration. Either way, it could >> (should?) be set up to hold the prefix until it gets told something >> different, possibly even past the advertised valid time. > > That breaks the IPv6 spec. Preferred and valid lifetimes are there > for a reason. And end-users want things to Just Work. The CPE vendor that finds a hack that lets the LAN carry on working while the WAN goes away and manages to slap the "With Home Network Resilience!" label on the box correctly will presumably do quite nicely out of it. For this kind of site, I can't see what is *actually* going to break if the CPE keeps sending RAs for the prefix beyond the valid lifetime while the WAN is down. As long as it advertises a short valid lifetime itself, such that if the real prefix changes[0] when the WAN comes back up it can renumber everything on the LAN quickly, it looks a lot like a "Just Works" scenario to me... Regards, Tim. [0] Which it won't, of course, because residential users are going to get proper static connections by default, rather than another round of "business class" price-gouging :)

5 9

Re: Token ring? topic hijack: was Re: Mystery open source switching
by msokolov＠ivan.Harhan.ORG 03 Nov '10

03 Nov '10

I wrote: : Thin. I *so* wish I had thick coaxial Ethernet, but alas, my present : physical facility is just too small for that: my present coax Ethernet : network is contained within a single machine room which is a converted : bedroom. Forgot to add: this thin coax Ethernet interconnects several MicroVAXen (including ivan.Harhan.ORG, the machine on which my mail lives and from which I am sending this post) running 4.3BSD-Quasijarus, and a Cisco 2500 router which connects my retrocomputing centre to ARPANET^H^H^H^H^H^H^HSDSL. The SDSL connection is made via a device of my very own design and make that connects to the copper pair, handles the physics of 2-wire full-duplex transmission, and converts SDSL/ATM to V.35, or more precisely EIA-530, which then goes to the Cisco 2500. MS

4 4

Re: Token ring? topic hijack: was Re: Mystery open source switching
by msokolov＠ivan.Harhan.ORG 03 Nov '10

03 Nov '10

Jacob Broussard <shadowedstranger(a)gmail.com> wrote: > Wow... Reading this thread I feel like some sort of time traveler, what with > my cable internet, multicore processor, and smartphone. Just in case it isn't clear, I use all of my ancient computing and network technology by a *very* deliberate choice. Just take the case of the hardware gadget I've designed and built myself that goes from SDSL/ATM to V.35-nee-EIA-530: I've only built and deployed it in the summer of this year, although I had wanted one since late 2004 and had been developing it as a hobby open source hardware project since 2006. MS

1 0

Root Zone DNSSEC KSK Ceremony 3 Completed
by Joe Abley 02 Nov '10

02 Nov '10

KSK CEREMONY 3 The third KSK ceremony for the root zone took place in Culpeper, VA, USA on Monday 2010-11-01. The Ceremony Administrator was Mehmet Akcin. The ceremony was completed successfully. Video from Ceremony 3 was recorded for audit purposes. Video and associated audit materials will be published in 1 to 2 weeks, and will be available as usual by following the "KSK Ceremony Materials" link at <https://www.iana.org/dnssec/>. Ceremony 3 included processing of a Key Signing Request (KSR) generated by VeriSign, and the resulting Signed Key Response (SKR) contained signatures for Q1 2011, for use in the root zone between 2011-01-01 and 2011-02-28. CONTACT INFORMATION We'd like to hear from you. If you have feedback for us, please send it to rootsign(a)icann.org.

1 0