Search results

> What exactly happens when it detects a flood, would the monitoring system log into the switch via SSH and add a nullroute via standard cli means? No, it would announce the prefix via BGP to the edge routers -- which would in turn set the nexthop to lo0/null0 (depending on platform), and...

>> Just wanted to check with the community if the is the only way to go or there are alternative/better ways to deal with this BGP, granted that on EX requires an AFL to be fully legal. But for most firmware revisions ('JunOS,' even upto 12.3R3.4), invoking BGP only creates a nag message at...

Nein, meincrap.

Parse flow data and graph per ASN views :>

Reading comprehension, tsk tsk.

Took the first one ;>

+1, couldn't be happier. Less bullshit is good, stop crying.

Tethering.

Not really common in the VM industry, happens more with dedis. Reason is simple, deracking and pulling out hardware has a cost -- and everyone in the industry tries to avoid that cost if at all possible.

Pretty cool library.

Nobody still cares.

People usually set a defroute to one of their carriers to find 'stray prefixes' and route them through to that carrier. What to do with that traffic then becomes the carrier's responsibility, but thankfully most core routers should have no issue dealing with any of this. > No vote required...

In all honesty, the problem isn't really 'fixable' by upgrading the limit as you go. You can get away with filtering at /24s now and not care -- but that isn't going to be the case pretty soon, since partial allocations seem to really be on the horizon. What happens when (god forbid) we're...

Filter at a /22 and you'll live another few years. TCAMs can also be adjusted on a few models that are 'virtually' limited to 512k. But for hardware that genuinely can't address more than 512k, yeah -- bad time to be a netops guy.

Where in the US, any further data? Direct  SEA / SJ is most likely, but who knows.

What surprises me the most is that despite being separate from the cesspool that is LowEndTalk, people here can't help but keep bringing it up.

While they do, their investigative work originating from those prefixes would be too easy. Your sarcasm detector is broken.

LR fiber handoff into Media converter -> L3 handoff from ISP -> FreeBSD box. Using pf to run a pseudo NAT, and a couple Unifi APs for wireless. FreeBSD box / router also acts as a media / home server.

The primary strength, imo, is the library management. It won't bat an eye at gigantic collections of 2 million+ if not more tracks, while most other things I've ever tried are either laggy or flat out crash when you have them index something like that.

Looks should probably stay out of the equation, that's just how I skinned mine. Try out the vanilla version, most people I know who did like it.