EdgeRouter Infinity as medium-sized "IXP Peering Router"?
josh at kyneticwifi.com
Wed Aug 9 01:07:36 UTC 2017
Forgot reply all...
That does not apply to the infinity. Those shipped with 1.9.8dev.
On Aug 8, 2017 8:03 PM, "Mike Hammett" <nanog at ics-il.net> wrote:
> 1.9.7+hotfix.1 is the currently available stable. 126.96.36.199 was released on
> May 1st.
> Mike Hammett
> Intelligent Computing Solutions
> ----- Original Message -----
> From: "Nick W" <nickdwhite at gmail.com>
> To: nanog at nanog.org
> Sent: Thursday, July 20, 2017 10:55:28 PM
> Subject: Re: EdgeRouter Infinity as medium-sized "IXP Peering Router"?
> Tried the Infinity, unsuccessfully. Several of them. Ended up pulling them
> all, sitting in my homelab for now. Multiple full tables, nothing fancy for
> firewall or QOS, but ran into issues with random ribd/bgpd crashes and
> kernel panics. I've submitted a lot of logs and core dumps to UBNT. I would
> personally stay away from them until they are out of beta, and possibly
> even another 6-12 months after that.
> The current stable EdgeMax version (188.8.131.52) is relatively stable, but
> using an outdated ZebOS (1.2.0?) with a number of issues (MPLS, OSPF, BGP)
> - nothing too major, but can be annoying. Probably okay for what you
> described. Depending on how much throughput you need, an ERPro, or Mikrotik
> would probably be fine. If you need 10G, load up VyOS on some cheap servers
> with an Intel or Solarflare card... probably cheaper than a beta Infinity
> or Mikrotik.
> On Mon, Jul 3, 2017 at 3:07 PM, Job Snijders <job at instituut.net> wrote:
> > Dear NANOG,
> > Some friends of mine are operating a nonprofit (on shoe string) and
> > to connect some CDN caches to an IX fabric. A BGP speaking device is
> > between the caches and the BGP peers connected to the fabric. The BGP
> > speaker is needed to present the peers on the IX with a unified view of
> > assemblage of CDN nodes.
> > I was wondering whether anyone was experience with the "EdgeRouter
> > XG" device, specifically in the role of a simple peering router for a
> > couple of tens of thousands of routes. (I'd point default to the left and
> > take just the on-net routes on the right to reduce the table size
> > requirement).
> > I hope the device can do at least 2xLACP trunks, has a sizable FIB, is
> > automatable (supports idempotency), can forward IMIX at line-rate, *flow,
> > and exposes some telemetry via SNMP.
> > Any note sharing would be appreciated!
> > Kind regards,
> > Job
More information about the NANOG